[
https://issues.jboss.org/browse/JBIDE-23768?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-23768:
------------------------------------
So, because the workflow is different for snapshots and releases, I've done this in
the parent pom jobs:
{code}
pom=${WORKSPACE}/sources/parent/pom.xml
pomVersion=$(grep "<version>" ${pom} | head -1 | sed -e
"s#.*<version>\(.\+\)</version>.*#\1#")
echo "pomVersion=${pomVersion}" > ${WORKSPACE}/env.properties # eg.,
4.4.4.Final
MVN="/qa/tools/opt/maven3-latest/bin/mvn
-Dmaven.repo.local=${WORKSPACE}/.repository/"
pushd ${WORKSPACE}/sources/parent/
if [[ ${pomVersion} == *"-SNAPSHOT" ]]; then
${MVN} deploy
else
${MVN} clean deploy -DskipRemoteStaging=true -DstagingDescription="[${JOB_NAME}
${BUILD_TIMESTAMP} ${BUILD_NUMBER}] :: ${pomVersion} :: deploy to local"
${MVN} nexus-staging:deploy-staged -DstagingDescription="[${JOB_NAME}
${BUILD_TIMESTAMP} ${BUILD_NUMBER}] :: ${pomVersion} :: deploy to stage + close"
${MVN} nexus-staging:release -DstagingDescription="[${JOB_NAME}
${BUILD_TIMESTAMP} ${BUILD_NUMBER}] :: ${pomVersion} :: release"
fi{code}
Publish tagged version of jboss tools parent pom to public
repository
---------------------------------------------------------------------
Key: JBIDE-23768
URL:
https://issues.jboss.org/browse/JBIDE-23768
Project: Tools (JBoss Tools)
Issue Type: Task
Components: build
Affects Versions: 4.4.2.Final, 4.4.3.AM1
Reporter: Aurélien Pupier
Assignee: Nick Boldt
Labels: releasework
Fix For: 4.4.3.Final
it will allow Fuse Tooling (and other dependent projects) to have tagged version of their
parent pom for tagged release.
i'm talking about org.jboss.tools:parent
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)