Update gitlab pipeline with node setup #11243
Merged
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.
Summary
Fixes #11240
Node.js
v14
is incompatible with the latest dashboard build, bumping the package to nodejs16 does not solve the problem of the openssl incompatibility. In order to circumvent this, node.jsv16
needs to be installed manually as the original package fromhttps://download.opensuse.org/repositories/devel:languages:nodejs/SLE_12_SP5/devel:languages:nodejs.repo
is outdated.Occurred changes and/or fixed issues
I've added a
node-setup
script to the pipeline that will download the specified release declared in theNODE_DISTRO
variable from the nodejs releases index.Technical notes summary
The
variables
stanza now has some variables to alleviate any further issues with upgrading node and yq.Areas or cases that should be tested
Installing the Extension catalog image that is published to the gitlab container registry of the repository.
Areas which could experience regressions
Screenshot/Video
You can see a passing test of this pipeline here.
Checklist