-
New Feature
-
Resolution: Unresolved
-
Major
-
None
Use Case:
I have a multi-branch pipeline
Root : mxnet-validation
Jobs : unix-cpu, unix-gpu, windows-cpu, windows-cpu etc
I want to trigger a branch scan for a specific job. Right now I have configured same token for all 8 jobs. This causes all 8 jobs to have a branch scan.
Current work-around
I have to manually set different tokens for different jobs to be able to trigger Scan on each of them separately. This is a bit of a hassle.
New Feature:
New feature would have a parameter : to pass the job along with token so as to trigger branch scan specifically for that job (and not all jobs with the same token)
Hi igalg
Yes currently plugin scans for all the branches for changes and triggers only changed branch. So can we only scan the changed branch and trigger only that?
So that we can avoid unnecessary system resource utilization by not scanning all other branches.
Let me know if there is any workaround for this, if the feature is not yet available.
Thanks in advance!