[jbosstools-issues] [JBoss JIRA] (JBIDE-18236) Produce better doc for project leads for how to build their component in Jenkins

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-18236:
------------------------------------

How about using the description field in JIRA for each component to list:

* that component's github repo (with prefix #)
* that component's associated jenkins jobs (comma separated)

Then we could pull the JSON via JIRA's REST API, filter out anything but the pertinent URLs and repo, and generate some pretty HTML in tabular form w/ all the links you need in one place. 

I won't bother to point out where the current job naming convention is documented because it's fairly straightforward if you go to https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/ and compare the prefixes to github repos and the suffixes to github branch names. If you want a new convention for the 4.3.x stream, now's the time to request it, BEFORE we create the Alpha1 jobs.

> Produce better doc for project leads for how to build their component in Jenkins
> --------------------------------------------------------------------------------
>
>                 Key: JBIDE-18236
>                 URL: https://issues.jboss.org/browse/JBIDE-18236
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: build
>    Affects Versions: 4.2.0.CR1
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 4.3.0.Alpha1
>
>
> Max wants a  page with links to all the /build pages for all the Jenkins jobs for a given stream, ie., 4.2.luna, 4.3.mars, master.
> This could be awestructed adoc, or just static HTML a la http://download.jboss.org/jbosstools/builds/cascade pages.



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)