August 2017 - jbosstools-issues - Jboss List Archives

[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. 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. 3. And, we should fire the jiralint-weekly to spam people w/ reminders of which JIRAs are unresolved for the code-frozen version. was: 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. 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. And, we should fire the jiralint-weekly to spam people w/ reminders of which JIRAs are unresolved for the code-frozen version. > 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. > 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. > 3. And, we should fire the jiralint-weekly to spam people w/ reminders of which JIRAs are unresolved for the code-frozen version. -- 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: ------------------------------- Fix Version/s: 4.5.1.AM1 (was: 4.5.0.Final) > 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-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 commented on JBIDE-24485: ------------------------------------ New matrix jobs are: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... Also created these two, but they'll probably be deleted when I'm sure the matrices work as expected: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > 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) update the list of nag emails to send on QE stage day

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24674?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24674: ------------------------------------ This worked great as a local python exec for 11.0.0.GA: {code} python -W ignore /tmp/jbt.github/jbosstools-build-ci/util/checkUnresolvedIssues.py --jbt 4.5.0.Final --jbt_NEXT 4.5.1.AM1 --ds 11.0.0.GA --ds_NEXT 11.1.0.AM1 --sprint "devex #135 July 2017" --sprint_NEXT "devex #136 August 2017" --jira https://issues.jboss.org --jirauser nickboldt --jirapwd PASSWORD [INFO] [1] Check devex #135 July 2017 + devex #136 August 2017, JBIDE 4.5.0.Final + JBDS 11.0.0.GA, for unresolved blockers/criticals + issues in NEXT sprint: move to NEXT sprint/milestone + Update https://issues.jboss.org/browse/JBIDE-24674 : update the list of nag emails to send on QE stage day ? [Y/n] n + Update https://issues.jboss.org/browse/JBIDE-24448 : Application wizard: error decoration is not removed when I correct "Custom Template" url to be valid ? [Y/n] y + Update https://issues.jboss.org/browse/JBIDE-24125 : Import wizard: adapt ITs to changes introduced in JBIDE-24048 ? [Y/n] y + Update https://issues.jboss.org/browse/JBIDE-23652 : Testing: coretests composite site not updated when publishing to /static and /stable ? [Y/n] n + Update https://issues.jboss.org/browse/JBDS-4493 : Virtualization detection never terminates on powershell version <= 2 ? [Y/n] y + Update https://issues.jboss.org/browse/JBDS-4482 : Create 'About' dialog to show most relevant information about installer ? [Y/n] y + Update https://issues.jboss.org/browse/JBDS-4408 : DevSuite 1.4 Installer document how to clean up after a failed install ? [Y/n] + Update https://issues.jboss.org/browse/JBDS-4404 : DevSuite 1.4 Installer hung during install waiting for cygwin ? [Y/n] [INFO] [2] Check JBIDE 4.5.0.Final + JBDS 11.0.0.GA, for unresolved issues NOT in the next sprint: move to .x + Update https://issues.jboss.org/browse/JBIDE-24485 : Refactoring: split release job into two pieces so jbosstools and devstudio can run in parallel to save time ? [Y/n] n + Update https://issues.jboss.org/browse/JBIDE-24447 : Look for minishift configuration in MINISHIFT_HOME ? [Y/n] + Update https://issues.jboss.org/browse/JBIDE-23590 : Integration tests global refactoring: org.jboss.tools.portlet.ui.bot.test ? [Y/n] + Update https://issues.jboss.org/browse/JBIDE-23583 : Integration tests global refactoring: org.jboss.tools.freemarker.ui.bot.test ? [Y/n] + Update https://issues.jboss.org/browse/JBIDE-23581 : Integration tests global refactoring: org.jboss.tools.examples.ui.bot.test ? [Y/n] + Update https://issues.jboss.org/browse/JBIDE-23576 : Integration tests global refactoring: org.jboss.tools.cdk.ui.bot.test ? [Y/n] + Update https://issues.jboss.org/browse/JBIDE-23575 : Integration tests global refactoring: org.jboss.tools.central.ui.bot.test ? [Y/n] + Update https://issues.jboss.org/browse/JBIDE-23569 : Integration tests global refactoring: org.jboss.tools.aerogear.ui.bot.test ? [Y/n] {code} Not sure I want to fully automate this with a job wrapper, as some JIRAs shouldn't be moved automatically. Maybe we just need to filter out those issues with labels = releasework ? > update the list of nag emails to send on QE stage day > ----------------------------------------------------- > > 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 > > > 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. > 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. > And, we should fire the jiralint-weekly to spam people w/ reminders of which JIRAs are unresolved for the code-frozen version. -- 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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24674?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24674: ------------------------------- Summary: automatically punt unresolved issues to .x or the next sprint (was: update the list of nag emails to send on QE stage day) > automatically punt unresolved issues to .x or the next sprint > ------------------------------------------------------------- > > 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 > > > 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. > 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. > And, we should fire the jiralint-weekly to spam people w/ reminders of which JIRAs are unresolved for the code-frozen version. -- 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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24674?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24674: ------------------------------- Fix Version/s: 4.5.1.AM1 (was: 4.5.0.Final) > automatically punt unresolved issues to .x or the next sprint > ------------------------------------------------------------- > > 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 > > > 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. > 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. > And, we should fire the jiralint-weekly to spam people w/ reminders of which JIRAs are unresolved for the code-frozen version. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24125) Import wizard: adapt ITs to changes introduced in JBIDE-24048

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24125?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24125: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = 4.5.1.AM1 and sprint 6391 > Import wizard: adapt ITs to changes introduced in JBIDE-24048 > ------------------------------------------------------------- > > Key: JBIDE-24125 > URL: https://issues.jboss.org/browse/JBIDE-24125 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Andre Dietisheim > Assignee: Josef Kopriva > Fix For: 4.5.1.AM1 > > > In JBIDE-24048 changes have been done to the import wizard. We should change the ITs to cover these changes. > @rhopp @bdshadow can you please test this since it's a rather larger change and provides changes in how it behaves? > * Validations were extended: > ** is the existing clone destination a git repo? > ** is the existing clone destination a clone of the source that is used in OpenShift? > * We now also ask the user if he wants to checkout the correct branch (the one that's used in OpenShift) in the existing git repo > * UI was slightly changed according to requests made in JBIDE-21935 > * We now also close the wizard dialog before executing the import. This should allow the user to continue working. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4493) Virtualization detection never terminates on powershell version <= 2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4493?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4493: ----------------------------- Fix Version/s: 11.1.0.AM1 (was: 11.0.0.GA) > Virtualization detection never terminates on powershell version <= 2 > --------------------------------------------------------------------- > > Key: JBDS-4493 > URL: https://issues.jboss.org/browse/JBDS-4493 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 11.0.0.AM2 > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 11.1.0.AM1 > > > Follow up on the mail thread about detection not finishing on win 7. > Namely methods from the Platform class that call powershell commands: > - isVirtualizationEnabled > - getHypervisorVersion > - isHypervisorEnabled > For some reason when called instead of erroring (since these commands dont work on older powershell) they don't terminate and block the detection. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4493) Virtualization detection never terminates on powershell version <= 2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4493?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4493: ---------------------------------- [checkUnresolvedIssues.py] Slip to fixversion = 11.1.0.AM1 and sprint 6391 > Virtualization detection never terminates on powershell version <= 2 > --------------------------------------------------------------------- > > Key: JBDS-4493 > URL: https://issues.jboss.org/browse/JBDS-4493 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 11.0.0.AM2 > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 11.1.0.AM1 > > > Follow up on the mail thread about detection not finishing on win 7. > Namely methods from the Platform class that call powershell commands: > - isVirtualizationEnabled > - getHypervisorVersion > - isHypervisorEnabled > For some reason when called instead of erroring (since these commands dont work on older powershell) they don't terminate and block the detection. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4482) Create 'About' dialog to show most relevant information about installer

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4482?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4482: ----------------------------- Fix Version/s: 11.1.0.AM1 (was: 11.0.0.GA) > Create 'About' dialog to show most relevant information about installer > ----------------------------------------------------------------------- > > Key: JBDS-4482 > URL: https://issues.jboss.org/browse/JBDS-4482 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 11.0.0.GA > Reporter: Denis Golovin > Assignee: Sudhir Verma > Labels: New_and_noteworthy, ui > Fix For: 11.1.0.AM1 > > > Dialog should contain: > 1. Application logo, name and version > 2. Link to documentation > 3. Link to release notes > 4. Link to documentation how to report issues > Dialog can be requested trough context menu 'About' and should show modal dialog with content listed above > Good Example is Atom editor About Page. -- 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