Cflinuxfs5 pipeline validation#1338
Closed
Milena-Encheva wants to merge 28 commits into
Closed
Conversation
…release-candidate
|
Contributor
|
Hello friend, it looks like your pull request has failed one or more of our checks. Please take a look! 👀 |
Contributor
|
Hello friend, it looks like your pull request has failed one or more of our checks. Please take a look! 👀 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
WHAT is this change about?
Adds cflinuxfs5 stack validation to the experimental Concourse pipeline (hermione). This includes adding cflinuxfs5-release to the update-releases pipeline inputs, applying the add-cflinuxfs5.yml ops file in the experimental deploy jobs, and introducing a new experimental-cats-cflinuxfs5 job to run cf-acceptance-tests against the cflinuxfs5 stack.
What customer problem is being addressed? Use customer persona to define the problem e.g. Alana is unable to...
George (CF operator) needs confidence that the upcoming cflinuxfs5 stack works correctly with cf-deployment before it is promoted as a default or GA'd stack. Without this pipeline validation, there is no automated signal that cflinuxfs5 is stable and compatible with current cf-deployment.
Please provide any contextual information.
Part of #1323. Follows the same experimental validation approach previously used for cflinuxfs4 before it became the default stack. Depends on operations/experimental/add-cflinuxfs5.yml (introduced in Attila's PR) and the cflinuxfs5_integration_config.json in relint-envs.
Has a cf-deployment including this change passed cf-acceptance-tests?
Does this PR introduce a breaking change? Please take a moment to read through the examples before answering the question.
How should this change be described in cf-deployment release notes?
Add cflinuxfs5-release to experimental pipeline validation; introduces experimental-cats-cflinuxfs5 job to run CATs against the cflinuxfs5 stack.
Does this PR introduce a new BOSH release into the base cf-deployment.yml manifest or any ops-files?
Does this PR make a change to an experimental or GA'd feature/component?
Please provide Acceptance Criteria for this change?
1.) The experimental-deploy job in the hermione pipeline applies operations/experimental/add-cflinuxfs5.yml without errors.
2.) After a successful experimental-deploy, the new experimental-cats-cflinuxfs5 job triggers and completes CATs against the cflinuxfs5 stack using cflinuxfs5_integration_config.json.
What is the level of urgency for publishing this change?
Tag your pair, your PM, and/or team!
@oliver-heinrich @jochenehret