Comments

  • 1-2 of 2
  • Tom Bell
    posted July 2, 2009 in Go > Troubleshooting

    Hi Derek

    I had a look at that post but saw the comment that it would be fixed in the next version due out in a month, the post was dated 2006 so i thought this was a different issue

    Im using Cruise 1.2.1(6310-134674c9634f) and have mailed the file to ccdev

    Its not blocking anything at the moment, ill look at using that fix a bit later.

  • Tom Bell
    posted July 1, 2009 in Go > General Discussion

    Hitting this issue as well. Our pipeline looks like :

    (auto)Stage 1 - [Prepare DB] -> (auto)Stage 2 - Job[Run Unit Tests] Job[Run Browser Automation Tests] ->

    (manual)Stage 3 - [Deploy]

    Parallelising our tests looked like a big win as each suite can take around +10mins (was thinking of adding another for coverage as well) but since cruise doesnt wait for a stage to finish before running previous stages the Prepare DB stage would trigger from a new checkin and run while the tests were still running from the last checkin. This rebuilds the db in the middle of another agents Job.

    Is there any way to prevent a new pipeline build while "Auto" stages are still running from a previous run?