Le 17/06/2024 à 08:16, Andreas Tille a écrit :
The problems Pierre described with upgrading Gradle might be some
indication that some more skilled packagers could help.
We would need a core Gradle and/or Kotlin developer to tackle this
issue, but I don't think they are interested in spending days or weeks
figuring out an upgrade path for old versions of Gradle.
I intentionally linked to some response I once received[2] which says:
"java-team have pipelines disabled by default". I consider this a
really unfortunate blocker to simply switch on Salsa CI. If there is no
policy to use Salsa CI or not please make sure developers will not need
extra hurdles to switch it on.
If I remember well, the repository creation script [1] for the Java team
disables the CI feature, because at the time it was written the Salsa CI
wasn't implemented yet.
Regarding the "IRC spam": IMHO this is not a Salsa CI feature but
rather the KGB bot you can switch of.
I'd like KGB to report commits but not CI builds, if that's possible.
For me as someone who barely
speaks any Java and just crossing fingers that the upstream build system
works flawlessly it helps a lot to have some build log available online
very easily which I can link to in some mail to the Debian Java list to
get further help. This might be true for potential newcomers as well.
That's indeed a convenience, but with an energy cost and a CO2 impact on
the planet.
Emmanuel Bourg
[1]
https://salsa.debian.org/java-team/pkg-java-scripts/-/blob/master/setup-salsa-repository
