![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Unassigned |
|
Attachments:
|
promotion-traceback.txt |
|
Components:
|
promoted-builds-plugin |
|
Created:
|
19/Feb/15 3:57 PM
|
|
Description:
|
Starting a promotion of a build in a specific branch of a multi-branch project gives an empty promotions page. There is no promotion possible.
Stepping back out to the parent multi-branch project and clicking the promotion icon gives a promotion rule unexpectedly. At this layer of a multi-branch project, the promotion plugin has no means of identifying which branch to promote. Running it anyways results in an attempt to promote artifacts from the parent project directory, resulting in an inability to find the artifacts and a traceback. Traceback attached. Promotion not working.
Workaround available: The promotion runs a shellscript that signs the artifact debian packages and pushes them to a repository. Manually running the script completes normally.
It would appear that the multi-branch plugin and the promotion plugin do not work together, as the promotion plugin is too brittle to handle $WORKSPACE being down one more directory level than in a single-branch project.
|
|
Environment:
|
Ubuntu 12.04.1, Jenkins 1.599 (latest), promoted builds plugin 2.20 (latest), multi-branch plugin 0.1.3
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
John Mellor
|
|
|
|
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
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/d/optout.
