Most package repo plugins will setup an environment variable containing the URL of the artifact, along with some additional metadata (version, co-ordinates, etc). The expectation is that any scripts in the task will download the artifact and use them as they see fit.
See: https://github.com/1and1/go-maven-poller#published-environment-variables https://github.com/1and1/go-maven-poller#downloading-the-package - Ketan On Tue, Sep 25, 2018 at 2:42 PM Роман Щербаков < scherbakov.roman....@gmail.com> wrote: > Hi! I have a package repository (Maven). And I use it as a material for my > pipeline. Connection with the repo is OK. I turned on the "Fetch Materials" > option and turned off the "Clean Working Directory" option, but after my > pipeline starts or done, there are no any files of my package in the > working directory (/var/lib/go-agent/pipelines/MyPipeline/). What should I > do to fix it or maybe "Fetch Materials" is designed for something else? > Thanks for any help > > -- > 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 go-cd+unsubscr...@googlegroups.com. > 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 go-cd+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
