-
Notifications
You must be signed in to change notification settings - Fork 56
use self hosted agent #388
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
Conversation
Apparently this is done through labels. If we get more machines we can consider changing this. |
Some lessons learned about self-hosted agents.
I'm having to install those from within the CI workflow or outside (as in the case of docker). |
I don't have permission on the link you included there. Looks like the doc build hung up for some reason. I never noticed the line ending thing before, thanks. I'll add the necessary .gitattributes commands for htis. |
I think that's only available for admins.
Sending you the IP and pem of the agent for you to connect to it. Nice thing about a self-hosted agent is the ability to debug on the machine. |
cf0bbce
to
e79e644
Compare
@akaszynski The CI is currently failing with the error |
8facdb1
to
2829ea6
Compare
The latest CI run is successful and the PR is now ready to merge. |
Use our self-hosted agent
pyfluent-ci-1
within our new pyansys-self-hosted self hosted agent group.Bonus
processor_count
to 4 on most of the examples.\n
.