Articles in this section

See more

Controlling upstream versions of pipeline materials (autoUpdate)

Avatar
Brett Cave
Updated
Follow 

Hi,

When configuring a new pipeline, is there a way to configure certain materials to update to the latest version, while allowing other materials to use the same version?

For example, I have configured a pipeline that has 1 SVN material and 1 upstream pipeline. When changes are committed to SVN, I want the pipeline to run with the new SVN material, but still use the old pipeline material. Is this possible (e.g. using a combination of autoUpdate on materials, approval types and fetchMaterials?)

 

thanks

Comments

2 comments

Sort by Date Votes
  • Avatar
    Ian Bridson

    Hi Brett


     


    what triggers the upstream pipeline or is it fairly static? I have a similar setup where the upstream artifact is controlled by a manual approval stage that 'generates' the artifact, so only approved artifacts can be fed into the next pipeline. This allows certain control over what gets promoted, but it would always be the latest artifact, unless the you use Trigger with Options to select a previous version. I don't tihnk Fetchmaterials goes as far as specifying a particular version.

    0
    Comment actions Permalink
  • Avatar
    Brett Cave

    Hi Ian,


     


    The upstream pipeline is triggered by svn / further upstream pipelines. I think adding another stage with manual approval would work well


     


    Thanks for the advice.

    0
    Comment actions Permalink

Please sign in to leave a comment.