[JBoss JIRA] (JBIDE-21363) create bugzilla importer for JIRA
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21363?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-21363:
------------------------------------
Now running in Jenkins:
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jiralint-b...
> create bugzilla importer for JIRA
> ---------------------------------
>
> Key: JBIDE-21363
> URL: https://issues.jboss.org/browse/JBIDE-21363
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Max Rydahl Andersen
> Fix For: 4.4.0.Alpha1
>
>
> Looking to create some kind of jiralint-like scraper tool to facilitate JIRA-like scrum/dashboard tracking of upstream projects, not located in JBoss JIRA.
> This scraper would:
> * [REQ1] find all bugzillas associated with a particular query, such as https://bugs.eclipse.org/bugs/buglist.cgi?status_whiteboard=RHT (18 issues)
> * [REQ2] generate a JIRA for each one found (no dupes should be created)
> * [REQ3] scrape several fields: product, component, version, target milestone, comment #0, summary, bug #
> * [REQ4] need a mapping table for Eclipse-prod:proj:component:fixversion-or-target-milestone to Neon milestone so we can set default values for affectsversion/fixversion/targetrelease in created JIRAs.
> * [REQ5] need a mapping table for Eclipse-prod:proj:component to ERT:component, eg., WTP:JSDT -> javascript
> * [REQ6] created test issues here: https://issues.stage.jboss.org/browse/ERT
> * [REQ7] run as a Jenkins job every 3 hours
> Generated JIRA example:
> {code}
> title: (scraped from summary) Support for smart Import Mechanism [Eclipse BZ 464535]
> issue link: (scraped from BZ ID#) https://bugs.eclipse.org/464535
> description: (scraped from BZ comment #0)
> affectsversion: (scraped from BZ version 1.6.0)
> fixversion: (scraped from BZ target milestone ---)
> component: (scraped from product:component = m2e:ui)
> labels: RHT, ERT
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBTIS-552) create install tests for JBTIS/JBDSIS
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-552?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBTIS-552 at 2/2/16 3:11 PM:
----------------------------------------------------------
So, to set this up, I need the list of URLs to use as the installation input, or INSTALL_PLAN:
{code}
# jbosstools_site_stream = master, 4.3.mars, 4.4.neon
# SET = central, earlyaccess
if [[ ${PROJECT} == "jbosstools" ]]; then
INSTALL_PLAN="http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-dis..."
elif [[ ${PROJECT} == "devstudio" ]]; then
INSTALL_PLAN="https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discovery.c..."
fi
{code}
Paul, can you provide URLs for the latest nightly/snapshot/CI builds of your input sites? We could either use the URLs you have in ide-config.properties, or to mirror what I'm doing above, you would use sites that include ONLY the IS content (not the IS content mixed in with JBT/JBDS via a composite site).
We could do BOTH types of tests (install just the stack; install stack + JBT or JBDS), so if you want both types of install test, we'll need TWO sets of URLs and TWO jobs.
was (Author: nickboldt):
So, to set this up, I need the list of URLs to use as the installation input:
{code}
# jbosstools_site_stream = master, 4.3.mars, 4.4.neon
# SET = central, earlyaccess
if [[ ${PROJECT} == "jbosstools" ]]; then
INSTALL_PLAN="http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-dis..."
elif [[ ${PROJECT} == "devstudio" ]]; then
INSTALL_PLAN="https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discovery.c..."
fi
{code}
Paul, can you provide URLs for the latest nightly/snapshot/CI builds of your input sites? We could either use the URLs you have in ide-config.properties, or to mirror what I'm doing above, you would use sites that include ONLY the IS content (not the IS content mixed in with JBT/JBDS via a composite site).
We could do BOTH types of tests (install just the stack; install stack + JBT or JBDS), so if you want both types of install test, we'll need TWO sets of URLs and TWO jobs.
> create install tests for JBTIS/JBDSIS
> -------------------------------------
>
> Key: JBTIS-552
> URL: https://issues.jboss.org/browse/JBTIS-552
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution, target-platform
> Affects Versions: 4.3.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Beta1
>
>
> Implement p2director install tests for JBTIS & JBDSIS to verify no missing deps in TP and no conflicting install deps (eg., different IS projects w/ conflicting singleton dependencies)
> Should be based on JBT/JBDS p2director install job [1].
> [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> Later we could also create a job that maps to the JBT/JBDS install-grinder job [2].
> [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBTIS-552) create install tests for JBTIS/JBDSIS
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-552?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBTIS-552:
----------------------------------
So, to set this up, I need the list of URLs to use as the installation input:
{code}
# jbosstools_site_stream = master, 4.3.mars, 4.4.neon
# SET = central, earlyaccess
if [[ ${PROJECT} == "jbosstools" ]]; then
INSTALL_PLAN="http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-dis..."
elif [[ ${PROJECT} == "devstudio" ]]; then
INSTALL_PLAN="https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discovery.c..."
fi
{code}
Paul, can you provide URLs for the latest nightly/snapshot/CI builds of your input sites? We could either use the URLs you have in ide-config.properties, or to mirror what I'm doing above, you would use sites that include ONLY the IS content (not the IS content mixed in with JBT/JBDS via a composite site).
We could do BOTH types of tests (install just the stack; install stack + JBT or JBDS), so if you want both types of install test, we'll need TWO sets of URLs and TWO jobs.
> create install tests for JBTIS/JBDSIS
> -------------------------------------
>
> Key: JBTIS-552
> URL: https://issues.jboss.org/browse/JBTIS-552
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution, target-platform
> Affects Versions: 4.3.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Beta1
>
>
> Implement p2director install tests for JBTIS & JBDSIS to verify no missing deps in TP and no conflicting install deps (eg., different IS projects w/ conflicting singleton dependencies)
> Should be based on JBT/JBDS p2director install job [1].
> [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> Later we could also create a job that maps to the JBT/JBDS install-grinder job [2].
> [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months