◆ Microsoft Azure

Change current working directory in Azure Pipelines

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskIn the 'BuildAndDeploy' Pipeline, I need to change the current working directory for the…+
In the 'BuildAndDeploy' Pipeline, I need to change the current working directory for the 'RunTests' step to 'src/tests'. Apply this change and save the pipeline.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I finalize the 'BuildAndDeploy' pipeline, make sure the current working directory for…+
Before I finalize the 'BuildAndDeploy' pipeline, make sure the current working directory for the 'RunTests' step is robust. It needs to work correctly if the repository structure changes slightly, or if the pipeline is run from a different agent. Flag any hardcoded paths that could break it.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe 'RunTests' step in the 'BuildAndDeploy' Pipeline is failing, saying it can't find the test…+
The 'RunTests' step in the 'BuildAndDeploy' Azure Pipeline is failing, saying it can't find the test files, even though I've set the working directory.
The 'RunTests' step in the 'BuildAndDeploy' Pipeline is failing, saying it can't find the test files, even though I've explicitly set the working directory to 'src/tests'. I'm not sure if the path is relative to the repository root or the agent's default working directory, and the error message isn't clear. I'm afraid of breaking other steps if I just guess. What's the actual base path for pipeline steps, and what's the safest way to debug this path issue without deploying multiple times?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently encounter build failures in Pipelines due to incorrect working directory settings…+
I frequently encounter build failures in Azure Pipelines due to incorrect working directory settings for various steps.
I frequently encounter build failures in Pipelines due to incorrect working directory settings for various steps. It's a constant source of frustration and wasted pipeline runs. What habit should I change in how I define or test working directories in my pipeline YAML to ensure they are always correct and robust?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Microsoft Azure's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.