Github actions gradle manual#

This gives us cheap nightly builds of Golo. Pull-requests are being built just like you would expect, and the distribution is attached to the workflow run.With the new process that I recently put in place the whole deployment happens in GitHub Actions.

Github actions gradle manual#

This is clearly a manual process where empowering somebody else like Yannick who’s the project co-leader is harder than it should be.

I would push to Maven Central from Bintray using the synchronisation feature.

Bintray would sign all artifacts to meet the Maven Central requirements.

gradlew publish to upload to Bintray, with my credentials for the Gradle build being safely stored in ~/.gradle/gradle.properties on my computer Golo used to be released using a fairly manual process:

regular jar archives to be published on Maven Central.

a distribution zip archive of Golo with the libraries, documentation, execution scripts, samples, etc.

Golo needs to publish 2 types of release artifacts: 💡 You can get all the source code and automation from the Eclipse Golo project on GitHub. This has been a great occasion to re-consider how releases would be published.

We are converging towards a 3.4.0 release after 2 years of hiatus, and we are doing contributions at our own (leisure) pace. With my friends Yannick and Philippe we have decided to re-ignite the development of Eclipse Golo. Publishing from Gradle to Maven Central with GitHub Actions