post commit auto deploy

In 4 steps

1. svn commit to the repository
2. the pre-commit hook will check the code with svnlook and will validate the commit message (based on regexp such has bug# …, text minimal size…)
3. the post-commit hook will try to connect to the ITT (Integration Team Testing) if you have the good acronym, I’ll update
4. once connected a script should be launched (and forgot &;) This script should:
   • Do a svn checkout locally so the code could be tested (in /var/www …). This method has several drawback: instability of the site while exporting, destruction of ITT generated file (if any)…
   • Do a svn checkout in a temporary directory (/export/<projectname>) and then use rsync to do a fast compare and copy changes only without deleting the existing, excluding the .svn folders
   • Do a svn export in a temporary directory (/tmp/<projectname>) and then use the same rsync than above but this time you don’t have to exclude the .svn

   The fastest is the second one (svn checkout -> /export/<projectname> + rsync – .svn folders)

Option 2

There is another alternative if you have space and sufficient right on your svn repository: the svn export/svn checkout is done locally and you use rsync to deploy the site on the ITT server.

Option 3

There is a third alternative if you have one more server (a synchro server) that will be used to store the svn export (at least the last one and maybe 2-3 version before) and that will take care of the rsync between one of its local checkout/export and the ITT server.

Conclusion

The last option has the big advantage of being a intermediate repository that can deploy any revision to any server … but that’s another paper.

I used the 3 options, and the first one (the simplest/cheapest) is very easy to maintain and to set up, so it’s a must have for team < 15 … bigger team may think about the other options but will have to put additional resources to design the whole deployment system.

Dr. Wave ready to listen

While muting a wave and moving it to the trash folder :-)

I can’t wait to wave :P

And unfortunately, I will not be retired at that time… I’m pretty sure that it will be like in the 80s with every developer thinking that his code will last only few months (years)… when it will actually last much longer.

Most of the liunuix (linux and unix) systems use timestamp stored as an unisgned integer 32 bit starting Thu, 01 Jan 1970 01:00:00 +0100.

The idea was to be able to measure time for a “long” period of time, from now (in the 70s) and in the past.
So they decided to use half of the 2^32 for the past (prior to 1/1/1970) and the other half for the future.

So be it…

Now we are about 40 years later, and we still use the same representation. We already had a party for the unix timestamp 1234567890 (which is quite stupid because it’s in base 10).

And now javascript, Java, PHP and C … use the unix timestamp… which means ajax, web 2.0, comet … which means: most of the online banking system, internet sites and all the smalls scripts that in few line check your credential and your billing to allow you to connect to the Internet… All the logging system, all the monitoring systems… well everything that you don’t see, just under the internet sea you surf on.

So what will be the next party thema?

• the end of the internet as we knew it
• the end of the unix system
• the 0×80000000 seconds since epoch?

Anyway, because of the ongoing ecological breakdown, the human kind will probably collapse before… so after the Y2K38 bug, the world will just be their kingdom. The kingdom of bugs.

Unless we spend time (which is running) in each of our application to think about that right now (and if we spend just about the same amount of time solving the earth ecology problem it will not be useless).

Cindy Foster – CindyFoster1533@live.com
to quechupxxx@xxx.sbw.be

H! I find your post interesting. I am pretty chick. I am moving to your area from russia
I am looking for a good man to show me around and may be more ;)
Could you please kindly reply to me at jclapptakomapark@gmail.com
I will send you some of my pictures back in reply.
Could you reply to my email account I am supplying in the body of this email as I am writing from my work email which i don’t use for personal correspondence

Windows Live™: Keep your life in sync. Check it out.

–> Don’t use quechup

Au menu:
- échange d’idée
- de point de vue
- bière
- et puis on refait le monde

Lieu: la lunette place de la monnaie à Bruxelles.

Timestamp: 1216400400 (to convert go to http://code.sbw.be/php/timestamp.php and feel free to use any http://code.sbw.be/ scripts)

Facebook: http://www.facebook.com/event.php?eid=25240684187