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

[Denis Golovin (JIRA)]

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

Denis Golovin commented on JBIDE-21120:
---------------------------------------

if we don't consume zips from nexus I don't see any reason to keep deploying them. 
We often deploy almost the same bit especially when only one p2 repo updated in multiple TP .target file, like it was with jetty. 

> 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)