Hi, In an effort to parallelise our build, we have a number of jobs building different components from a single subversion directory. Unfortunately some jobs depend on others and by the time dependant builds start, additional changes have often been committed; with the resulting combined product ultimately built from a set of revisions rather than a specific one. What we'd really like to do is build all these jobs from a consistent revision but I don't see an easy way to achieve that in Jenkins as it stands.
Is there a recommended way of achieving this type of arrangement? One solution I've been pondering is to change Jenkins such that on subversion checkout/update, the revision can be exported as a parameter for triggered builds, which can then checkout/update to a specific revision rather than HEAD. Are there any obvious problems with this approach that I need to think about? Would such changes be welcome into the subversion-plugin or should I be considering a separate plugin to achieve this? Thanks for your advice! Rob -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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.
