forked from jupyterhub/binderhub
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
7 changed files
with
4 additions
and
794 deletions.
There are no files selected for viewing
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,14 +1,6 @@ | ||
name: Publish helm chart and docker images | ||
|
||
on: | ||
pull_request: | ||
paths-ignore: | ||
- "**.md" | ||
- "**.rst" | ||
- "docs/**" | ||
- "examples/**" | ||
- ".github/workflows/**" | ||
- "!.github/workflows/publish.yml" | ||
push: | ||
paths-ignore: | ||
- "**.md" | ||
|
@@ -33,7 +25,7 @@ jobs: | |
# | ||
Publish: | ||
runs-on: ubuntu-latest | ||
if: startsWith(github.ref, 'refs/tags/') || (github.ref == 'refs/heads/main') | ||
if: github.ref == 'refs/heads/release-depositar' | ||
steps: | ||
- uses: actions/checkout@v4 | ||
with: | ||
|
@@ -67,66 +59,15 @@ jobs: | |
- name: Build binderhub wheel | ||
run: python3 -m build --wheel . | ||
|
||
- name: Setup push rights to jupyterhub/helm-chart | ||
# This was setup by... | ||
# 1. Generating a private/public key pair: | ||
# ssh-keygen -t ed25519 -C "jupyterhub/binderhub" -f /tmp/id_ed25519 | ||
# 2. Registering the private key (/tmp/id_ed25519) as a secret for this | ||
# repo: | ||
# https://github.com/jupyterhub/binderhub/settings/secrets/actions | ||
# 3. Registering the public key (/tmp/id_ed25519.pub) as a deploy key | ||
# with push rights for the jupyterhub/helm chart repo: | ||
# https://github.com/jupyterhub/helm-chart/settings/keys | ||
# | ||
run: | | ||
mkdir -p ~/.ssh | ||
ssh-keyscan github.com >> ~/.ssh/known_hosts | ||
echo "${{ secrets.JUPYTERHUB_HELM_CHART_DEPLOY_KEY }}" > ~/.ssh/id_ed25519 | ||
chmod 600 ~/.ssh/id_ed25519 | ||
- name: Setup push rights to Quay.io | ||
# This was setup by... | ||
# 1. Creating a [Robot Account](https://quay.io/organization/jupyterhub?tab=robots) in the JupyterHub | ||
# 1. Creating a [Robot Account](https://quay.io/organization/depositar?tab=robots) in the JupyterHub | ||
# . quay.io org | ||
# 2. Giving it enough permissions to push to the binderhub image | ||
# 3. Putting the robot account's username and password in GitHub actions environment | ||
run: | | ||
docker login -u "${{ secrets.QUAY_USERNAME }}" -p "${{ secrets.QUAY_PASSWORD }}" quay.io | ||
docker login -u "${{ secrets.DOCKER_USERNAME }}" -p "${{ secrets.DOCKER_PASSWORD }}" docker.io | ||
- name: Configure a git user | ||
# Having a user.email and user.name configured with git is required to | ||
# make commits, which is something chartpress does when publishing. | ||
# While Travis CI had a dummy user by default, GitHub Actions doesn't | ||
# and require this explicitly setup. | ||
run: | | ||
git config --global user.email "[email protected]" | ||
git config --global user.name "GitHub Actions user" | ||
- name: Publish images and chart with chartpress | ||
env: | ||
GITHUB_REPOSITORY: "${{ github.repository }}" | ||
run: | | ||
./tools/generate-json-schema.py | ||
./ci/publish | ||
PyPI-testbuild: | ||
runs-on: ubuntu-latest | ||
steps: | ||
- uses: actions/checkout@v4 | ||
with: | ||
# Versioneer requires past tags | ||
fetch-depth: 0 | ||
- uses: actions/setup-python@v5 | ||
with: | ||
python-version: "3.11" | ||
- name: Install pypa/build | ||
run: python -mpip install build | ||
- name: Build a sdist, and a binary wheel from the sdist | ||
run: python -mbuild . | ||
# ref: https://github.com/actions/upload-artifact#readme | ||
- uses: actions/upload-artifact@v4 | ||
with: | ||
name: pypi-dist | ||
path: "dist/*" | ||
if-no-files-found: error |
Oops, something went wrong.