ci: Fix problem locating build component

[matrei]

The transitive build script dependency org.jfrog.buildinfo:build-info-extractor:2.3.2 cannot be found.

This commit adds Groovy's artifactory repo to the build script repositories, to make the build find the missing dependency.

The problem started occurring in Grails groovy-joint-workflow Github action.
Error message is:

:buildSrc:compileJava NO-SOURCE
:buildSrc:compileGroovy FROM-CACHE
:buildSrc:processResources NO-SOURCE
:buildSrc:classes UP-TO-DATE
:buildSrc:jar
:buildSrc:assemble
:buildSrc:compileTestJava NO-SOURCE
:buildSrc:compileTestGroovy NO-SOURCE
:buildSrc:processTestResources NO-SOURCE
:buildSrc:testClasses UP-TO-DATE
:buildSrc:test NO-SOURCE
:buildSrc:check UP-TO-DATE
:buildSrc:build

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring root project 'groovy'.
> Could not resolve all artifacts for configuration ':classpath'.
   > Could not find org.jfrog.buildinfo:build-info-extractor:2.3.2.
     Searched in the following locations:
       - https://repo.maven.apache.org/maven2/org/jfrog/buildinfo/build-info-extractor/2.3.2/build-info-extractor-2.3.2.pom
       - https://plugins.gradle.org/m2/org/jfrog/buildinfo/build-info-extractor/2.3.2/build-info-extractor-2.3.2.pom
       - https://oss.sonatype.org/content/repositories/snapshots/org/jfrog/buildinfo/build-info-extractor/2.3.2/build-info-extractor-2.3.2.pom
       - https://jitpack.io/org/jfrog/buildinfo/build-info-extractor/2.3.2/build-info-extractor-2.3.2.pom
     Required by:
         project : > org.jfrog.buildinfo:build-info-extractor-gradle:3.0.3

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.9.4/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 20s

[matrei]

Related: grails/grails-core#13573

[matrei]

I see now, that this caused another build dependency problem instead, in the "Distribute Groovy SNAPSHOT" workflow:
(should this workflow really be triggered on pull_request by the way?)

* What went wrong:
Execution failed for task ':groovy-ant:asciidoctor'.
> Could not resolve all files for configuration ':groovy-ant:asciidoctor'.
   > Could not find asciidoctorj-groovy-dsl-1.0.0.Alpha2.jar (org.asciidoctor:asciidoctorj-groovy-dsl:1.0.0.Alpha2).
     Searched in the following locations:
         https://groovy.jfrog.io/artifactory/libs-release/org/asciidoctor/asciidoctorj-groovy-dsl/1.0.0.Alpha2/asciidoctorj-groovy-dsl-1.0.0.Alpha2.jar

[paulk-asert]

Merged, Thanks!

The trigger on pull_request is intentional. It doesn't load the generated artifacts into the normal snapshot repo but rather builds artifacts which are available at the bottom of the action run log, e.g. scroll to the bottom of:

https://github.com/apache/groovy/actions/runs/10164041226

This makes it easier for us to test someone's PR when needed. Maybe "Generate Groovy SNAPSHOT" would be a better name than "Distribute Groovy SNAPSHOT".

P.S.: We have a different CI job that actually pushes real snapshot artifacts to the real snapshot repo.