Enhance promotion job names and parameters

[HannesWell]

This PR enhances the Jenkins jobs in https://ci.eclipse.org/releng/job/Releng/ for the build promotion and publication first by renaming

• Releng/renameAndPromote to Releng/promoteBuild
• Releng/makeVisible to Releng/publishPromotedBuild

which I think is a bit more suitable.
@MohananRahul and maybe @merks or anybody else: What do you think?

And second by reducing the number of parameters of the (previous renameAndPromote) promoteBuild job as they are actually redundant and can be deirved from other values or data.

This still needs some testing but I would like to have this ready for M2 so that the new jobs can be used for that promotion, @MohananRahul. Or is M2 totally silent and no promotion to Milestone happen?

[HannesWell]

My testing was successful, so lets see if it also works in the real world.

[HannesWell]

@MohananRahul the new jobs are created at:

• https://ci.eclipse.org/releng/job/Releng/job/promoteBuild/
• https://ci.eclipse.org/releng/job/Releng/job/publishPromotedBuild/

Please use them when you do the M2 promotion tomorrow (your today).

I have not yet deleted the old jobs to keep them as a reference until the M2 promotion is done.

[HannesWell]

And in the future I plan to move more tasks into the two new jobs like sending the mails when the publication is completed or triggering the maven-deployment (only to Central staging, the final release still has to be done by hand) when a release is promoted.
And for M (and maybe also RC) promotion, the make visible job could be triggered automatically by the promote job already.

[MohananRahul]

@MohananRahul the new jobs are created at:

• https://ci.eclipse.org/releng/job/Releng/job/promoteBuild/
• https://ci.eclipse.org/releng/job/Releng/job/publishPromotedBuild/

Please use them when you do the M2 promotion tomorrow (your today).

I have not yet deleted the old jobs to keep them as a reference until the M2 promotion is done.

M2 Successfully promoted https://download.eclipse.org/eclipse/downloads/drops4/S-4.37M2-202507241800/

[HannesWell]

M2 Successfully promoted https://download.eclipse.org/eclipse/downloads/drops4/S-4.37M2-202507241800/

Great, thanks for reporting back.
Will delete the old jobs soon.

[MohananRahul]

@HannesWell, just to confirm - for the final release, can we use the DROP_ID as S-4.3XRC2-X-X for the promotion?
ie, S-4.37RC2-202508280630

[HannesWell]

for the final release, can we use the DROP_ID as S-4.3XRC2-X-X for the promotion?
ie, S-4.37RC2-202508280630

Yes, that's possible and I would even recommend to use the RC2(x) ID as we then don't have to disable any clean job to ensure the source I-build is present.

In fact you can promote all of I-builds, milestones or RCs to GA release (i.e. an empty CHECKPOINT). Only if you want to promote a non-empty CHECKPOINT (MX or RCX), you have to use an I-build as source.
In detail you find the pipelines code at:

eclipse.platform.releng.aggregator/JenkinsJobs/Releng/promoteBuild.jenkinsfile

Lines 31 to 40 in 8b27105

	if ((idMatcher = env.DROP_ID =~ /I(?<date>\d{8})-(?<time>\d{4})/).matches()) {
	assignEnvVariable('BUILD_LABEL', "${DROP_ID}")
	} else if ((idMatcher = env.DROP_ID =~ /S-(?<label>\d+\.\d+(\.\d+)?(M|RC)\d+[a-z]?)-(?<date>\d{8})(?<time>\d{4})/).matches()) {
	assignEnvVariable('BUILD_LABEL', idMatcher.group('label'))
	if ("${CHECKPOINT}") {
	error "Stable build DROP_ID=${DROP_ID} may only be promoted to release CHECKPOINT, which therefore must be empty: ${CHECKPOINT}"
	}
	} else {
	error "DROP_ID, ${DROP_ID}, did not match any expected pattern."
	}