|
||||||||
|
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.
It's actually even easier to implement in the context of the ClearCse UCM plugin, since the component ($component) and the stream ($stream) are already available from the job context
we could simply do something like:
cleartool lsbl -fmt "%Xn\n" -stream $stream -component $component
and report the changeset by comparing the most recent baseline (the current) with the second most recent baseline (the immediately preceding one on the same stream).
If the output only has one baseline, it means that the current baseline is the first baseline ever built in this context, and we simply don't report a changeset at all.