> I assume you're looking for something more than: "source ./version; docker > build --rm -t local/dummy:$GO_PIPELINE_LABEL ." ? >
Yes, the main point is to have a variable which is available on all stages (like a global one I guess), but is set up programmatically from one of stages. > Typically, the only way to share information between stages is to use > artifacts. External artifact plugins allow environment variables to be set, > which affect other tasks within a job, but a standard artifact is probably > the most straightforward way. > Thanks, this is exactly the answer to my question. -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/d01f976e-3fd1-4b0e-9178-39a9bb063597%40googlegroups.com.
