But dev uat and prod seem like a linear progression. Why not model you build this way?
Build/test/package -> dev -> uat -> prod
You could model each of those as either stages or pipelines, and just pass the original artifact around? Unless I’m misunderstanding what you are doing?
FWIW I’m assuming dev, uat, and prod are deploy environments
@Raji2420 if you model each as a pipeline you have the flexibility to do what you want. You’ll need to understand the concept of upstream pipelines.
Here’s some reading material on modeling pipelines this way:
@ssanchez227 not sure that I understand your question— are you asking if the value of an environment variable can be a list of things? If so, environment variables are always text values in any common operating system. If you are trying to model non-text structures through an environment variable you’ll have to serialize them to text. The same would be true for any build automation software, including Jenkins.
If that was not your question, then please clarify?
@ssanchez227 ok, I see. There isn’t a way to have prepopulated suggestions for env variables on the trigger with options modal AFAIK.
However, maybe there are other ways to solve your problem:
Maybe someone more clever than me has a better idea