Hello, I have a use case in which I need to maintain a 1:1 relationship between a corporate parent POM and a LTS Jenkins parent POM. The corporate POM in this case is a child of the Jenkins POM, plus attributes.
To implement this, I'm planning to run automated daily checks in which the version of the parent POM in the corporate POM is updated to the latest LTS version of Jenkins. The easy way to update automatically via maven is using mvn versions:update-parent It indeed works perfect for regular Jenkins releases: C:\workspaces\rafael_workspace\jenkins-parent-pom>mvn versions:update-parent [INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Jenkins Corporate POM 1.580.3 [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- versions-maven-plugin:1.3.1:update-parent (default-cli) @ jenkins -ci --- [INFO] artifact org.jenkins-ci.plugins:plugin: checking for updates from nexus-cdg [INFO] Updating parent from 1.580.3 to 1.602 [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 15.466s [INFO] Finished at: Thu Mar 12 18:59:51 CET 2015 [INFO] Final Memory: 18M/124M [INFO] ------------------------------------------------------------------------ Then, what should I do to update to the latest LTS version instead of the regular versions? -- Rafael -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/9f72c900-5199-4dc9-a92e-3660103551a3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
