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.

  1. Artifact path specified incorrectly
  2. 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 Directory: components/web/WebPortal
  • Destination: components


A subtle but important difference. The source dir MUST match your build artifact location.  In this example, the build artifact looks like:
Source: components/web/WebPortal
Destination: components/web

For the latter example, it's pretty obvious wha happen.
Check here on your Go server:
/var/lib/go-server/artifacts/pipelines/DevelopmentCI-Build/744/ExtractCIcomponents/1/ExtractZip/components/web/

If you no see files n junk...it's been purged.  But there is a way out!!

To regen the files, simply re-run the build from that original pipeline run - the files will re-appear, and any call to 'latest' for that pipeline run will be re-populated.  (although the one time this came up, the code piece built, but the tests piece did not)  It was enough to get us past the production deployment - we could then say 'hay hay hay give Go more disk!'.

Comments

Post a Comment

Popular posts from this blog

Learning through failure - a keyboard creation journey

Image
tl;dr Built a custom keyboard cuz I have weirdo nerve pain issues.   Learned a lot cuz I failed a lot.   Maybe 'do it right the first time' is a bad frame of mind.   The keyboard ended up being kinda nifty.   It has lights, and a trackball, and QMK, and it helps my issues.   \o/ ( tl;dr is internet lingo that means, too long; didn't read ) Pain as a key ingredient An old proverb says, 'necessity is the mother of invention', and that is how this story begins. Over the last few years, age or stress or something has caught up with me and I developed the need to change my human-to-computer interface.  Mousing changed to trackballing.  The traditional keyboard was swapped out for an ergonomic, and then split keyboard.  Complicated multi-finger-and-hand key combinations were replaced by single keypress macros.  And yet more was still needed. It's often said that change only happens with pain - indeed, the organizations many...
Read more

Learning Opportunities - Watching/listening list

Over the last year I've spent a lot of time learning (thank you, long commute & lunch hours).  Many topics ranging from Chef to DevOps to architecture concepts to management concepts and everything in between.  Why have I done this? DevOps Demystified with Ben Rockwood: https://www.youtube.com/watch?v=h5E--QSBVBY DevOps at ancestry.com: https://www.youtube.com/watch?v=pF5ya0q53kk Those two presentations were key in sending me down this road.  First, and most important, was Mr. Rockwood's explanation as to the real 'why', and the point behind DevOps from an operational perspective.  Second, and no less important but for a different reason, the continuous delivery system at ancestry.com really made it real to me because they are a 'Windows shop'.  So much of what I'd been reading about Chef/config mgmt. relied on amazing tools (see the error there?) only available to the Linux world.  Suddenly here's this guy telling me that it's possible...
Read more

DFSR - eventid 4312 - replication just won't work

This warning isn't documented that well on the googles, so here's some google fodder: You are trying to set up replication for a DFS folder (no existing replication) Source server is 2008R2, 'branch office' server is 2012R2 (I'm moving all our infra to 2012R2) You have no issues getting replication configured You see the DFSR folders get created on the other end, but nothing stages Finally you get EventID 4312: The DFS Replication service failed to get folder information when walking the file system on a journal wrap or loss recovery due to repeated sharing violations encountered on a folder. The service cannot replicate the folder and files in that folder until the sharing violation is resolved.    Additional Information:  Folder: F:\Users$\user.name\Desktop\Random Folder Name\  Replicated Folder Root: F:\Users$  File ID: {00000000-0000-0000-0000-000000000000}-v0  Replicated Folder Name: Users  Replicated Folder ID: 33F0449D...
Read more