June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20151) Tweak jbosstools-promote job to allow omission of core

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20151?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20151: ------------------------------- Fix Version/s: 4.3.0.Beta2 > Tweak jbosstools-promote job to allow omission of core > ------------------------------------------------------ > > Key: JBIDE-20151 > URL: https://issues.jboss.org/browse/JBIDE-20151 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.3.0.Beta2 > > > As discussed previously via email, I would like a small change to the jbosstools-promote job [1]. > We publish RedDeer to urls such as: > http://download.jboss.org/jbosstools/updates/development/luna/core/reddee... > http://download.jboss.org/jbosstools/updates/stable/luna/core/reddeer/0.7.0/ > The job currently supports having NONE for luna/mars. But there is no way to omit the "core" part. For us it really has no meaning, and the simpler the url the better, so it would be nice if this could be empty. > This most probably just requires something similar to this: > {code} > if [[ ${TARGET_PLATFORM} == "NONE" ]]; then TARGET_PLATFORM=""; fi > {code} > in https://github.com/jbosstools/jbosstools-build-ci/blob/master/publish/pro... > And then a new option for NONE for the PARENT_FOLDER parameter in the jenkins job. > If you agree this is fine, I can make it happen (create PR for jbosstools-build-ci and update the job). > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20151) Tweak jbosstools-promote job to allow omission of core

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20151?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20151: ------------------------------- Sprint: Sprint #5 Jun 2015 > Tweak jbosstools-promote job to allow omission of core > ------------------------------------------------------ > > Key: JBIDE-20151 > URL: https://issues.jboss.org/browse/JBIDE-20151 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.3.0.Beta2 > > > As discussed previously via email, I would like a small change to the jbosstools-promote job [1]. > We publish RedDeer to urls such as: > http://download.jboss.org/jbosstools/updates/development/luna/core/reddee... > http://download.jboss.org/jbosstools/updates/stable/luna/core/reddeer/0.7.0/ > The job currently supports having NONE for luna/mars. But there is no way to omit the "core" part. For us it really has no meaning, and the simpler the url the better, so it would be nice if this could be empty. > This most probably just requires something similar to this: > {code} > if [[ ${TARGET_PLATFORM} == "NONE" ]]; then TARGET_PLATFORM=""; fi > {code} > in https://github.com/jbosstools/jbosstools-build-ci/blob/master/publish/pro... > And then a new option for NONE for the PARENT_FOLDER parameter in the jenkins job. > If you agree this is fine, I can make it happen (create PR for jbosstools-build-ci and update the job). > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20151) Tweak jbosstools-promote job to allow omission of core

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20151?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20151: ------------------------------------ I have a better idea. I hope you'll like it. Instead of using the obsolete/deprecated promote.sh script, wrapped by the jbosstools-promote job, use this NEW job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-rsync which wraps the current rsync.sh [0] script. [0] https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.3.x/p... Please note [1]: !http://static.comicvine.com/uploads/square_small/5/52246/1676758-spidey_507.jpg! -- [1] http://static.comicvine.com/uploads/square_small/5/52246/1676758-spidey_5... Please use it wisely, and do NOT use it for wacky and inconsistent paths [2], [3]. [2] https://github.com/jboss-reddeer/reddeer/issues/1111 [3] https://github.com/jboss-reddeer/reddeer/pull/1110 > Tweak jbosstools-promote job to allow omission of core > ------------------------------------------------------ > > Key: JBIDE-20151 > URL: https://issues.jboss.org/browse/JBIDE-20151 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Martin Malina > Assignee: Nick Boldt > > As discussed previously via email, I would like a small change to the jbosstools-promote job [1]. > We publish RedDeer to urls such as: > http://download.jboss.org/jbosstools/updates/development/luna/core/reddee... > http://download.jboss.org/jbosstools/updates/stable/luna/core/reddeer/0.7.0/ > The job currently supports having NONE for luna/mars. But there is no way to omit the "core" part. For us it really has no meaning, and the simpler the url the better, so it would be nice if this could be empty. > This most probably just requires something similar to this: > {code} > if [[ ${TARGET_PLATFORM} == "NONE" ]]; then TARGET_PLATFORM=""; fi > {code} > in https://github.com/jbosstools/jbosstools-build-ci/blob/master/publish/pro... > And then a new option for NONE for the PARENT_FOLDER parameter in the jenkins job. > If you agree this is fine, I can make it happen (create PR for jbosstools-build-ci and update the job). > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-453) Update site for JBDS-IS 8.0.2.GA contains also JBDS categories

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-453?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-453. ------------------------------ Fix Version/s: 8.0.2.GA Resolution: Done Hey [~apodhrad] - sorry - I was looking at the git repo (where it was correct). I know I updated this on the server - it somehow reverted. Anyway - it's back to being correct on the server again. Please let me know if this slips back again... Thkx > Update site for JBDS-IS 8.0.2.GA contains also JBDS categories > -------------------------------------------------------------- > > Key: JBTIS-453 > URL: https://issues.jboss.org/browse/JBTIS-453 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.2.GA > Environment: JBDS 8.1.0.GA + JBDS-IS 8.0.2.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 8.0.2.GA > > Attachments: jbdsis-802ga_categories.png > > > The following update site > https://devstudio.jboss.com/updates/8.0/integration-stack/ > contains also all JBDS categories (+ JBDS-IS categories). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-453) Update site for JBDS-IS 8.0.2.GA contains also JBDS categories

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-453?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-453: ----------------------------------------- Please see the attached screenshot, I think that only categories directly related to JBDS-IS should be displayed. > Update site for JBDS-IS 8.0.2.GA contains also JBDS categories > -------------------------------------------------------------- > > Key: JBTIS-453 > URL: https://issues.jboss.org/browse/JBTIS-453 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.2.GA > Environment: JBDS 8.1.0.GA + JBDS-IS 8.0.2.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Attachments: jbdsis-802ga_categories.png > > > The following update site > https://devstudio.jboss.com/updates/8.0/integration-stack/ > contains also all JBDS categories (+ JBDS-IS categories). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-453) Update site for JBDS-IS 8.0.2.GA contains also JBDS categories

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-453?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-453: ------------------------------------ Attachment: jbdsis-802ga_categories.png > Update site for JBDS-IS 8.0.2.GA contains also JBDS categories > -------------------------------------------------------------- > > Key: JBTIS-453 > URL: https://issues.jboss.org/browse/JBTIS-453 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.2.GA > Environment: JBDS 8.1.0.GA + JBDS-IS 8.0.2.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Attachments: jbdsis-802ga_categories.png > > > The following update site > https://devstudio.jboss.com/updates/8.0/integration-stack/ > contains also all JBDS categories (+ JBDS-IS categories). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3472) Why does JBDS list the latest JBT target platform site?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3472?page=com.atlassian.jira.plugin.... ] Nick Boldt resolved JBDS-3472. ------------------------------ Resolution: Done Regression in JBDS 9 only, since we didn't have central-site and earlyaccess-site builders here: https://github.com/jbosstools/jbosstools-build-sites/tree/jbosstools-4.2.... PR pushed into jbosstools-build-sites (which is why this was a JBIDE jira, not JBDS one). Should be verifiable after the next build: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... >=3430 > Why does JBDS list the latest JBT target platform site? > ------------------------------------------------------- > > Key: JBDS-3472 > URL: https://issues.jboss.org/browse/JBDS-3472 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 9.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.0.Beta2 > > Attachments: jbds0update-site-in-eclipse-mars.png > > > When I install JBDS "BYOE" feature from https://devstudio.redhat.com/9.0/development/updates/ , I see that > "JBoss Tools Target Platform - Mars" is also added and enabled. This shouldn't be the case; JBDS doesn't need to reference http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/mars/ to support installation, as it points at https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.50.0.Bet... instead (composite child within https://devstudio.redhat.com/9.0/development/updates/ ). > So, this is bad & needs to be fixed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19851) Cannot refresh environment variable(s) for an OpenShift application

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19851?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-19851: --------------------------------------- Reopening OpenShift Explorer view does not help. I tried several things. The least you can do is to perform refresh on the connection. Refreshing only on domain does not help neither. > Cannot refresh environment variable(s) for an OpenShift application > ------------------------------------------------------------------- > > Key: JBIDE-19851 > URL: https://issues.jboss.org/browse/JBIDE-19851 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Priority: Minor > Labels: environment_variables, openshift_v2 > Fix For: 4.3.0.Beta2 > > > In Manage Application Environment Variable shell opened either via servers adapter or OpenShift Explorer view are listed environment variables for a specific application. Refresh button should refresh state of variables according to state on a server, but click on Refresh button shows following error dialog with following stack in log: > {code} > com.openshift.client.OpenShiftSSHOperationException: Failed to execute remote ssh command "eapapp" > at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:892) > at com.openshift.internal.client.ApplicationResource.loadPorts(ApplicationResource.java:860) > at com.openshift.internal.client.ApplicationResource.refresh(ApplicationResource.java:634) > at org.jboss.tools.openshift.express.internal.ui.wizard.environment.EditEnvironmentVariablesWizardModel.refreshEnvironmentVariables(EditEnvironmentVariablesWizardModel.java:35) > at org.jboss.tools.openshift.express.internal.ui.wizard.environment.EnvironmentVariablesWizardPage$RefreshEnvironmentVariablesJob.doRun(EnvironmentVariablesWizardPage.java:292) > at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: com.jcraft.jsch.JSchException: session is down > at com.jcraft.jsch.Session.openChannel(Session.java:844) > at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:885) > ... 6 more > {code} > Otherwise adding, editing and removing environment variables work OK. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19010) As a user, I want to create OpenShift resources that support an existing “deployment” that does not require source code from a template

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19010?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-19010: --------------------------------------- My original thoughts was this addresses deploying something like a database, but [~maxandersen] seems to be talking about binary deployment, which I don't know that we ever flushed out. Seems to me that we need a 'builder' image that knows how to take the binary and create the target image. Alternatively, I think we need an image that has persistent storage that knows where to find the binary and functionality to push the binary to persistent storage. I think I need a better understanding of how we envision a user doing this deployment and the use case > As a user, I want to create OpenShift resources that support an existing “deployment” that does not require source code from a template > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19010 > URL: https://issues.jboss.org/browse/JBIDE-19010 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Assignee: Max Rydahl Andersen > Priority: Blocker > Labels: application_wizard, openshift_v3 > Fix For: 4.3.0.Beta2 > > > https://trello.com/c/HyTyFlHw > This is the usecase where we want to deploy an image that most likely does not include a buildconfig, i.e. a database image. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19851) Cannot refresh environment variable(s) for an OpenShift application

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19851?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-19851: ---------------------------------- Workaround Description: Perform refresh on the connection. Workaround: Workaround Exists > Cannot refresh environment variable(s) for an OpenShift application > ------------------------------------------------------------------- > > Key: JBIDE-19851 > URL: https://issues.jboss.org/browse/JBIDE-19851 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Priority: Minor > Labels: environment_variables, openshift_v2 > Fix For: 4.3.0.Beta2 > > > In Manage Application Environment Variable shell opened either via servers adapter or OpenShift Explorer view are listed environment variables for a specific application. Refresh button should refresh state of variables according to state on a server, but click on Refresh button shows following error dialog with following stack in log: > {code} > com.openshift.client.OpenShiftSSHOperationException: Failed to execute remote ssh command "eapapp" > at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:892) > at com.openshift.internal.client.ApplicationResource.loadPorts(ApplicationResource.java:860) > at com.openshift.internal.client.ApplicationResource.refresh(ApplicationResource.java:634) > at org.jboss.tools.openshift.express.internal.ui.wizard.environment.EditEnvironmentVariablesWizardModel.refreshEnvironmentVariables(EditEnvironmentVariablesWizardModel.java:35) > at org.jboss.tools.openshift.express.internal.ui.wizard.environment.EnvironmentVariablesWizardPage$RefreshEnvironmentVariablesJob.doRun(EnvironmentVariablesWizardPage.java:292) > at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: com.jcraft.jsch.JSchException: session is down > at com.jcraft.jsch.Session.openChannel(Session.java:844) > at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:885) > ... 6 more > {code} > Otherwise adding, editing and removing environment variables work OK. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 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 June 2015