![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Nicolas De Loof
|
|
Components:
|
git, repo |
|
Created:
|
17/Aug/12 7:57 PM
|
|
Description:
|
It seems that every time a build job configuration is modified, the code list changes cannot be identified for the first build after the modification.
The Jenkins repo plugin seems to be failing to properly parse and record all the changes that trigger a build. Either that or not all commits are showing up in the log
In place of changes, the message 'Failed to determine' is displayed with a link to the log. Looking at the log does not reveal any errors or stack traces.
|
|
Environment:
|
Linux RHEL server
Linux Ubuntu slave agents
Linux RHEL slave agents
Jenkins 1.472
Repo 1.2.1
Git 1.1.21
|
|
Project:
|
Jenkins
|
|
Labels:
|
plugin
configuration
jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
rejesi
|
|
|
|
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
|
