Skip to content

Commit ba941f9

Browse files
authored
Merge pull request #87 from olblak/master
Move PROMOTE_STAGING_MAVEN_ARTIFACTS_ARGS default declaration position
2 parents 704a2d4 + 05097dc commit ba941f9

File tree

2 files changed

+20
-5
lines changed

2 files changed

+20
-5
lines changed

README.adoc

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -404,6 +404,20 @@ Show pkcs12 information
404404

405405
More information about Jenkins Core maintainers and the different roles can be found in https://github.com/jenkinsci/jenkins/blob/master/docs/MAINTAINERS.adoc[MAINTAINERS].
406406

407+
== FAQ
408+
409+
**The stage release failed and we already push commits during the maven release.**
410+
411+
The problem here, is if we re-trigger the release job, we also update the release version again.
412+
So if the process fails on running `mvn release:stage`, then we can re-trigger it from inside the container as custom parameters are located in `settings-release.xml`.
413+
414+
```
415+
kubectl get pods -n release # Looking for the correct jenkins agent name
416+
kubectl exec -i -t -n release -c maven <pod_name alias jenkins agent> bash
417+
cd /home/jenkins/agent/workspace/core_release_master/release
418+
mvn -B -DstagingRepository=releases::default::https://repo.jenkins-ci.org/releases -s settings-release.xml --no-transfer-progress -Darguments=--no-transfer-progress release:stage
419+
```
420+
407421
== Miscellaneous
408422

409423
* Jenkins docker images are describe from https://github.com/jenkinsci/docker[jenkinsci/docker] repository and deployed to DockerHub as link:https://hub.docker.com/r/jenkins/jenkins[jenkins/jenkins]

utils/release.sh

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -43,11 +43,6 @@ source ""$(dirname "$(dirname "$0")")"/profile.d/$RELEASE_PROFILE"
4343
: "${RELEASE_GIT_STAGING_BRANCH:=$RELEASE_GIT_BRANCH}"
4444
: "${RELEASE_GIT_PRODUCTION_REPOSITORY:=$RELEASE_GIT_REPOSITORY }"
4545
: "${RELEASE_GIT_PRODUCTION_BRANCH:=$RELEASE_GIT_BRANCH}"
46-
# Following line will copy every items from source to destination,
47-
# keeps in mind that it won't delete from source and override on destination if already exist!.
48-
# It's wise to disable delete permission on destination repository
49-
# as explained here https://www.jfrog.com/confluence/display/JFROG/Permissions#Permissions-RepositoryPermissions
50-
: "${PROMOTE_STAGING_MAVEN_ARTIFACTS_ARGS:=item --mode copy --source $MAVEN_REPOSITORY_NAME --destination $MAVEN_REPOSITORY_PRODUCTION_NAME --url $MAVEN_REPOSITORY_URL --username $MAVEN_REPOSITORY_USERNAME --password $MAVEN_REPOSITORY_PASSWORD --search '/org/jenkins-ci/main' $(./utils/getJenkinsVersion.py --version)}"
5146

5247
export JENKINS_VERSION
5348
export JENKINS_DOWNLOAD_URL
@@ -62,6 +57,12 @@ export CREDENTIAL
6257
export GPG_PASSPHRASE_FILE
6358
export GPG_KEYNAME
6459

60+
# Following line will copy every items from source to destination,
61+
# keeps in mind that it won't delete from source and override on destination if already exist!.
62+
# It's wise to disable delete permission on destination repository
63+
# as explained here https://www.jfrog.com/confluence/display/JFROG/Permissions#Permissions-RepositoryPermissions
64+
: "${PROMOTE_STAGING_MAVEN_ARTIFACTS_ARGS:=item --mode copy --source $MAVEN_REPOSITORY_NAME --destination $MAVEN_REPOSITORY_PRODUCTION_NAME --url $MAVEN_REPOSITORY_URL --username $MAVEN_REPOSITORY_USERNAME --password $MAVEN_REPOSITORY_PASSWORD --search '/org/jenkins-ci/main' $(./utils/getJenkinsVersion.py --version)}"
65+
6566
if [ ! -d "$WORKING_DIRECTORY" ]; then
6667
mkdir -p "$WORKING_DIRECTORY"
6768
fi

0 commit comments

Comments
 (0)