A Smattering of Selenium #60
This instalment of catch-up week is brought to you by the letters C and I.
Categories:
This instalment of catch-up week is brought to you by the letters C and I.
- The pre-scm-buildstep plugin for jenkins adds a useful step into the job workflow.
- Understanding your tools is important. Here is an explanation of Jenkings Action and its subtypes
- You think your CI setup is impressive? Check out the Apache Foundation’s Jenkins server
- The easiest way to get CI going is with the ubiquitious but completely unoffically Ant JUnit XML format. Publishing Python unit test results in Jenkins discusses a python package a bit for it.
- To me, using a headless browser like HTMLUnit makes very little sense. Now, a headful browser on a headless machine — that makes sense. Setting up Jenkins CI to run selenium tests and record video in three easy steps explains how to do this in Ruby.
- Travis CI – Selenium setup shows the similar thing minus the recording of a video for the Travis CI environment.
- So far it seems that one should just subscribe to the Multunus blog and be done with it. Or at least the continuous delivery category.
- Think your web app deployment is ‘hard’? Continuous Delivery: How do we deliver in 3 clicks to 7000 machines? discusses a .NET client application. Now go count your blessings and get that remote svn export scripted.
- Won’t somebody please think of the systems? looks at CI with a bit of an ITIL lens
- Distributed Check-in Tokens: Pass-The-Puppy presents a quick technical solution for not breaking the build through tokens. You could of course talk to each other but there are sometimes time zones conspiring against you.
