[JIRA] [clearcase-ucm] (JENKINS-18278) Change set is not correctly calculated after a rebase of the integration stream, case 9489

Mon, 24 Jun 2013 06:00:22 -0700

Lars, I see two differences in functionality with the original perl-script.

  • the foreach is not needed in the plugin (because the plugin has one single baseline to control all the rest).
  • In case it's the first baseline in a stream, the change set would be empty in your proposal, while the perl script would calculate in that case the difference with the foundation baseline.

Elaboring a bit on the second bullet above:

  • for streams which use a foundation baseline from an existing stream it makes some sense to display the difference between the first baseline and the original foundation baseline as the change set of the first baseline.
  • But for streams which are created by means of a delivery from another stream, it is not useful to compare the first baseline with its foundation baseline (which is in that case probably the INIITIAL baseline). Furthermore, calculation of such a change set would take again a lot of time, because a describe of "all" elements would be executed in that case.

But to cut a long story short: your proposed implementation is sufficient for us (no need to have the change set for the first baseline in a stream).
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.
 
 

Reply via email to