-
-
Notifications
You must be signed in to change notification settings - Fork 314
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clone reference repo path is looking for '$HOME' #1789
Comments
AdamBrousseau
added a commit
to AdamBrousseau/aqa-tests
that referenced
this issue
May 23, 2020
It is currently set in the job config and propagated down to the build during checkout scm. The problem is the '$HOME' variable is not getting resolved so the clone is looking for exactly that. Moving it out of the job config (template) and into the pipeline will allow it to be esolved properly. It is also not needed on the job config because we use a lightweight checkout. Fixes adoptium#1789 Signed-off-by: Adam Brousseau <[email protected]>
AdamBrousseau
added a commit
to AdamBrousseau/aqa-tests
that referenced
this issue
May 23, 2020
It is currently set in the job config and propagated down to the build during checkout scm. The problem is the '$HOME' variable is not getting resolved so the clone is looking for exactly that. Moving it out of the job config (template) and into the pipeline will allow it to be resolved properly. It is also not needed on the job config because we use a lightweight checkout. Fixes adoptium#1789 Signed-off-by: Adam Brousseau <[email protected]>
llxia
pushed a commit
that referenced
this issue
May 27, 2020
It is currently set in the job config and propagated down to the build during checkout scm. The problem is the '$HOME' variable is not getting resolved so the clone is looking for exactly that. Moving it out of the job config (template) and into the pipeline will allow it to be resolved properly. It is also not needed on the job config because we use a lightweight checkout. Fixes #1789 Signed-off-by: Adam Brousseau <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
https://github.com/AdoptOpenJDK/openjdk-tests/blame/fb7463af44f406b233def68085a7bfc5f4bb7e83/buildenv/jenkins/testJobTemplate#L204
#1484
I believe when this executes the job actually looks for
$HOME/openjdk_cache
instead of, for example/home/jenkins/openjdk_cache
I see this error on a machine which has the cache setup
At OpenJ9 we pull this value based on what plaform we are running on as it changes from linux to osx to windows. Hardcoding it to
/home/jenkins/openjdk_cache
would be a slight improvement but it wouldn't help osx for example.To Reproduce
Steps to reproduce the behavior (or Grinder rerun link):
Run a test job on a machine which has
~/openjdk_cache
vs a machine which does not.Expected behavior
Should find the cache.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: