Day 72: A Parameter and a Boot Script
Day 72 of DevOps, Day 22 of Azure. Both tasks today were about a value crossing from outside into something that runs it, and what happens at the boundary. A Jenkins parameter crosses into a shell script. A boot script crosses into a brand new VM. In both cases, the interesting part is not the value, it is the handoff, and yesterday's bug turns out to explain today's safety. One Jenkins task, one…
Day 72 of DevOps marked a focus on the handoff between Jenkins and Azure, and the lessons learned from a previous bug. Two tasks were completed using the KodeKloud Engineer platform.
First, two build parameters were added to a Jenkins job named parameterised-job. The job had a String parameter named Stage with a default value of Build, and a Choice parameter env with options Development, Staging, and Production. A shell step was used to leverage these parameters. The documentation gap for choice parameters and freestyle projects was noted, as Jenkins only documents parameter as a member of the params variable.
Second, a boot script was used to configure a brand new VM named nautilus-vm. The script installed and started nginx on first boot, making the VM reachable on port 80. The script passed disk flags and corrected a mistake from Day 21, explaining the default storage SKU and size. The same default error from Day 21 prevented the VM from being repeated, but the explanation was corrected.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
