Ensure FIPS builds are EE
What does this MR do?
As a result of FIPS builds being named gitlab-fips
instead of gitlab-ee
in !6113 (merged), the packages were downgraded from EE to CE. We should explicitly set these to build as EE.
We could alternatively change the Build::Check.is_ee?
to true
if use_system_ssl?
were set, but this seems like it could cause confusion because it's possible to have a CE edition with a system SSL build.
Related issues
Relates to #6935 (closed)
Checklist
See Definition of done.
For anything in this list which will not be completed, please provide a reason in the MR discussion
Required
-
Merge Request Title, and Description are up to date, accurate, and descriptive -
MR targeting the appropriate branch -
MR has a green pipeline on GitLab.com -
Pipeline is green on dev.gitlab.org if the change is touching anything besides documentation or internal cookbooks -
trigger-package
has a green pipeline running against latest commit
Expected (please provide an explanation if not completing)
-
Test plan indicating conditions for success has been posted and passes -
Documentation created/updated -
Tests added -
Integration tests added to GitLab QA -
Equivalent MR/issue for the GitLab Chart opened
Edited by Stan Hu