March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13800) Error when installing jenkins-client cartridge just after creating the jenkins application (on LiveCD)

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-13800: ------------------------------------- Summary: Error when installing jenkins-client cartridge just after creating the jenkins application (on LiveCD) Key: JBIDE-13800 URL: https://issues.jboss.org/browse/JBIDE-13800 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.1.0.Alpha1 Reporter: Xavier Coulon Assignee: Andre Dietisheim In REST API version 1.0 (running a LiveCD on VirtualBox), I got the following error message when I tried to install a jenkins-client on my application. Could not embed cartridges for application test2 Could not request https://192.168.56.101/broker/rest/domains/devoxx/applications/test2/cart...: Operation failed on parameter "cartridge", sevirty "ERROR" with exit code "157".Reason given: "Error contacting Jenkins server. Could not download https://jenkins-devoxx.example.com/jnlpJars/jenkins-cli.jar" I also created the jenkins application since I did not have one in my domain before, so my guess is that the lib download occurred before the application was available, which ended up with that error message. Trying to install the same jenkins-client embedded cartridge a few minutes later worked. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13746) BrowserSim: make standalone available for download/launch

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13746?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov reassigned JBIDE-13746: ---------------------------------------------- Assignee: Konstantin Marmalyukov (was: Yahor Radtsevich) > BrowserSim: make standalone available for download/launch > --------------------------------------------------------- > > Key: JBIDE-13746 > URL: https://issues.jboss.org/browse/JBIDE-13746 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Visual Page Editor core > Reporter: Max Rydahl Andersen > Assignee: Konstantin Marmalyukov > Fix For: 4.1.x > > > We want to make browersim easily available. > To do that we need: > A) buildable from our target platform > B) built in jenkins > C) put on nexus -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13307) Set up the "All JBoss Tools" build+test

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13307?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13307: ---------------------------------------- Build Flow plugin is still incubating and has a few annoying issues. For example I reported this one: https://issues.jenkins-ci.org/browse/JENKINS-17249 > Set up the "All JBoss Tools" build+test > --------------------------------------- > > Key: JBIDE-13307 > URL: https://issues.jboss.org/browse/JBIDE-13307 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha2 > > > This job would take all JBoss Tools and build everything at once. It can be used to ensure everything builds together. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13796) rename jbosstools-integration-tests to jbosstools-itests

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13796?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13796: ---------------------------------------- How is "itests" a clearer name than "integration-tests"? What are the benefit of this rename (except 11 chars in URLs) ? > rename jbosstools-integration-tests to jbosstools-itests > -------------------------------------------------------- > > Key: JBIDE-13796 > URL: https://issues.jboss.org/browse/JBIDE-13796 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools, updatesite > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.1.0.Alpha2 > > > To be consistent and more clear about purpose/content, I propose we rename the github project jbosstools-integration-tests to jbosstools-itests. > Once renamed, will need to refactor: > * job name > * destination publishing folder - http://download.jboss.org/jbosstools/updates/nightly/integrationtests/ -> http://download.jboss.org/jbosstools/updates/nightly/itests/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-12850) Investigate usage of Jenkins Build Pipeline & Build Flow plugins for our build stream

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12850?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-12850: ------------------------------------ With the new BuildFlow plugin in Jenkins, I've merged the 5 Build Flow jobs into a single one to see if this works better, now that we can skip FAILURE conditions: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow... > Investigate usage of Jenkins Build Pipeline & Build Flow plugins for our build stream > ------------------------------------------------------------------------------------- > > Key: JBIDE-12850 > URL: https://issues.jboss.org/browse/JBIDE-12850 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Nick Boldt > Labels: f2f2012 > Fix For: 4.1.x > > Attachments: buildflow.png, pipeline_40.png, pipeline_buildflow.png > > > In order to build the whole JBoss Tools in one click, we could try to use the https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin plugin to -orchestrate- display the whole build workflow, and the https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin plugin to orchestrate it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13307) Set up the "All JBoss Tools" build+test

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13307?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13307: ------------------------------------ With the new BuildFlow plugin in Jenkins, I've merged the 5 Build Flow jobs into a single one to see if this works better, now that we can skip FAILURE conditions: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow... > Set up the "All JBoss Tools" build+test > --------------------------------------- > > Key: JBIDE-13307 > URL: https://issues.jboss.org/browse/JBIDE-13307 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha2 > > > This job would take all JBoss Tools and build everything at once. It can be used to ensure everything builds together. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-29) Migrate runtime detection plugins for SOA Tooling to their respective projects

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-29?page=com.atlassian.jira.plugin.s... ] Nick Boldt commented on JBTIS-29: --------------------------------- Since this is a cross-project integration issue for multiple SOA projects, I've moved it to JBTIS-29 from JBIDE-11098. > Migrate runtime detection plugins for SOA Tooling to their respective projects > ------------------------------------------------------------------------------ > > Key: JBTIS-29 > URL: https://issues.jboss.org/browse/JBTIS-29 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: distribution, drools/ jBPM5, ESB, jBPM3, releng, runtime-soa > Affects Versions: 4.0.0 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.0.0 > > > You'll no doubt want a new feature wrapper for each of these plugins, as they'll need to be installable from their respective projects' sites: > * org.jboss.tools.runtime.drools.detector > * org.jboss.tools.runtime.esb.detector > * org.jboss.tools.runtime.jbpm.detector -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-11098) Migrate runtime detection plugins for SOA Tooling to their respective projects

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11098?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-11098 at 3/17/13 9:57 PM: ------------------------------------------------------------- Assign to [~maxandersen] or [~dgolovin] to apply these PRs in the runtime-soa project. * -https://github.com/jbosstools/jbosstools-runtime-soa/pull/7 (remove jbpm and esb from master branch; drools awaits upstream PR)- * -https://github.com/jbosstools/jbosstools-runtime-soa/pull/8 (remove esb from 41x branch; drools and jbpm await upstream PRs)- * -https://github.com/jbosstools/jbosstools-runtime-soa/pull/9 (remove jbpm and esb from 40x branch; drools awaits upstream PR)- More PRs to come once upstream PRs for jbpm (JBIDE-13389) and drools (JBIDE-11099) PRs are applied. * -https://github.com/jbosstools/jbosstools-jbpm/pull/10 (master branch)- * -https://github.com/jbosstools/jbosstools-jbpm/pull/11 (4.1.0.Alpha1x branch)- * -https://github.com/jbosstools/jbosstools-jbpm/pull/12 (4.0.x branch)- * -https://github.com/droolsjbpm/droolsjbpm-tools/pull/15 (master branch for drools 6)- was (Author: nickboldt): Assign to [~maxandersen] or [~dgolovin] to apply these PRs in the runtime-soa project. * https://github.com/jbosstools/jbosstools-runtime-soa/pull/7 (remove jbpm and esb from master branch; drools awaits upstream PR) * https://github.com/jbosstools/jbosstools-runtime-soa/pull/8 (remove esb from 41x branch; drools and jbpm await upstream PRs) * https://github.com/jbosstools/jbosstools-runtime-soa/pull/9 (remove jbpm and esb from 40x branch; drools awaits upstream PR) More PRs to come once upstream PRs for jbpm (JBIDE-13389) and drools (JBIDE-11099) PRs are applied. * -https://github.com/jbosstools/jbosstools-jbpm/pull/10 (master branch)- * -https://github.com/jbosstools/jbosstools-jbpm/pull/11 (4.1.0.Alpha1x branch)- * -https://github.com/jbosstools/jbosstools-jbpm/pull/12 (4.0.x branch)- * -https://github.com/droolsjbpm/droolsjbpm-tools/pull/15 (master branch for drools 6)- > Migrate runtime detection plugins for SOA Tooling to their respective projects > ------------------------------------------------------------------------------ > > Key: JBIDE-11098 > URL: https://issues.jboss.org/browse/JBIDE-11098 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: drools, esb, jbpm, runtime-detection, SOA Tooling > Affects Versions: 3.3.0.Beta1-SOA > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.0.0.Alpha1-SOA > > > You'll no doubt want a new feature wrapper for each of these plugins, as they'll need to be installable from their respective projects' sites: > * org.jboss.tools.runtime.drools.detector > * org.jboss.tools.runtime.esb.detector > * org.jboss.tools.runtime.jbpm.detector -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-29) Migrate runtime detection plugins for SOA Tooling to their respective projects

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-29?page=com.atlassian.jira.plugin.s... ] Nick Boldt updated JBTIS-29: ---------------------------- Component/s: releng runtime-soa > Migrate runtime detection plugins for SOA Tooling to their respective projects > ------------------------------------------------------------------------------ > > Key: JBTIS-29 > URL: https://issues.jboss.org/browse/JBTIS-29 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: distribution, drools/ jBPM5, ESB, jBPM3, releng, runtime-soa > Affects Versions: 4.0.0 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.0.0 > > > You'll no doubt want a new feature wrapper for each of these plugins, as they'll need to be installable from their respective projects' sites: > * org.jboss.tools.runtime.drools.detector > * org.jboss.tools.runtime.esb.detector > * org.jboss.tools.runtime.jbpm.detector -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-11098) Migrate runtime detection plugins for SOA Tooling to their respective projects

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11098?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-11098 at 3/17/13 9:57 PM: ------------------------------------------------------------- Assign to [~maxandersen] or [~dgolovin] to apply these PRs in the runtime-soa project. * https://github.com/jbosstools/jbosstools-runtime-soa/pull/7 (remove jbpm and esb from master branch; drools awaits upstream PR) * https://github.com/jbosstools/jbosstools-runtime-soa/pull/8 (remove esb from 41x branch; drools and jbpm await upstream PRs) * https://github.com/jbosstools/jbosstools-runtime-soa/pull/9 (remove jbpm and esb from 40x branch; drools awaits upstream PR) More PRs to come once upstream PRs for jbpm (JBIDE-13389) and drools (JBIDE-11099) PRs are applied. * -https://github.com/jbosstools/jbosstools-jbpm/pull/10 (master branch)- * -https://github.com/jbosstools/jbosstools-jbpm/pull/11 (4.1.0.Alpha1x branch)- * -https://github.com/jbosstools/jbosstools-jbpm/pull/12 (4.0.x branch)- * -https://github.com/droolsjbpm/droolsjbpm-tools/pull/15 (master branch for drools 6)- was (Author: nickboldt): Assign to [~maxandersen] or [~dgolovin] to apply these PRs in the runtime-soa project. * https://github.com/jbosstools/jbosstools-runtime-soa/pull/7 (remove jbpm and esb from master branch; drools awaits upstream PR) * https://github.com/jbosstools/jbosstools-runtime-soa/pull/8 (remove esb from 41x branch; drools and jbpm await upstream PRs) * https://github.com/jbosstools/jbosstools-runtime-soa/pull/9 (remove jbpm and esb from 40x branch; drools awaits upstream PR) More PRs to come once upstream PRs for jbpm (JBIDE-13389) and drools (JBIDE-11099) PRs are applied. * https://github.com/jbosstools/jbosstools-jbpm/pull/10 (master branch) * https://github.com/jbosstools/jbosstools-jbpm/pull/11 (4.1.0.Alpha1x branch) * https://github.com/jbosstools/jbosstools-jbpm/pull/12 (4.0.x branch) * https://github.com/droolsjbpm/droolsjbpm-tools/pull/15 (master branch for drools 6) > Migrate runtime detection plugins for SOA Tooling to their respective projects > ------------------------------------------------------------------------------ > > Key: JBIDE-11098 > URL: https://issues.jboss.org/browse/JBIDE-11098 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: drools, esb, jbpm, runtime-detection, SOA Tooling > Affects Versions: 3.3.0.Beta1-SOA > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.0.0.Alpha1-SOA > > > You'll no doubt want a new feature wrapper for each of these plugins, as they'll need to be installable from their respective projects' sites: > * org.jboss.tools.runtime.drools.detector > * org.jboss.tools.runtime.esb.detector > * org.jboss.tools.runtime.jbpm.detector -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 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 2013