Enable running as root user in CI environment #11
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… root, to be able to run npm builds.
…t have a version set. Force the same version across all projects.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Due to a difference in how the workspace is mounted on the TeamCity CI environment (vs. my personal TeamCity Test setup) the user running the build for Reposilite needs to be root (to be able to override the ownership handling of both the teamcity agent container (running as the teamcity user) as well as the gradle runtime (running as the gradle user)).
Additionally this updates the runtime gradle environment, so that for now no gradle wrapper needs to be downloaded, and the version is forced on all projects.