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

Force a fixed node image version when building client for Jenkins. #5382

Merged
merged 1 commit into from Jan 24, 2018

Conversation

Projects
None yet
3 participants
@jmchilton
Member

jmchilton commented Jan 24, 2018

At least one of our Jenkins nodes - possibly more - is failing to build the client without failing the test outright. Can see this toward the top of the logs - this is why the Selenium tests in #5365 are failing.

Force a new node version when building client for Jenkins.
At least one of our Jenkins nodes - possibly more - is failing to build the client without failing the test outright.
@dannon

This comment has been minimized.

Member

dannon commented Jan 24, 2018

Seems like a good idea to lock this.

@dannon dannon merged commit d627e5e into galaxyproject:dev Jan 24, 2018

3 of 6 checks passed

api test Test started.
Details
framework test Test started.
Details
selenium test Test started.
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
integration test Build finished. 79 tests run, 4 skipped, 0 failed.
Details
toolshed test Build finished. 577 tests run, 0 skipped, 0 failed.
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment