Open bytestack opened 5 years ago
Yeah, it's strange that it was not marked as failed. Seems like the exit code 0
was given. IMHO this is a bug either in gradle or the nebula-publishing-plugin, as we only execute ./gradlew publish
and expect to get exit code non-zero if anything fails.
Problem
The last two release train versions (6.6.18 and 6.6.17) are incomplete on maven central. According to the build pipeline there was a
SocketException
but the pipeline didn't fail.Truncated log output:
Proposal
Links