SVN not updating when build triggered with options



1 comment

  • Avatar
    Yogi Kulkarni
    This behavior, of pegging revisions in trigger-with-options, is intentional. For deployment pipelines it ensures you don't inadvertently push a revision that's not stable.
    You can always select the latest revision from the auto-complete drop-down for each material.
    When you trigger-with-options from the Pipeline Dependecies tab of an upstream pipeline, the upstream pipeline's revision is pegged but the rest of the materials default to the last run revision as expected (but the latest can be explicitly selected if required).

Please sign in to leave a comment.