Thoughtworks Go - dreaded 404 on artifact fetching
I've run into this more than I'd care to admit, so figured I should post it up. Often when chaining Go pipelines I run into a message like: 19:40:33.412 [go] Could not fetch artifact https://ip.ad.dr.es:8154/go/remoting/files/DevCI-Build/852/ExtractCIcomponents/1/ExtractZIP/components/WebPortal.zip. Pausing 15 seconds to retry. Error was : Unsuccessful response '404' from the server I've found there are two reasons for this message to come up. Artifact path specified incorrectly Go server purging accidentally removed the file An example bad artifact path is visible in the example above. If you check the pipeline details, you see: Pipeline Name: #{fetchPipeline} Stage Name: ExtractCIcomponents Job Name: ExtractZIP Source Directory: components/WebPortal Destination: components What you SHOULD see is: Pipeline Name: #{fetchPipeline} Stage Name: ExtractCIcomponents Job Name: ExtractZIP Source Di...