Syndicate content


warning: Creating default object from empty value in /var/www/ on line 33.
Sep 27

Sensible Auto Git Tagging Deployments to Production on Jenkins

Tue, 09/27/2016 - 07:03 — peter

The Problem

You've built your code, and you have a spiffy Jenkins setup to pull from git and run your tests for you, and you want to keep track of the pushes you do to your production environment. By default, Jenkins produces a local tag on the job's workspace named something like this: jenkins-<job-name>-<sequence-number>. However that doesn't tell you much. And that is not pushed to the remote repo.

As a developer, I'd prefer to just look at the list of tags on a repo and know which ones refer to pushes to production, and also know some more information about them without having to check them out and without having to inspect their logs. As you must know, according to Uber-Geek Larry Wall, developers are lazy! And impatient! And full of hubris! And that is a very good thing!

Jul 17

easy way to change the current branch (HEAD) on a remote git repo...

Wed, 07/17/2013 - 10:00 — peter

Just had an interesting problem today where I needed to blast away the remote copy of a git master branch (don't ask!), but I couldn't do that because it was the current branch.

I quick question to a local git guru and the answer was very easy:

git remote set-head <remote> <branch>

Then I was able to delete the rotten origin/master branch, create it again from a good branch, reset it to HEAD and life was good again!

Easy Peasy!