Skip to content
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

[Darc] Create process for auto-updating common scripts/tools #60

Closed
weshaggard opened this issue Mar 14, 2018 · 1 comment
Closed

[Darc] Create process for auto-updating common scripts/tools #60

weshaggard opened this issue Mar 14, 2018 · 1 comment
Assignees

Comments

@weshaggard
Copy link
Member

weshaggard commented Mar 14, 2018

No matter what tools/infra we currently use there is always a need for some boiler-plate scripts, config files, etc that need to be maintained across many repos. Today that is mostly manual and is a very tedious process to ensure everything is in-sync and consistent. We need some process, perhaps maestro, that will monitor changes to common files and then submit auto-PRs to all repo's that subscribe to the engineering system.

We have issue dotnet/buildtools#1709 tracking a similar feature but I think this is going to be key for getting people to arcade and keeping them updated so I've filed the issue here.

Some general requirements:

  1. Any auto-updated files should be blindly updated by this tool and never have any customizations from the individual repos. If customizations are needed then it should be handled by an extension point where repo owners can plug into from a separate file.
  2. These files should be in well known locations in each repo so the updating is just a simple overwrite.
  3. We may need the flexibility in the system to move files if we decide we need to rename or move a file for some reason.
@jcagme jcagme self-assigned this Apr 17, 2018
@jcagme jcagme changed the title Create process for auto-updating common scripts/tools [Darc] Create process for auto-updating common scripts/tools Jul 12, 2018
@jcagme
Copy link
Contributor

jcagme commented Jul 30, 2018

Included in #296

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants