Usability issue: fetching artifacts from ancestor pipelines

Comments

4 comments

  • Avatar
    Marco Abis

    Hi Jason,

          not a direct answer to your request but you mention you have "pipeline chains of 8" which is often either a symptom of a huge (and I mean HUGE) setup or an indication that parallelization would bring lots of benefit. Our motto lately has been "Fail Fast, Learn Fast" :-)

    Have you thought about running (some) pipelines in parallel? 

    Cheers

    Marco

    0
    Comment actions Permalink
  • Avatar
    Jason Duff

    The point is, whether it is a chain of 8 or 3, that having to explicitly enter the entire path for ancestor artifcats is a usability issue.  It is especially problematic when using templates which then requires you to use a parameter to represent the path because it has to be different.

    As far as the # of pipelines goes, i didn't think 8 was necessarily odd though I'm fairly new to using GO as well.  For instance

    #1 - Build and Test

    #2 - AcceptanceTests

    #3 - DeployToDev

    #4 - SITStageGate (this is a workaround for the inability to templatize the manual/automatic flag)

    #5 - DeployToSIT

    #6 - UATStageGate (workaround)

    #7 - DeployToUAT

    #8 - ProdStageGate (workaround)

    #9 - DeployToProd

    ...

     

    I don't want to hijack this thread but it seems to me that this would be a typical flow.

    0
    Comment actions Permalink
  • Avatar
    Shilpa Goley

     

    Hi Jason,

    As you rightly said, Go has the information of the pipeline hierarchy. But which path should be used to pull the artifact is very important. This is because the pipeline counter from which the artifact is being pulled will completely dependent on the exact ancestor path. Hence, Go does not make that decision and lets the user decide.

    I agree it is tedious given a long hierarchy, but Go tries to give all the possible options in the pipeline drop down to make it easier.

    0
    Comment actions Permalink
  • Avatar
    Jason Duff

    At the very least you could give us the option to specify only the artifact pipeline.  If we don't enter the entire path then by default GO should figure it out, just choose one.  I would imagine that in most cases there is only one path between the pipelines.

    As I mentioned, this is an issue when using templates as the path then needs to differ and we have to resort to using parameters and the like.

    0
    Comment actions Permalink

Please sign in to leave a comment.