I'm using the API to trigger a pipeline. I'd like pass a (json) file which contains an arbitrary (variable) number of parameters to the pipeline and then process this file in the pipeline. I'm thinking that the most appropriate way would be to upload the json file as an artifact (also via the API).
Could anyone please explain the proper flow and API calls required to achieve this? 1. Do I need to trigger the pipeline and call "Create Artifact" immediately after? Does the pipeline need to be running for the create artifact api to work? 2. How can I make sure that the execution of the pipeline continues only after the artifact is loaded? Some ideas I have: Use a manual stage? - stage 1 will stop and I'll create the artifact. Stage 2 is manual. After the artifact is loaded, I'd need to somehow release stage 2 via API, but I'm not sure this can be done. Or, should I do something similar but with two pipelines instead of stages? Pipeline 1: does nothing, after being triggered it will stop and I'll create the artifact in it Pipeline2 (downstream): after the artifact is loaded, trigger this pipeline (via API) which will then fetch the artifact and process it. -- 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]. For more options, visit https://groups.google.com/d/optout.
