Hello, First I'm not sure this is the right forum, but its the closest I can find.
I have a view in Jenkins which has about 50 maven projects in the trunk of SVN. The projects are all full projects (not parents and modules) and they're all marked as snapshots. Jenkins builds the projects without issue, recognising the upstream and downstream dependencies (which is awesome). We're in the early stages of the project so currently this is fine. But we need to move towards a stable pipeline in which we can issue release candidates not at snapshot, and final releases to live. To complicate matters, the project is OSGi, and we're hoping to keep flexibility where individual bundles can be altered and dropped into the container (Karaf), without having to rebuild and redeploy the other projects (where possible). We can do this using a versioning strategy where all bundles accept anything with the same minor and micro versions. I think the start is to fix all the versions (in the module poms) in trunk. Then I don't know how to move towards a system where developers can build snapshot versions and promote release candidates etc. with the most simplicity. Can someone suggest a strategy to me? -- View this message in context: http://jenkins-ci.361315.n4.nabble.com/Continuous-Integration-Strategies-HELP-tp4678293.html Sent from the Jenkins users mailing list archive at Nabble.com. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" 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.
