Archive
Git-Flow – Updates – Ideas
As some of you that follow me may have seen, I’ve been quiet in the last week. This is/was for good reason. I’ve been a bit busy doing quite a number of things including writing more articles, some of which are more around the grey areas in development like Architecture, Methodologies of Development, Design Practices and so on. I’ve also been busy trying to get my Code Project articles completed, which I’m hoping to publish very soon. It’s been a bit strange putting these together and even though I’m going to take a while to publish all of them, they did get me to read a lot about various things and they also got me thinking about things that I’ve always done and re-evaluating those principles that I have and that most of us developers like to talk about.
So, hopefully I’ll get those done and hopefully they will get people talking a bit and I may even have some of you challenge my thoughts on some of the concepts that I’ll put out there, even though there won’t be too many new things. The idea is to start having the discussions in an open platform where everyone is on the same foot and all the different paths can be explored in an honest manner. Anyway, I’m not going to go too much into it right now… 🙂 Just know that it will be coming in the next month or so and it should be interesting to hear what some of you say…
In the meanwhile I’ve just finished my article on Git-Flow called “Getting Started – Git-Flow” and I hope you’ll enjoy it. Git-Flow is a very interesting concept that builds on the powers that Git gives you, even though it can be implemented on just about any and every other Version Control System there is. So, if you were looking for a good Branching Strategy or a good process to implement for when your company/team is doing development, try it and give me some feedback to say where I can help you adopt it or where my explanations are lacking a bit.
In the meanwhile, I’m going to continue writing those other articles which will hopefully take me a bit more into the code and a bit less into the environmental things that makes our lives easier by giving business the visibility they need.
Have fun!!!! 🙂
Setup – Jenkins and RVM
I’ve just completed another article related to Environments called “Setup – Jenkins and RVM“. In this article I take you through the setup process to get Jenkins and Ruby Version Manager (RVM) to play nice with each other. I start with the Build Server and RVM setup and then take you through to pulling your first GitHub hosted Ruby code, doing a Bundle Install and finally running a rake for your Unit Tests. I hope this will help someone out there, seeing that I have struggled to understand why things on Jenkins don’t work or why my Jenkins install doesn’t pick up that I have RVM running with the correct Rubies. It was fun and it seems to be working. So, enjoy!!! 🙂
Setup – Apache and Jenkins
So, there is now something called Jenkins in the world of Open Source Build Servers and it seems like it’s been around for a few months. Why is this remarkable? Well… Simply because Jenkins = Hudson. I was installing another server with Hudson today following the instructions in my article “Setup – Apache and Hudson” and only when I completed the install did I realise that Hudson is now actually called Jenkins. So, has anything changed? Nope, not really. Why did they decide to make this bold move? I can’t say, other than that there is some speculation that the guys over at Oracle wanted to start charging license fees for the use of Hudson and that the previously known Hudson guys then decided to for Hudson, rename it to Jenkins and to continue with the project in the old Open Source manner. Well, if this is true, then I am glad, because since I started using Hudson/Jenkins I haven’t looked back or had the urge to explore some of the other platforms out there. It simply works 🙂
To top it off, I obviously opted to uninstall Hudson and to install Jenkins and once that was done I thought that it might be a good idea to add/update another article to show you how to install the new Jenkins platform. You can find this article, called “Setup – Apache and Jenkins” here. I’m sure you’ll enjoy Jenkins as much as you’ve enjoyed Hudson and I’m also sure that we can expect to see this project grow in the coming months as we’ve seen it grow from the beginning. I wish them all the luck in their bold move and hope they continue to have fun 🙂 I know we will 🙂
Heads up though, I’m in the process of writing an article on how to use Jenkins as your Build Server runnig Continuous Integration for Ruby projects under Ruby Version Manager (RVM).
Related Articles
- Hudson becomes Jenkins (i-programmer.info)
- Hudson is dead, long live Jenkins (nighthacks.com)
- Hudson moves to Github (h-online.com)
GitHub – Getting Started
Even though I’ve been away from this site for a while (bad, really bad) I am coming back to it with some ideas and hope to continue the fun. So, for my come back, I’ve just published a “Getting Started” article under the Environments menu for getting into GitHub and I’ve also added a “Source Repository” menu item under the “About” menu that should take you to a place where I’ll hopefully be hosting some of the source of those articles that I’ve been promising for so long. I did some research on the various online repository hosting companies and must say that the solution that GitHub gives you is very comprehensive. So, I chose them as part of my “Ultimate Environments” range of tools I would recommend and that I will be using myself. Take into consideration that the entire range is still under construction and I will be refining, changing and adding more information as I continue. So, none of the articles on this site will at any stage be seen as complete, just like the code we write on a daily basis. In the real world, we only stop coding on a project when we start with a new one and if we start with a new one, we all know that we did the previous one wrong. I hope you like it and find it helpful and I look forward for any feedback and changes you may like.