-
Notifications
You must be signed in to change notification settings - Fork 50
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
Setup Cuda testing on Jenkins #78
Conversation
@sslattery The AoSoA test did not pass. I suggest we fix this in another PR. As you see if you follow this link the build hooks are in place and seem to work. Some adjustment might be needed in the Jenkins configuration (possibly the white list for the trigger) but I granted you and Christoph permissions to edit it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yet another CI system? Didn’t we wanted to install a gitlab runner on that machine?
GitLab does not mirror the PRs. |
Their idea of verification is that a developer review external PRs and push the sha on a local branch, which will trigger gitlab CI! |
It seems this broke like a month ago. |
We are back in business! |
And it seems gitlab.com triggers pull requests automatically now! |
Closing per #19 (comment) and disabling the job on the Jenkins server |
https://gitlab.com/gitlab-org/gitlab-ee/issues/5667 confuses me. I am not sure why your fork got triggered |
Codecov Report
@@ Coverage Diff @@
## master #78 +/- ##
======================================
Coverage 97.7% 97.7%
======================================
Files 17 17
Lines 1100 1100
======================================
Hits 1075 1075
Misses 25 25 Continue to review full report at Codecov.
|
Merged #80 that fixed the test failure into that branch. The build did not trigger on Jenkins though. Will look into it. |
Went to the GitHub webhooks settings and redelivered the payload. Build passed. Let me do a rebase or something similar to re-trigger and be 100% sure it works now. |
Build triggered. This is ready to merged. |
@junghans @sslattery NOTE the CI is only setup for PRs at this time. |
Note that all existing PRs will need to be rebased on these changes for Jenkins build to work.