Hello Veeral, On Mon, Sep 30, 2019 at 14:36:48 -0700, Veeral Patel wrote: > I was thinking of setting it up so computing the file's MD5 is one job and > the other operations using the MD5 are additional jobs (which run in > parallel). > > My question is, how do I allow the additional jobs to access the MD5 > computed from the previous job? I could create a text file artifact which > contains the MD5, but I'm wondering if I could make the MD5 a "string > artifact" if that makes sense.
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. Between jobs, the usual way to share information is through file artifacts. Of course, you can upload that information to a different system (say a Docker image can be considered an artifact which resides in the Docker registry). GoCD has the concept of a pluggable, external artifact where the artifact is not necessarily a file. For instance, the Docker registry artifact plugin (https://github.com/gocd/docker-registry-artifact-plugin) allows you to publish and fetch Docker images as artifacts. GoCD manages the metadata using regular artifact files in the background. 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/20191001221915.yevkuqtnap6amy7s%40arvindsv.com.
