[
https://issues.jboss.org/browse/JBIDE-19025?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-19025 at 4/15/15 5:18 PM:
-------------------------------------------------------------
We now have 2 update sites for Central and 2 for Early Access:
* Central Update Site (contains only things from JBT)
** Job:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit...
** Output:
http://download.jboss.org/jbosstools/mars/snapshots/updates/central/master/
* Central TP (third party stuff)
** Job:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-centralta...
** Output:
http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/
* Early Access Update Site (contains only things from JBT)
** Job:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit...
** Output:
http://download.jboss.org/jbosstools/mars/snapshots/updates/earlyaccess/m...
* Early Access TP (third party stuff)
** Job:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-centralta...
** Output:
http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget/
This results in discovery sites for JBT Central, JBT EA, JBDS Central, and JBDS EA, built
here [1]:
http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis...
http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis...
https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.ce...
https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.ea...
So now when things change in JBT, they're rebuilt into an *update site* instead of
affecting a *target platform*, which will make our release process more efficient.
[1]
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-discovery...
was (Author: nickboldt):
We now have 2 update sites for Central and 2 for Early Access:
* Central Update Site (contains only things from JBT)
** Job:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit...
** Output:
http://download.jboss.org/jbosstools/mars/snapshots/updates/central/master/
* Central TP (third party stuff)
** Job:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-centralta...
** Output:
http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/
* Early Access Update Site (contains only things from JBT)
** Job:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit...
** Output:
http://download.jboss.org/jbosstools/mars/snapshots/updates/earlyaccess/m...
* Early Access TP (third party stuff)
** Job:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-centralta...
** Output:
http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget/
This results in discovery sites for JBT Central, JBT EA, JBDS Central, and JBDS EA:
http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis...
http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis...
https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.ce...
https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.ea...
So now when things change in JBT, they're rebuilt into an *update site* instead of
affecting a *target platform*, which will make our release process more efficient.
Separate JBT and JBDS Central and EA sites
------------------------------------------
Key: JBIDE-19025
URL:
https://issues.jboss.org/browse/JBIDE-19025
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: discovery
Affects Versions: 4.2.2.Final
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 4.3.0.Beta1
Currently, we have to repeat (and update very often) some JBT artifacts in the Central
.target files because JBDS needs them.
This adds some long steps to the JBT staging process (
https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui...
), whereas this is a JBDS need.
So we should split the content of Central/EA update sites for JBT and JBDS, and have them
separated in distinct .target files: a Central/EA couple for JBT and another Central/EA
couple for JBDS. JBDS only would add the necessary addition that are part of JBT but not
part of JBDS.
Since we're there, it would even be cleaner to have those artifacts in distinct repo,
so that JBDS wouldn't leak in JBT.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)