#204 ✓resolved
Chad Woolley

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

    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

    Alexey Verkhovsky September 9th, 2008 @ 05:36 PM

    Couldn't reproduce this with Git on Ubuntu 7. Chad apparently sees this behavior with Git and Ubuntu 8.

  • Matt Wynne

    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

    Jeremy Lightsmith October 30th, 2008 @ 10:40 AM

    • Assigned user set to “Jeremy Lightsmith”
    • Milestone set to current
    • State changed from “new” to “resolved”

    this should be fixed now - we do submodule stuff by default

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป