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 Azure task. Add two parameters to a job and use them, then build a VM that configures itself at first boot. The tasks come from the KodeKloud Engineer platform.

Task 1: Two build parameters

The task: a job named parameterised-job , with a String parameter Stage defaulting to Build , and a Choice parameter env offering Development , Staging and Production . Then a shell step that uses them.

Step 1: Add them, and notice the documentation gap

Both go under This project is parameterised. That part is a form.

What is missing is any documentation of it.…