Robin Shen
opened 2 years ago
No description
-
Previous Value Current Value Mask job secret value
Mask job secret value while editing
-
OneDev
changed state to 'Closed' 2 years ago
Previous Value Current Value Open
Closed
-
State changed as code fixing the issue is committed (8cb9dfd1)
-
OneDev
changed state to 'Released' 2 years ago
Previous Value Current Value Closed
Released
-
State changed as build #4795 is successful
-
Previous Value Current Value Released
Open
-
Hi Robin,
Why this setting has changed again ?? Maybe turn on/off three time in 4 years.
Hiding job secret value make the debugging of job harder as we don't know if the value is correct or up to date.
?
-
Showing secret value is considered risky. Finally I decide to go with the GitHub style of hiding the value.
-
Previous Value Current Value Open
Closed
-
@robin Maybe could it be an administrator option to show/hide job secret value (with default value to hide to keep fresh install as secure as you want) ?
-
is there a way to show job secret in build? it is a lot harder to debug when working with job secrets.
-
Please check this OD-1949
| Type |
Improvement
|
| Priority |
Normal
|
| Assignee | |
| Labels |
No labels
|
Issue Votes (0)
Watchers (3)
