August 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24799) Testing: add tests to configuration/pom.xml to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final, dev instead of stable, 4.5.0.Final instead of 4.5)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24799?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24799: ------------------------------- Summary: Testing: add tests to configuration/pom.xml to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final, dev instead of stable, 4.5.0.Final instead of 4.5) (was: Testing: add tests to configuration/pom.xml to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final)) > Testing: add tests to configuration/pom.xml to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final, dev instead of stable, 4.5.0.Final instead of 4.5) > ------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-24799 > URL: https://issues.jboss.org/browse/JBIDE-24799 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM2 > > > * add tests to configuration/pom.xml [1] to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final) > [1] https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j... > Should also verify that development and stable are used correctly. > * For example, this is wrong: > https://github.com/jbosstools/jbosstools-download.jboss.org/commit/7e7662... > (we shouldn't have a dev milestone 4.5.0.Final taking priority over 4.5) > * And this it wrong too: > https://github.com/jbosstools/jbosstools-download.jboss.org/commit/7e7662... > (we shouldn't use the /development/ URLs for stable releases) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24799) Testing: add tests to configuration/pom.xml to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final, dev instead of stable, 4.5.0.Final instead of 4.5)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24799?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24799: ------------------------------- Priority: Critical (was: Major) > Testing: add tests to configuration/pom.xml to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final, dev instead of stable, 4.5.0.Final instead of 4.5) > ------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-24799 > URL: https://issues.jboss.org/browse/JBIDE-24799 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.5.1.AM2 > > > * add tests to configuration/pom.xml [1] to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final) > [1] https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j... > Should also verify that development and stable are used correctly. > * For example, this is wrong: > https://github.com/jbosstools/jbosstools-download.jboss.org/commit/7e7662... > (we shouldn't have a dev milestone 4.5.0.Final taking priority over 4.5) > * And this it wrong too: > https://github.com/jbosstools/jbosstools-download.jboss.org/commit/7e7662... > (we shouldn't use the /development/ URLs for stable releases) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24799) Testing: add tests to configuration/pom.xml to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24799?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24799: ------------------------------- Description: add tests to configuration/pom.xml to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final) * https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j... Should also verify that development and stable are used correctly. For example, this is wrong: https://github.com/jbosstools/jbosstools-download.jboss.org/commit/7e7662... (we shouldn't have a dev milestone 4.5.0.Final taking priority over 4.5) was: add tests to configuration/pom.xml to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final) * https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j... > Testing: add tests to configuration/pom.xml to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final) > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24799 > URL: https://issues.jboss.org/browse/JBIDE-24799 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM2 > > > add tests to configuration/pom.xml to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final) > * https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j... > Should also verify that development and stable are used correctly. > For example, this is wrong: > https://github.com/jbosstools/jbosstools-download.jboss.org/commit/7e7662... > (we shouldn't have a dev milestone 4.5.0.Final taking priority over 4.5) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24485) Refactoring: split release job into two pieces so jbosstools and devstudio can run in parallel to save time

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24485?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24485: ------------------------------- Sprint: devex #132 May 2017, devex #136 August 2017 (was: devex #132 May 2017) > Refactoring: split release job into two pieces so jbosstools and devstudio can run in parallel to save time > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24485 > URL: https://issues.jboss.org/browse/JBIDE-24485 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.5.1.AM1 > > > Should split release job [1] into two pieces so jbosstools and devstudio can run in parallel to save time. > [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24674) automatically punt unresolved issues to .x or the next sprint; send reminder emails about sprint creation

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24674?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24674: ------------------------------------ Done: * filter out those issues with labels = releasework, using --skipLabels * add --dry-run flag * support use of `export userpass=jirauser:jirapwd` to make running the script easier https://github.com/jbosstools/jbosstools-build-ci/commit/6efd5122df54b883... Also added the 'task' label to the N&N jiras, so they can be filtered out when using this script, and added userpass support to the N&N script too. https://github.com/jbosstools/jbosstools-build-ci/commit/ba3b432269adb7fe... > automatically punt unresolved issues to .x or the next sprint; send reminder emails about sprint creation > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24674 > URL: https://issues.jboss.org/browse/JBIDE-24674 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.5.1.AM1 > > > 1. We should send nag emails re: sprint triage when pushing QE stage build to remind people to move their issues to the next sprint, or resolve them. > * *NEW*: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > 2. We should also send a nag email to Jeff to create the new sprint versions in JIRA so that triage can actually occur, or else people won't be able to assign existing (slipped) issues to the forthcoming sprint. > * *NEW*: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > 3. And, we should fire the jiralint-weekly to spam people w/ reminders of which JIRAs are unresolved for the code-frozen version. > *TODO*: > * filter out those issues with labels = releasework, using --skipLabels > * add --dry-run flag > * support use of `export userpass=jirauser:jirapwd` to make running the script easier -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24674) automatically punt unresolved issues to .x or the next sprint; send reminder emails about sprint creation

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24674?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24674: ------------------------------- Description: 1. We should send nag emails re: sprint triage when pushing QE stage build to remind people to move their issues to the next sprint, or resolve them. * *NEW*: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... 2. We should also send a nag email to Jeff to create the new sprint versions in JIRA so that triage can actually occur, or else people won't be able to assign existing (slipped) issues to the forthcoming sprint. * *NEW*: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... 3. And, we should fire the jiralint-weekly to spam people w/ reminders of which JIRAs are unresolved for the code-frozen version. *TODO*: * filter out those issues with labels = releasework, using --skipLabels * add --dry-run flag * support use of `export userpass=jirauser:jirapwd` to make running the script easier was: 1. We should send nag emails re: sprint triage when pushing QE stage build to remind people to move their issues to the next sprint, or resolve them. * *NEW*: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... 2. We should also send a nag email to Jeff to create the new sprint versions in JIRA so that triage can actually occur, or else people won't be able to assign existing (slipped) issues to the forthcoming sprint. * *NEW*: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... 3. And, we should fire the jiralint-weekly to spam people w/ reminders of which JIRAs are unresolved for the code-frozen version. *TODO*: * filter out those issues with labels = releasework > automatically punt unresolved issues to .x or the next sprint; send reminder emails about sprint creation > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24674 > URL: https://issues.jboss.org/browse/JBIDE-24674 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.5.1.AM1 > > > 1. We should send nag emails re: sprint triage when pushing QE stage build to remind people to move their issues to the next sprint, or resolve them. > * *NEW*: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > 2. We should also send a nag email to Jeff to create the new sprint versions in JIRA so that triage can actually occur, or else people won't be able to assign existing (slipped) issues to the forthcoming sprint. > * *NEW*: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > 3. And, we should fire the jiralint-weekly to spam people w/ reminders of which JIRAs are unresolved for the code-frozen version. > *TODO*: > * filter out those issues with labels = releasework, using --skipLabels > * add --dry-run flag > * support use of `export userpass=jirauser:jirapwd` to make running the script easier -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24894) NPE caused by fix to JBIDE-24758

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24894?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24894: ------------------------------- Fix Version/s: 4.5.1.AM2 > NPE caused by fix to JBIDE-24758 > -------------------------------- > > Key: JBIDE-24894 > URL: https://issues.jboss.org/browse/JBIDE-24894 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.1.AM1 > Reporter: Rob Stryker > Fix For: 4.5.1.AM2 > > > it's possible the fix in JBIDE-24758 has created an NPE opportunity with substantial effects. While testing must go on, to isolate concrete broken usecases, the jira should be opened now. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24894) NPE caused by fix to JBIDE-24758

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24894?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-24894: ---------------------------------- Assignee: Rob Stryker > NPE caused by fix to JBIDE-24758 > -------------------------------- > > Key: JBIDE-24894 > URL: https://issues.jboss.org/browse/JBIDE-24894 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.1.AM1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.5.1.AM2 > > > it's possible the fix in JBIDE-24758 has created an NPE opportunity with substantial effects. While testing must go on, to isolate concrete broken usecases, the jira should be opened now. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24894) NPE caused by fix to JBIDE-24758

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24894?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-24894: ------------------------------------- In wildfly 11, local mode, the port section is botched. Won't show up. > NPE caused by fix to JBIDE-24758 > -------------------------------- > > Key: JBIDE-24894 > URL: https://issues.jboss.org/browse/JBIDE-24894 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.1.AM1 > Reporter: Rob Stryker > > it's possible the fix in JBIDE-24758 has created an NPE opportunity with substantial effects. While testing must go on, to isolate concrete broken usecases, the jira should be opened now. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24674) automatically punt unresolved issues to .x or the next sprint; send reminder emails about sprint creation

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24674?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24674: ------------------------------- Description: 1. We should send nag emails re: sprint triage when pushing QE stage build to remind people to move their issues to the next sprint, or resolve them. * *NEW*: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... 2. We should also send a nag email to Jeff to create the new sprint versions in JIRA so that triage can actually occur, or else people won't be able to assign existing (slipped) issues to the forthcoming sprint. * *NEW*: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... 3. And, we should fire the jiralint-weekly to spam people w/ reminders of which JIRAs are unresolved for the code-frozen version. *TODO*: * filter out those issues with labels = releasework was: 1. We should send nag emails re: sprint triage when pushing QE stage build to remind people to move their issues to the next sprint, or resolve them. * *NEW*: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... 2. We should also send a nag email to Jeff to create the new sprint versions in JIRA so that triage can actually occur, or else people won't be able to assign existing (slipped) issues to the forthcoming sprint. * *NEW*: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... 3. And, we should fire the jiralint-weekly to spam people w/ reminders of which JIRAs are unresolved for the code-frozen version. *TODO*: * filter out those issues with labels = releasework * if yesno is null, assume Y > automatically punt unresolved issues to .x or the next sprint; send reminder emails about sprint creation > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24674 > URL: https://issues.jboss.org/browse/JBIDE-24674 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.5.1.AM1 > > > 1. We should send nag emails re: sprint triage when pushing QE stage build to remind people to move their issues to the next sprint, or resolve them. > * *NEW*: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > 2. We should also send a nag email to Jeff to create the new sprint versions in JIRA so that triage can actually occur, or else people won't be able to assign existing (slipped) issues to the forthcoming sprint. > * *NEW*: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > 3. And, we should fire the jiralint-weekly to spam people w/ reminders of which JIRAs are unresolved for the code-frozen version. > *TODO*: > * filter out those issues with labels = releasework -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 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 August 2017