Migration processCreate new projectsJENKINS PLUGINS projectKEY : JPLUGINS Create JENKINS INFRA projectKEY : JINFRA Components distributionThis table of current components in JENKINS project describe their distribution in new projects :
Update irc bot to create components for plugins in new Jira projectSources : https://github.com/jenkinsci/backend-ircbot/ Update Default Dashboard
Move issues
Create versions in JENKINS projectFrom 1.400 ? Future stepsProposal : Split JENKINS PLUGINS Jira project to have one project per plugin ... |
Jira Projects Split and Cleanup
Skip to end of metadata
Go to start of metadata
Comments (4)
Mar 03, 2011
fcamblor - says:
Wouldn't it be possible to call a jenkins maven plugin during the release proces...Wouldn't it be possible to call a jenkins maven plugin during the release process of a plugin ?
This plugin would :
- Create the jira plugin project _if it doesn't already exist_ corresponding to currently released plugin
- Add a new version to the jira plugin project
Mar 08, 2011
Arnaud Heritier says:
Creating projects using RPC may be possible : http://docs.atlassian.com/rpc-jira...Creating projects using RPC may be possible : http://docs.atlassian.com/rpc-jira-plugin/latest/com/atlassian/jira/rpc/soap/JiraSoapService.html
But they don't always keep the compat between versions thus it could be annoying to maintain
About the version it could be possible.
Mar 11, 2011
Cédric Lamalle says:
If using version numbers only for 'Fix Version/s' field, it's ok to start with 1...If using version numbers only for 'Fix Version/s' field, it's ok to start with 1.400. If using them with 'Affects Version/s' field it will be useful to create earlier versions.
Apr 14, 2011
Mirko Friedenhagen says:
Will it be possible to add versions for plugins as well? We could use componentN...Will it be possible to add versions for plugins as well? We could use componentName-VERSION for this.
Add Comment