|
Unknown opened 1 year ago
|
||||
|
Managing personal secret is cubersome, for instance it is difficult to decide whose secret should be used for auto-triggered / scheduled builds, etc. It complicates things a lot and do not provide too much value to my understanding. |
||||
|
|
OTOH, for manual build, one can input password at time of triggering build, with a job param of secret type. |
||||
|
|
Robin Shen changed state to 'Closed' 1 year ago
|
| Type |
Improvement
|
| Priority |
Critical
|
| Assignee |
Issue Votes (0)
Watchers (3)
In Onedev builds, variables can be used to prevent the leaking of personal access tokens, for example to push to other platforms.
I have searched the wiki but I can not find anyway to make them personal, IE: prevent EVERYONE from being able to see the access token, even other maintainers.
I propose the addition of personal variables, these are only added when the user executed the build, if another user executes the build it should be ignored.