[jbosstools-issues] [JBoss JIRA] (JBIDE-20664) JBT disco sites should include latest IS jars too

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBIDE-20664:
---------------------------------------------

if we pickup staging/development urls from IS then we would be relasing  that to our discovery site *before* it should so that just sounds very wrong.

Can you try explain how this will avoid us releasing discovery content to GA/Final that point to IS staging/devel sites ? 

The discovery site we add to our GA release should *not* point to  staging or development based discovery site - that is just wrong.


> JBT disco sites should include latest IS jars too
> -------------------------------------------------
>
>                 Key: JBIDE-20664
>                 URL: https://issues.jboss.org/browse/JBIDE-20664
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: discovery
>    Affects Versions: 4.3.0.CR1
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 4.3.0.CR1
>
>
> Now that IS has published some plugins, we can start aggregating them into the output of the JBT CI buils for discovery.central and discovery.earlyaccess.
> Here's where I found some jars:
> http://download.jboss.org/jbosstools/mars/staging/updates/integration-stack/discovery/
> http://download.jboss.org/jbosstools/mars/staging/updates/integration-stack/discovery/4.3.0.Alpha1a/plugins/org.jboss.tools.central.discovery.integration-stack.earlyaccess_4.3.0.Alpha1a-v20150909-1509-B418.jar
> http://download.jboss.org/jbosstools/mars/staging/updates/integration-stack/discovery/4.3.0.Alpha1a/plugins/org.jboss.tools.central.discovery.integration-stack_4.3.0.Alpha1a-v20150909-1509-B418.jar
> http://download.jboss.org/jbosstools/mars/staging/updates/integration-stack/discovery/9.0.0.Alpha1/plugins/com.jboss.jbds.central.discovery.integration-stack.earlyaccess_9.0.0.Alpha1-v20150722-1329-B106.jar
> http://download.jboss.org/jbosstools/mars/staging/updates/integration-stack/discovery/9.0.0.Alpha1/plugins/com.jboss.jbds.central.discovery.integration-stack_9.0.0.Alpha1-v20150722-1329-B106.jar
> https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discovery/
> https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discovery/9.0.0.Alpha1/plugins/com.jboss.jbds.central.discovery.integration-stack.earlyaccess_9.0.0.Alpha1-v20150821-1511-B127.jar
> https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discovery/9.0.0.Alpha1/plugins/com.jboss.jbds.central.discovery.integration-stack_9.0.0.Alpha1-v20150821-1511-B127.jar
> Not sure why there's JBDS IS jars on the JBT server, or why there's no Alpha1a for JBDS. [~pleacu] can you help me know which jars to collect into the JBT / JBDS sites? If you need help doing cleanup of old artifacts, let me know.
> Also, can you change your publishing process so that you're not dumping dozens of old jars into the same folder?
> 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)