Closed jwillemsen closed 4 years ago
I am for this. The fact that linting errors can hide in timeouts on Travis has caused issues before.
With github actions we get for free 20 concurrent jobs so this scales better (see https://help.github.com/en/actions/getting-started-with-github-actions/about-github-actions)
For taox11 we are using github actions for compilation, works very good, see https://github.com/RemedyIT/taox11/actions
What has to change in the GitHub repo configuration to get it to run the Action as part of the PR checks?
What has to change in the GitHub repo configuration to get it to run the Action as part of the PR checks?
There's an "Actions" page in the repo settings with radio switch to enable them.
What has to change in the GitHub repo configuration to get it to run the Action as part of the PR checks?
There's an "Actions" page in the repo settings with radio switch to enable them.
It is (and has been) set to "Enable local and third party Actions for this repository"
I didn't had to enable anything specifically for AXCIOMA/TAOX11/ACE
It is (and has been) set to "Enable local and third party Actions for this repository"
I didn't had to enable anything specifically for AXCIOMA/TAOX11/ACE
Yeah, I think it's enabled by default, but I wanted to give the option if Adam wanted to be sure.
Any plans to merge this?
Any plans to merge this?
Can we see the results of the GitHub actions here first? Or is it just not possible?
No idea how, I would expect it that github would trigger a new check
It did run om my branch, can you see it there?
It did run om my branch, can you see it there?
Sure, but that's not exactly what I'm asking about. If we are using this as a Check for each PR, then this very PR that we are working on should show it passing.
Maybe we should split this up so that this PR doesn't modify travis. Then once it's working we can come back and change travis.yml.
Also, this may be a good opportunity to rename the script(s) since fuzz has an actual meaning in the wider software world (https://en.wikipedia.org/wiki/Fuzzing)
Also, this may be a good opportunity to rename the script(s) since fuzz has an actual meaning in the wider software world (https://en.wikipedia.org/wiki/Fuzzing)
If we're not doing that here, I would like to do it in #1366.
See https://github.com/jwillemsen/OpenDDS/actions?query=workflow%3Afuzz