-
OneDev
changed state to 'Closed' 2 years ago
Previous Value Current Value Open
Closed
-
State changed as code fixing the issue is committed (f97b1746)
-
OneDev
changed state to 'Released' 2 years ago
Previous Value Current Value Closed
Released
-
State changed as build #3946 is successful
| Type |
Improvement
|
| Priority |
Minor
|
| Assignee | |
| Labels |
No labels
|
Issue Votes (0)
Hi,
We set job secret and use it in the onedev-buildspec. If the later is tracked by git and allow previous commit to run job, we need to maintains the associated job secret which is a pain.
Examples
from 2023-01-01 to 2023-06-30
gmaps_apijob secret and use it ononedev-buildspec.onedev-buildspecmultple timefrom 2023-07-01 to ....
gmaps_apito a better patternapi_gmaps_certificateonedev-buildspecgmaps_apiSo with time, it's a little mess to maintain job secret when there were multiple renames.
Could you add something to filter current/old job secret (with a end date, old flag or other workaround).
Thanks