-
Notifications
You must be signed in to change notification settings - Fork 303
Circle CI 2.1 conf #5627
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
Circle CI 2.1 conf #5627
Conversation
54f4dc6
to
8020bff
Compare
cdaa3e2
to
a5475c7
Compare
…ole to venture into now
…h 6.17 is the latest hmm
Codecov Report
@@ Coverage Diff @@
## 0.17.x #5627 +/- ##
===========================================
- Coverage 66.05% 46.33% -19.73%
===========================================
Files 113 113
Lines 6508 6514 +6
===========================================
- Hits 4299 3018 -1281
- Misses 2209 3496 +1287
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No code was changed, just tests and build scripts. And a bit of developer documentation. Hence, I will self-merge this in order to have functional builds restored for other release PRs.
Summary
Buildkite and Circle CI is restored, however Selenium-based tests now fail. The failures seem to be related to new breakages, but not the Selenium/geckodriver updates which seem to work.
Background
Circle CI has killed the 1.0 API that we were using. So we needed to either go back to Travis CI or start using their 2.0. The changes introduced here have no new value other than just extending the lifespan of the automated tests and builds. It's very sad the way that Circle CI has removed their old API and forced us into this.
The reason why this problem went under the radar was that the Circle CI integration was simply shut down, so we kept getting ✔️ on our builds because Buildkite was still building artifacts.. but alas, no testing was done.
It also turned out that the combination of geckodriver+Selenium+Firefox wasn't reproducible in the new Circle CI docker containers.. I couldn't make it work, sticking to the same Selenium version and going through a series of different geckodriver+Firefox combinations, including the ones we had used before.
The automated tests are the only means to introduce changes to a somewhat large codebase that will be difficult to support in case of breakage.
https://circleci.com/sunset1-0/
TODO
Reviewer guidance
If your PR has a significant size, give the reviewer some helpful remarks
Issues addressed
List the issues solved or partly solved by the PR