I don’t know whether this currently happens when I force a pipeline, but if not, I’d like an option for saying to start a pipeline but to have it update from materials first.

(I’d also REALLY like cruise to know about svn 1.5, since there’s that silent working-copy update between major versions…).

Cruise 1.1 (out next week) understands svn 1.5 (in fact, we no longer bundle Subversion with 1.1, so you’ll have to make sure you have it installed on your server and any agents).

We’ve changed the way “forcing” a pipeline works a bit for 1.1. When you press the play button, it will always look for modifications, and either schedule a new pipeline (including any new modifications if present) or re-run the previous pipeline (if it can’t find any new modifications).

Jez.

Excellent; thanks.