March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21844) Deploying a docker image doesn't always result in a deployment on openshift

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21844?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-21844: --------------------------------------------- Should be investigated to know why - get help from openshift team to debug it. Same problem happens on both CDK and engint (according to @fbricon) > Deploying a docker image doesn't always result in a deployment on openshift > --------------------------------------------------------------------------- > > Key: JBIDE-21844 > URL: https://issues.jboss.org/browse/JBIDE-21844 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Priority: Critical > Fix For: 4.3.1.CR1 > > > If I deploy sonatype/nexus to the cdk (OS 3.1.1) or engint (3.1), a deployment is triggered right away. > If I deploy saturnism/spring-boot-helloworld-ui, no deployment is triggered automatically. I need to do it manually -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21844) Deploying a docker image doesn't always result in a deployment on openshift

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21844?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-21844: ---------------------------------------- Summary: Deploying a docker image doesn't always result in a deployment on openshift (was: Deploying a docker image doesn't always generate a deployment) > Deploying a docker image doesn't always result in a deployment on openshift > --------------------------------------------------------------------------- > > Key: JBIDE-21844 > URL: https://issues.jboss.org/browse/JBIDE-21844 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Priority: Critical > > If I deploy sonatype/nexus to the cdk (OS 3.1.1) or engint (3.1), a deployment is triggered right away. > If I deploy saturnism/spring-boot-helloworld-ui, no deployment is triggered automatically. I need to do it manually -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21843) CDK Poller always fails on OSX

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21843?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-21843: ---------------------------------------- Priority: Major (was: Minor) > CDK Poller always fails on OSX > ------------------------------ > > Key: JBIDE-21843 > URL: https://issues.jboss.org/browse/JBIDE-21843 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Environment: OSX > Reporter: Fred Bricon > Assignee: Rob Stryker > Fix For: 4.3.1.CR1 > > > Starting the CDK on OSX always fails. Whether it was already started from CLI or not. > The vagrant up command is properly executed, you can see the output in the console, but it ends up with a message "Server CDK Server Adapter at localhost failed to start." > I traced the problem back to: > {noformat} > VagrantPoller.parseOutput(String[]) line: 220 > VagrantPoller.onePing(IServer, String) line: 160 > VagrantPoller.onePing(IServer) line: 138 > VagrantPoller.getCurrentStateSynchronous(IServer) line: 114 > CDKLaunchController$2.run() line: 222 > {noformat} > In parseOutput, the value of lines is : > [1457536005,,error-exit,Vagrant::Errors::ProviderNotUsable,The provider 'virtualbox' that was requested to back the machine\n'cdk' is reporting that it isn't usable on this system. The\nreason is shown below:\n\nVagrant could not detect VirtualBox! Make sure VirtualBox is properly installed.\nVagrant uses the `VBoxManage` binary that ships with VirtualBox%!(VAGRANT_COMMA) and requires\nthis to be available on the PATH. If VirtualBox is installed%!(VAGRANT_COMMA) please find the\n`VBoxManage` binary and add it to the PATH environmental variable.] > this is not properly parsed as it later goes into this block > {code} > Collection<VagrantStatus> stats = status.values(); > if( stats.size() == 0 ) { > return IStatus.ERROR; > } > {code} > And the message in the lines is lost completely -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21853) bump version of SpringIDE 3.7.3 from CI to RELEASE

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21853?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21853: ------------------------------- Fix Version/s: 4.3.1.CR1 > bump version of SpringIDE 3.7.3 from CI to RELEASE > -------------------------------------------------- > > Key: JBIDE-21853 > URL: https://issues.jboss.org/browse/JBIDE-21853 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central > Affects Versions: 4.3.1.CR1 > Reporter: Nick Boldt > Fix For: 4.3.1.CR1 > > > We're still using a pre-release version of Spring IDE 3.7.3 in Central. Since we've now moved up to the 3.7.3.RELEASE version in master, I'm going to make the same change in 4.3.x. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21853) bump version of SpringIDE 3.7.3 from CI to RELEASE

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21853?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-21853: ---------------------------------- Assignee: Nick Boldt > bump version of SpringIDE 3.7.3 from CI to RELEASE > -------------------------------------------------- > > Key: JBIDE-21853 > URL: https://issues.jboss.org/browse/JBIDE-21853 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central > Affects Versions: 4.3.1.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.CR1 > > > We're still using a pre-release version of Spring IDE 3.7.3 in Central. Since we've now moved up to the 3.7.3.RELEASE version in master, I'm going to make the same change in 4.3.x. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21854) Use the dedicated "link" field for report link

by Aurélien Pupier (JIRA)

Aurélien Pupier created JBIDE-21854: --------------------------------------- Summary: Use the dedicated "link" field for report link Key: JBIDE-21854 URL: https://issues.jboss.org/browse/JBIDE-21854 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: aeri Reporter: Aurélien Pupier Priority: Minor In the description when creating a JIRA from AERI, there are 2 links available in "Other resources" I think that it makes sens having the first one "Report:" available in the specific Link JIRA field. Manually, you can do "More->Link -> Web Link" see https://issues.jboss.org/browse/FUSETOOLS-1702 in "Issue links" section for a sample -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21843) CDK Poller always fails on OSX

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21843?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-21843: ---------------------------------------- Priority: Minor (was: Critical) > CDK Poller always fails on OSX > ------------------------------ > > Key: JBIDE-21843 > URL: https://issues.jboss.org/browse/JBIDE-21843 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Environment: OSX > Reporter: Fred Bricon > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.3.1.CR1 > > > Starting the CDK on OSX always fails. Whether it was already started from CLI or not. > The vagrant up command is properly executed, you can see the output in the console, but it ends up with a message "Server CDK Server Adapter at localhost failed to start." > I traced the problem back to: > {noformat} > VagrantPoller.parseOutput(String[]) line: 220 > VagrantPoller.onePing(IServer, String) line: 160 > VagrantPoller.onePing(IServer) line: 138 > VagrantPoller.getCurrentStateSynchronous(IServer) line: 114 > CDKLaunchController$2.run() line: 222 > {noformat} > In parseOutput, the value of lines is : > [1457536005,,error-exit,Vagrant::Errors::ProviderNotUsable,The provider 'virtualbox' that was requested to back the machine\n'cdk' is reporting that it isn't usable on this system. The\nreason is shown below:\n\nVagrant could not detect VirtualBox! Make sure VirtualBox is properly installed.\nVagrant uses the `VBoxManage` binary that ships with VirtualBox%!(VAGRANT_COMMA) and requires\nthis to be available on the PATH. If VirtualBox is installed%!(VAGRANT_COMMA) please find the\n`VBoxManage` binary and add it to the PATH environmental variable.] > this is not properly parsed as it later goes into this block > {code} > Collection<VagrantStatus> stats = status.values(); > if( stats.size() == 0 ) { > return IStatus.ERROR; > } > {code} > And the message in the lines is lost completely -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21843) CDK Poller always fails on OSX

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21843?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-21843: ---------------------------------------- Fix Version/s: 4.3.1.CR1 > CDK Poller always fails on OSX > ------------------------------ > > Key: JBIDE-21843 > URL: https://issues.jboss.org/browse/JBIDE-21843 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Environment: OSX > Reporter: Fred Bricon > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.3.1.CR1 > > > Starting the CDK on OSX always fails. Whether it was already started from CLI or not. > The vagrant up command is properly executed, you can see the output in the console, but it ends up with a message "Server CDK Server Adapter at localhost failed to start." > I traced the problem back to: > {noformat} > VagrantPoller.parseOutput(String[]) line: 220 > VagrantPoller.onePing(IServer, String) line: 160 > VagrantPoller.onePing(IServer) line: 138 > VagrantPoller.getCurrentStateSynchronous(IServer) line: 114 > CDKLaunchController$2.run() line: 222 > {noformat} > In parseOutput, the value of lines is : > [1457536005,,error-exit,Vagrant::Errors::ProviderNotUsable,The provider 'virtualbox' that was requested to back the machine\n'cdk' is reporting that it isn't usable on this system. The\nreason is shown below:\n\nVagrant could not detect VirtualBox! Make sure VirtualBox is properly installed.\nVagrant uses the `VBoxManage` binary that ships with VirtualBox%!(VAGRANT_COMMA) and requires\nthis to be available on the PATH. If VirtualBox is installed%!(VAGRANT_COMMA) please find the\n`VBoxManage` binary and add it to the PATH environmental variable.] > this is not properly parsed as it later goes into this block > {code} > Collection<VagrantStatus> stats = status.values(); > if( stats.size() == 0 ) { > return IStatus.ERROR; > } > {code} > And the message in the lines is lost completely -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21853) bump version of SpringIDE 3.7.3 from CI to RELEASE

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-21853: ---------------------------------- Summary: bump version of SpringIDE 3.7.3 from CI to RELEASE Key: JBIDE-21853 URL: https://issues.jboss.org/browse/JBIDE-21853 Project: Tools (JBoss Tools) Issue Type: Bug Components: build, central Affects Versions: 4.3.1.CR1 Reporter: Nick Boldt We're still using a pre-release version of Spring IDE 3.7.3 in Central. Since we've now moved up to the 3.7.3.RELEASE version in master, I'm going to make the same change in 4.3.x. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21851) Bad redirection when create a new JIRA from AERI

by Marcel Bruch (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21851?page=com.atlassian.jira.plugi... ] Marcel Bruch resolved JBIDE-21851. ---------------------------------- Fix Version/s: 4.3.1.CR1 Resolution: Done The html templates referred to the (bugzilla) bugId field. Changed JS to use jira field "identifier" instead. > Bad redirection when create a new JIRA from AERI > ------------------------------------------------ > > Key: JBIDE-21851 > URL: https://issues.jboss.org/browse/JBIDE-21851 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aeri > Reporter: Aurélien Pupier > Priority: Minor > Fix For: 4.3.1.CR1 > > > I was using was using a Fuse Tools incident, in case it is related to the component. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 March 2016