[
https://issues.jboss.org/browse/JBIDE-20141?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-20141:
------------------------------------
{quote}in just a week seen cases of where having the public urls be separate from the
internal schemas are helpful.{quote}
I agree with the policy of "simple public URLs which provide a facade over longer
internal ones", but it's helpful to provide examples backing your thesis rather
than just stating it. When did you see this?
---
That aside, I suggested we remove these:
*
http://download.jboss.org/jbosstools/updates/nightly/master/
*
http://download.jboss.org/jbosstools/updates/nightly/mars/
*
http://download.jboss.org/jbosstools/updates/development/mars/
To clarify the original suggestion, I'm suggesting we replace them with these:
*
http://download.jboss.org/jbosstools/mars/snapshots/updates/core/master/ [or
something similar starting with /mars/snapshots/ ?]
*
http://download.jboss.org/jbosstools/mars/snapshots/updates/core/4.3.mars/ [or
something similar starting with /mars/snapshots/ ?]
*
http://download.jboss.org/jbosstools/mars/development/updates/
You said you like a & b, which sounds like "don't change anything" but
then you said "no, /updates/snapshots works too" so I'm not sure what the
net results is of these seemingly conflicting statements. Please clarify for those in the
audience who don't read minds well on Monday mornings. :D
Define which vanity URLs to use for publishing JBT/JBDS nightlies
& dev sites
-----------------------------------------------------------------------------
Key: JBIDE-20141
URL:
https://issues.jboss.org/browse/JBIDE-20141
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build, updatesite
Affects Versions: 4.3.0.Beta1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.3.0.Beta2
Today, we produce a lot of artifacts w/ every CI (snapshot), staging, development, &
stable build.
But sometimes, finding these artifacts can be a daunting task.
Below are some URLs where things can be found.
*CI builds / SNAPSHOTS / nightlies*
*
http://download.jboss.org/jbosstools/updates/nightly/master/ ->
../../mars/snapshots/builds/jbosstools-discovery.central_master/latest/all/repo/
(composite of Core + Central, *OLD URL PATTERN*)
*
http://download.jboss.org/jbosstools/updates/nightly/mars ->
../../mars/snapshots/builds/jbosstools-discovery.central_master/latest/all/repo/
(composite of Core + Central, *OLD URL PATTERN*)
*
http://download.jboss.org/jbosstools/mars/nightly/updates/ ->
../../mars/snapshots/builds/jbosstools-discovery.central_master/latest/all/repo/
(composite of Core + Central)
*
http://download.jboss.org/jbosstools/mars/snapshots/updates/ (individual projects'
update sites)
**
http://download.jboss.org/jbosstools/mars/snapshots/updates/core/master/
**
http://download.jboss.org/jbosstools/mars/snapshots/updates/core/4.3.mars/
**
http://download.jboss.org/jbosstools/mars/snapshots/updates/webtools/master/
**
http://download.jboss.org/jbosstools/mars/snapshots/updates/webtools/4.3....
** ..
*
http://download.jboss.org/jbosstools/mars/snapshots/builds/ (individual timestamped CI
builds)
*Staging Sites*
*
http://download.jboss.org/jbosstools/mars/staging/builds/
*
http://download.jboss.org/jbosstools/mars/staging/updates/
*Development Milestones*
*
http://download.jboss.org/jbosstools/updates/development/mars/ ->
../../mars/development/updates/ (*OLD URL PATTERN*)
*
http://download.jboss.org/jbosstools/mars/development/updates/ (composites &
content that isn't *static*)
*
http://download.jboss.org/jbosstools/static/mars/development/updates/ (actual update
sites, moved here for Akamai performance)
----
For JBDS, we follow the same pattern as above but use
https://devstudio.redhat.com/9.0/
instead of
http://download.jboss.org/jbosstools/mars/ ... but we also have a
/builds/installer/ folder because the public JBDS site now includes the standalone
installer:
*
https://devstudio.redhat.com/9.0/development/builds/installer/
Also, for JBDS we don't have to differentiate between /static/ and non-static
content, since Akamai set up the entire server to be mirrored to their servers.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)