There are two thing that you have mentioned here, and both are different processes. 1. Pushing to github - manages source code 2. Doing a mvn release - makes your new version of plugin avaliable in the updatecenter.
1. Pushing to github, This is the process of making changes, resolving issues to your plugin, these pushes to github are just making the code accessable. this allows the plugin to be built on the Buildhive to make sure that it compiles and passes all tests. 2. Doing a mvn release This process does a clean of the workarea, modification of the version in the pom.xml e.g. 0.2-SNAPSHOT -> 0.2. Then does a mvn compile test and uploads the generated jar and hpi files to the repository defined in the pom.xml Then sets up the version for the next iteration of work e.g. 0.2 -> 0.3-SNAPSHOT. See details of this at https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins When this is done the Jenkins backend will detect the new version in the repo and add/update the update center data, making the new version avalible to all Jenkins users. Make sure you read through the important points on https://wiki.jenkins-ci.org/display/JENKINS/Extend+Jenkins which covers all of the information needed on creating and modifying existing plugins. Hope this makes things clearer. Chris. On Friday, July 13, 2012 6:02:05 AM UTC+1, Louis wrote: > > Hi all, > > This is a beginner question, but what's the difference between pushing to > github via mvn release and pushing manually? Will both allow plugins to be > updated in the page? (I'm not sure how the plugin scanning / build process > works). > > Thanks! > Louis >
