[
https://issues.jboss.org/browse/JBIDE-18762?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen updated JBIDE-18762:
----------------------------------------
Description:
Max:
{quote}
Couldn't we actually "encode" that in the description field on Jira so these
scripts and the ones in jiralint and whatsnew scripts could share that info ? {quote}
Nick:
{quote}
You mean add something like #jbosstools-aerogear into the description so we can parse it
over the REST API?
Yes, we could pull the description field as JSON:
https://issues.jboss.org/rest/api/2/component/12320840
{quote}
The above tiny script could then be called from other scripts to pull a parent project
name for any given properly declared JIRA component, in order to avoid maintenance like
this:
https://github.com/jbosstools/jbosstools-build-ci/pull/115
https://github.com/jbdevstudio/jbdevstudio-ci/pull/141
P
was:
Max:
{quote}
Couldn't we actually "encode" that in the description field on Jira so these
scripts and the ones in jiralint and whatsnew scripts could share that info ? {quote}
Nick:
{quote}
You mean add something like #jbosstools-aerogear into the description so we can parse it
over the REST API?
Yes, we could pull the description field as JSON:
https://issues.jboss.org/rest/api/2/component/12320840
{quote}
The above tiny script could then be called from other scripts to pull a parent project
name for any given properly declared JIRA component, in order to avoid maintenance like
this:
https://github.com/jbosstools/jbosstools-build-ci/pull/115
https://github.com/jbdevstudio/jbdevstudio-ci/pull/141
create python scriptlet to pull description field from a given
component's JSON in order to determine its parent project
------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-18762
URL:
https://issues.jboss.org/browse/JBIDE-18762
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Affects Versions: 4.2.0.Final
Reporter: Nick Boldt
Max:
{quote}
Couldn't we actually "encode" that in the description field on Jira so
these scripts and the ones in jiralint and whatsnew scripts could share that info ?
{quote}
Nick:
{quote}
You mean add something like #jbosstools-aerogear into the description so we can parse it
over the REST API?
Yes, we could pull the description field as JSON:
https://issues.jboss.org/rest/api/2/component/12320840
{quote}
The above tiny script could then be called from other scripts to pull a parent project
name for any given properly declared JIRA component, in order to avoid maintenance like
this:
https://github.com/jbosstools/jbosstools-build-ci/pull/115
https://github.com/jbdevstudio/jbdevstudio-ci/pull/141
P
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)