Enable GitLab pages without user custom domains
Enables the use of GitLab pages without configuring user custom domains. Also added the ability to configure the port of pages in the virtual service, as sets it to port 80, whereas the pages pod uses port 8090. Both default to the same behavior as before if not specified in values, though I'm not sure how that worked with the port being 80. Fixes #196 (closed)
Merge request reports
Activity
@john.p.potter 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 statusreviewMR Title Keywords
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.
MR Labels
Similar to the MR title keywords described above, gitlab labels can be added to Merge Requests to adjust CI pipeline behavior.
Labels for BigBang MRs
- all-packages -- Enables all BigBang packages. This will typically cause the cluster to run slower due to the increased resource usage, so it can be helpful in making sure any timeouts you've set aren't too short or check for any conflicts between packages, etc.
-
<package-name>
-- Adding a package name as a label will enable that package. - test-ciinfra -- Add stages to provision and destroy the cloud infrastructure where the tests will run.
Labels for BigBang and package MRs
- test-cirelease -- Test the release CI, which includes the package and release stages.
- disable-ci -- Disables all pipeline runs.
- kinddocs -- For MRs with only document changes. Won't run any pipelines.
- skip-bb-mr -- Will skip the auto-creation of a merge request into BigBang.
-
added needs-labels label
added community-contribution label
added 9 commits
-
2ebe1e2b...702f438c - 8 commits from branch
big-bang/product/packages:main
- d6251d51 - Merge branch gitlab:main into fix-pages
-
2ebe1e2b...702f438c - 8 commits from branch
mentioned in issue #196 (closed)
assigned to @john.p.potter
Hi @john.p.potter. thank you for your contribution. In order to move this forward we need you (The contributor) to..
- Regenerate the readme using this process
- Update the changelog.md following the existing format in that file.
- Bump the bb.x version of the chart in the Chart.yaml
- Once these steps are completed we can look to our pipelines for a successful test.
added statusreview label
@john.p.potter also just for future contributions. Your MR typically won't get any visibility until the status::review label is added. Also if your MR is tied to any specific issue please also reference that in the description or comments
@chris.oconnell Unfortunately, I don't have permission to add/edit labels. I have 4-5 MRs languishing for BB products without much attention, but I can't do anything but comment on them. I'll update the readme and changelog as requested though, thank you
added 5 commits
-
d6251d51...8359b49e - 4 commits from branch
big-bang/product/packages:main
- 641506da - feat: add support for pages without custom-domains
-
d6251d51...8359b49e - 4 commits from branch
@chris.oconnell Files updated as requested, thanks for the info on that.
@john.p.potter ah sorry about that. I didn't realize. I'll get the review label added to your MRs
!206 (merged) opened to replicate these changes for merge. Changes merged just now. Will be present in 2.10
removed statusreview label