#1480  Archive or set a end date to job secret
Released
bufferUnderrun opened 9 months ago

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

  • we set the gmaps_api job secret and use it ononedev-buildspec.
  • we modify onedev-buildspec multple time
  • all commits during are buildable

from 2023-07-01 to ....

  • we rename the secret gmaps_api to a better pattern api_gmaps_certificate
  • we update the corresponding onedev-buildspec
  • BUT in order to keep previous commit buildable before 2023-07-01, we need to keep the old job secret gmaps_api

So 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

OneDev changed state to 'Closed' 9 months ago
Previous Value Current Value
Open
Closed
OneDev commented 9 months ago

State changed as code fixing the issue is committed (f97b1746)

OneDev changed state to 'Released' 9 months ago
Previous Value Current Value
Closed
Released
OneDev commented 9 months ago

State changed as build #3946 is successful

issue 1 of 1
Type
Improvement
Priority
Minor
Assignee
Labels
No labels
Issue Votes (0)
Watchers (3)
Reference
onedev/server#1480
Please wait...
Page is in error, reload to recover