Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[#25541] Stop use of self hosted runners for some workflows. #25542

Merged
merged 1 commit into from
Feb 17, 2023

Conversation

lostluck
Copy link
Contributor

Stop use of self hosted runners for some workflows. This is a stopgap to get the repo automation healthy again.

See #25541 for context.


Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

  • Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
  • Update CHANGES.md with noteworthy changes.
  • If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

Build python source distribution and wheels
Python tests
Java tests
Go tests

See CI.md for more information about GitHub Actions CI.

@lostluck
Copy link
Contributor Author

R: @damccorm

@@ -32,7 +32,7 @@ on:

jobs:
generate_tags:
runs-on: [self-hosted, ubuntu-20.04]
runs-on: ubuntu-latest
Copy link
Contributor

Choose a reason for hiding this comment

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

Its not totally clear if these release tasks will work on hosted runners (or if they'll work at all), but its probably fine to include them. I may try these out during my release

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I thought this was the bot that tagged finished issues/PRs with the release that includes them, and since a release just went out...

Copy link
Contributor

Choose a reason for hiding this comment

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

No, that one is different - this is only run manually and can do one of the release steps (tagging a released version in GitHub) -

(workflow_dispatch means manual trigger only). You're thinking of
name: Assign Milestone on issue close

Copy link
Contributor

Choose a reason for hiding this comment

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

Fortunately, that should be functioning fine since its on a hosted runner

@damccorm
Copy link
Contributor

GitHub won't pick up workflow changes until they're merged, so LabelPrs will still not work on this PR - just calling that out so that you don't block on it

@lostluck lostluck merged commit 6de6744 into master Feb 17, 2023
@lostluck
Copy link
Contributor Author

And now we wait.

@johnjcasey johnjcasey mentioned this pull request Feb 21, 2023
3 tasks
@lostluck lostluck deleted the beam25541 branch April 12, 2023 17:34
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.

2 participants