Skip to content

CircleCI 2.0 migration #1109

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

Merged
merged 30 commits into from
Aug 17, 2018
Merged

CircleCI 2.0 migration #1109

merged 30 commits into from
Aug 17, 2018

Conversation

jonmmease
Copy link
Contributor

@jonmmease jonmmease commented Aug 13, 2018

Port of test suite to 2.0, with improvements. Thanks to @scjody for the reminders 🙂

General approach: There is now a workflow for each Python version / test suite combination. This way all of the jobs can run in parallel. I also refactored the core tests to pull out the tests that rely on plot.ly interaction. These are currently the slowest tests, and pulling them out means that the core tests run really fast. It also means that if there is an intermittent failure due to plot.ly communication, we can restart only the plot.ly tests for the particular version of Python that had the failure.

Updates:

  • Split plot.ly tests into separate directory
  • Add core and core+optional workflows for 2.7, 3.4, 3.5, 3.6, and 3.7 (These run pretty fast now without the plot.ly tests)
  • plot.ly tests for 2.7, 3.4, and 3.7?
  • Add pytest validator tests to optional (these tests need the extra dependencies)
  • Add useful caching Caching tox sped builds up by a minute at most and would add a lot of extra complexity to the build file. So holding off for now.

Future testing wishlist: #1113

cc @cldougl @chriddyp @Kully @scjody

@jonmmease
Copy link
Contributor Author

Ok, I got the tests running for a few configurations. I'm making each tox configuration a separate workflow so that testing the different configurations can happen in parallel.

I took the opportunity to split out the tests that interact with plot.ly into a separate directory plotly/tests/test_plot_ly. This way the core tests run much faster. I'm thinking of running the plot_ly tests only once on a Python 2 build and once on a Python 3 build, but running the core and optional tests on each supported version.

We need to add configurations for Python 3.6 and 3.7 and we can drop 3.3 since it's past end of life.

cc @Kully @cldougl

@jonmmease jonmmease mentioned this pull request Aug 15, 2018
@jonmmease jonmmease changed the title [WIP] towards circle 2.0 CircleCI 2.0 migration Aug 15, 2018
@jonmmease jonmmease added this to the v3.2.0 milestone Aug 15, 2018
@jonmmease
Copy link
Contributor Author

Alright, time to merge this thing. Goodbye CircleCI 1.0!

@jonmmease jonmmease merged commit 7767b44 into master Aug 17, 2018
@nicolaskruchten nicolaskruchten deleted the circle_2.0 branch June 19, 2020 16:10
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.

1 participant