[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:all-tabpanel ]

Nick Boldt updated JBIDE-21120:
-------------------------------
    Description: 
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

Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the jbosstools-targetplatform & jbosstools-discovery root pom to prevent this waste of time/space?

  was:
Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo.

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

Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ?



> 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
> Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the jbosstools-targetplatform & jbosstools-discovery root pom to prevent this waste of time/space?



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