I found a workaround for this. (This may be the intended solution, but the plugin configuration page doesn't mention this. https://wiki.jenkins-ci.org/display/JENKINS/Artifactory+Plugin)
I had to add a post-build action of "Git Publisher". I checked "Push Only If Build Succeeds". Then I clicked "Add Branch" and put "master" in the branch to push (because I had master in the git "Checkout to a specific local branch" box, per the plugin config page) and "origin" in the "Target remote name" block. This forced a push of the locally-committed updated POM. It would be nice if the plugin did this automatically for maven, like it does for gradle. Thanks, Kirk -- View this message in context: http://forums.jfrog.org/Jenkins-plugin-not-updating-git-for-maven-job-tp7579393p7579395.html Sent from the Artifactory - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
