[jbosstools-issues] [JBoss JIRA] (JBIDE-21120) Why do we deploy TP zips to Nexus snapshots repo?

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-21120:
------------------------------------

Reverted previous changes since Mickael's solution is easier/cleaner and more "maven-friendly".

https://github.com/jbosstools/jbosstools-target-platforms/commits/4.60.x

Here's the job config change:

https://github.com/jbdevstudio/jbdevstudio-ci/commit/0349c99e890e1c1b06dd065bb65397c26a9a397c

Which results in this order of 8 steps (5 mvn, 3 bash):

* checkout correct branch of code based on the input VERSION = 4.51.1.CR1-SNAPSHOT or 4.51.2.Beta1-SNAPSHOT or 4.60.0.Alpha1-SNAPSHOT
** git checkout ${branch}
* push multiple .target to nexus
** mvn clean deploy -U -e -f multiple/pom.xml 
* resolve TP to get site + zip
** mvn install -U -Pmultiple2repo -e  -f multiple/pom.xml
* publish the full target platform + zip to dl.jb.o / ds.rh.c
** rsync ...
* since unified .target depends on having published new bits to dl.jb.o / ds.rh.c, we can now build and deploy that
**  mvn clean deploy -U -e -f unified/pom.xml 
* fetch dependencies for doing install tests
** org.jboss.tools.installation-tests:scripts
** org.jboss.tools.releng:jbosstools-releng-publish
* now, do install tests (which might fail if the Eclipse JEE bundle contains incompatible versions of something in the TP (eg., we include a newer egit or m2e)
** getAndInstallEclipse.groovy ...
** installFromTarget.sh ...


> Why do we deploy TP zips to Nexus snapshots repo?
> -------------------------------------------------
>
>                 Key: JBIDE-21120
>                 URL: https://issues.jboss.org/browse/JBIDE-21120
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build, updatesite
>    Affects Versions: 4.3.0.Final, 4.4.0.Alpha1
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> Currently, we deploy our TP update sites to the JBoss Nexus snapshots repo.
> {code}
> Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/targetplatforms/jbdevstudio-multiple/4.51.2.Beta1-SNAPSHOT/jbdevstudio-multiple-4.51.2.Beta1-20151120.225728-3.pom
> Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/targetplatforms/jbdevstudio-multiple/4.51.2.Beta1-SNAPSHOT/maven-metadata.xml
> Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/targetplatforms/jbdevstudio-multiple/maven-metadata.xml
> Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/targetplatforms/jbdevstudio-multiple/4.51.2.Beta1-SNAPSHOT/jbdevstudio-multiple-4.51.2.Beta1-20151120.225728-3-jbdevstudio-multiple.target
> Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/targetplatforms/jbdevstudio-multiple/4.51.2.Beta1-SNAPSHOT/maven-metadata.xml
> Uploading: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/targetplatforms/jbdevstudio-multiple/4.51.2.Beta1-SNAPSHOT/jbdevstudio-multiple-4.51.2.Beta1-20151120.225728-3.zip
> ...
> {code}
> But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just:
> * eat disk space in Nexus
> * consume time/resources in Jenkins
> So, why don't we set a custome deployment strategy (eg., akin to *maven.deploy.skip=true*) in the jbosstools-targetplatform & jbosstools-discovery root pom to prevent this waste of time/space? Then we can just deploy the .target files, not the zips. 
> This would certainly speed up builds, which currently take 30-60 mins per TP build. 



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)