-
Task
-
Resolution: Won't Do
-
Minor
-
None
Problem statement
Currently, updating the backend is done manually through this kind of PR
https://github.com/jenkins-infra/jenkins-infra/pull/1174
Expected
This PR should be filed automatically when a new backend is available (i.e. new image tag available at https://hub.docker.com/r/jenkinsciinfra/evergreen-backend/).
Bonus point: maybe this PR should be created automatically only when there're changes in the services directory of evergreen (excluding on essentials.yaml and a few other files possibly).
[JENKINS-54174] Automate backend update PR
Assignee | Original: R. Tyler Croy [ rtyler ] |
Labels | New: newbie-friendly |
Description |
Original:
h3. Problem statement Currently, updating the backend is done manually through this kind of PR https://github.com/jenkins-infra/jenkins-infra/pull/1174 h3. Expected This PR should be filed automatically when a new backend is available. Bonus point: maybe this PR should be created automatically only when there're changes in the services directory of evergreen (excluding on {{essentials.yaml}} and a few other files possibly). |
New:
h3. Problem statement Currently, updating the backend is done manually through this kind of PR https://github.com/jenkins-infra/jenkins-infra/pull/1174 h3. Expected This PR should be filed automatically when a new backend is available (i.e. new image tag available at https://hub.docker.com/r/jenkinsciinfra/evergreen-backend/). Bonus point: maybe this PR should be created automatically only when there're changes in the services directory of evergreen (excluding on {{essentials.yaml}} and a few other files possibly). |
Labels | Original: newbie-friendly |
Resolution | New: Won't Do [ 10001 ] | |
Status | Original: Open [ 1 ] | New: Closed [ 6 ] |