This message was deleted.
# community-supports
Slackbot
10/21/2022, 4:07 PMThis message was deleted.
c
Chris Lee
10/21/2022, 4:13 PMhard to diagnose with out a reproducible minimal project. The failing project possibly isn’t using the same settings.gradle that defines the versions.
✅ 1
Chris Lee
10/21/2022, 4:17 PMIt may be worth reviewing the working directories used to execute each build vs locations of
settings.gradle✅ 1
Chris Lee
10/21/2022, 4:18 PMParticularly this:
Gradle supports arbitrary physical layouts for a multi-project build, but for such arbitrary layouts you need to execute the build from the directory where the settings file is located.
👀 1
e
Eric Kolotyluk
10/21/2022, 4:26 PMAs is often the case, a reproducible minimal project can be very difficult to construct, and because of intellectual property issues, I cannot just share everything...
Yes, I will have to dig in and understand our GitLab pipeline more than I wanted to...
My personal philosophy is to put as much build logic in the build tools like Maven, SBT, Gradle, etc. However, this seems antithetical to most build pipeline engineers who believe their scripts are always better than the build tools... as they would rather not edit files like
setting.gradlebuild.gradlec
Chris Lee
10/21/2022, 4:27 PMperhaps start with an empty representative project layout (no source, just build files) and work from there to narrow things down.
e
Eric Kolotyluk
10/21/2022, 4:29 PMI think I need to understand the YAML files in the pipeline that are launching Gradle, because they are using the same gradle files, but there may be some other contextual differences...
c
Chris Lee
10/21/2022, 4:29 PMthis should be reproducible w/o the build pipeline by executing the same gradle commands (e.g.
./gradlew build✅ 1
e
Eric Kolotyluk
10/21/2022, 4:30 PMokay... will start there...
v
Vampire
10/21/2022, 4:31 PMMaybe one pipeline injects some init scripts that break things
c
Chris Lee
10/21/2022, 4:31 PMcould be. also worth checking if there are multiple settings.gradle files in play.
Chris Lee
10/21/2022, 4:32 PMinit scripts would be evident on the Gradle command line, or perhaps in scripting that places files in certain locations.
v
Vampire
10/21/2022, 4:33 PMAlso in the info (or latest in the debug) logs they should be mentioned
Vampire
10/21/2022, 4:33 PMIf possible you could also share a build scan
c
Chris Lee
10/21/2022, 4:34 PMah yea, good point.
e
Eric Kolotyluk
10/21/2022, 4:37 PMI will try to see if I can reproduce locally first, as Chris suggests...
👌 1
Eric Kolotyluk
10/21/2022, 6:53 PMOkay, problem solved... the same
build.gradlesettings.gradlesettings.gradlebuild.gradle👌 1
c
Chris Lee
10/21/2022, 6:54 PMGlad this worked out 🍻
🙌 1
e
Eric Kolotyluk
10/21/2022, 6:57 PMI have sure learned a lot about gradle here... I am promoting this Slack site at work...
👌 1
v
Vampire
10/22/2022, 12:19 AMYeah, having a project part of multiple builds is seldomly a good idea. Usually a project should always only belong to one build and if you need it in another build you should use composite builds.
✅ 1
3 Views