After generating the artifacts, you may want to write a task that copies them where ever you want, and then generate a readme file that you artefact in Go. This readme could contain the path where you've copied your artefacts, for e.g.
-- Ram On Fri, Jul 8, 2016 at 5:32 PM, Salomé L. <[email protected]> wrote: > Hello ! > My pipeline includes packaging a delivery folder and it should be copied > in a global delivery folder. But in GoCD the artifacts are stored in the > artifacts folder in a complicated tree (pipelines, counter...) so it's > difficult to access it. > Is it possible to create a task which will put the artifacts in a shorter > path ? (Not necessarily in the Go Server folder) > Thanks and keep up the good job :) > Salomé > > -- > 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. > -- 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.
