[RelEng] Rename publishToMaven job to deployToMaven

to better match the Maven terminology.

Author: HannesWell

JenkinsJobs/Builds/build.jenkinsfile

@@ -316,7 +316,7 @@ spec:
 				}
 			}
 			steps {
-				build job: 'Releng/PublishToMaven', wait: false, parameters: [
+				build job: 'Releng/deployToMaven', wait: false, parameters: [
 					string(name: 'sourceRepository', value: "https://download.eclipse.org/eclipse/updates/${RELEASE_VER}-${BUILD_TYPE}-builds/${BUILD_IID}")
 				]
 			}

JenkinsJobs/Releng/FOLDER.groovy

@@ -2,36 +2,36 @@ folder('Releng') {
 	description('Jobs related to routine releng tasks. Some are periodic, some are "manual" jobs ran only when needed.')
 }
 
-pipelineJob('Releng/PublishToMaven'){
-	displayName('Publish to Maven')
+pipelineJob('Releng/deployToMaven'){
+	displayName('Deploy to Maven')
 	description('''\
 <p>
 This job uses the <a href="https://github.com/eclipse-cbi/p2repo-aggregator">CBI aggregator</a> to produce a Maven-compatible repository 
-with contents as specified by the <a href="https://github.com/eclipse-platform/eclipse.platform.releng.aggregator/blob/master/eclipse.platform.releng/publish-to-maven-central/SDK4Mvn.aggr">SDK4Mvn.aggr</a> and
-then publishes the artifacts for <code>Eclipse-Platform</code>, <code>JDT</code>, <code>Equinox</code> and <code>PDE</code> from the output:
+with contents as specified by the <a href="https://github.com/eclipse-platform/eclipse.platform.releng.aggregator/blob/master/eclipse.platform.releng/deploy-to-maven/SDK4Mvn.aggr">SDK4Mvn.aggr</a> and
+then deploys the artifacts for <code>Eclipse-Platform</code>, <code>JDT</code>, <code>Equinox</code> and <code>PDE</code> from the output:
 </p>
 <ul>
 <li>
-Snapshots are published to <a href="https://repo.eclipse.org/content/repositories/eclipse-snapshots/">https://repo.eclipse.org/content/repositories/eclipse-snapshots/</a>.
+Snapshots are deployed to <a href="https://repo.eclipse.org/content/repositories/eclipse-snapshots/">https://repo.eclipse.org/content/repositories/eclipse-snapshots/</a>.
 </li>
 <li>
-Releases are published to <a href="https://repo1.maven.org/maven2/org/eclipse/">Maven central</a> by publishing to a <a href="https://oss.sonatype.org/#stagingRepositories">staging repository</a>.
+Releases are deployed to <a href="https://repo1.maven.org/maven2/org/eclipse/">Maven central</a> by deploying to a <a href="https://oss.sonatype.org/#stagingRepositories">staging repository</a>.
 </li>
 </ul>
 <p>
 ''')
 	parameters { // Define parameters in job configuration to make them available even for the very first build after this job was (re)created.
 		stringParam('sourceRepository', null, '''\
-The URL of the source P2 repository to be published.<br>
-For a snapshot publication, the 4.x-I-Builds child repository of the specific build should be specified, e.g. 'https://download.eclipse.org/eclipse/updates/4.37-I-builds/I20250710-1800/'<br>
+The URL of the source P2 repository to be deployed.<br>
+To deploy a snapshot, the 4.x-I-Builds child repository of the specific build should be specified, e.g. 'https://download.eclipse.org/eclipse/updates/4.37-I-builds/I20250710-1800/'<br>
 <b>To deploy a <em>Release</em>, the corresponding release repository should be specified</b>, e.g. 'https://download.eclipse.org/eclipse/updates/4.36/R-4.36-202505281830/'<br>
-If left blank (not recommended), the latest I-build is published.
+If left blank (not recommended), the latest I-build is deployed.
 <ul>
 <li>
-Snapshots are published to <a href="https://repo.eclipse.org/content/repositories/eclipse-snapshots/">https://repo.eclipse.org/content/repositories/eclipse-snapshots/</a>.
+Snapshots are deployed to <a href="https://repo.eclipse.org/content/repositories/eclipse-snapshots/">https://repo.eclipse.org/content/repositories/eclipse-snapshots/</a>.
 </li>
 <li>
-Releases are published to <a href="https://repo1.maven.org/maven2/org/eclipse/">Maven central</a> by publishing to a <a href="https://oss.sonatype.org/#stagingRepositories">staging repository</a>.
+Releases are deployed to <a href="https://repo1.maven.org/maven2/org/eclipse/">Maven central</a> by deploying to a <a href="https://oss.sonatype.org/#stagingRepositories">staging repository</a>.
 </li>
 </ul>
 ''')
@@ -42,7 +42,7 @@ Releases are published to <a href="https://repo1.maven.org/maven2/org/eclipse/">
 			scm {
 				github('eclipse-platform/eclipse.platform.releng.aggregator', 'master')
 			}
-			scriptPath('JenkinsJobs/Releng/publishToMaven.jenkinsfile')
+			scriptPath('JenkinsJobs/Releng/deployToMaven.jenkinsfile')
 		}
 	}
 }

JenkinsJobs/Releng/publishToMaven.jenkinsfile renamed to JenkinsJobs/Releng/deployToMaven.jenkinsfile

@@ -26,7 +26,7 @@ pipeline {
 		stage('Aggregate Maven repository') {
 			steps {
 				sh '''#!/bin/bash -xe
-					FILE_SDK_AGGR="${WORKSPACE}/git-repo/eclipse.platform.releng/publish-to-maven-central/SDK4Mvn.aggr"
+					FILE_SDK_AGGR="${WORKSPACE}/git-repo/eclipse.platform.releng/deploy-to-maven/SDK4Mvn.aggr"
 
 					# Set the specified source repository
 					if [ -n "${sourceRepository}" ]; then
@@ -71,7 +71,7 @@ pipeline {
 			}
 		}
 		stage('Validate repository') {
-			// Tests that each to-be-published artifact can transitively resolve all its dependencies.
+			// Tests that each to-be deployed artifact can transitively resolve all its dependencies.
 			steps {
 				dir('repo-validation') { // Do the work in a clean folder without a pom.xml
 					sh '''#!/bin/bash -xe
@@ -83,7 +83,7 @@ pipeline {
 				}
 			}
 		}
-		stage('Publish artifacts to Maven-Central') {
+		stage('Deploy artifacts') {
 			matrix {
 				axes {
 					axis { // environment variable is also used by called scripts!
@@ -92,7 +92,7 @@ pipeline {
 					}
 				}
 				stages {
-					stage('Publish project to Maven'){
+					stage('Deploy project to Maven'){
 						environment {
 							SETTINGS = "/home/jenkins/.m2/settings-deploy-ossrh-${PROJECT == 'platform' ? 'releng': PROJECT}.xml"
 							// The location of the temporarily file that contains the secret file content
@@ -101,7 +101,7 @@ pipeline {
 							MAVEN_GPG_PASSPHRASE = credentials("secret-subkeys-${PROJECT == 'platform' ? 'releng': PROJECT}.asc-passphrase")
 						}
 						steps {
-							dir("publish-${PROJECT}"){
+							dir("deploy-${PROJECT}"){
 								sh '''#!/bin/sh -xe
 									# Copy configuration pom into clean directory to stop maven from finding the .mvn folder of this git-repository
 									cp "${WORKSPACE}/git-repo/eclipse-platform-parent/pom.xml" eclipse-parent-pom.xml

RELEASE.md

@@ -108,11 +108,11 @@ The actual steps to release
       - Change the DL_TYPE from S to R.  
       - TAG will be set to R as well, for example `R4_27` 
     - You can subscribe to [cross-project-issues](https://accounts.eclipse.org/mailing-list/cross-project-issues-dev) to get the notifications on Simrel releases.
-  * #### **Publish to Maven central**
-    - Publishing to maven should happen by at least Tuesday before the release since there is up to a 24 hour delay for the maven mirrors.
-    - Run the [Publish to Maven](https://ci.eclipse.org/releng/job/Releng/job/PublishToMaven/) job in Jenkins with the release build as `sourceRepository`.
+  * #### **Deploy to Maven central**
+    - Deploying to maven should happen by at least Tuesday before the release since there is up to a 24 hour delay for the maven mirrors.
+    - Run the [Deploy to Maven](https://ci.eclipse.org/releng/job/Releng/job/deployToMaven/) job in Jenkins with the release build as `sourceRepository`.
       - About a minute after triggering the job, Jenkins will ask for confirmation on the console, if the specified build should really be deployed to Maven-Central staging.
-    - Once that publish job has completed successfully, log into https://oss.sonatype.org/#stagingRepositories and close the Platform, JDT and PDE repositories.
+    - Once that deploy-job has completed successfully, log into https://oss.sonatype.org/#stagingRepositories and close the Platform, JDT and PDE repositories.
       - If you do not have an account on oss.sonatype.org for performing the rest of the release request one by creating an issue like https://issues.sonatype.org/browse/OSSRH-43870 to get permissions for platform, JDT and PDE projects and tag an existing release engineer to give approval.
   * **Contribute to SimRel**
     - If SimRel is not updated before the I-builds are cleaned up (specifically the build for RC2/GA) it will break. 

RELENG.md

@@ -29,7 +29,7 @@ Adding a job to Jenkins should be as easy as adding a new groovy file to git, bu
 
 * **No dashes in filenames**, it breaks JobDSL. If there was a `-` in the job name I changed it to `_` in the file name.
 * **Job Names**
-  - No spaces, this is just for the good of scripts etc. The job NAME is used in the url, but you can always add a `displayName` field if you want the job to appear with a more natural looking name on the page. See (Releng/PublishToMaven)[JenkinsJobs/Releng/FOLDER.groovy] as an example.
+  - No spaces, this is just for the good of scripts etc. The job NAME is used in the url, but you can always add a `displayName` field if you want the job to appear with a more natural looking name on the page. See (Releng/deployToMaven)[JenkinsJobs/Releng/FOLDER.groovy] as an example.
   - The folder needs to be part of the job name, otherwise Jenkins will just create the job at the dashboard level.
 * **job vs pipelineJob**
   - Anything that can build on a regular jenkins node or via an available lable uses the (job)[https://jenkinsci.github.io/job-dsl-plugin/#path/job] template.

eclipse.platform.releng/publish-to-maven-central/.project renamed to eclipse.platform.releng/deploy-to-maven/.project

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <projectDescription>
-	<name>publish-to-maven-central</name>
+	<name>deploy-to-maven</name>
 	<comment></comment>
 	<projects>
 	</projects>