Make Jenkins v3-nightly jobs like v2-nightly ?

[Tom Zeller]

Mostly Ian,

I think I will propose for Friday’s dev call that we make the v3-nightly Jenkins jobs like v2, in that we (a) drop the *-nightly-central-disabled jobs, and (2) add -Pcentral-disabled to the v3-nightly jobs.

My reason is that I think the pre-release testers[1] should grab IdPv3 snapshots from Nexus produced via those jobs, and I’d rather not deploy artifacts without -Pcentral-disabled if we don’t have to.

Originally, I think I created the *-central-disabled jobs configured with Maven’s ‘verify’ goal (instead of ‘deploy’) in order not block builds while working through the whole central-disabled process, which I think is well understood now, at least by me.

The end result will be one (well 5) less Jenkins jobs, and consistency between v2 and v3, although that importance seems to be less so, but the whole point is only publishing artifacts from our repo.

If okay, I’d like to make the change on Friday for the freeze (although, no, I am not fond of more changes).

Oh, and another outcome is that unknown/unblessed dependencies will block snapshot deployment / fail the job.

Thoughts ?

Thanks !

[1] Dave, Marvin, Nate, Walter, et al. ?