[jbosstools-issues] [JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo?

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-21012:
------------------------------------

I was halfway through sending an email to ci-issues@ to report that the unzip process wasn't working, when suddenly this appeared:

https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/freemarker/freemarker.site/1.5.100-SNAPSHOT/freemarker.site-1.5.100-SNAPSHOT-Alpha1-v20151026-1848-B310.zip-unzip/

But when I look elsewhere (in another browser) this is still empty:

https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/freemarker/freemarker.site/1.5.100-SNAPSHOT/

So... if I just use the BUILD_ALIAS we can have reusable URLs for all of a given branch (for any given BUILD_ALIAS & project.version combination).

So, I did that... updated the PR, and kicked a fresh build B311.

Results:

* *{color:green}This now exists:{color}* https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/freemarker/freemarker.site/1.5.100-SNAPSHOT/freemarker.site-1.5.100-SNAPSHOT-Alpha1.zip-unzip/

* *{color:red}This has vanished / is 404'd:{color}* https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/freemarker/freemarker.site/1.5.100-SNAPSHOT/freemarker.site-1.5.100-SNAPSHOT-Alpha1-v20151026-1848-B310.zip-unzip/

HOWEVER... seems there's about a 20 min lag between the Jenkins job and the unzip URL appearing. 

So... we can use this approach, but it's a bit slower than the lag on download.jboss.org. 

> Why do we deploy JBT components to Nexus snapshots repo?
> --------------------------------------------------------
>
>                 Key: JBIDE-21012
>                 URL: https://issues.jboss.org/browse/JBIDE-21012
>             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 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) ?



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