Setting system-wide variables for use in pipelines

Follow

Comments

4 comments

  • Avatar
    Manoj

    Setting environment variables in an environment ( and adding the piplines you need to that environment ) can be thought of as setting "system wide variables" and may or may not be useful to you depending on what you are doing.

  • Avatar
    Matt Gross

    That would make sense in being able to pass environment variables to jobs. But in this case, Go itself is doing the work of contacting the Mercurial repositories. The pipeline parameters work perfectly for this, but you have to add the same parameter to each separate pipeline.

  • Avatar
    Manoj

    That's why I said depending on what you want / can do.


    By making the fetchMaterials attribute false, you can basically move the  materials fetching / update part to within your scripts rather than the cruise config and make these scripts read the set environment values? ( you can also read the revison variables that Go sets while running jobs to make sure you checkout the right revision )


    It is ugly, but I think this is the closest you can get as of now.

  • Avatar
    Jason Duff

    +1 on System-wide env variables, would remove some duplication

Please sign in to leave a comment.