2.150.1

Code execution through crafted URLsJenkins uses the Stapler web framework for HTTP request handling. Stapler’s basic premise is that it uses reflective access to code elements matching its naming conventions. For example, any public method whose name starts with get, and that has a String, int, long, or no argument can be invoked this way on objects that are reachable through these means. As these naming conventions closely match common code patterns in Java, accessing crafted URLs could invoke methods never intended to be invoked this way.

CI/CD

Since October last year I try to understand Travis CI and have over 70 builds already, but I still don't get it. I don't know if it is Travis CI (random failures, no DB socket available, etc.), PHPUnit, HHVM (extremely slow running unit tests). Just tired.

Last week I had to work with Jenkins' Pipelines for a work project. It also took me 2 full days and 60 replays to learn and understand, but it is really amazing! I have a complete workflow with building, testing, feedback to Gerrit, publishing of reports, ordinary artifacts archiving, deployment to QA, eMail notifications and manual approval to deploy to production. There are also some bugs, no question, especially I am missing Gerrit trigger for multi-branch Pipelines, so I can test pull requests already, but it makes so much more fun to work with.

Tear down docker test containers based on image name

Given your #CI generates #Docker images from your Git commits and tags them with something like web01-qa:$BUILD_NUMBER. Right now I can not set a name for the container that gets spun up after every commit, so I needed a solution to tear down the old containers after successful start of a new container based on the image they were created from. This is what I came up with: