Hello,
My project has 5 components developed in different languages (Java, Groovy, 
Python, Scala) and they each build separately. However, we release them as 
a single build consisting on individual artefacts. I have started setting 
up GO and created a Fan-in pipeline to create a release candidate.
My challenge is at this stage, I am not sure what tasks to configure for 
this pipeline; the release will need to be deployed and tested in QA and 
UAT but there two separate pipelines for them. I don't want the release 
candidate pipeline to do any build but use the artefacts from upstream 
jobs. I am wondering if I should create a shell script to copy all the 
artefacts to a release candidate repository and that should be all what 
this pipeline does.

Does anybody has similar experience or suggestions?

Thanks a lot.

Regards
Charles

-- 
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.

Reply via email to