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

Nick Boldt updated JBTIS-498:
-----------------------------
    Attachment: JBDSIS-sites-contain-Alpha2-TP-and-Beta1-TP.png


OK, so that last glitch is fixed. But I just noticed that the JBDS IS discovery sites have BOTH Alpha2 and Beta1 TPs in them. I can't even.

!JBDSIS-sites-contain-Alpha2-TP-and-Beta1-TP.png!

> 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
>         Attachments: IS-updated-composite-sites-development.png, IS-updated-composite-sites-staging.png, JBDSIS-sites-contain-Alpha2-TP-and-Beta1-TP.png
>
>
> 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)