Skip to content

Automation improvements #2123

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
crummel opened this issue Apr 15, 2021 · 5 comments
Closed

Automation improvements #2123

crummel opened this issue Apr 15, 2021 · 5 comments
Labels
area-infra Source-build infrastructure and reporting Epic Groups multiple user stories. Can be grouped under a theme.

Comments

@crummel
Copy link
Contributor

crummel commented Apr 15, 2021

Situation

There are currently many manual steps in and around our build and release process for servicing. These cause problems because they can be easily forgotten, they may not be done consistently between servicing events, and they make servicing take longer.

Objective

Improve servicing ease and turn-around times by automating work that is currently done manually. Prioritize work that is easier to automate and takes the most effort manually.

Execution

Identify opportunities for automating manual servicing work, estimate and prioritize them. All these improvements should be small and independent so improvements can be made gradually whenever we have time. Ideally we will make at least one improvement per servicing cycle that we can then try out in that cycle.

@ghost ghost added the untriaged label Apr 15, 2021
@ghost
Copy link

ghost commented Apr 15, 2021

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

@crummel crummel added Epic Groups multiple user stories. Can be grouped under a theme. area-infra Source-build infrastructure and reporting labels Apr 15, 2021
@MichaelSimons
Copy link
Member

[Triage] It would be beneficial to identify which issues would still exist with ArPow. Additionally we would like to identify phases w/the idea being the top phase would be the items we would like to tackle first. Once the phases are identified, they should be reviewed by the triage team.

@MichaelSimons
Copy link
Member

[Triage] The decision is that we will commit to fixing one issue per servicing cycle. @crummel, please add to project board and assign milestones.

@MichaelSimons
Copy link
Member

[Triage] This is superseded by #3065

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-infra Source-build infrastructure and reporting Epic Groups multiple user stories. Can be grouped under a theme.
Projects
None yet
Development

No branches or pull requests

2 participants