Conversation
daljit46
force-pushed
the
weekly_releases
branch
from
35c00b6 to
8ec7867
Compare
daljit46
force-pushed
the
weekly_releases
branch
from
8ec7867 to
addbba0
Compare
This will allow a developer to manually create a release for a given branch.
|
The workflow now supports a "branch" input that a developer can specify to build a release from a specific branch. |
daljit46
changed the title
|
After thinking about this, I think it'd be better if we had one single release workflow that can handle:
This will prevent code duplication in the CI code. One problem is that we want to test the workflows on master and dev. However, master is still on the old build system rather than CMake. To get around this, I think it's best to wait until master is also on CMake and incrementally implement the three features above. |
1 participant
This PR adds support for weekly releases. It provides a single workflow that builds and creates appropriate packages for each OS. Naming convention has been set to
mrtrix3-OS-weekly-DATE-COMMIT.extension. Packages will be built for Linux, MacOS and Windows and released every Sunday at 12AM UTC time.To enable this we need to create a new release tagged
weeklywhich will be updated every week replacing the assets built the week before.Tasks to be completed:
weeklyand changeRELEASE_IDandUPLOAD_URLvariable inside the workflow.Needs to merged onto
masterbecause the workflow needs to run periodically, but it will the usedevbranch to build the packages.Feedback welcome.