You're better off doing what Ashwath recommends - checking in the Docker file into a source code repo and using that as material.
This way, you'd have version control of the Dockerfile, traceability of the actions originating from it, and the ability to trigger pipelines upon changing the Docker file. -- Ram On Fri, Mar 17, 2017 at 6:43 PM, 'Ashwanth Kumar' via go-cd < [email protected]> wrote: > I don't think it is possible to add a static file to a pipeline. Have you > considered the option of Adding the file as part of a repo and use white / > black list to control what triggers the pipeline? If it's only manually > triggered it doesn't matter to set up the white / black lists. > > If you want to fetch that file to multiple pipelines, you can expose it as > an artifact and Fetch it at other places. > > On Fri, Mar 17, 2017 at 3:57 PM, Hugh Acland <[email protected]> wrote: > >> Hi >> >> I need to add a single file to a pipeline (it is a Dockerfile). Is it >> possible to upload that into Go so it is copied as a single "material" each >> time into the place I want it? >> >> thanks >> regards >> Hugh >> >> -- >> 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. >> > > > > -- > > Ashwanth Kumar / ashwanthkumar.in > > -- > 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.
