Skip to content

Add docs for GHA self-hosted settings#2025

Merged
jaimergp merged 2 commits into
conda-forge:mainfrom
isuruf:self-hosted-gha
Nov 6, 2023
Merged

Add docs for GHA self-hosted settings#2025
jaimergp merged 2 commits into
conda-forge:mainfrom
isuruf:self-hosted-gha

Conversation

@isuruf

@isuruf isuruf commented Oct 31, 2023

Copy link
Copy Markdown
Member

PR Checklist:

  • note any issues closed by this PR with closing keywords
  • put any other relevant information below

See conda-forge/conda-smithy#1703

Comment thread src/maintainer/conda_forge_yml.rst
@jaimergp

jaimergp commented Nov 6, 2023

Copy link
Copy Markdown
Member

I'm going to merge this for now. There's a chance we need to expand a bit on the details of GPU runners but for now this is valid information even if it's in a general way for any kind of self-hosted GHA runners.

@jaimergp jaimergp merged commit 1903abf into conda-forge:main Nov 6, 2023
@hmaarrfk

hmaarrfk commented Nov 6, 2023

Copy link
Copy Markdown
Contributor

so can i donate a computer of mine to conda-forge to build some packages for us ;) or is this for non-conda-forge users to setup their own self hosted stuff?

Comment on lines +389 to +398
github_actions_labels:
# use Microsoft free runners
- hosted # [osx or win]
# Use self-hosted runner with custom label
- - self-hosted # [linux and aarch64]
- custom-label # [linux and aarch64]
# Use self-hosted runner from cirun
- cirun-openstack-cpu-large # [linux and ppc64le]
# Use self-hosted gpu runner from cirun
- cirun-openstack-gpu-large # [linux and x86_64]

@adrianinsaval adrianinsaval Mar 18, 2024

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Could somebody explain how do I interpret this? how do I use this? how can I achieve this output:

          - CONFIG: osx_arm64_python3.11.____cpython
            UPLOAD_PACKAGES: True
            os: macos
            runs_on: ['macos-14']

macos-14 are github's new arm macos runners

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.

You can't, this is only for self-hosted runners, or organizations that are not conda-forge. We haven't enabled native osx-arm64 runners with Github. See discussion at #1781

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

I'm trying to do it for a not conda-forge feedstock. Would be nice if smithy woudl support that in such cases, loks like most of the building blocks needed for such functionality are there. It's a PITA manually changing back to the specific runner I want every time I rerender. I also want to specify the macos version for the x86_64 runner, my builds hang for a prolonged time sometimes until timeout on macos-latest but usually run without issue on macos-11

@jakirkham jakirkham Mar 20, 2024

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.

Should we convert this to a conda-smithy issue?

Would help if we can capture what exactly is being tried, what happens now, and what the use case needs to work in the ideal case

Edit: Links to PRs, code, etc. would also be helpful context

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.

6 participants