search

dmitryserbin / azdev-release-orchestrator

Azure DevOps extension to manage and orchestrate release pipelines
MIT License
23 stars 13 forks source link

Creating Release with Specific Source Version or Build Number #67

Open benwalpole opened 2 years ago

benwalpole commented 2 years ago

Hi,

I've managed to get the extension to trigger a release against a specific branch but I want to be able to specify a specific build of that branch. I've tried using the Build Number of the build I want and the Source Version (i.e. Git commit hash) but I always get the message that no builds matching the filter can be found.

Is it possible to do this? I could just be using the wrong YAML parameters.

dmitryserbin commented 2 years ago

Hi, you may need to specify both parameters, then both filter will apply:

artifactVersion: YOUR_BUIL_NUMBER (i.e. 20220302.1) artifactBranch: refs/heads/your_branch

I'm also pretty sure if you just specify build number without specifying branch filter - it will work just fine too as the build number is unique.

My guess it didn't work because use specify commit id instead of the build number.

Hope this helps!

benwalpole commented 2 years ago

Unfortunately I've tried adding both and just setting the Artifact Version to the Build Number but I get the same error in both cases.

Are you able to share any info on how the AzureDevOps API is being queried to implement the filtering?

dmitryserbin commented 2 years ago

Could you please run it with debug mode on and share the logs?

benwalpole commented 2 years ago

Yeah sure, I don't fully understand the documentation for debug mode, do i just need to set System.Debug=true on the pipeline?

dmitryserbin commented 2 years ago

Either add System.Debug=true or Debug=release-orchestrator:* variable

radulaurentiu02 commented 11 months ago

hello, are there any updates on this topic? I think I am facing the same issue. Thanks!