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

Register GPU machine for Cuda builds through gitlab.com #19

Closed
junghans opened this issue Oct 3, 2018 · 5 comments
Closed

Register GPU machine for Cuda builds through gitlab.com #19

junghans opened this issue Oct 3, 2018 · 5 comments
Assignees
Labels
blocked Blocked by another necessary change

Comments

@junghans
Copy link
Member

junghans commented Oct 3, 2018

Here is how you register a runner:
https://docs.gitlab.com/runner/register/

then we need to modify our .gitlab-ci.yml to use that runner on bare metal.

@dalg24
Copy link
Collaborator

dalg24 commented Mar 7, 2019

#78 proposes Cuda testing using a ORNL Jenkins CI server and slave machine with a Volta GPU.

@junghans suggested we register a specific gitlab runner instead. I did not realize GitLab was able to mirror GitHub PRs initiated from forks (instead of a branch on the main repo). I am fine closing #78 and setting up a new entry in the .gitlab-ci.yml and register a new runner.

@sslattery What do you think?

@sslattery
Copy link
Collaborator

sslattery commented Mar 7, 2019

If it does what we want it to do, is just as easy to maintain as the Jenkins route, and is consistent with the current CI then I am fine closing #78

@dalg24
Copy link
Collaborator

dalg24 commented Mar 12, 2019

Reopened #78 and closed #79 since GitLab CI does not support PRs initiated from GH forks at the moment. We got confused because the mirroring on GitLab on manually reset and all PRs opened at that time triggered a build.

@dalg24
Copy link
Collaborator

dalg24 commented Mar 12, 2019

I disabled the gitlab-runner with the GPU but I can restart it if we reopen #78 in the future.

@dalg24
Copy link
Collaborator

dalg24 commented Mar 12, 2019

I recommend we close this issue and move it to the backlog. @junghans ?

@junghans junghans added the blocked Blocked by another necessary change label Mar 12, 2019
junghans pushed a commit to sslattery/Cabana that referenced this issue May 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked Blocked by another necessary change
Projects
None yet
Development

No branches or pull requests

3 participants