Hi Marc ...sorry for the late reply - maybe you've already solved your issue?
The change set is reported against the previous baseline - no matter what it's promotion level is. In your case, you have a stream where there are mixed promotion levels - some are BUILT others are REJECTED - consequently this is not the right context (stream) for you to do the comparison. What you should do is that you should *harvest* the good builds to another stream, where all the BUILT ones lies as pearls on a sting. This is something the plugin is designed to do: The recommended strategy for what you want to achieve is this: - Setup a new project - name it "built", "stable" or something like that - enable interproject deliveries on the project. - On your current UCM project, enable interproject deliveries and set the "default target" property of your project integration to point to the integration stream of you new Built project. -Setup a seperate job on Jenkins. Let it run on the integration stream in your new Built project and run the job in "poll sibling" mode, Set the promotion level to scan for the BUILT level. What happens here, is that all the baselines that are have promotion level BUILT on your project integration stream end up as new baselines on the Built projects integration stream. You have succesfully harvested the "good" baselines to a different context (stream) and in this context they will be succeeding each other - and and your changeset will now contain what you're looking for. Feel free to contact me if you want me to elaborate further (skype ID:Lakruzz) Have a look at the blog post http://www.praqma.com/stories/ccucm Lars Kruse Partner & co-founder Praqma On Wednesday, October 31, 2012 3:46:43 PM UTC+1, marcdb wrote: > > Hello, > > I am trying to set up a Jenkins project with the ClearCase UCM plugin. Our > build system is based on oobs and ivy and we use the dependencies defined > in ivy to determine what needs to be built. I wanted to use the changeset > generated during a build job for further processing inside that job. So my > first question is whether it is possible to access this changeset ? I found > some groovy code on stackoverflow (http://stackoverflow.com/a/6261180) > illustrating this concept for other SCM-systems, but I don't know if this > can also be used for the ClearCase UCM plugin. > > I also wanted to know what is included in the changeset produced by the > plugin. What I actually want, is a changeset consisting of the difference > between: > > - the most recent INITIAL baseline on a stream and > - the most recent BUILT baseline. > > I will be using the stream in self-polling mode. Then I want to rebuild > all modules (our modules are sub-directories of our UCM components) and > their dependees that have been changed since the last BUILT baseline. If > the build would fail, the baseline would not be promoted to BUILT and the > next run should rebuild also all changed modules from that run. > > Actually it is more complicated then I thought when I started writing > this: if nothing would have been changed between two INITIAL baselines, > then it doesn't make sense to start a new build anyway. So I realise now I > need two changesets: one to trigger a new build (based on the difference > between the previous INITIAL baseline) and a changeset based on the > difference between the latest INITIAL and the latest BUILT baseline. > > Has anybody else done something similar ? Can the current ClearCase UCM > plugin be used for this ? > > Thanks, > Marc > >
