Skip to content
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

Do not allow NODE to be null #2343

Merged
merged 1 commit into from
Jul 9, 2018

Conversation

AdamBrousseau
Copy link
Contributor

  • If NODE is set as a build parameter but is not set,
    the current logic will set NODE to params.node which
    will be null. This will produce an IllegalArgumentException
    'Null value not allowed as an environment variable: NODE'.
    The updated logic should first look to the param,
    then fetch from the variable file if it is not passed.
    It will then throw an error if neither can be determined.

[skip ci]

Signed-off-by: Adam Brousseau adam.brousseau88@gmail.com

- If NODE is set as a build parameter but is not set,
  the current logic will set NODE to params.node which
  will be null. This will produce an IllegalArgumentException
  'Null value not allowed as an environment variable: NODE'.
  The updated logic should first look to the param,
  then fetch from the variable file if it is not passed.
  It will then throw an error if neither can be determined.

[skip ci]

Signed-off-by: Adam Brousseau <adam.brousseau88@gmail.com>
@AdamBrousseau
Copy link
Contributor Author

Jenkins compile xlinux jdk8

@AdamBrousseau
Copy link
Contributor Author

adam test sanity plinux jdk8

1 similar comment
@AdamBrousseau
Copy link
Contributor Author

adam test sanity plinux jdk8

@AdamBrousseau
Copy link
Contributor Author

@vsebe please review

@mleipe
Copy link

mleipe commented Jul 9, 2018

@vsebe is on vacation until August.

@pshipton pshipton merged commit 3ffa77b into eclipse-openj9:master Jul 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants