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

fix: Adding github URL to config.cmd #3842

Closed

Conversation

rfsmart-bcleary
Copy link

@rfsmart-bcleary rfsmart-bcleary commented Apr 9, 2024

#3737 This adds the variable gh_url, creates a SSM parameter containing the value from gh_url, and passes in the value of gh_url to the config.cmd call.

@rfsmart-bcleary rfsmart-bcleary changed the title Adding github URL to config.cmd fix: Adding github URL to config.cmd Apr 10, 2024
Copy link
Contributor

This pull request has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the Stale label May 11, 2024
@github-actions github-actions bot closed this May 21, 2024
@dhlaurap
Copy link

Hello, I am running into this issue, when could this be available in a release?

@dhlaurap
Copy link

I was just looking at this more closely and since multiple repos can use the runner would it be better if the webhook lambda stored the repo URL (from the webhook payload) into SSM for the runner to pick-up when running the user_data script?

@jonanderson10
Copy link

+1 I am seeing this issue as well

@dhlaurap
Copy link

dhlaurap commented Jun 20, 2024

I actually ended up fixing this by using a custom image and modifying the start-runner script by removing the .\config.cmd call and adding the --jitconfig argument to the run.cmd action like this:

$action = New-ScheduledTaskAction -WorkingDirectory "$pwd" -Execute "run.cmd" -Argument "--jitconfig $config"

From what I could gather, a similar fix went into the linux start-runner script but the Windows one was never fixed.

Adding the --url argument did not fix it when I was trying to figure this out btw, it started asking for the --token arg and then I got another error. Eventually found that --jitconfig is what I needed.

@ardole
Copy link

ardole commented Jun 25, 2024

@dhlaurap can you confirm which version of the github runner are you using please ?

this project is great but seems to suffer of a lack of testability (or i haven't found it), can somebody give tricks on how to quickly test the AMI without need to deploy the whole lambdas ? for instance start-runner.ps1 depends on a ssm-parameters and registration done in lambdas.

@dhlaurap
Copy link

Just confirmed it is currently running with the github runner version 2.317.0. I should mention we are using ephemeral runners with a custom AMI and a warming pool. Our setup is very similar to the "ephemeral" example but using windows runners.

Could it be that your $config object is missing something? I didn't have to change it but I am not sure how it's assembled since it comes from SSM.

@ardole
Copy link

ardole commented Jun 26, 2024

You are right, something was wrong with the $config that i generated manually to debug.
After new try i was able to make it working with the argument you suggested.

I opened a new issue #3950 and suggest a simple fix #3951

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants