|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Unfortunately, I found out that the option "-nmerge" is not correct either:
Imagine you have a stream called "foundation" and another called "child". In foundation we have FOUND_BL1 and FOUND_BL2. We rebase then "child" from FOUND_BL1 to FOUND_BL2. In that case:
So without the option "-nmerge", we get too many changed elements, and with the option "-nmerge" we don't get all the changes. That's why I propose to NOT use the option "-nmerge" in the plugin.
As an alternative, I am planning to implement the following logic in my own build script (which is called in our Jenkins Job when the UCM plugin fires a job):
This is probably more work and for me it's not necessary to have this in the Changes list of Jenkins. I'll just use it myself in my build script (which is in Perl). If you want to have the code afterwards to port it to Java, I can provide it to you.
If you prefer not to implement this, you can close this issue or lower its priority.