jonnybot0 commented on issue #213: URL: https://github.com/apache/groovy-geb/issues/213#issuecomment-2675418754
So, https://ci-builds.apache.org/job/Groovy/job/Geb%20to%20Groovy%20dev%20website/ _only_ publishes the Groovy website, right? And https://ci-builds.apache.org/job/Groovy/job/Geb%20snapshot%20build/ only publishes the snapshot build. Seems we still need a build to run the whole test suite that CircleCI is currently doing. GitHub actions is running `./gradlew -Pci --no-daemon --no-build-cache check -x rat `. I did a `--dry-run` of that task locally, just to see what all get runs and make sure it covers the same ground as the above checks. # check Command: `./gradlew --no-daemon --max-workers 4 --parallel -Pci module:check internal:check integration:check doc:site:check --continue` Only additional Gradle task this would run that the GitHub Actions check wouldn't was the `rat` task, which we run in `license-check.yml`. So that's covered by GitHub actions (`build-check.yml` and `license-check.yml` for `rat`). # manual Command: `./gradlew --no-daemon --max-workers 4 --parallel -Pci :doc:manual-snippets:check :doc:manual-snippets:fixtures:check :doc:manual-snippets:real-browser:check :doc:manual:build :doc:asciidoctor-extension:check` This runs `:doc:manual:assemble` and `:doc:manual:build`. While those are covered by the Geb website deployment, we should probably have them as GitHub actions to make sure we're not breaking the manual on a PR. I'll work on pushing up a PR to do that in a separate action. # dockerised-cross-browser This one definitely isn't running in GitHub Actions or Jenkins at the moment. I'll include that with the `manual` work. # local-cross-browser Also not run currently. Again, should be doable as a GH action. I'm going to assume based on that survey that probably the rest (non-ie, ie, and saucelabs) aren't run in anything we've got either. Seems like a good contribution for a Friday afternoon. :) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
