|
If you were logged in you would be able to see more operations.
|
|
|
Pulse
Created: 03/Mar/09 02:24 AM
Updated: 02/Jul/09 09:47 AM
|
|
| Component/s: |
None
|
| Affects Version/s: |
2.0.19
|
| Fix Version/s: |
2.1.4,
2.0.33
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
I had a rule set up in Clean Update mode pointing at a particular git repo and branch. It did some builds against that repo and branch.
Then I changed the repo and branch it pointed to, and the server stopped seeing new changes. These messages were in the log:
03/03/2009 10:05:28: Polling SCM for changes...
03/03/2009 10:05:29: Error polling SCM: Git command: git log --name-status --pretty=format:%H%n%cn%n%cd%n%s%n. --reverse a1dd87faaaf3420b4f4c506c643ebbf8d6f3fa5b..HEAD exited with non zero exit code: 128.
03/03/2009 10:11:26: Polling SCM for changes...
03/03/2009 10:11:28: Error polling SCM: Git command: git log --name-status --pretty=format:%H%n%cn%n%cd%n%s%n. --reverse a1dd87faaaf3420b4f4c506c643ebbf8d6f3fa5b..HEAD exited with non zero exit code: 128.
I think the problem is that a1dd87faaaf3420b4f4c506c643ebbf8d6f3fa5b is a commit in the old repo and not the new repo, therefore the command fails.
The problem persisted even after doing a reinitialization.
Currently I'm about to attempt the workaround of temporarily setting the project to Clean Checkout, letting it do one build in that mode, then setting it back to Clean Update (which is unfortunate because a full checkout takes hours).
|
|
Description
|
I had a rule set up in Clean Update mode pointing at a particular git repo and branch. It did some builds against that repo and branch.
Then I changed the repo and branch it pointed to, and the server stopped seeing new changes. These messages were in the log:
03/03/2009 10:05:28: Polling SCM for changes...
03/03/2009 10:05:29: Error polling SCM: Git command: git log --name-status --pretty=format:%H%n%cn%n%cd%n%s%n. --reverse a1dd87faaaf3420b4f4c506c643ebbf8d6f3fa5b..HEAD exited with non zero exit code: 128.
03/03/2009 10:11:26: Polling SCM for changes...
03/03/2009 10:11:28: Error polling SCM: Git command: git log --name-status --pretty=format:%H%n%cn%n%cd%n%s%n. --reverse a1dd87faaaf3420b4f4c506c643ebbf8d6f3fa5b..HEAD exited with non zero exit code: 128.
I think the problem is that a1dd87faaaf3420b4f4c506c643ebbf8d6f3fa5b is a commit in the old repo and not the new repo, therefore the command fails.
The problem persisted even after doing a reinitialization.
Currently I'm about to attempt the workaround of temporarily setting the project to Clean Checkout, letting it do one build in that mode, then setting it back to Clean Update (which is unfortunate because a full checkout takes hours). |
Show » |
|
Bug
Resolved
3
Polling git scm fails after changing git repository
OK, let me know how you go, although if the problem is with the commit id, then I suspect a clean checkout will not fix it. The scm polling process keeps track of the last commit id so that it can check for changes since then. The project re-init process does not clear that, and a clean checkout will not clean that either. That information is actually stored in memory, so a server reboot should fix that temporarily.
Please let me know how you go.