[jbosstools-issues] [JBoss JIRA] (JBIDE-18846) create replacement page for cascade/swimlanes pages, to facilitate access to build, discovery, TP, and update site URLs

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-18846:
------------------------------------

For now, there's this:

https://github.com/jbosstools/jbosstools-devdoc/blob/master/list_of_projects.adoc

But yes, migrating this to yaml would be nice. Especially if we could generate this page from out of jjb/buildchow. :D

> create replacement page for cascade/swimlanes pages, to facilitate access to build, discovery, TP, and update site URLs
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-18846
>                 URL: https://issues.jboss.org/browse/JBIDE-18846
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: build, website
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 4.3.0.CR1
>
>
> Borrowing heavily from https://projects.eclipse.org/list-of-projects we need a new landing page for the aggregates, which list where to find such things as:
> builds (nightly, staging, dev, stable)
> updates (nightly, staging, dev, stable)
> Jenkins jobs
> discovery sites (nightly, staging, dev, stable)
> target platforms
> etc.
> And for each component, we can list:
> build
> update
> Jenkins job
> etc.
> The old cascade pages are here: http://download.jboss.org/jbosstools/builds/cascade/swimlanes_42.html
> Unsure whether generated HTML (via script) or simple .adoc is better for this.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)