[jbosstools-issues] [JBoss JIRA] (JBIDE-20141) Define which vanity URLs to use for publishing JBT/JBDS nightlies & dev sites

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-20141:
------------------------------------

{quote}I don't follow what you mean with index copied or symlinked. The html should just say something like "This is updatesite for JBoss Tools snapshot/development/release".{quote}

I was suggesting a page like this one: http://download.jboss.org/jbosstools/static/mars/development/updates/core/4.3.0.Beta1/index.html
Rather than a simple one like this: http://download.jboss.org/jbosstools/mars/development/updates/README.html

If you're happy w/ a static one rather than one that changes w/ every release, that's even easier for me. :)

{quote}
What content is it that you expect to be needing accurate/current ? The list of features/bundles ? just listing the one from from jboss tools core would not be correct anyway - it would just show what is in the raw core site.
{quote}

Good point - if you don't want the JBT feature listing (because the site's actually a composite of JBT+TP+Central+TP), then again, that makes the requirement to have a pretty HTML page simpler. 

{quote}
 I thought you said you wanted the core raw site to be browsable so you could navigate it to more easy check its content ? {quote}

No, I didn't mean that. But it doesn't matter. The point of this jira was to define which vanity URLs to use and what to locate in them. I've stopped arguing for what *I* want and instead will simply do what *you* want. :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.mars/
> ** ..
> * 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)