Skip to content

Custom sleep, pools, agents and Windows template#13

Open
BlWasp wants to merge 1 commit intosynacktiv:mainfrom
BlWasp:DevOps_Improvements
Open

Custom sleep, pools, agents and Windows template#13
BlWasp wants to merge 1 commit intosynacktiv:mainfrom
BlWasp:DevOps_Improvements

Conversation

@BlWasp
Copy link
Copy Markdown

@BlWasp BlWasp commented Mar 13, 2026

Hello all!

I recently found myself on an pentest that included Azure DevOps, and I used nord-stream to perform all the extracts I needed.
This PR makes a few improvements that I had to add during testing to adapt to the environment:

--sleep: allows you to specify a custom value for the wait time to retrieve the pipeline output. This is useful in “busy” DevOps environments, where other developers run a lot of pipelines in parallel, causing queues
--pool-name: allows you to specify a custom agent pool in case the default “Azure Pipeline” pool is no longer present. This value will be set as the pool name in the pipeline YAML file
--default-agent: allows you to specify a default agent pool for deployment. This is not necessarily the same pool as the one specified in the YAML. In the web GUI, this can be found in the pipeline editor -> Triggers -> YAML. The pipelines API does not allow you to specify this value at creation; you must go through the definitions API and specify a “queue” that can be found via the distributedtask/queues API.
--os: useful in cases where all available agents are running Windows. Not only does this require running a PowerShell script instead of Bash, but it also turns out that in Windows, passing variables from a variable group via the env does not work well at all. So I had to trick it by passing the variables directly into the script.

I only had Azure DevOps available to perform my tests and modifications. However, I imagine that these types of options could be ported to other CI/CD environments.

@hugo-syn
Copy link
Copy Markdown
Collaborator

Hello, thank you so much for this PR, I'll try to test it when I have some time :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants