It's all about the answers!

Ask a question

How to un-promote/ demote / reverse, change sets and its corresponding build outputs that were promoted in RTC Enterprise extensions

Ravikanth Chavali (401724) | asked Oct 07 '15, 1:18 a.m.
edited Oct 07 '15, 1:28 a.m.
Is there a separate action to undo the promotion action in enterprise extensions ?

Scenario 1:- When we reverse change sets from a stream that impacts part of a source code file, then when we reverse the change set, it creates a reverse patch that is delivered and upon rebuild, the changes are promoted to the target stream which overrides the old build output file with the new build output files that are promoted.


Scenario 2:- when reversing a change set from a stream deletes the complete file out of the stream. The reverse patch change set is delivered that deletes the complete source file from the stream and we request a build there is no source file to be built or overridden.

How to make sure the corresponding build outputs are also deleted when the reverse operation or similar to demote a change set is performed ?

Thank you,
Ravikanth Chavali

One answer

permanent link
Nicolas Dangeville (31632425) | answered Oct 07 '15, 9:23 a.m.
In the z/OS build definition, in the z/OS dependency build section, there's a check box (since 5.02 I think), called delete obsolete outputs. The build is going to monitor the deletion of buildable files in the stream and add extra processing to obtain from the previous build map the outputs of the deleted files, to make sure that they are not produced now by someone else, and will delete the files.
This option is turned off by default as people usually don't want us to delete binaries, as it can have side effects to their process.

Note that Build & packaging handle deletion but not promotion (i.e. promote w/ binaries a deletion). We have an enhancement open for that: promotion should handle deletions (325481)

James Cole commented Oct 30 '15, 9:55 a.m.

Hi Nicolas, 

Is this option available for i/OS (IBMi)?

To add to these scenarios, how will handle the following.

If a developer makes a change to a COBOL program (CBL001), which is compiles.
The next day another developer makes a file change (PF001), which recompiles (CBL001). 
Now the file change is reversed, which should remove CBL001. 

However, as CBL001 was already there before this change set, will it automatically recompile CBL001, with the source it had before the dependency compile ? 

Many Thanks


Your answer

Register or to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.