Skip to content

WIP: Binary distributions via GitHub Releases.#98

Open
zivy wants to merge 1 commit into
SimpleITK:mainfrom
zivy:releaseAndBinaryPackages
Open

WIP: Binary distributions via GitHub Releases.#98
zivy wants to merge 1 commit into
SimpleITK:mainfrom
zivy:releaseAndBinaryPackages

Conversation

@zivy
Copy link
Copy Markdown
Member

@zivy zivy commented May 19, 2026

When a tag that matches the SITK_TARGET is pushed
to the repository, binary R packages for all tested platforms and that specific tag are created and uploaded to a draft release on GitHub.

Binary packages built and uploaded by CircleCI
use the GitHub CLI tool and requiere a GitHub
personal access token (PAT) with full repo control. In CircleCI project settings, under
Environment Variables add a variable:
GITHUB_TOKEN = PAT_value.

When a tag that matches the SITK_TARGET is pushed
to the repository, binary R packages for all tested
platforms and that specific tag are created and uploaded
to a draft release on GitHub.

Binary packages built and uploaded by CircleCI
use the GitHub CLI tool and requiere a GitHub
personal access token (PAT) with full repo control.
In CircleCI project settings, under
Environment Variables add a variable:
GITHUB_TOKEN = PAT_value.
@zivy zivy requested a review from blowekamp May 19, 2026 16:41
@blowekamp blowekamp requested a review from Copilot May 20, 2026 20:16
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.


# Binary package is only created for tag pushes that match SITK_TARGET
# (tag/SITK_TARGET match is validated at the beginning of the workflow).
- name: Create binary package from installed package
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd would always create the packages.

mv "$PKG_FILE" "$NEW_NAME"
ls -lh artifacts/

- name: Upload binary package
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd aways upload the results too, so they can be used and inspected.

name: Create GitHub Draft Release
# Only run this job for tag pushes after the R-build job completes
# successfully (also means the pushed tag matches SITK_TARGET since
# R-build validates that at the beginning).
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Keep it simple. Just run when there is a tag starting with be. The whole comparison is really not needed.

# it with the GitHub Actions artifacts and the release description/body.
- name: Create or Update Draft Release
uses: softprops/action-gh-release@v2
env:
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would just use the gh command line directly and not use the third party action.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants