[
https://issues.jboss.org/browse/JBTIS-498?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBTIS-498:
----------------------------------
Re: #5 above, here's a PR, which should:
* put directory.xml in discovery-site/, not discovery-site/plugins/ and
* put plugins in discovery-site/plugins/, not plugins/
so that the site doesn't need massaging after building to be able to publish it:
https://github.com/jbosstools/jbosstools-integration-stack/pull/425
I haven't tested this locally yet - thought you might want to have a look.
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/
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)