# Fixing Jenkins Builds and Go Imports After Changing a GitHub Username

DevFeed: [Fixing Jenkins Builds and Go Imports After Changing a GitHub Username](<https://devfeed.tech/articles/scripting-your-way-outta-hell-35193.md>)

Original publisher: [Read original article](<https://blog.jessfraz.com/post/scripting-your-way-outta-hell/>)

Published: 2016-09-30T15:09:26Z

Content type: opinion

Language: en

Sources: [Jessie Frazelle](<https://devfeed.tech/sources/jessie-frazelle.md>)

Topics: [Scripting](<https://devfeed.tech/topics/scripting.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [Jenkins](<https://devfeed.tech/topics/jenkins.md>), [Go Language](<https://devfeed.tech/topics/go-language.md>), [Docker](<https://devfeed.tech/topics/docker.md>), [Vim](<https://devfeed.tech/topics/vim.md>), [pull-requests](<https://devfeed.tech/topics/pull-requests.md>)

Tags: [docker](<https://devfeed.tech/tags/docker.md>), [github](<https://devfeed.tech/tags/github.md>), [go](<https://devfeed.tech/tags/go.md>), [jenkins](<https://devfeed.tech/tags/jenkins.md>), [pull-requests](<https://devfeed.tech/tags/pull-requests.md>), [scripting](<https://devfeed.tech/tags/scripting.md>), [vim](<https://devfeed.tech/tags/vim.md>)

## AI overview

Jess Frazelle recounts changing her GitHub username and repairing the resulting Jenkins checkout failures and Go import paths across roughly 50 repositories.

## Source excerpt

It all started innocently enough. I had "jfrazelle" as my GitHub handle for years, but my Twitter, IRC and other handles are all "jessfraz". No one on GitHub was actually using "jessfraz" so I sat on it waiting to make my move. I'm currently on vacation this week so of course I was looking to break all the things. One thing you must know about me is that at no point was I thinking I hate this. I actually love stuff like this, I live for pain. Why else would I run Linux on the desktop? But back to the story. I polled the twitterverse... Over/Under how many links you think I will break if I change my github username? (Yes, I know there are redirects, but still.) -- Jess Frazelle (@jessfraz) September 30, 2016 And then I made my move... It is done. Let's watch the world burn together. https://t.co/YpLqpP1X38 pic.twitter.com/4MX1tTthHO -- Jess Frazelle (@jessfraz) September 30, 2016 Everything was fine for a few minutes. Another thing you must know about me is: I have a private Jenkins instance for continuous builds and testing. Yes, I am this much of a nerd, but it is essential for building all the Dockerfiles for my publicly readable private docker registry at r.j3ss.co. I will save all that for another blog post, but the jobs started triggering. Immediately I got a bunch of emails about failed builds because Jenkins could not clone the repos. oh noe pic.twitter.com/ZRQnwWNR5L -- Jess Frazelle (@jessfraz) September 30, 2016 "This is fine" I thought to myself. It's all configured with Jenkins DSLs and I can just do a sed on those files and it will work again. I do this. The "apply-dsl" job is still red, oh duh because it cannot clone the repo where the DSLs live to even fix the problem. So I change it manually. This is fine. The builds all start again. Except now all the Go builds are failing because importing "jfrazelle/..." is not working. Vendor your crap kids!!! So I fix all these repos with the best vim command ever argdo. argdo will apply the script you run to all the ope