I told myself I would do a whole lot more writing than I’ve been doing. I’ve even got ideas of things I would like to write on! Honest. Anyway, between Christmas, kids and a project (that’s related to this blog!) that I’ve been working on, I haven’t had a lot of time to sit down and focus.
So to my whopping 0 subscribers, just you wait! There will be content. Oh yes. There will be content.
I’m not typically one to outright throw my beliefs in the faces of others just to be noticed, and that isn’t the intent here either. For those of you who haven’t heard or don’t know, Canada has a parliamentary form of government which you can kind of boil down to the fact that it’s possible for someone to run the government, but without a clear majority. This week in Canada, the left wing parties have decided to try and form a Coalition Government to overthrow the Conservatives.
As well, some of you may notice the reference in my blog to The Dead Milkmen a humorous punk band from the 80′s and 90′s.
Well a friend of mine and I have taken this opportunity to show not only a tribute to the Milkmen, but also to make light of the situation in the country. So here, for all posterity I give unto you my version of Beach Party Vietnam:
Bloc Party Quebecois
Duceppe and Bouchard with Michaëlle Jean
When Duceppe got a letter from Mr. Dion
Said get Layton and everyone
We’re gonna start a co-ali-tion.
With the Bloc Party Quebecois
Parle anglais? Je ne c’est pas!
Seperatists eating foie gras
It’s a Bloc Party Quebecois!
Hey Duceppe! Aren’t you gonna try and be PM?
I’m afraid I can’t do that Bouchard.
Why not?
Because I don’t have any support in english Canada!!!
(AAAAAAAAAAAAAAAAHHHHHHHHHHH!)
Bloc Party Quebecois
Parle anglais? Je ne c’est pas!
Seperatists eating foie gras
It’s a Bloc Party Quebecois!
Duceppe he wants Harpers head
Harper wants the Bloc dead.
Hangin on the east side
Gonna be some party genocide
It’s a Bloc Party Quebecois
Parle anglais? Je ne c’est pas!
Seperatists eating foie gras
It’s a Bloc Party Quebecois!
YEAH!!!
Today I was suddenly reminded of a question I saw somewhere a couple weeks back. I wasn’t going to admit it at first, but it was on Stack Overflow. I actually went looking for the question, but can’t seem to find it, so here’s my version of the story from memory.
The question basically said that after every commit to a code base, it would trigger a build on their build server. The build generated a file (I think it was called revision.txt) that was tagged with the current revision number, and then checked back into source control, which would then trigger a build, which would generate a file……. and so on.
I was so focused on the fact that they would be generating something that could be retrieved at any point in time from the repository that I failed to see the value of what was really being asked. I the fact that you would create a file with a revision number, and check it into the repository, effectively nullifying that revision number was so consuming for me that I didn’t stop to think that it might actually be helpful to not build on every commit.
Then this morning I was working on some test documentation for a deployment that we’re doing soon. As I made changes and checked them into the repository, I kept triggering builds. Then it hit me. I realized that there’s really no reason why a test doc that has nothing to do with a the build. I mean, in this case, the build doesn’t take long, but we have some pretty big projects here that can really hit our build server hard (which causes emails to be sent out to our server admins).
It didn’t take me long to find the Filtered Source Control Block and update our configuration to use it.
But it got me thinking. Though I don’t fully agree with the process being described in the original question, I was so focused on what was wrong that I completely missed out on learning about what was actually a valid, useful and soon-to-be relevant feature in my build server.