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

🐈 Task: Clean up GitHub Actions Workflows #1231

Open
DhanshreeA opened this issue Aug 19, 2024 · 2 comments
Open

🐈 Task: Clean up GitHub Actions Workflows #1231

DhanshreeA opened this issue Aug 19, 2024 · 2 comments
Assignees

Comments

@DhanshreeA
Copy link
Member

Summary

We have a lot of workflows in the repository currently, a lot of which are not even getting used, and some workflows are duplicated. For example,

  1. Install Ersilia and Run Pytest workflows could go into the same file as parallel jobs since they both have the same triggers. Test Colab could also go in the same file as a parallel job, or sequential to Run Pytest.
  2. Quick Model Test (manual), Ersilia model ouptut prediction (Manual), and Ersilia model output prediction - all seem to be doing the same thing, and they all require a manual trigger, even though the last one was supposed to run on a schedule at some point.
  3. Ersilia Base Image to DockerHub Upload and Ersilia Installer to DockerHub upload can both go into the same file as parallel jobs since they both have the same workflow trigger, and are independent of each other. There's a slight caveat, the trigger for these jobs depends on a workflow that no longer exists. Tagging and versioning now happen in the Ersilia Release workflow. On second thoughts, I think the DockerHub uploads can be bundled in this workflow as sequential jobs after the GH and PyPI releases are successful.

Objective(s)

TODO

Documentation

No response

@dzumii
Copy link
Contributor

dzumii commented Aug 21, 2024

@DhanshreeA I have started working on this, do you advise i take each on different PRs? So i can easily test and not mess things up too much at a go.

@GemmaTuron
Copy link
Member

Hi @DhanshreeA

There is a bunch of PR's linked to this. Can you update of the mentioned issues, which ones are remaining to tackle?

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

No branches or pull requests

3 participants