lordran opened 4 months ago
Hi, I'm facing something unexpected, ask for some help.
1、I'm building on master branch, and setting "Post Build Actions":
why dose the Deploy (test) job can be executed? and why dose job secret(KUBECONFIG-test) can be used?
2、can we provide a way to hide some jobs in here:
OneDev version: 9.2.4
For your case, I guess head of master can also be reached from test branch.
I filed an improvement request #1635 to match build ref directly.
As to hide particular jobs from run menu, you may create necessary role without permission to run those jobs, and login as user with that role for your daily work.
@robin Thanks for your reply.
Then, what should I do if I want to only click Build job, and execute a branch-based job? Due to the above question, now we have to click Deploy (prod) on master branch, click Deploy (test) on test branch.Yes, both jobs have a job dependency to Build job.
And we maybe also use a Build Promotion, but in Builds section, the deployment process involves too many steps: choose a param named branch > choose a job to click.
Do you have suggestions about my case?
You may create only one deployment job, and configure it to behave differently based on value of variable
Robin Shen changed state to 'Closed' 4 months ago
If so, I have to delete job secret Authorization, this is unacceptable for security.If I don't delete job secret Authorization and write a shell as follows:
this will lead to an error when running on test branch:
You may refer to #682 for a workaround.
To make such task easier, future version will improve job secrets so that multiple secrets with same name can be defined, and secret access will be tried one by one until an authorized secret can be found.
build #4343 (9.3.0) is required to use this feature