June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22630) bzira/jiralint fails often because of missing pip install

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22630?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-22630. ------------------------------ Resolution: Done > bzira/jiralint fails often because of missing pip install > --------------------------------------------------------- > > Key: JBIDE-22630 > URL: https://issues.jboss.org/browse/JBIDE-22630 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.4.1.M1 > > > bzia/jiralint oftenn fails because pip are missing from the servers it runs on. > shuold limit the nodes it runs on or get pip installed more generally. > error from build mails > {code} > + pip install --upgrade --user bugzilla bugzillatools python-bugzilla jira pytz > Traceback (most recent call last): > File "/qa/services/hudson/.local/bin/pip", line 7, in <module> > from pip import main > ImportError: No module named pip > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19081) Use simpler Surefire include/exclude pattern in parent pom

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19081?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19081: ------------------------------------ [~fbricon] What's the status here? Ready to go live? More pondering? > Use simpler Surefire include/exclude pattern in parent pom > ---------------------------------------------------------- > > Key: JBIDE-19081 > URL: https://issues.jboss.org/browse/JBIDE-19081 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.4.x > > > 1. In JBDS9, use these new default patterns for Surefire to define which test classes to run/exclude: > {code} > include = *Test*, *Test, *TestCase > exclude = *Abstract* > {code} > 2. If that causes test failures because running incorrectly named > abstract stuff, they can refactor, add their own root pom overrides, use > a TestSuite, or use @Ignore in test classes. > 3. If the count of tests run suddenly DROPS because the pattern isn't > running the correct # of tests, they can add their own root pom > overrides, or use a TestSuite. > Ref: http://lists.jboss.org/pipermail/jbosstools-dev/2015-January/009688.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22672) PR builds failing because old, deleted dependency (4.60.0.Final-SNAPSHOT vs. 4.60.0.Final)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22672?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-22672: ---------------------------------------- {quote}I've just rebased but don't forget the root cause is that we had in time one artifact that has not been published{quote} Not exactly. The SNAPSHOT was published. Then the TP was released and Nexus policy is to remove the snapshots once the version is released. The root cause is that the parent pom usually needs to be updated just after TP release to consume the released version rather than snapshot. This was the missing step that Nick just did a few minutes ago. > PR builds failing because old, deleted dependency (4.60.0.Final-SNAPSHOT vs. 4.60.0.Final) > ------------------------------------------------------------------------------------------ > > Key: JBIDE-22672 > URL: https://issues.jboss.org/browse/JBIDE-22672 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Assignee: Mickael Istria > Fix For: 4.4.1.M1 > > > The new PR builds may fail because of a dependency (target platform) is not available on Nexus. Seems some versions have not been published. > See https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/DevStud... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22619) Decide strategy for fixversion targets in JIRA

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22619?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22619: ------------------------------------ Leaving a note to myself that we need to update https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/versio... to discuss AM* milestones instead of Alpha/Beta/CR milestones. Note: AM stands for any of these: A Milestone, Another Milestone, Agile Milestone, Alternative Modularity, Applied Monkeywork, Andersen Max, ... :D > Decide strategy for fixversion targets in JIRA > ---------------------------------------------- > > Key: JBIDE-22619 > URL: https://issues.jboss.org/browse/JBIDE-22619 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.4.1.M1 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.4.1.M1 > > > We need to decide the strategy for milestones / fixversions in JIRA. > One suggestion has been to align fixversions w/ sprint numbers, thus: > * 4.4.1.S116, 4.4.1.S117, 4.4.1.S118, 4.4.1.S119, ...? > instead of > * 4.4.1.Alpha1, 4.4.1.Alpha2, 4.4.1.Alpha3, 4.4.1.Beta1, ... ? > Questions/concerns: > * what do we do for unscheduled milestones (4.5.0.Alpha1, 11.0.0.Alpha1) and placeholders (4.4.1.Final, 10.0.1.GA) ? Should we just use Alpha1 or Final/GA until we know which sprint applies? > * whatever schema we adopt has to work with bzira and jiralint > * any other systems that parse JIRA for integration purposes? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22672) PR builds failing because old, deleted dependency (4.60.0.Final-SNAPSHOT vs. 4.60.0.Final)

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22672?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22672: ------------------------------------ I've just rebased but don't forget the root cause is that we had in time one artifact that has not been published > PR builds failing because old, deleted dependency (4.60.0.Final-SNAPSHOT vs. 4.60.0.Final) > ------------------------------------------------------------------------------------------ > > Key: JBIDE-22672 > URL: https://issues.jboss.org/browse/JBIDE-22672 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Assignee: Mickael Istria > Fix For: 4.4.1.M1 > > > The new PR builds may fail because of a dependency (target platform) is not available on Nexus. Seems some versions have not been published. > See https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/DevStud... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22672) PR builds failing because undeployed dependency

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22672?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22672: ------------------------------------ I've fixed the TP reference in the 4.4.0.Final-SNAPSHOT parent pom to point to 4.60.0.Final. But in master branch, Jeff, you should be using the 4.4.1.* parent pom. So please update your PR to be rebased against master, not 4.4.0.x. > PR builds failing because undeployed dependency > ----------------------------------------------- > > Key: JBIDE-22672 > URL: https://issues.jboss.org/browse/JBIDE-22672 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Assignee: Mickael Istria > Fix For: 4.4.1.M1 > > > The new PR builds may fail because of a dependency (target platform) is not available on Nexus. Seems some versions have not been published. > See https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/DevStud... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22672) PR builds failing because old, deleted dependency (4.60.0.Final-SNAPSHOT vs. 4.60.0.Final)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22672?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22672: ------------------------------- Summary: PR builds failing because old, deleted dependency (4.60.0.Final-SNAPSHOT vs. 4.60.0.Final) (was: PR builds failing because undeployed dependency) > PR builds failing because old, deleted dependency (4.60.0.Final-SNAPSHOT vs. 4.60.0.Final) > ------------------------------------------------------------------------------------------ > > Key: JBIDE-22672 > URL: https://issues.jboss.org/browse/JBIDE-22672 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Assignee: Mickael Istria > Fix For: 4.4.1.M1 > > > The new PR builds may fail because of a dependency (target platform) is not available on Nexus. Seems some versions have not been published. > See https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/DevStud... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22606) Document go_offline.groovy usage

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22606?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22606: -------------------------------- Sprint: devex #116 June 2016 > Document go_offline.groovy usage > -------------------------------- > > Key: JBIDE-22606 > URL: https://issues.jboss.org/browse/JBIDE-22606 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: project-examples > Affects Versions: 4.4.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > > The go_offline.groovy scripts currently lacks a detailed documentation, most notably on the example descriptor format requirements, we ought to fix that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22241) OpenShift Explorer: Cascade resource deletion

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22241?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22241: -------------------------------- Sprint: (was: devex #117 July 2016) > OpenShift Explorer: Cascade resource deletion > --------------------------------------------- > > Key: JBIDE-22241 > URL: https://issues.jboss.org/browse/JBIDE-22241 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: explorer, openshift_v3, ux > Fix For: 4.4.1.M1 > > > It would be nice to have a possibility to allow cascading deletion, deletion of related resource/resource managed by the resource which is about to be deleted. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22671) Hardcoded docker registry url contains a trailing space

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22671?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-22671: ----------------------------------- Fix Version/s: 4.4.1.M1 Story Points: 1 Sprint: devex #116 June 2016 Assignee: Martin Malina (was: Rob Stryker) > Hardcoded docker registry url contains a trailing space > ------------------------------------------------------- > > Key: JBIDE-22671 > URL: https://issues.jboss.org/browse/JBIDE-22671 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.0.Final > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 4.4.1.M1 > > > JBIDE-22441 added a hardcoded url for docker registry url for cdk/openshift. > But there is a trailing space in the url: > https://github.com/jbosstools/jbosstools-openshift/commit/132cea25129ffca... > That looks like an error? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2016