|
|
|
Issue Type:
|
Bug
|
Affects Versions:
|
current |
Assignee:
|
Unassigned |
Components:
|
build-alias-setter |
Created:
|
10/Feb/14 3:10 AM
|
Description:
|
When a job with aliases is used as a copy for a new job, the build aliases are copied over to the new project.
It might not fail immediately, but at the very least the job can't be reloaded from disk and it can't be found.
Sample from system logs include:
Failed Loading job XXXXXXXXXX (new job)
java.lang.NullPointerException
at java.util.Vector.addAll(Vector.java:880)
at hudson.model.AbstractProject.createTransientActions(AbstractProject.java:756)
at hudson.model.Project.createTransientActions(Project.java:213)
at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:749)
at hudson.model.AbstractProject.onLoad(AbstractProject.java:336)
....
Feb 09, 2014 7:03:14 PM INFO jenkins.InitReactorRunner$1 onAttained
Loaded all jobs
|
Environment:
|
Linux SLES 11.2; Jenkins v1.543
|
Project:
|
Jenkins
|
Labels:
|
job
copy-job
build-alias
|
Priority:
|
Major
|
Reporter:
|
Patrice Matignon
|
|
|
|
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/groups/opt_out.