February 2017 - jbosstools-issues

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

by Jeff MAURY (JIRA)

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

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23626) Preferences: link to download oc may lead me to try to use an incompatible oc binary for my origin/CDK

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23626?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23626: ------------------------------- Fix Version/s: 4.4.4.AM2 (was: 4.4.3.Final) > Preferences: link to download oc may lead me to try to use an incompatible oc binary for my origin/CDK > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-23626 > URL: https://issues.jboss.org/browse/JBIDE-23626 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Andre Dietisheim > Labels: oc_binary, preferences > Fix For: 4.4.4.AM2 > > > oc 1.4, which is available from github is not compatible with the lastest CDK 2.3 (it's only compatible oc 1.3). Futhermore there are specific enterprise oc binaries which follow the OSE versioning scheme 3.2, 3.3 etc. making it hard for the user to know what oc he should use. > Our preferences offer a link to the github releases but there's no info nor logic that makes sure that the user will use compatible combinations (oc 1.4 with CDK 2.3, oc 1.2 with CDK 2.3 etc.) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23676) Try openshift integration tests with CDK3/minishift

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23676?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23676: ------------------------------- Affects Version/s: 4.4.3.AM2 (was: 4.4.4.AM2) > Try openshift integration tests with CDK3/minishift > --------------------------------------------------- > > Key: JBIDE-23676 > URL: https://issues.jboss.org/browse/JBIDE-23676 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, openshift > Affects Versions: 4.4.3.AM2 > Reporter: Radim Hopp > Assignee: Radim Hopp > Fix For: 4.4.4.AM2 > > > As we now have CDK3 alpha release in our hands, integration tests should be against it. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23676) Try openshift integration tests with CDK3/minishift

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23676?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23676: ------------------------------- Fix Version/s: 4.4.4.AM2 (was: 4.4.3.Final) > Try openshift integration tests with CDK3/minishift > --------------------------------------------------- > > Key: JBIDE-23676 > URL: https://issues.jboss.org/browse/JBIDE-23676 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, openshift > Affects Versions: 4.4.3.AM2 > Reporter: Radim Hopp > Assignee: Radim Hopp > Fix For: 4.4.4.AM2 > > > As we now have CDK3 alpha release in our hands, integration tests should be against it. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23660) CDK Server adapter should have an option to configure stop command

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23660?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23660: ------------------------------- Fix Version/s: 4.4.4.AM2 (was: 4.4.3.Final) > CDK Server adapter should have an option to configure stop command > ------------------------------------------------------------------ > > Key: JBIDE-23660 > URL: https://issues.jboss.org/browse/JBIDE-23660 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk > Affects Versions: 4.4.2.Final > Reporter: Ricardo Martinelli Oliveira > Assignee: Rob Stryker > Fix For: 4.4.4.AM2 > > > CDK Server adapter lets configure the vagrant startup options. There should have an option to do the same in the stop. > Why? > It seems that CDK Server adapter uses _vagrant destroy_ to stop CDK, but using that option has its drawbacks, like for example: > * If I'm stopping it to save resources, then I'm loosing all my job in it. > * All images already pulled will be lost, so I cannot work offline -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23704) Application wizard: Application based on builder images do not have prefilled configuration when opened from Central

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23704?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23704: ------------------------------- Affects Version/s: 4.4.3.AM1 (was: 4.4.4.AM2) > Application wizard: Application based on builder images do not have prefilled configuration when opened from Central > -------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23704 > URL: https://issues.jboss.org/browse/JBIDE-23704 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM1 > Environment: Devstudio 10.3.0.AM1. > Reproducible against internal OS3 instance and agains OS inside CDK 2.3 > Reporter: Radim Hopp > Labels: application_wizard, openshift_v3 > Fix For: 4.4.4.AM2 > > Attachments: git-repo-missing.png, git-repo-prefilled.png > > > This test started to fail: https://github.com/jbosstools/jbosstools-integration-tests/blob/master/te... and I was able to reproduce it by hand. > It looks very simmilar to JBIDE-22704 except App name is preconfigured, but Git repo URL is not (and thus I cannot continue to next pages of this wizard). > This works when new openshift app wizard is opened via File -> New -> Other... -> OpenShift -> OpenShift Application or by right-clicking on OpenShift connection or OpenShift project in OpenShift explorer. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23704) Application wizard: Application based on builder images do not have prefilled configuration when opened from Central

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23704?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23704: ------------------------------- Fix Version/s: 4.4.4.AM2 (was: 4.4.3.Final) > Application wizard: Application based on builder images do not have prefilled configuration when opened from Central > -------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23704 > URL: https://issues.jboss.org/browse/JBIDE-23704 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM1 > Environment: Devstudio 10.3.0.AM1. > Reproducible against internal OS3 instance and agains OS inside CDK 2.3 > Reporter: Radim Hopp > Labels: application_wizard, openshift_v3 > Fix For: 4.4.4.AM2 > > Attachments: git-repo-missing.png, git-repo-prefilled.png > > > This test started to fail: https://github.com/jbosstools/jbosstools-integration-tests/blob/master/te... and I was able to reproduce it by hand. > It looks very simmilar to JBIDE-22704 except App name is preconfigured, but Git repo URL is not (and thus I cannot continue to next pages of this wizard). > This works when new openshift app wizard is opened via File -> New -> Other... -> OpenShift -> OpenShift Application or by right-clicking on OpenShift connection or OpenShift project in OpenShift explorer. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23708) Pod Log: unable to get build log if build failed with error

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23708?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23708: ------------------------------- Affects Version/s: 4.4.3.AM1 (was: 4.4.4.AM2) > Pod Log: unable to get build log if build failed with error > ----------------------------------------------------------- > > Key: JBIDE-23708 > URL: https://issues.jboss.org/browse/JBIDE-23708 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Andre Dietisheim > Labels: logs, properties > Fix For: 4.4.4.AM2 > > Attachments: cannot-get-logs-for-erroring-build.png, webconsole-logs-for-erroring-build.png > > > steps to reproduce: > # ASSERT: make sure that you have a build that failed (ex. launch a nodejs build and shut down your vpn. The build will fail because it cannot connect to the registry) > # EXEC: in Properties view: select "Builds" tab and choose your erroring build. Choose "Build Log..." in it's context menu > Result: > You're told that you cannot get the logs for an erroring build. You therefore cannot have insights on why your build failed: > !cannot-get-logs-for-erroring-build.png! > The webconsole allows you to inspect those logs: > !webconsole-logs-for-erroring-build.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23708) Pod Log: unable to get build log if build failed with error

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23708?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23708: ------------------------------- Fix Version/s: 4.4.4.AM2 (was: 4.4.3.Final) > Pod Log: unable to get build log if build failed with error > ----------------------------------------------------------- > > Key: JBIDE-23708 > URL: https://issues.jboss.org/browse/JBIDE-23708 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Andre Dietisheim > Labels: logs, properties > Fix For: 4.4.4.AM2 > > Attachments: cannot-get-logs-for-erroring-build.png, webconsole-logs-for-erroring-build.png > > > steps to reproduce: > # ASSERT: make sure that you have a build that failed (ex. launch a nodejs build and shut down your vpn. The build will fail because it cannot connect to the registry) > # EXEC: in Properties view: select "Builds" tab and choose your erroring build. Choose "Build Log..." in it's context menu > Result: > You're told that you cannot get the logs for an erroring build. You therefore cannot have insights on why your build failed: > !cannot-get-logs-for-erroring-build.png! > The webconsole allows you to inspect those logs: > !webconsole-logs-for-erroring-build.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23711) Properites: "Edit default route" on Build config does nothing

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23711?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23711: ------------------------------- Affects Version/s: 4.4.3.AM1 (was: 4.4.4.AM2) > Properites: "Edit default route" on Build config does nothing > ------------------------------------------------------------- > > Key: JBIDE-23711 > URL: https://issues.jboss.org/browse/JBIDE-23711 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Radim Hopp > Labels: openshift_v3, properties > Fix For: 4.4.4.AM2 > > > Context menu of build configs in properties view has entry "Edit default route..." which does nothing. Is it even supposed to be there? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 February 2017