Update KAS version
Update KAS to the latest green master
What should I do if this pipeline is red?
- Look at the failure. If it looks unrelated to KAS, it's likely a master:broken or failureflaky-test.
- Open the Pipelines tab and click Run Pipeline.
- This will run a pipeline for merge result.
- If it looks related to KAS, notify the KAS team in
#f_agent_for_kubernetes
on Slack.
What should I do in case of merge conflicts?
If someone updates GITLAB_KAS_VERSION
with another MR, we may have a merge conflict.
In such unlikely circumstances, the better option will be closing this merge request and deleting the release-tools/update-kas
branch.
release-tools
will take care of creating a new merge request in about 1 hour.
Do you want to improve this message? You can find it here! groupenvironments loves merge requests.
Merge request reports
Activity
changed milestone to %17.4
assigned to @gitlab-release-tools-bot
added pipelinetier-3 pipeline:run-e2e-omnibus-once labels
added devopsdeploy sectioncd labels
E2E Test Result Summary
allure-report-publisher
generated test report!e2e-test-on-gdk:
✅ test report for 1acdf743expand test summary
+------------------------------------------------------------------+ | suites summary | +-------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +-------------+--------+--------+---------+-------+-------+--------+ | Package | 20 | 0 | 12 | 0 | 32 | ✅ | | Verify | 44 | 0 | 2 | 0 | 46 | ✅ | | Create | 128 | 0 | 15 | 0 | 143 | ✅ | | Plan | 73 | 0 | 0 | 0 | 73 | ✅ | | Govern | 71 | 0 | 0 | 0 | 71 | ✅ | | Data Stores | 31 | 0 | 1 | 0 | 32 | ✅ | | Analytics | 2 | 0 | 0 | 0 | 2 | ✅ | | Release | 5 | 0 | 0 | 0 | 5 | ✅ | | Manage | 1 | 0 | 1 | 0 | 2 | ✅ | | Monitor | 8 | 0 | 0 | 0 | 8 | ✅ | | Secure | 3 | 0 | 0 | 0 | 3 | ✅ | | Fulfillment | 2 | 0 | 0 | 0 | 2 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+ | Total | 388 | 0 | 31 | 0 | 419 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+
Closing since this is a duplicate of !163402 (comment 2066593846)