How to migrate your old account/workspace/... to the new Jenkins infrastructure
- Migrate your old java.net user account (or create a new one)
- Switch your SVN workspace:
If you already have a workspace checked out, you need to run the following command to have it point to the new location:
Moving plugin development to Jenkins
Override the maven release plugin configuration
This is only for plugin that depend on a parent POM 1.387 and earlier. This prevents the release process from executing
hpi:announce goals, which fail.
Override the SCM setting
For plugins on GitHub, add the following entry in your POM:
You may also use GitHub
https URLs if your corporate network blocks ssh connections.
For plugins still on Subversion, add the following entry in your POM. This is only needed when you depend on 1.397 and earlier.
Override the Maven repository location
Add the following declaration in your plugin POM:
Specify new tools location in