Day 79 of DevOps, Day 29 of Azure. Both tasks today turned out to run somewhere other than where the configuration implied.

A Jenkins job set up to build on an agent polls the repository from the controller, which is the machine the last four days have been about getting work off. And a container image meant to be built by the registry got built on the lab host instead, because the permission for the server-side build was missing.

One Jenkins task, one Azure task. Make a job trigger itself on a commit, then create a container registry and push an image to it. The tasks come from the KodeKloud Engineer platform.

Task 1: A job that triggers itself

The task: a job named datacenter-app-deployment , running on the stapp01 agent, triggered when a commit lands on master , updating /var/www/html .

Step 1: Check the ownership first

Check that /var/www/html is owned by sarah before relying on it.

Small step, worth naming, because this batch answers one question three different ways.…