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

Migrating to GH actions #5913

Closed
14 of 16 tasks
dstansby opened this issue Feb 23, 2022 · 1 comment · Fixed by #5939
Closed
14 of 16 tasks

Migrating to GH actions #5913

dstansby opened this issue Feb 23, 2022 · 1 comment · Fixed by #5939
Labels
Effort High Requires a large time investment Priority High Rapid action required Tests Affects tests in some measure

Comments

@dstansby
Copy link
Member

dstansby commented Feb 23, 2022

Provide a general description of the issue or problem.

Since our ability to use Azure pipelines is dwindling, we've decided to re-create our CI on Github actions. This has already been started, but there is still plenty to do. Off the top of my head the list is below; please edit/add items!

Tests

Write a GitHub workflow to replace the azure pipelines tox workflow, currently here but ultimately should be in an openastronomy repo.

  • Install list of libraries
  • Install and execute tox
  • Install tox-pypi-filter
  • Codecov
  • Test inside a conda environment
  • [N/A] Skip CI doesn't skip required builds (if even possible) Don't think this is possible unless we use an alternative command such as [sunpy skip].
  • (optional) xvfb
  • (optional) Run inside docker container [32bit and python betas]

Release

Sunpy specific things:

  • Cron jobs
  • Matrix notifications (https://github.com/KrazyKirby99999/matrix-commit)
  • Break the jobs up into stages like we had on Azure to fail early.
  • Build wheels and test them on branches (not PRs)
  • Implement release on successful test run on tag
@dstansby dstansby added Effort High Requires a large time investment Priority High Rapid action required Tests Affects tests in some measure labels Feb 23, 2022
@Cadair
Copy link
Member

Cadair commented Feb 24, 2022

I had a call with Azure support today, and they were very helpful and understanding but ultimately unable to clarify what exactly was causing their automated abuse detection to shut us down, so I think we are left with few other options than to abandon ship.

@ConorMacBride ConorMacBride linked a pull request Mar 16, 2022 that will close this issue
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Effort High Requires a large time investment Priority High Rapid action required Tests Affects tests in some measure
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants