![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Unassigned |
|
Components:
|
changelog-history-plugin |
|
Created:
|
31/Oct/14 9:19 PM
|
|
Description:
|
This issue cropped up for me while I was debugging jobs affected by JENKINS-21785 (some jobs were never reconfigured with the additional credentials). I noticed that the changelog history (Recent Changes) for both the failed and the following successful jobs would be blank.
What would happen:
1. An external for a project in the Subversion repo would get updated
2. A job that checks out that aforementioned project would be started (Note this job is not configured with the additional credentials like it's supposed to)
3. The main project as well as the external would be checked out from the repo successfully
4. The Subversion plugin would throw a revision check error on the external (as expected), causing the build to fail
5. The job is run again, resulting in a successful build
The first build in this scenario had new stuff to deploy compared to the previous, successful build. If the build had been successful, these changes and their revision numbers would be noted in the Recent Changes section for the job, but they weren't.
This behavior kind of makes sense to me since they weren't deployed*; however, on the subsequent build that was successful, again, no changes were logged--and this time they were deployed!
I would have expected the changes to be logged in at least one of these jobs.
- It would equally make sense to log changes introduced in a given build even if it fails, but then only when the a compilation failure is caused by borked code, so you could see which changes contributed to the failure; however, in this case, the job failed due to a credentials issue--before any build steps were run.
|
|
Environment:
|
Jenkins 1.587; Credentials Plugin 1.18, Subversion Plugin 2.4.4
RHEL 6.6
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Nathan Malinoski
|
|
|
|
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.
