]
Nick Boldt commented on JBTIS-498:
----------------------------------
Your staging sites look way better now.
However, I see that you're including the same contents twice, which impacts
performance when loading the site.
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
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-sta...
https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discov...
And contrast that with the way the JBT & JBDS discovery jars are done:
http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis...
https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.ce...
(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/