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

move e2e test to circle-ci #5459

Merged
merged 1 commit into from
Mar 24, 2018
Merged

move e2e test to circle-ci #5459

merged 1 commit into from
Mar 24, 2018

Conversation

rubycut
Copy link
Contributor

@rubycut rubycut commented Mar 6, 2018

Summary

Move e2e test to circle-ci, Closing #4863

Test plan

This pull request is about tests, so we are not testing the tests.

@rubycut
Copy link
Contributor Author

rubycut commented Mar 6, 2018

@Daniel15 Can you check if this is going into the right direction, I managed to get first test pass. It works for ubuntu 16.04.

@Daniel15
Copy link
Member

Daniel15 commented Mar 6, 2018 via email

Copy link
Member

@Daniel15 Daniel15 left a comment

Choose a reason for hiding this comment

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

This is a good start! Let's try to get all versions (12.04, 14.04, 16.04) running with minimal duplication in the config.yml file :)

@@ -1,4 +1,5 @@
#!/bin/bash
# Starts an Ubuntu 16.04 Docker container and runs the Yarn end-to-end test on it
set -ex
./data/start-ubuntu.sh ubuntu:16.04
cd data
./run-ubuntu.sh
Copy link
Member

Choose a reason for hiding this comment

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

Just call run-ubuntu.sh directly (in config.yml) rather than modifying this script. This script should remain as-is, as it's still useful when running the test suite on your own computer.

@rubycut rubycut force-pushed the e2e_circleci branch 2 times, most recently from e611326 to 96b4f6c Compare March 11, 2018 13:06
@rubycut
Copy link
Contributor Author

rubycut commented Mar 11, 2018

@Daniel15 , all three ubuntu versions are added, script are intact so manually runnging them should still work. This looks ready to be merged.

Copy link
Contributor

@dhruvdutt dhruvdutt left a comment

Choose a reason for hiding this comment

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

LGTM! I raised this a while ago on Discord.

@Daniel15
Copy link
Member

This looks great!

Where do failures get published to? The current E2E tests have their results recorded at https://build.dan.cx/job/yarn-e2e/.

@rubycut
Copy link
Contributor Author

rubycut commented Mar 12, 2018

@Daniel15 , I am not sure what you mean. If you merge this pull requests, e2e builds will run every night and results will be visible in circle-ci.

@arcanis
Copy link
Member

arcanis commented Mar 24, 2018

What do you think, @Daniel15 ?

@Daniel15
Copy link
Member

This looks good to me! Let's get this in 😃

f you merge this pull requests, e2e builds will run every night and results will be visible in circle-ci.

@rubycut - What I mean is, how will we know that the tests have failed? With pull requests we see the CircleCI build status directly on the PR, with the current E2E tests they open a GitHub issue on failure. What happens if these ones fail?

@Daniel15 Daniel15 merged commit dcaf03a into yarnpkg:master Mar 24, 2018
@rubycut
Copy link
Contributor Author

rubycut commented Mar 25, 2018

@Daniel15 I was assuming that you have some kind of notification setup in circleCI, this would allow you to get email when e2e tests fail. Let me know if there is anything else I can do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants