Were you checking the go-agent's working directory? They get replaced / purged after each run of the stage. Assuming you've exposed the artifacts as described in here <https://docs.gocd.org/current/configuration/managing_artifacts_and_reports.html>, then GoCD Server stores artifacts versioned by the pipeline build number and stage counter for each stage.
The location of the artifacts is on the gocd server instance. It's available under the server's working directory like */data/go-server/artifacts/pipelines/*. If you're looking at the right place then probably check your disk usage, GoCD has Auto Delete Artifacts <https://docs.gocd.org/current/configuration/delete_artifacts.html> feature which can also cause problems on large setups. In such cases consider using something like gocd-janitor <https://github.com/ashwanthkumar/gocd-janitor> . On Wed, Jan 16, 2019 at 9:46 PM ankur gupta <[email protected]> wrote: > Hi All, > > Old Artifacts gets replaced in the server box when new build is triggered > in the pipeline as its default behaviour, unlike Jenkins where build number > is used to store the Artifacts for the trigger. > > So, just wanted to understand if this is its default behaviour ? > > Thanks > > -- > 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.
