INNER CODE UNIT · Java
deployDir
dashbuilder/dashbuilder · scripts/release/dashbuilder-createAndDeploy.sh:35
deployDir=$WORKSPACE/deployDir
# (1) do a full build, but deploy only into local dir
# we will deploy into remote staging repo only once the whole build passed (to save time and bandwith)
mvn -B -e -U clean deploy -Dfull -Drelease -T1C -DaltDeploymentRepository=local::default::file://$deployDir -Dmaven.test.failure.ignore=true\
-Dgwt.memory.settings="-Xmx2g -Xms1g -Xss1M" -Dgwt.compiler.localWorkers=2
# (2) upload the content to remote staging repo
cd $deployDir
mvn -B -e org.sonatype.plugins:nexus-staging-maven-plugin:1.6.5:deploy-staged-repository -DnexusUrl=https://repository.jboss.org/nexus -DserverId=jboss-releases-repository\
-DrepositoryDirectory=$deployDir -DstagingProfileId=$stagingProfile -DstagingDescription="dashbuilder $newVersion" -DstagingProgressTimeoutMinutes=30
cd $WORKSPACE/dashbuilder
# pushes the release-branches to rhub.com:jboss-integration or github.com:dashbuilder [IMPORTANT: "push -n" (--dryrun) should be replaced by "push" when script is finished and will be applied]
if [ "$target" == "community" ]; then
git push origin $releaseBranch
else
git remote add upstream git@github.com:jboss-integration/dashbuilder.git
git push upstream $releaseBranch