Skip to content
New issue

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

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

Already on GitHub? # to your account

Add initial content #1

Merged
merged 1 commit into from
Aug 31, 2022
Merged

Conversation

makubacki
Copy link
Member

This adds starting content for the Mu Developer Operations (DevOps)
repo.

This repo (at least at this time) is primarily composed of Azure
Pipelines YAML files used as common resources between many Project
Mu repositories.

Repos are intended to bind against a source repository at pipeline
build time to expose the templates used for the build.
https://docs.microsoft.com/en-us/azure/devops/pipelines/process/resources?view=azure-devops&tabs=schema#define-a-repositories-resource

Each "leaf" YAML file (the YAML file used in the actual pipeline) is
expected to define a repository resource onto this repo and include
the appropriate top-level template file.

Typically, this is:

  • Jobs/PrGate.yml
  • Steps/BuildPlatform.yml

Each template provides parameter customization for common config
points of steps implemented in the template.

This change is considered an initial refactoring and convergence of
build functionality with the goal to replicate pipeline behavior
using these templates in this converged repo. It will be iterated
and impoved upon in future changes.

Signed-off-by: Michael Kubacki michael.kubacki@microsoft.com

This adds starting content for the Mu Developer Operations (DevOps)
repo.

This repo (at least at this time) is primarily composed of Azure
Pipelines YAML files used as common resources between many Project
Mu repositories.

Repos are intended to bind against a source repository at pipeline
build time to expose the templates used for the build.
https://docs.microsoft.com/en-us/azure/devops/pipelines/process/resources?view=azure-devops&tabs=schema#define-a-repositories-resource

Each "leaf" YAML file (the YAML file used in the actual pipeline) is
expected to define a repository resource onto this repo and include
the appropriate top-level template file.

Typically, this is:
  - Jobs/PrGate.yml
  - Steps/BuildPlatform.yml

Each template provides parameter customization for common config
points of steps implemented in the template.

This change is considered an initial refactoring and convergence of
build functionality with the goal to replicate pipeline behavior
using these templates in this converged repo. It will be iterated
and impoved upon in future changes.

Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
@makubacki
Copy link
Member Author

Mu repos using this repo: Pipelines - Mu DevOps CI Testing

@makubacki makubacki merged commit 5d8748f into microsoft:main Aug 31, 2022
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants