Updated pipelines to only run CI and PR gates on release/202208 and r… #131
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
os-d
approved these changes
Oct 19, 2022
makubacki
added a commit
to makubacki/mu_basecore
that referenced
this pull request
Oct 21, 2022
…08 and release/202202 (microsoft#131)" Reverts commit 4bbdb46 to reduce conflicts with a new approach to pipeline management with YAML files.
makubacki
added a commit
that referenced
this pull request
Oct 21, 2022
* Revert "Updated pipelines to only run CI and PR gates on release/202208 and release/202202 (#131)" Reverts commit 4bbdb46 to reduce conflicts with a new approach to pipeline management with YAML files. * Use Mu DevOps Updates this repo to use mu_devops for Azure Pipeline definitions. In order to centralize definitions and avoid build churn in individual Mu repos, some changes are made to allow build administrators to quickly adjust settings: - Toolchain, VM image, and architecture are controlled by build administrators through centralized variable groups - CI triggers, CI schedules, and PR triggers are controlled by build administrators within the individual pipeline UI settings - [ ] Breaking change? - Will this change break pre-existing builds or functionality without action being taken? **No** Verified in test pipelines. N/A - No developer integration required Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
TaylorBeebe
pushed a commit
that referenced
this pull request
Feb 3, 2023
TaylorBeebe
pushed a commit
that referenced
this pull request
Feb 3, 2023
* Revert "Updated pipelines to only run CI and PR gates on release/202208 and release/202202 (#131)" Reverts commit 4bbdb46 to reduce conflicts with a new approach to pipeline management with YAML files. * Use Mu DevOps Updates this repo to use mu_devops for Azure Pipeline definitions. In order to centralize definitions and avoid build churn in individual Mu repos, some changes are made to allow build administrators to quickly adjust settings: - Toolchain, VM image, and architecture are controlled by build administrators through centralized variable groups - CI triggers, CI schedules, and PR triggers are controlled by build administrators within the individual pipeline UI settings - [ ] Breaking change? - Will this change break pre-existing builds or functionality without action being taken? **No** Verified in test pipelines. N/A - No developer integration required Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
TaylorBeebe
pushed a commit
to TaylorBeebe/mu_basecore
that referenced
this pull request
Apr 27, 2023
TaylorBeebe
pushed a commit
to TaylorBeebe/mu_basecore
that referenced
this pull request
Apr 27, 2023
* Revert "Updated pipelines to only run CI and PR gates on release/202208 and release/202202 (microsoft#131)" Reverts commit 4bbdb46 to reduce conflicts with a new approach to pipeline management with YAML files. * Use Mu DevOps Updates this repo to use mu_devops for Azure Pipeline definitions. In order to centralize definitions and avoid build churn in individual Mu repos, some changes are made to allow build administrators to quickly adjust settings: - Toolchain, VM image, and architecture are controlled by build administrators through centralized variable groups - CI triggers, CI schedules, and PR triggers are controlled by build administrators within the individual pipeline UI settings - [ ] Breaking change? - Will this change break pre-existing builds or functionality without action being taken? **No** Verified in test pipelines. N/A - No developer integration required Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
TaylorBeebe
pushed a commit
to TaylorBeebe/mu_basecore
that referenced
this pull request
Apr 27, 2023
TaylorBeebe
pushed a commit
to TaylorBeebe/mu_basecore
that referenced
this pull request
Apr 27, 2023
* Revert "Updated pipelines to only run CI and PR gates on release/202208 and release/202202 (microsoft#131)" Reverts commit 4bbdb46 to reduce conflicts with a new approach to pipeline management with YAML files. * Use Mu DevOps Updates this repo to use mu_devops for Azure Pipeline definitions. In order to centralize definitions and avoid build churn in individual Mu repos, some changes are made to allow build administrators to quickly adjust settings: - Toolchain, VM image, and architecture are controlled by build administrators through centralized variable groups - CI triggers, CI schedules, and PR triggers are controlled by build administrators within the individual pipeline UI settings - [ ] Breaking change? - Will this change break pre-existing builds or functionality without action being taken? **No** Verified in test pipelines. N/A - No developer integration required Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
kenlautner
added a commit
that referenced
this pull request
Apr 28, 2023
kenlautner
pushed a commit
that referenced
this pull request
Apr 28, 2023
* Revert "Updated pipelines to only run CI and PR gates on release/202208 and release/202202 (#131)" Reverts commit 4bbdb46 to reduce conflicts with a new approach to pipeline management with YAML files. * Use Mu DevOps Updates this repo to use mu_devops for Azure Pipeline definitions. In order to centralize definitions and avoid build churn in individual Mu repos, some changes are made to allow build administrators to quickly adjust settings: - Toolchain, VM image, and architecture are controlled by build administrators through centralized variable groups - CI triggers, CI schedules, and PR triggers are controlled by build administrators within the individual pipeline UI settings - [ ] Breaking change? - Will this change break pre-existing builds or functionality without action being taken? **No** Verified in test pipelines. N/A - No developer integration required Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
kenlautner
added a commit
that referenced
this pull request
May 3, 2023
kenlautner
pushed a commit
that referenced
this pull request
May 3, 2023
* Revert "Updated pipelines to only run CI and PR gates on release/202208 and release/202202 (#131)" Reverts commit 4bbdb46 to reduce conflicts with a new approach to pipeline management with YAML files. * Use Mu DevOps Updates this repo to use mu_devops for Azure Pipeline definitions. In order to centralize definitions and avoid build churn in individual Mu repos, some changes are made to allow build administrators to quickly adjust settings: - Toolchain, VM image, and architecture are controlled by build administrators through centralized variable groups - CI triggers, CI schedules, and PR triggers are controlled by build administrators within the individual pipeline UI settings - [ ] Breaking change? - Will this change break pre-existing builds or functionality without action being taken? **No** Verified in test pipelines. N/A - No developer integration required Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
kenlautner
pushed a commit
that referenced
this pull request
May 4, 2023
* Revert "Updated pipelines to only run CI and PR gates on release/202208 and release/202202 (#131)" Reverts commit 4bbdb46 to reduce conflicts with a new approach to pipeline management with YAML files. * Use Mu DevOps Updates this repo to use mu_devops for Azure Pipeline definitions. In order to centralize definitions and avoid build churn in individual Mu repos, some changes are made to allow build administrators to quickly adjust settings: - Toolchain, VM image, and architecture are controlled by build administrators through centralized variable groups - CI triggers, CI schedules, and PR triggers are controlled by build administrators within the individual pipeline UI settings - [ ] Breaking change? - Will this change break pre-existing builds or functionality without action being taken? **No** Verified in test pipelines. N/A - No developer integration required Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
kenlautner
pushed a commit
that referenced
this pull request
May 4, 2023
* Revert "Updated pipelines to only run CI and PR gates on release/202208 and release/202202 (#131)" Reverts commit 4bbdb46 to reduce conflicts with a new approach to pipeline management with YAML files. * Use Mu DevOps Updates this repo to use mu_devops for Azure Pipeline definitions. In order to centralize definitions and avoid build churn in individual Mu repos, some changes are made to allow build administrators to quickly adjust settings: - Toolchain, VM image, and architecture are controlled by build administrators through centralized variable groups - CI triggers, CI schedules, and PR triggers are controlled by build administrators within the individual pipeline UI settings - [ ] Breaking change? - Will this change break pre-existing builds or functionality without action being taken? **No** Verified in test pipelines. N/A - No developer integration required Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
kenlautner
pushed a commit
that referenced
this pull request
May 5, 2023
* Revert "Updated pipelines to only run CI and PR gates on release/202208 and release/202202 (#131)" Reverts commit 4bbdb46 to reduce conflicts with a new approach to pipeline management with YAML files. * Use Mu DevOps Updates this repo to use mu_devops for Azure Pipeline definitions. In order to centralize definitions and avoid build churn in individual Mu repos, some changes are made to allow build administrators to quickly adjust settings: - Toolchain, VM image, and architecture are controlled by build administrators through centralized variable groups - CI triggers, CI schedules, and PR triggers are controlled by build administrators within the individual pipeline UI settings - [ ] Breaking change? - Will this change break pre-existing builds or functionality without action being taken? **No** Verified in test pipelines. N/A - No developer integration required Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
kenlautner
pushed a commit
that referenced
this pull request
May 5, 2023
* Revert "Updated pipelines to only run CI and PR gates on release/202208 and release/202202 (#131)" Reverts commit 4bbdb46 to reduce conflicts with a new approach to pipeline management with YAML files. * Use Mu DevOps Updates this repo to use mu_devops for Azure Pipeline definitions. In order to centralize definitions and avoid build churn in individual Mu repos, some changes are made to allow build administrators to quickly adjust settings: - Toolchain, VM image, and architecture are controlled by build administrators through centralized variable groups - CI triggers, CI schedules, and PR triggers are controlled by build administrators within the individual pipeline UI settings - [ ] Breaking change? - Will this change break pre-existing builds or functionality without action being taken? **No** Verified in test pipelines. N/A - No developer integration required Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
kenlautner
pushed a commit
that referenced
this pull request
May 9, 2023
* Revert "Updated pipelines to only run CI and PR gates on release/202208 and release/202202 (#131)" Reverts commit 4bbdb46 to reduce conflicts with a new approach to pipeline management with YAML files. * Use Mu DevOps Updates this repo to use mu_devops for Azure Pipeline definitions. In order to centralize definitions and avoid build churn in individual Mu repos, some changes are made to allow build administrators to quickly adjust settings: - Toolchain, VM image, and architecture are controlled by build administrators through centralized variable groups - CI triggers, CI schedules, and PR triggers are controlled by build administrators within the individual pipeline UI settings - [ ] Breaking change? - Will this change break pre-existing builds or functionality without action being taken? **No** Verified in test pipelines. N/A - No developer integration required Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
kenlautner
pushed a commit
that referenced
this pull request
Oct 17, 2023
* Revert "Updated pipelines to only run CI and PR gates on release/202208 and release/202202 (#131)" Reverts commit 4bbdb46 to reduce conflicts with a new approach to pipeline management with YAML files. * Use Mu DevOps Updates this repo to use mu_devops for Azure Pipeline definitions. In order to centralize definitions and avoid build churn in individual Mu repos, some changes are made to allow build administrators to quickly adjust settings: - Toolchain, VM image, and architecture are controlled by build administrators through centralized variable groups - CI triggers, CI schedules, and PR triggers are controlled by build administrators within the individual pipeline UI settings - [ ] Breaking change? - Will this change break pre-existing builds or functionality without action being taken? **No** Verified in test pipelines. N/A - No developer integration required Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
kenlautner
pushed a commit
that referenced
this pull request
Oct 18, 2023
* Revert "Updated pipelines to only run CI and PR gates on release/202208 and release/202202 (#131)" Reverts commit 4bbdb46 to reduce conflicts with a new approach to pipeline management with YAML files. * Use Mu DevOps Updates this repo to use mu_devops for Azure Pipeline definitions. In order to centralize definitions and avoid build churn in individual Mu repos, some changes are made to allow build administrators to quickly adjust settings: - Toolchain, VM image, and architecture are controlled by build administrators through centralized variable groups - CI triggers, CI schedules, and PR triggers are controlled by build administrators within the individual pipeline UI settings - [ ] Breaking change? - Will this change break pre-existing builds or functionality without action being taken? **No** Verified in test pipelines. N/A - No developer integration required Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
kenlautner
pushed a commit
that referenced
this pull request
Oct 20, 2023
* Revert "Updated pipelines to only run CI and PR gates on release/202208 and release/202202 (#131)" Reverts commit 4bbdb46 to reduce conflicts with a new approach to pipeline management with YAML files. * Use Mu DevOps Updates this repo to use mu_devops for Azure Pipeline definitions. In order to centralize definitions and avoid build churn in individual Mu repos, some changes are made to allow build administrators to quickly adjust settings: - Toolchain, VM image, and architecture are controlled by build administrators through centralized variable groups - CI triggers, CI schedules, and PR triggers are controlled by build administrators within the individual pipeline UI settings - [ ] Breaking change? - Will this change break pre-existing builds or functionality without action being taken? **No** Verified in test pipelines. N/A - No developer integration required Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
kenlautner
pushed a commit
that referenced
this pull request
Oct 23, 2023
* Revert "Updated pipelines to only run CI and PR gates on release/202208 and release/202202 (#131)" Reverts commit 4bbdb46 to reduce conflicts with a new approach to pipeline management with YAML files. * Use Mu DevOps Updates this repo to use mu_devops for Azure Pipeline definitions. In order to centralize definitions and avoid build churn in individual Mu repos, some changes are made to allow build administrators to quickly adjust settings: - Toolchain, VM image, and architecture are controlled by build administrators through centralized variable groups - CI triggers, CI schedules, and PR triggers are controlled by build administrators within the individual pipeline UI settings - [ ] Breaking change? - Will this change break pre-existing builds or functionality without action being taken? **No** Verified in test pipelines. N/A - No developer integration required Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
kenlautner
pushed a commit
that referenced
this pull request
Dec 16, 2023
* Revert "Updated pipelines to only run CI and PR gates on release/202208 and release/202202 (#131)" Reverts commit 4bbdb46 to reduce conflicts with a new approach to pipeline management with YAML files. * Use Mu DevOps Updates this repo to use mu_devops for Azure Pipeline definitions. In order to centralize definitions and avoid build churn in individual Mu repos, some changes are made to allow build administrators to quickly adjust settings: - Toolchain, VM image, and architecture are controlled by build administrators through centralized variable groups - CI triggers, CI schedules, and PR triggers are controlled by build administrators within the individual pipeline UI settings - [ ] Breaking change? - Will this change break pre-existing builds or functionality without action being taken? **No** Verified in test pipelines. N/A - No developer integration required Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
kenlautner
pushed a commit
that referenced
this pull request
Dec 18, 2023
* Revert "Updated pipelines to only run CI and PR gates on release/202208 and release/202202 (#131)" Reverts commit 4bbdb46 to reduce conflicts with a new approach to pipeline management with YAML files. * Use Mu DevOps Updates this repo to use mu_devops for Azure Pipeline definitions. In order to centralize definitions and avoid build churn in individual Mu repos, some changes are made to allow build administrators to quickly adjust settings: - Toolchain, VM image, and architecture are controlled by build administrators through centralized variable groups - CI triggers, CI schedules, and PR triggers are controlled by build administrators within the individual pipeline UI settings - [ ] Breaking change? - Will this change break pre-existing builds or functionality without action being taken? **No** Verified in test pipelines. N/A - No developer integration required Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Updated pipelines to only run CI and PR gates on release/202208 and release/202202"
No.
How This Was Tested
Pipelines passed.
Integration Instructions
N/A