Hello Helge Thanks for your kind reply. Either of the option is not solving the git-checkout at every stage. Is there way we can achieve to run stage by executing download the artefacts from Artifactory. (Can we put curl command in the pipeline.yaml itself? if so can you please give me some example?) Thanks again!!!
Regards Prakash On Wednesday, 5 August 2020 at 18:40:11 UTC+10 bewal...@gmail.com wrote: > Hello Prakash, > > there are 2 ways to achieve this: > 1. You can store the created artifact from the previous stage as a > resulting artifact ( > https://docs.gocd.org/20.4.0/configuration/managing_artifacts_and_reports.html) > > and then fetch the artifact in the next stage with the "Fetch Artifact" > task for further use. > 2. Upload the artifact to the Artifactory in the previous stage and > retrieve the artifact in next stage using a simple curl task. > I would prefer the first option because all the artifact handling is done > by GoCD internally. > > Regards, > Helge > > > Am Mittwoch, 5. August 2020 09:41:40 UTC+2 schrieb Prakash Tirumalareddy: >> >> Hello Everyone >> >> Is there anyway we can configure a particular stage not to do >> git-checkout and instead download the artefacts from external repository >> (such jfrog artifactory) which was built and pushed in previous stage? >> >> Currently what have seen that at every stage it does the git-checkout for >> the commit hash. >> I know there is a stage configuration which says not to checkout the >> material. But when we enable this option then there is no way in that stage >> to do required task. >> >> Your help will be greatly appreciated. >> >> Regards >> Prakash >> >> -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/30100a03-ea99-47cd-8958-a6e9fda9f761n%40googlegroups.com.
