Closed rjferguson21 closed 8 months ago
Your contribution to the DSO Repo1 has been mirrored to https://repo1.dso.mil/big-bang/product/packages/monitoring/-/merge_requests/230
Comments will be mirrored to the associated GitLab Merge Request.
Quote Replies will mirror to Gitlab as a Thread
Updates to code will be pushed to the associated GitLab Merge Request.
Closing the PR will close the associated GitLab Merge Request.
Comments on code will not be mirrored
Merge Request synchronized with commit https://github.com/DoD-Platform-One/monitoring/pull/2/commits/1b608dd8761b07224cf6c51577fffb0842177583
Merge Request synchronized with commit https://github.com/DoD-Platform-One/monitoring/pull/2/commits/fe752a98911c06f8d17eaad5419f1d73ab4d1115
@group_3988_bot_f3cc1a4c3f66ffe8398fad5cbe77e8ec This merge request is unlabelled and not marked as draft. Please add one or more labels.
To mark as draft prefix this merge request title with Draft:
If this merge request is ready for review remove Draft:
and label ~status::review
To easily adjust the pipeline behavior without a commit, keywords can be placed in the title of Merge Requests.
Supported keywords:
DEBUG
-- Enables debug mode. This will set -x in shell scripts so each command is printed before it runs, and dumps information such as the networking configuration (virtual services, gateways, dns, /etc/hosts files), cluster information (kustomize, cluster resources, memory and cpu usage), and dumps the cluster logs.SKIP UPGRADE
-- Skips the upgrade test stage of a pipeline.SKIP UPDATE CHECK
-- Skips the check in the configuration validation stage to see if the chart version was incremented.SKIP INTEGRATION
-- Skips the integration stage which is used in the third-party and sandbox pipelines.Similar to the MR title keywords described above, gitlab labels can be added to Merge Requests to adjust CI pipeline behavior.
<package-name>
-- Adding a package name as a label will enable that package.Merge Request synchronized with commit https://github.com/DoD-Platform-One/monitoring/pull/2/commits/bbfc3489998e8c5976e4ef75d417e7cb4935aa4a
@rjferguson21 Can we test moving the cleanup script portions to the main container as outlined in one of the items of the issue
Pipeline is running at https://repo1.dso.mil/big-bang/product/packages/monitoring/-/pipelines/2289087
The related MR: https://repo1.dso.mil/big-bang/product/packages/monitoring/-/merge_requests/230 was merged. Closing the PR.
This partially addresses https://repo1.dso.mil/big-bang/product/packages/monitoring/-/issues/118
The way the job is written at the moment creates a race condition between the
cleanup-proxy
and thecreate
pod.