Git commits sometimes cause two (or more?) builds
Reported by Chad Woolley | July 21st, 2008 @ 06:07 PM | in current
Especially on a new project
Comments and changes to this ticket
-
Chad Woolley August 24th, 2008 @ 06:26 PM
- → Tag changed from “git” to “git minor”
This only seems to happen when the project is first created
-
Alexey Verkhovsky September 9th, 2008 @ 05:36 PM
Couldn't reproduce this with Git 1.5.2.5 on Ubuntu 7. Chad apparently sees this behavior with Git 1.6.0.1 and Ubuntu 8.
-
Matt Wynne September 11th, 2008 @ 01:08 PM
We had this happen when we had submodules as part of the project being built.
When the submodules changed, because cruise wasn't configured to do git submodule update, it just built and built over and over again.
By going into the working folder for the project inside CRUISE_DATA_ROOT I fixed it by manually running the git command. We could (and probably will, when this rears its head again) make this part of the cruise rake task.
-
Jeremy Lightsmith October 30th, 2008 @ 10:40 AM
- → Milestone changed from “” to “current”
- → State changed from “new” to “resolved”
- → Assigned user changed from “” to “Jeremy Lightsmith”
this should be fixed now - we do submodule stuff by default
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
