SimVascular / SimVascular/svMultiPhysics
Add building installers to GitHub Actions
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 45
- Forks
- 60
- Avg merge
- 5d 23h
- Merged PRs (30d)
- 11
Description
Problem
We currently build installers manually, so they have to be rebuilt by hand every time we want to release a new version (or provide an installer to a user).
Solution
Add building installers to GitHub Actions. We did this for the 0D solver. This way, every run of the actions has installers that anyone can download. When crafting a new release, installers can be included easily.
Additional context
Adapting this code should give us what we want.
Code of Conduct
- I agree to follow this project's Code of Conduct and Contributing Guidelines
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the repository's existing GitHub Actions workflows, then compare them with the referenced .github/workflows/test.yml from svZeroDSolver. Adapt the installer-building approach for svMultiPhysics and verify that workflow runs produce downloadable installers and that release creation can include them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, github-actions
- Domain
- build-system, ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100