August 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24850) For JBIDE 4.5.1.AM1: Prepare for 4.5.1.AM1 / 11.1.0.AM1 [foundation]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24850?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24850: ------------------------------------ bump up to parent pom version = 4.5.1.AM1-SNAPSHOT > For JBIDE 4.5.1.AM1: Prepare for 4.5.1.AM1 / 11.1.0.AM1 [foundation] > -------------------------------------------------------------------- > > Key: JBIDE-24850 > URL: https://issues.jboss.org/browse/JBIDE-24850 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: foundation > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.5.1.AM1 > > > For JBIDE 4.5.1.AM1 [foundation]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.5.1.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.1.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.1.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.70.2.Final > > {code} > mvn clean verify -Dtpc.version=4.70.2.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.70.2.Final > > {code} > mvn clean verify -Dtpc.version=4.70.2.Final > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for foundation task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- 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. 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. *TODO*: * filter out those issues with labels = releasework * if yesno is null, assume Y * new job: ** generate sprint creation reminder email (runs on last Thurs of sprint) ** generate sprint triage reminder email (last Thurs of sprint) ** trigger downstream job jiralint-weekly 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. 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. > 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. > *TODO*: > * filter out those issues with labels = releasework > * if yesno is null, assume Y > * new job: > ** generate sprint creation reminder email (runs on last Thurs of sprint) > ** generate sprint triage reminder email (last Thurs of sprint) > ** trigger downstream job jiralint-weekly -- 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 edited comment on JBIDE-24674 at 8/10/17 5:53 PM: ------------------------------------------------------------- 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. was (Author: nickboldt): 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. *TODO*: * filter out those issues with labels = releasework ? * if yesno is null, assume Y * generate sprint creation reminder emails (new job, runs every 3 weeks) * > 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-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 edited comment on JBIDE-24674 at 8/10/17 5:52 PM: ------------------------------------------------------------- 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. *TODO*: * filter out those issues with labels = releasework ? * if yesno is null, assume Y * generate sprint creation reminder emails (new job, runs every 3 weeks) * was (Author: nickboldt): 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 ? > 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-23575) Integration tests global refactoring: org.jboss.tools.central.ui.bot.test

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23575?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23575: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = 4.5.x > Integration tests global refactoring: org.jboss.tools.central.ui.bot.test > ------------------------------------------------------------------------- > > Key: JBIDE-23575 > URL: https://issues.jboss.org/browse/JBIDE-23575 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: central, integration, integration_tests > Fix For: 4.5.x > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.central.ui.bot.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23569) Integration tests global refactoring: org.jboss.tools.aerogear.ui.bot.test

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23569?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23569: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.Final) > Integration tests global refactoring: org.jboss.tools.aerogear.ui.bot.test > -------------------------------------------------------------------------- > > Key: JBIDE-23569 > URL: https://issues.jboss.org/browse/JBIDE-23569 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Gorkem Ercan > Labels: aerogear, integration, integration-test > Fix For: 4.5.x > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.aerogear.ui.bot.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23569) Integration tests global refactoring: org.jboss.tools.aerogear.ui.bot.test

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23569?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23569: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = 4.5.x > Integration tests global refactoring: org.jboss.tools.aerogear.ui.bot.test > -------------------------------------------------------------------------- > > Key: JBIDE-23569 > URL: https://issues.jboss.org/browse/JBIDE-23569 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Gorkem Ercan > Labels: aerogear, integration, integration-test > Fix For: 4.5.x > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.aerogear.ui.bot.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23652) Testing: coretests composite site not updated when publishing to /static and /stable

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23652?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23652: ------------------------------- Fix Version/s: 4.5.1.AM1 (was: 4.5.0.Final) > Testing: coretests composite site not updated when publishing to /static and /stable > ------------------------------------------------------------------------------------ > > Key: JBIDE-23652 > URL: https://issues.jboss.org/browse/JBIDE-23652 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.2.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: releasework > Fix For: 4.5.1.AM1 > > > Realized the other day that the composite*.xml files in http://download.jboss.org/jbosstools/static/neon/stable/updates/coretests/ and http://download.jboss.org/jbosstools/neon/stable/updates/coretests/ were not updated after 4.4.0.Alpha1... and probably should be part of what's updated when we release to /development, /stable, /static, etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23590) Integration tests global refactoring: org.jboss.tools.portlet.ui.bot.test

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23590?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23590: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = 4.5.x > Integration tests global refactoring: org.jboss.tools.portlet.ui.bot.test > ------------------------------------------------------------------------- > > Key: JBIDE-23590 > URL: https://issues.jboss.org/browse/JBIDE-23590 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: portal-gatein > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Peter Palaga > Labels: integration, integration_tests, portlet > Fix For: 4.5.x > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.portlet.ui.bot.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23583) Integration tests global refactoring: org.jboss.tools.freemarker.ui.bot.test

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23583?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23583: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.Final) > Integration tests global refactoring: org.jboss.tools.freemarker.ui.bot.test > ---------------------------------------------------------------------------- > > Key: JBIDE-23583 > URL: https://issues.jboss.org/browse/JBIDE-23583 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: freemarker > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Denis Golovin > Labels: freemarker, integration, integration_tests > Fix For: 4.5.x > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.freemarker.ui.bot.test -DskipTests=false > {code} -- 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