Finally got a Jenkins server installed. Had a host of system issues, like communicating to our source code repo.
Jenkins is a joy to use. Well, it is not perfect, what is? Like, I need to pass the user’s name that invoked a build via Jenkins to the target DOS script (yea, Windows) that eventually invokes the legacy Ant scripts. A quick Google search shows that this is asked in various ways, but no answers. For example, here or here. Hmmmm.
Anyway, now comes a trial use, to see if it is what we really need and can we manage it to do what we will want. With 400 plugins, I don’t see how it could lack. Plus, I’m sure I can use the Groovy plugin to cobble something up. Jenkins even includes a Groovy Console. Finally, there is a road map for possible migration of legacy Ant scripts to Gradle using the Gradle Plugin.
I take back my past snarky comment. Jenkins is not just a pretty face on Cron.
Was watching the Easyb intro video. BDD is interesting. Definitely “should” is a better then “test”. With so many great tools why are products still bug ridden?
Enterprise Level CI Server?
I was told that QuickBuild is better for corporate use.
Wikis and the home link
BTW, is there some Wiki law that says a wiki shall never ever have a link to the parent project? If you get tossed into a wiki by following a link, invariably you will click in agony at links that should go to the real home. Instead, you have to edit the URL in the address bar. Since I never curse, I can’t write “wtf”.
- Jenkins home page
- Continuous integration Not a very good Wikipedia article
- Continuous Integration Much better
- Continuous Integration in Agile Software Development
- Hooking into the Jenkins(Hudson) API
- Five Cool Things You Can Do With Groovy Scripts
- Parameterized Builds in Jenkins – choosing subversion folders
- Groovy Console
- Groovy plugin
- Switching to Jenkins–Download and Install Artifact Script for Tester
- Gradle Plugin