SVN material in downstream Pipeline

Comments

6 comments

  • Avatar
    Simon Dean

    This is still proving to be an important issue for us.  Has the feature been considered for an upcoming release?  

    Thanks

    0
    Comment actions Permalink
  • Avatar
    Shilpa Goley

    Hi Simon,

    We apologize for the delay caused in the reply to your query.

    If both your pipelines "CI Pipeline" and "Test Environment Deployment Pipeline" depend on the same SVN Material, then, GO makes sure that whichever revision the parent pipeline ran with, the child pipeline runs with the same revision. Provided the definition (url, username) of the SVN material is exactly same in both the pipeline configs.

    Could you confirm if your've tried having your pipeline configurations in the above pattern? Also, may I know the Go version that you are using

    Thanks

    Shilpa

     

    0
    Comment actions Permalink
  • Avatar
    Simon Dean

    Hi Shilpa.  We're using 12.2.1 (15143-a840079e35f9f0).  It doesn't work when the first step of the downstream pipeline is manually triggered, which is a common use case for pipelines that deploy to environments.  We've had to work round it on an ad-hoc basis by adding an extra - otherwise unneeded - stage to each pipeline; the extra stage is automatically triggered and pulls in the correct combination of upstream pipeline and SVN revision.  However the workaround is proving confusing for people as every build triggers the first stage of the pipelines instead of just the builds that people manually trigger; the approach is also confusing for people creating new pipelines.  

     

    Thanks for your assistance

    Simon 

    0
    Comment actions Permalink
  • Avatar
    Shilpa Goley

    Hi Simon,

    Yes, you are right. If you manually trigger a pipeline using the "trigger" button, it will always take the latest revision. We suggest you to use "trigger with options" button. This allows you to pick the revision which you want.

    We have some features coming up in future releases which will automatically resolve the right revisions within trigger with options popup. 

    Regards

    Shilpa

    0
    Comment actions Permalink
  • Avatar
    Simon Dean

    Hi Shilpa.  With the current trigger with options approach it's obviously quite easy for someone to pick the wrong combination of build number and SVN revision.  Please consider this feature request as being one for the feature you mention where the trigger with options popup will automatically select the right SVN revision (or other VCS revision number) to go with the upstream build number.  

    Actually we'd also request that the new feature applies the same logic to the normal tigger button (not the with options one) so that a normal trigger also automatically selects the right SVN revision to go with the upstream build number.  

    Thanks again

    Simon 

    0
    Comment actions Permalink
  • Avatar
    Shilpa Goley

    Hi Simon,

    We'll record your feature request.

    Thanks

    Shilpa

    0
    Comment actions Permalink

Please sign in to leave a comment.