• Type: Epic
• Resolution: Won't Do
• Priority: Critical
• Component/s: evergreen
• Labels:

  None

[JENKINS-54264] Automatically file PRs for repetitive tasks

Baptiste Mathus created issue - 2018-10-26 08:54

Baptiste Mathus made changes - 2018-10-26 08:54

Assignee

Original: R. Tyler Croy [ rtyler ]

New: Baptiste Mathus [ batmat ]

Baptiste Mathus made changes - 2018-10-26 08:55

Description

Original: h3. Problem statement There are a few repetitve tasks for the project that we have been handling manually until now that should be automated. They share the common feature that they end up being a PR on the Evergreen source repo itself or another. Running plugins or core upgrades, or npm packages security bumps, or bumping h3. Expected behavior These tasks should be automated. We should write a common tool that makes it easy to file a PR against a given repo with a set of change that a script or so has created.

New: h3. Problem statement There are a few repetitve tasks for the project that we have been handling manually until now that should be automated. They share the common feature that they end up being a PR on the Evergreen source repo itself or another. Examples: * running core or plugins upgrades * updating the backend to latest * updating npm packages * running {{npm audit fix}} to fix vulnerabilities * ... h3. Expected behavior These tasks should be automated. We should write a common tool that makes it easy to file a PR against a given repo with a set of change that a script or so has created.

Baptiste Mathus made changes - 2018-10-26 09:00

Description

Original: h3. Problem statement There are a few repetitve tasks for the project that we have been handling manually until now that should be automated. They share the common feature that they end up being a PR on the Evergreen source repo itself or another. Examples: * running core or plugins upgrades * updating the backend to latest * updating npm packages * running {{npm audit fix}} to fix vulnerabilities * ... h3. Expected behavior These tasks should be automated. We should write a common tool that makes it easy to file a PR against a given repo with a set of change that a script or so has created.

New: h3. Problem statement There are a few repetitive tasks for the project that we have been handling manually until now that should be automated. They share the common feature that they end up being a PR on the Evergreen source repo itself or another. Examples: * running core or plugins upgrades ([PR-330|https://github.com/jenkins-infra/evergreen/pull/330], [PR-327|https://github.com/jenkins-infra/evergreen/pull/327], [PR-326|https://github.com/jenkins-infra/evergreen/pull/326], [PR-318|https://github.com/jenkins-infra/evergreen/pull/318], ...) * updating the backend to latest (example: https://github.com/jenkins-infra/jenkins-infra/pull/1174) * updating all npm packages ([PR-323|https://github.com/jenkins-infra/evergreen/pull/323]) * running {{npm audit fix}} to fix vulnerabilities ([PR-329|https://github.com/jenkins-infra/evergreen/pull/329]) * ... h3. Expected behavior These tasks should be automated. We should write a common tool that makes it easy to file a PR against a given repo with a set of change that a script or so has created.

Mark Waite made changes - 2022-09-11 03:39

Resolution		New: Won't Do [ 10001 ]
Status	Original: Open [ 1 ]	New: Closed [ 6 ]