Skip to content

Improve readme #659

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

Merged

Conversation

marcofranssen
Copy link
Contributor

@marcofranssen marcofranssen commented Mar 9, 2021

When testing the Ubuntu example I ran into a few small issues. To resolve these I have slightly updated the docs and as well added some core dependencies in this example that allows others to use the ubuntu example without having issues running workflows that utilize commonly used actions.

@marcofranssen marcofranssen changed the base branch from develop to master March 9, 2021 16:21
@marcofranssen marcofranssen changed the base branch from master to develop March 9, 2021 16:22
@marcofranssen marcofranssen force-pushed the improve-readme branch 7 times, most recently from 3ab53ae to e806ed0 Compare March 10, 2021 15:34
@marcofranssen marcofranssen requested a review from npalm April 7, 2021 12:19
The module supports two main scenarios for creating runners. On repository level a runner will be dedicated to only one repository, no other repository can use the runner. On organization level you can use the runner(s) for all the repositories within the organization. See https://help.github.com/en/actions/hosting-your-own-runners/about-self-hosted-runners for more information. Before starting the deployment you have to choose one option.
The module supports two main scenarios for creating runners. On repository level a runner will be dedicated to only one repository, no other repository can use the runner. On organization level you can use the runner(s) for all the repositories within the organization. See [GitHub instructions](https://help.github.com/en/actions/hosting-your-own-runners/about-self-hosted-runners) for more information. Before starting the deployment you have to choose one option.

GitHub workflows fail immediately if there is no action runner available for your builds. Since this module supports scaling down to zero, builds will fail in case there is no active runner available. We recommend to create an offline runner with matching labels to the configuration. Create this runner manually by following the [GitHub instructions](https://help.github.com/en/actions/hosting-your-own-runners/about-self-hosted-runners) for adding a new runner on your local machine. If you stop the process after the step of running the `config.sh` script the runner will remain offline. This offline runner ensures that builds will not fail immediately and stay queued until there is an EC2 runner to pick it up.
Copy link
Contributor

Choose a reason for hiding this comment

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

What do you think about adding to link to this in Debugging section below? I ran into this because I missed it in the setup. It could help to have to called out.

@marcofranssen marcofranssen merged commit 01db901 into github-aws-runners:develop Apr 8, 2021
@marcofranssen marcofranssen deleted the improve-readme branch April 8, 2021 18:35
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.

4 participants