Hi,

Pipelines are self-contained and they should checkout to their own folders 
(each pipeline has its own sandbox in what concerns file system, let's say).

So, short answer: you cannot do what you're asking by using Go.

Still, you can try other things (which I wouldn't recommend anyway): have a 
symlink from your pipeline sandbox to the other place where you have your 
utils scripts checked out.

I'd say that if you need the scripts in all your pipelines, probably it 
makes sense for them to be a material. You can always blacklist if you 
don't want that material to auto trigger your pipelines.

Cheers,
Diogo

terça-feira, 27 de Junho de 2017 às 14:56:25 UTC+1, Jon A escreveu:
>
> Hi,
>
> I have a pipeline where the material is a set of utility scripts.
>
> I have other pipelines where they will need access to the scripts to be 
> able to run them. I didn't want to add the scripts material again to each 
> additional pipeline I have. Is it possibly that I can refer to my existing 
> pipeline that uses the scripts material?
>
> I have multiple agents which could run any of my additional pipelines but 
> would still need to be able to access and run the scripts.
>
>
> Thanks,
> Jon
>

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