The IAC team has been working on a lot of interesting things over the past week. Here’s a brief overview of what we’ve been up to:
Read Puppet’s blog: COVID-19 for the official statement. Puppet provided remote working for all employees to support COVID-19. This precautionary measure has been taken in order to keep everyone healthy and limit the spread of the virus.
The company supports employees by giving them all the essentials to work remotely and it also appreciates the fact that remote working requires everyone to adjust their working styles. It may not be smooth for everyone, but the company is doing its best to support all the employees during this challenging time.
So far, everyone is well equipped to work remotely to their best.
Updates to Puppet Modules
Over the last week we have released:
Facter 4 Testing
The Ghost team tested our modules with Facter 4 using pdksync. Except for the Apache module, all modules passed Facter 4 testing. (apache failed because of a custom fact in https://github.com/gentoo/puppet-portage.git). Thanks alot to Florin Dragos, Bogdan Irimie, Oana Tanasoiu, Sebastian Miclea, Gheorghe Popescu, Andrei Filipovici for all the help on module testing and the fixes.
As always we have been working with the brilliant Puppet Community to get their changes in to the modules. A few highlights this week:
- puppetlabs-postgresql#1150: A pleasure working with olifre to get this fix he authored over the line. Kudos on the first RSpec test!
- puppetlabs-docker#586: Many thanks to fe80 for this fix!
- puppetlabs-inifile#387: alexjfisher continues his never ending streak of great contributions!
- puppetlabs-chocolatey#206 is a WIP PR put up by nmaludy doing the hard and valuable work of adding Bolt tasks to the Chocolatey module!
There’s been plenty keeping us busy in our CI infrastructure this week:
- the Puppet repositories removed unencrypted HTTP access before all tooling upgrades were in place, breaking puppet 5 agent installs in our pipelines.
It was a good lesson how with so many products spanning so many repositories, even with the best foresight from all parties, there can be unforeseen knock on effects from a code change. When we discovered the root cause of the issues preventing the Puppet 5 agent installing on some older Linux systems, the Agent team were quick off the mark to address our issues. We’d like to thank the Agent team for their responsiveness in addressing issues that were causing CI test run failures. Thanks ciprianbadescu, lucywyman, beechtom](https://github.com/beechtom), underscorgan, e-gris, GabrielNagy and sarameisburger! This has been an interesting issue.
- the NTP module started failing in travis: puppetlabs-ntp#566. DavidS and carabasdaniel worked on IAC-615 and tried to analyse it, but the only thing that helped was bumping the build runner to bionic. Curiosity will likely get the better of us and we’ll want to know why these failures occurred on xenial. Check out the ticket if you’re interested or have any ideas.
Over the past week we have closed out an issue on the puppetlabs-stdlib module. As a result of this ticket we have decided to remove strftime from stdlib as it has already been deprecated and superseded by a function within the Puppet agent.
Community Reports Tool
Community reports tool is enhanced with an additional feature to report the PRs from tools maintained by the IAC team. See the Tools Report.
We are continously improving the Triage process - one change made recently has proven to be very beneficial. At the end of our rotation, we will hand off to our colleagues who are next up on Triage. Historically, this was done using a JIRA ticket, but now we have a living document on Confluence.
We’re also keeping more tightly in sync over video calls - historically, if you were parterned with someone in a different timezone, this was normal - now it’s the case for all of us, whether you’re 5 or 5000 miles apart.