[jbosstools-issues] [JBoss JIRA] (JBTIS-498) improve CI/snapshot/staging publishing of discovery jars to allow automatic self-cleaning

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBTIS-498:
----------------------------------

Your staging sites look way better now. 

http://download.jboss.org/jbosstools/mars/staging/updates/integration-stack/discovery/4.3.0.Alpha2/
http://download.jboss.org/jbosstools/mars/staging/updates/integration-stack/discovery/4.3.0.Alpha2/earlyaccess/

https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discovery/9.0.0.Alpha2/
https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discovery/9.0.0.Alpha2/earlyaccess

However, I see that you're including the same contents twice, which impacts performance when loading the site.

https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discovery/9.0.0.Alpha2/compositeArtifacts.xml and https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discovery/9.0.0.Alpha2/earlyaccess/compositeArtifacts.xml include
* https://devstudio.redhat.com/9.0/stable/updates/core/9.0.0.GA/
* https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.51.0.Final/REPO/ and
* https://devstudio.jboss.com/9.0/stable/updates/

But https://devstudio.jboss.com/9.0/stable/updates/ includes 
* https://devstudio.redhat.com/9.0/stable/updates/core/9.0.0.GA/
* https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.51.0.Final/REPO/ and

So you only need to include the one URL, not all three.

Meanwhile, for JBTIS, you have the opposite problem. You only include JBT, but not the JBT TP. This may impact a user's ability to install something.

So instead of including http://download.jboss.org/jbosstools/mars/development/updates/core/ you should be using http://download.jboss.org/jbosstools/mars/development/updates/ (or really, the *STABLE* site http://download.jboss.org/jbosstools/mars/stable/updates/ since we went GA this week).

Hope that helps!



> improve CI/snapshot/staging publishing of discovery jars to allow automatic self-cleaning
> -----------------------------------------------------------------------------------------
>
>                 Key: JBTIS-498
>                 URL: https://issues.jboss.org/browse/JBTIS-498
>             Project: JBoss Tools Integration Stack
>          Issue Type: Feature Request
>          Components: distribution
>            Reporter: Nick Boldt
>            Assignee: Paul Leacu
>
> Would it be possible to change your publishing process so that you're not dumping dozens of old jars into the same folder? Surely you aren't staging ALL these? (We only stage to QE once or twice per milestone... CR1, CR1a.)
> Have a look here:
> http://download.jboss.org/jbosstools/mars/staging/updates/integration-stack/discovery/4.3.0.Alpha1/plugins/
> https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discovery/9.0.0.Alpha1/plugins/
> And contrast that with the way the JBT & JBDS discovery jars are done:
> http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-discovery.central_master/
> https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.central_master/
> (using rsync.sh, you get automated build folder cleanup every time you publish a new build, or you can force cleanup it with this job [1]).
> [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-cleanup/



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