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

Migrate CI to GitHub actions #38

Closed
kwabenantim opened this issue Dec 15, 2022 · 4 comments
Closed

Migrate CI to GitHub actions #38

kwabenantim opened this issue Dec 15, 2022 · 4 comments

Comments

@kwabenantim
Copy link
Member

This issue continues the discussion for legacy trac ticket 3099:


fcooper8472 created the following ticket on 2022-05-20 at 11:11:57, it is owned by fcooper8472


Comment by kwabenantim on 2022-08-25 at 10:33:09

Portability Testing:

  • I've added some scripts in the Chaste dependency-modules repository for installing dependency versions as Environment Modules so that we can have multiple versions side-by-side and switch between them for testing Chaste.
  • The dependency-modules repo also contains scripts for building a Docker image to use as a self-hosted github actions runner, based on Ubuntu 20.04.
  • I've added some documentation on the wiki ??? about setting up the runner, and for developers who want to test Chaste with multiple versions of dependencies.
  • The next step is to shadow the current portability tests and fix any issues that may occur.

Comment by kwabenantim on 2022-08-25 at 13:15:46

Portability Testing:

  • Built and pushed the github actions runner image to docker hub as chaste/runner https://hub.docker.com/r/chaste/runner
  • Updated documentation on the wiki to use the chaste/runner image from docker hub.

Comment by kwabenantim on 2022-09-01 at 08:13:01

Portability Testing

@fcooper8472
Copy link
Member

Work on this issue is not yet complete, but the vast majority of the useful CI is now working. My plan is to merge the current state of the CI branch into develop this afternoon, and then update this issue with the remaining tasks.

This will then allow all open PRs to merge develop in, and get the benefit of CI running on the PRs which will help get the pipeline for merging working as intended.

@AlexFletcher AlexFletcher changed the title #3099 - Migrate CI to GitHub actions Migrate CI to GitHub actions Jul 4, 2023
@mirams
Copy link
Member

mirams commented Oct 31, 2023

This is another piece of magic that it would be nice to keep. I refer to it quite often:
https://chaste.cs.ox.ac.uk/trac/wiki/ChasteGuides/HowTo
(comments matching HOW_TO in the code make this wiki page automatically)

@fcooper8472
Copy link
Member

fcooper8472 commented Nov 6, 2023

The open tasks on this umbrella issue are:

@fcooper8472
Copy link
Member

I'm closing this now; the only outstanding issue is #39 which contains all the remaining website-related jobs.

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

No branches or pull requests

4 participants