My colleague Andrey Falko recently published a post on the Salesforce engineering blog about a tool
we built and open sourced called Dockerfile Image Update. It’s a pretty nice way of pushing pull requests to
child Docker images when a parent image has changed while avoiding using the
latest tag by plugging it into your
CI/CD flow. Check it out!
Today I ran across a case where we were trying to programmatically set the threshold for when Jenkins will automatically turn off a Jenkins agent (found under https://$YOUR_JENKINS_HOST/computer/configure). The default is 1GB and we’d like to bump that up a bit. We’re periodically wiping out any nodes that are offline (as well as the resources behind that node) so doing this will clean them out sooner.
I got an e-mail today from Amazon informing me that they have released the AWS Certificate Manager and that they would make it easy to get certificates added to your AWS resources. And, best of all, it is free.
As I mentioned in my Hello Jekyll! post, I’m administering this site with Jekyll. I’ve got all of my code in GitHub and am using Travis CI for continuous integration / continuous delivery of the site. That’s been working quite well thus far, though I’d like to add more testing utilities.
I’ve been working a little more on my Raspberry Pi Temperature Monitor and wanted to check out how to do some Test-driven Development. So, I started by looking into how I might write some tests and structure my code so I looked at the Python unittest documents and class documents. I also ran into this guide which was quite informative. I think it turned out alright (though I’m sure things may have evolved since 2009, when the guide was written. Like anything else, the code can be refactored and improved incrementally.