[ https://issues.jboss.org/browse/JBIDE-11111?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-11111: ------------------------------- Summary: create Jenkins jobs to build + publish JBT & JBDS Core Central discovery plugins (was: move JBT Core Central discovery plugin out of Central component's pom.xml + create matching Jenkins jobs to build + publish) Issue Type: Task (was: Bug) Fix Version/s: 3.3.0.CR1 (was: 3.3.0.Beta1-soa) Description: Instead of tightly coupling the central discovery plugin [1] into the central component builds, we need a way to respin this single plugin (and matching jbosstools-directory.xml file) in case there are out-of-band changes needed (eg., remove JRebel because they release a newer version which breaks in Central). [1] https://anonsvn.jboss.org/repos/jbosstools/trunk/central/plugins/org.jbos... I would think that we would still want to build this plugin as part of the whole central component, but ALSO be buildable after the fact. was: Need an org.jboss.tools.central.discovery.soa-tooling plugin akin to [1] or [2] for SOA Tooling contributions to Central in JBoss Tools. [1] https://anonsvn.jboss.org/repos/jbosstools/trunk/central/plugins/org.jbos... [2] https://svn.jboss.org/repos/devstudio/trunk/product-soa/plugins/com.jboss... Location should either be a new project in JBT SVN repo (or even in github) or else contained in the JBT SOA aggregate site (http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/soa-site/) Assignee: Nick Boldt (was: Snjezana Peco) Affects Version/s: 3.3.0.Beta1 (was: 3.3.0.Beta1-soa) Component/s: Build/Releng updatesite -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11111?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-11111: ------------------------------------ Bump to 3.3.1 because that's the first time we'll need this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11111?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-11111: ------------------------------------ In what scenario? Describe the use case. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11111?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-11111: ------------------------------- Description: Instead of tightly coupling the central discovery plugin [1] into the central component builds, we need a way to respin this single plugin (and matching jbosstools-directory.xml file) in case there are out-of-band changes needed (eg., remove JRebel because they release a newer version which breaks in Central). [1] https://anonsvn.jboss.org/repos/jbosstools/trunk/central/plugins/org.jbos... Max would like that we NO LONGER build this plugin as part of the whole central component / aggregate sites, but ONLY be buildable separately. Also need to ensure that update sites no longer include central discovery plugins / *-directory.xml files so they won't be accidentally installed by a user who doesn't read instructions. was: Instead of tightly coupling the central discovery plugin [1] into the central component builds, we need a way to respin this single plugin (and matching jbosstools-directory.xml file) in case there are out-of-band changes needed (eg., remove JRebel because they release a newer version which breaks in Central). [1] https://anonsvn.jboss.org/repos/jbosstools/trunk/central/plugins/org.jbos... I would think that we would still want to build this plugin as part of the whole central component, but ALSO be buildable after the fact. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11111?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-11111: ------------------------------- Comment: was deleted (was: In what scenario? Describe the use case.) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11111?page=com.atlassian.jira.plugi... ] Douglas Palmer updated JBIDE-11111: ----------------------------------- Fix Version/s: 4.0.0.Alpha1-SOA (was: 3.3.0.CR1-SOA) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11111?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-11111: ------------------------------- Fix Version/s: 4.0.0.Alpha1-SOA -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11111?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-11111: ------------------------------------ Already have features - they're used to stick the plugins onto the sites, which is non-ideal when we need to update Central discovery plugin between releases. * https://github.com/jbosstools/jbosstools-central/tree/master/central/feat... * https://svn.jboss.org/repos/devstudio/trunk/product/features/com.jboss.jb... What we want instead are two jobs (or one with parameters) that will: a) build the plugin * org.jboss.tools.central.discovery_*.jar * com.jboss.jbds.central.discovery_*.jar b) publish plugin jar to standard location * http://download.jboss.org/jbosstools/updates/JBossTools-4.0.0.Beta2.core/... * https://devstudio.jboss.com/updates/6.0-staging/discovery/com.jboss.jbds.... c) (re)generate *discovery.xml to point at updated jar. This step must not simply overwrite the old file, but edit a single line in it so that SOA entry is not wiped out. * http://download.jboss.org/jbosstools/updates/development/juno/jbosstools-... * https://devstudio.jboss.com/updates/6.0-staging/devstudio-directory.xml * http://download.jboss.org/jbosstools/updates/stable/indigo/jbosstools-dir... * https://devstudio.jboss.com/updates/5.0/devstudio-directory.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11111?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-11111: ---------------------------------------- Main issue here is that we have interlinked versionned URLs. Maybe we should consider versionned URLs of Discovery, and have a symlink or copy for each version of JBT. So jbosstools-discovery.xml for 4.1.0.Alpha1 would point to a org.jboss.tools.central.discovery_4.1.0.Alpha1.jar that would be a copy or a link to a concrete version of the jar. That way, we can update discovery without affecting JBT, and if we want JBT to use the newer version, we only change the copy or the link on the site. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11111?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-11111: ------------------------------------ symlinks don't work consistently across devstudio.jboss.com and download.jboss.org; not a good idea. since the pointer in question is the xml file, we need only publish a new jar, and update the xml file. It's like a symlink but without the danger of it not being read correctly on the server(s). So, yeah, we already do what you're suggesting: multiple iterations of the discovery plugin, with a single master directory.xml file which refers to the latest/best one (for a given milestone/release). Sorry about the mixing thing -- figured since these weren't strictly plugins in the sense that they're installed into Eclipse/JBDS and that they don't have source (except for plugin.xml and some images) there'd be little or no legal complaint with them co-existing in the same repo. But of course IANAL. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11111?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-11111: ---------------------------------------- Fix Version/s: 4.1.0.Alpha1 (was: 4.0.0.Alpha1-SOA) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11111?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-11111 at 12/3/12 2:47 PM: ------------------------------------------------------------- New job which builds the plugin, generates the xml, and publishes them to a unique location from which they can then be used for testing or re-published to a release site (eg., on devstudio.jboss.com): https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio-6.1_trunk.... You'll notice I'm also archiving the artifacts in the workspace. Next up, doing the same thing but for the stable_branch, minus the refactoring/move of the content: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio-6.0_stable... (what a pain in the butt that was. Refactored source version WAY more efficient.) was (Author: nickboldt): New job which builds the plugin, generates the xml, and publishes them to a unique location from which they can then be used for testing or re-published to a release site (eg., on devstudio.jboss.com): https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio-6.1_trunk.... You'll notice I'm also archiving the artifacts in the workspace. Next up, doing the same thing but for the stable_branch, minus the refactoring/move of the content. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira