Hey Veeral, On Tue, Oct 01, 2019 at 17:01:32 -0700, Veeral Patel wrote: > > As you mentioned, jobs run in parallel. So, it's possible that your > MD5-computing-job has not finished while your other jobs which need it have > started. That's the reason jobs cannot share artifacts. So, your > MD5-computing-job should be in a previous stage. > > Yes, I was envisioning putting the compute MD5 job into a different stage. > What's the best way to share string data like the MD5 between stages, in > your view?
Yes, it would be easiest to share a file with that information. Of course an ideal modeling approach would be: Stage 1: "Save" string to some key-value store. Stage 2: "Retrieve" string from the key-value store for "Stage 1". But, since it's not possible to model it that way, you will need to save it to a file. It is possible to write a pluggable artifact plugin which can do that. :) But, it seems like it would be overkill. Cheers, Aravind -- 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/20191002174003.i7c7iuym4b7xgyn2%40arvindsv.com.
