[
https://issues.jboss.org/browse/JBIDE-20664?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-20664:
------------------------------------
To recap what was decided (again) in IRC (again) and further clarify the language above
(again) here's what I re-titled this issue:
*JBT & JBDS discovery sites (CI only) should include latest IS jars too so QE can
better see the combined site in one place*
The discovery site that I will produce using this mechanism will include:
* JBT directory.xml
* JBT Central discovery plugin
* JBT EA discovery plugin
(no change from before)
And, now, this NEW site will also include in addition to the artifacts above:
* JBT IS Central discovery plugin
* JBT IS EA discovery plugin
* updated directory.xml listing all 4 plugins
I will do the same for JBDS / JBDS IS.
These sites will look very similar to what Paul produces here:
http://download.jboss.org/jbosstools/mars/snapshots/builds/integration-st...
But they'll be:
* self-cleaning (instead of having 100s of near-identical plugins in the plugins/ folder)
* contain all 4 plugins in a single folder (rather than a URL reference)
This way, IF the IS plugins are found on a /development/ site (via the
ide-config.properties file), the resulting site can be compared to the previously released
discovery site and it'll be much easier to do a release without the danger of:
* getting the wrong IS plugin versions
* removing IS plugins (xml overwrite)
create discovery site for testing only that merges latest IS
discovery jars with Core discovery jars
----------------------------------------------------------------------------------------------------
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-sta...
http://download.jboss.org/jbosstools/mars/staging/updates/integration-sta...
http://download.jboss.org/jbosstools/mars/staging/updates/integration-sta...
http://download.jboss.org/jbosstools/mars/staging/updates/integration-sta...
http://download.jboss.org/jbosstools/mars/staging/updates/integration-sta...
https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discov...
https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discov...
https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discov...
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-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)