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

[jenkins] ensure that JDK8 is in path #6590

Merged
merged 2 commits into from
Mar 21, 2016
Merged

Conversation

spalger
Copy link
Contributor

@spalger spalger commented Mar 21, 2016

Something changed recently and selenium (the same version we've been using for a while?) no longer runs on JDK7. Since this is the default JDK we need to intentionally put JDK8 into the PATH when we run our tests on jeknins.

@spalger spalger force-pushed the upgrade/selenium branch 2 times, most recently from fa0705f to 5c93813 Compare March 21, 2016 21:02
@@ -5,8 +5,8 @@ module.exports = function (grunt) {
grunt.option('os-packages', true);

grunt.task.run(compact([
'test',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you intend to change this?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, temporarily

@epixa
Copy link
Contributor

epixa commented Mar 21, 2016

The build failure seems to indicate that something is still looking for the old version of selenium.

@spalger spalger force-pushed the upgrade/selenium branch 4 times, most recently from 7750312 to f366402 Compare March 21, 2016 21:30
@spalger spalger force-pushed the upgrade/selenium branch 2 times, most recently from e78e473 to f53b8c1 Compare March 21, 2016 22:01
@spalger spalger changed the title [upgrade] selenium [jenkins] ensure that JDK8 is in path Mar 21, 2016
@spalger spalger added the review label Mar 21, 2016
@spalger
Copy link
Contributor Author

spalger commented Mar 21, 2016

The remaining failure here is due to elastic/elasticsearch#17217. Would like to merge and deal with these failures in another pr.

@lukasolson
Copy link
Member

LGTM

spalger added a commit that referenced this pull request Mar 21, 2016
[jenkins] ensure that JDK8 is in path
@spalger spalger merged commit 7f089c4 into elastic:master Mar 21, 2016
@spalger spalger deleted the upgrade/selenium branch October 18, 2019 17:37
cee-chen added a commit that referenced this pull request Feb 15, 2023
## Summary

`[email protected]` ⏩ `[email protected]`

---

## [`75.1.0`](https://github.com/elastic/eui/tree/v75.1.0)

- Added padding to `EuiStep` title to better align with icon
([#6555](elastic/eui#6555))
- Added a new `lineNumbers.annotations` API to `EuiCodeBlock`. This new
feature displays an informational icon next to the specified line
number(s), providing more context via popover
([#6580](elastic/eui#6580))

**Bug fixes**

- Fixed bug in `EuiRange` where styles were applied incorrectly when
custom ticks were passed but `showTicks` were false
([#6588](elastic/eui#6588))
- Fixed `fleetApp` and `agentApp` icons that were swapped
([#6590](elastic/eui#6590))

**CSS-in-JS conversions**

- Converted `EuiSteps` to Emotion; Removed `$euiStepStatusColorsToFade`,
`$euiStepNumberSize`, `$euiStepNumberSmallSize`, and
`$euiStepNumberMargin`
([#6555](elastic/eui#6555))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants