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

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-20664:
------------------------------------

{quote}what is this issue actually fixing ? {quote}
This fixes the fact that we have temporarily added a Fuse connector to JBT & JBDS discovery sites as per the commits for JBIDE-20100 and I need to remove those before we go GA. I only put them there so that people would be able to SEE the UX in Central w/ this new "Not (Yet) Available" certId.

{quote}shouldn't publishing of IS discovery be separate from JBT core discovery ?{quote}
Yes, but I'd like to automate the release process so it's less error-prone. Thus, if there's a published version of the JBTIS/JBDSIS discovery plugins available in their /staging/ or /development/ URLs, I can collect those and include them in the CI builds that I create with http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-discovery_4.3.mars/ and http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-discovery_master/

{quote}sounds like we are now forcing a hard linkage{quote}
Nope. We're just making sure that whatever Paul has listed in ide-config.props for JBTIS/JBDSIS discovery plugins appears in the CI builds for JBT/JBDS so that when I move from CI to staging I can simply copy bits without having to go hunting for newer versions.

But yes, when Paul is ready to release his Alpha1 from /staging/ to /development/ he will still have to manually (or scriptomatically) copy those newer jars into our site, and update the directory.xml, as he did for JBDS 8.

{quote}mix in some other bugs{quote}

* JBTIS-497 - remove JBDS IS discovery jars from download.jboss.org; should only be published to devstudio.redhat.com
* JBTIS-498 - improve CI/snapshot/staging publishing of discovery jars to allow automatic self-cleaning


> 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)