On behalf of the Jenkins Events Team,
I would like to invite you to the “Jenkins & Java 10 Online Hackathon” which will take place from June 18th to 22nd.
We will be working together on Jenkins core and plugins in order
to find and fix compatibility issues, share experiences and have some fun.
Everybody is welcome to join, independently of their Jenkins experience and amount of time...
A couple of weeks ago, Tyler mentioned some
developer improvements in Essentials
that had been recently introduced:
the ability for
builds to get deployed automatically to an “Incrementals” Maven repository,
as described in
For a plugin maintainer, you just need to
turn on this support
and you are ready to both deploy individual Git commits from your repository
without the need to run heavyweight traditional Maven releases,
and to depend directly on similar commits...
This sort of slid under the radar in the middle of some bigger changes
for the JEP-202
reference implementation, so I wanted to call it out now. Arguably this could
deserve a retroactive JEP, though I would rather fold it into a JEP for
JENKINS-49651 (see below).
As of Jenkins 2.118, or plugin parent POM 3.7, you can mark any Java member
(class, method, constructor, field, or I suppose also...