![]() |
|
|
|
|
Change By:
|
Gianni O'Neill
(11/Aug/14 4:03 PM)
|
|
Description:
|
Steps to reproduce:-
1) Run a job which uses the maven plugin and has a "Deploy artifacts to maven repository" Post-build step
2) while the job is running use the jenkins-cli update-job command to change the job configuration (the configuration doesn't need to actually change. Calling update-job with the same config will also trigger the problem)
When Jenkins attempts to deploy the artifacts it will give the error:
{noformat}
Archiving artifacts
[ERROR] No artifacts are recorded. Is this a Maven project?
{noformat}
What seems to be happening is that the api call causes the cache in the AbstractLazyLoadRunMap for the module to get reloaded from disk. Meaning that
when
the build number check in MavenModuleSetBuild (line 486) actually looks at the last completed build, rather than the currently executing build and therefore returns false.
|
|
|
|
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.
