[jbosstools-issues] [JBoss JIRA] (JBIDE-18772) Include publish steps in pom files

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071222#comment-13071222 ] 

Nick Boldt commented on JBIDE-18772:
------------------------------------

Still to do (could be in a second JIRA if people prefer):

The following job configs need to be changed to use this new deployment approach in Jenkins:

{code}
// NOTE: this check varies for each job
if [[ ${skipRevisionCheckWhenPublishing} == "true" ]] || [[ $(. ${WORKSPACE}/sources/util/checkLatestPublishedSHA.sh -s ${WORKSPACE}/sources/aggregate/${projectName}-site/target/fullSite/all/repo -t http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-build-sites.aggregate.${projectName}-site_${jbosstools_site_stream}/latest/all/repo/) == "true" ]]; then
  cd ${WORKSPACE}/sources/aggregate/${projectName}-site # or similar path for your project
  M2_HOME=/qa/tools/opt/apache-maven-3.2.5/
  $M2_HOME/bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=$WORKSPACE/.repository ${MAVEN_FLAGS}
else
  echo "Publish cancelled (nothing to do). Skip this check with skipRevisionCheckWhenPublishing=true"
  BUILD_DESCRIPTION="NOT PUBLISHED: UNCHANGED"
fi{code}

Jobs to fix (in _master and _4.3.mars):

{code}devstudio.product
jbosstools-browsersim-standalone
jbosstools-discovery
jbosstools-integration-stack-tests.aggregate
jbosstools-integration-tests.aggregate
jbosstools-locus.site
RedDeer_master {code}


> Include publish steps in pom files
> ----------------------------------
>
>                 Key: JBIDE-18772
>                 URL: https://issues.jboss.org/browse/JBIDE-18772
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: build
>            Reporter: Max Rydahl Andersen
>            Assignee: Mickael Istria
>            Priority: Critical
>             Fix For: 4.3.0.Beta1
>
>         Attachments: jbds-publish-to-snapshots.png
>
>
> instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses.
> suggestion:
> publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing.
> What this helps with is:
> a) can do changes to publish mechanism without affecting every past builds.
> b) more movable build system
> c) isolated testing possible 
>  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)