cforce: I had to check out the CVS plugin from Github (https://github.com/jenkinsci/cvs-plugin), since SNAPSHOT versions are not in the Jenkins Repo. I then build the plugin from source using Maven (i.e. mvn hpi:hpi), but Jenkins provides a Gradle build if you prefer. I then stopped our Jenkins service and deleted from JENKINS_HOME/plugins any of: cvs.hpi, cvs.jpi, cvs.jpi.pinned, cvs.jpi.pinned and the cvs directory. Finally, I copied the HPI that was built by Maven to the plugins directory and created an empty file named cvs.hpi.pinned to prevent Jenkins from overwriting our new custom plugin. Now you can restart Jenkins.

I verified in Jenkins -> Manage Plugins that I was running CVS plugin 2.6-SNAPSHOT, and found that the undesirable behavior of another closed issue (https://issues.jenkins-ci.org/browse/JENKINS-14141) is still in place. If you succeed in building/installing the SNAPSHOT, please post back whether you experience the same issues or not.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to