You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The latest Cbc stable release is available via Releases, but are 'nightly' builds of the master branch available? See the coin-or/Cbc#640 (comment).
The windows-ci and linux-ci build and run tests on every commit to master. However, these binaries are not stored. On the other hand, for PR builds the resulting binaries are uploaded as artifacts to the action (if: ${{ github.event_name == 'pull_request'}}).
How to publish binaries from builds of the master branch?
A very easy way to publish binaries for all builds, including master, is to simply remove the above if.
Disadvantage: such Action artifacts expire after 90 days.
A slightly more complicated alternative is to create one standing Release (a "pre-release") called something like Cbc-Master or Cbc-Latest or similar (or Cbc-3.0-prerelease?). Every successful build of master branch would update the assets of this release. See for example "Sonnet-Latest" https://github.com/coin-or/Sonnet/releases/tag/latest.
Advantage: Release assets do not expire.
We don't want to publish binaries from master.
The text was updated successfully, but these errors were encountered:
Option 1 (Artifacts are uploaded for master builds) is now (since 30 APR 2024) implemented for Cbc and dependencies. Related projects to follow shortly
Open Cbc master binaries from runs and click on the latest successful run of Linux or Windows and then see the binaries in the Artifacts sections at the bottom.
Alternatively, open https://github.com/coin-or/cbc/ -> Actions and filter for master branch.
The latest Cbc stable release is available via Releases, but are 'nightly' builds of the master branch available? See the coin-or/Cbc#640 (comment).
The windows-ci and linux-ci build and run tests on every commit to master. However, these binaries are not stored. On the other hand, for PR builds the resulting binaries are uploaded as artifacts to the action (
if: ${{ github.event_name == 'pull_request'}}
).How to publish binaries from builds of the master branch?
A very easy way to publish binaries for all builds, including master, is to simply remove the above
if
.Disadvantage: such Action artifacts expire after 90 days.
A slightly more complicated alternative is to create one standing Release (a "pre-release") called something like Cbc-Master or Cbc-Latest or similar (or Cbc-3.0-prerelease?). Every successful build of master branch would update the assets of this release. See for example "Sonnet-Latest" https://github.com/coin-or/Sonnet/releases/tag/latest.
Advantage: Release assets do not expire.
We don't want to publish binaries from master.
The text was updated successfully, but these errors were encountered: