January 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-1027) Clean earlyaccess sites

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-1027: ---------------------------------------- Summary: Clean earlyaccess sites Key: JBTIS-1027 URL: https://issues.jboss.org/browse/JBTIS-1027 Project: JBoss Tools Integration Stack Issue Type: Task Components: distribution Affects Versions: 10.1.0.CR1 Reporter: Andrej Podhradsky The following update site https://devstudio.redhat.com/10.0/staging/updates/integration-stack/early... still contains features even the Teiid Designer was moved to main update site Please also empty the EA update site once we go to GA. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1026) Extend and use Runtime annotation

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1026?page=com.atlassian.jira.plugin... ] Jozef Marko updated JBTIS-1026: ------------------------------- Description: Replace the usage of {code:java}org.jboss.tools.bpmn2.ui.bot.test.requirements.ProcessRuntimeRequirement{code} with {code:java}org.jboss.tools.runtime.reddeer.requirement.RuntimeRequirement{code} * The annotation corresponding to RuntimeRequirement is used for example here [1]. * How to run tests that uses this kind of annotation is shown here [2]. ** Notice there is maven goal over the *server-installer* repository ** Explore content of *server-installer* modules that are built ** Notice the usage of the system property *rd.config* like [3]. The property is described on the reddeer wiki [4]. The annotation currently supports only downloading of brms-runtime classes. However , support for bpms-runtime classes will be pretty similar to support of brms and just few changes will be needed at these places: * https://github.com/jbosstools/jbosstools-integration-stack-tests/blob/mas... * https://github.com/jbosstools/jbosstools-integration-stack-tests/blob/mas... * https://github.com/jbosstools/jbosstools-integration-stack-tests/tree/mas... * https://github.com/jbosstools/jbosstools-integration-stack-tests/blob/mas... * https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jbdsis/server-installer/... [1] https://github.com/jbosstools/jbosstools-integration-stack-tests/blob/mas... [2] https://jbdsis-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Drools/job... [3] -Drd.config=$WORKSPACE/server-installer/$SERVER/target/config [4] https://github.com/jboss-reddeer/reddeer/wiki/Tests-configuration was: Replace the usage of {code:java}org.jboss.tools.bpmn2.ui.bot.test.requirements.ProcessRuntimeRequirement{code} with {code:java}org.jboss.tools.runtime.reddeer.requirement.RuntimeRequirement{code} * The annotation corresponding to RuntimeRequirement is used for example here [1]. * How to run tests that uses this kind of annotation is shown here [2]. ** Notice there is maven goal over the *server-installer* repository ** Explore content of *server-installer* modules that are built ** Notice the usage of the system property *rd.config* like [3]. The property is described on the reddeer wiki [4]. There will be needed [1] https://github.com/jbosstools/jbosstools-integration-stack-tests/blob/mas... [2] https://jbdsis-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Drools/job... [3] -Drd.config=$WORKSPACE/server-installer/$SERVER/target/config [4] https://github.com/jboss-reddeer/reddeer/wiki/Tests-configuration > Extend and use Runtime annotation > --------------------------------- > > Key: JBTIS-1026 > URL: https://issues.jboss.org/browse/JBTIS-1026 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: BPMN2, QE > Affects Versions: 4.4.0.Alpha1 > Reporter: Jozef Marko > Assignee: Dominik Hanak > > Replace the usage of > {code:java}org.jboss.tools.bpmn2.ui.bot.test.requirements.ProcessRuntimeRequirement{code} > with > {code:java}org.jboss.tools.runtime.reddeer.requirement.RuntimeRequirement{code} > * The annotation corresponding to RuntimeRequirement is used for example here [1]. > * How to run tests that uses this kind of annotation is shown here [2]. > ** Notice there is maven goal over the *server-installer* repository > ** Explore content of *server-installer* modules that are built > ** Notice the usage of the system property *rd.config* like [3]. The property is described on the reddeer wiki [4]. > The annotation currently supports only downloading of brms-runtime classes. However , support for bpms-runtime classes will be pretty similar to support of brms and just few changes will be needed at these places: > * https://github.com/jbosstools/jbosstools-integration-stack-tests/blob/mas... > * https://github.com/jbosstools/jbosstools-integration-stack-tests/blob/mas... > * https://github.com/jbosstools/jbosstools-integration-stack-tests/tree/mas... > * https://github.com/jbosstools/jbosstools-integration-stack-tests/blob/mas... > * https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jbdsis/server-installer/... > [1] > https://github.com/jbosstools/jbosstools-integration-stack-tests/blob/mas... > [2] > https://jbdsis-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Drools/job... > [3] > -Drd.config=$WORKSPACE/server-installer/$SERVER/target/config > [4] > https://github.com/jboss-reddeer/reddeer/wiki/Tests-configuration -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1026) Extend and use RuntimeRequirement annotation

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1026?page=com.atlassian.jira.plugin... ] Jozef Marko updated JBTIS-1026: ------------------------------- Description: Replace the usage of {code:java}org.jboss.tools.bpmn2.ui.bot.test.requirements.ProcessRuntimeRequirement{code} with {code:java}org.jboss.tools.runtime.reddeer.requirement.RuntimeRequirement{code} * The annotation corresponding to RuntimeRequirement is used for example here [1]. * How to run tests that uses this kind of annotation is shown here [2]. ** Notice there is maven goal over the *server-installer* repository ** Explore content of *server-installer* modules that are built ** Notice the usage of the system property *rd.config* like [3]. The property is described on the reddeer wiki [4]. There will be needed [1] https://github.com/jbosstools/jbosstools-integration-stack-tests/blob/mas... [2] https://jbdsis-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Drools/job... [3] -Drd.config=$WORKSPACE/server-installer/$SERVER/target/config [4] https://github.com/jboss-reddeer/reddeer/wiki/Tests-configuration was: Replace the usage of {code:java}org.jboss.tools.bpmn2.ui.bot.test.requirements.ProcessRuntimeRequirement{code} with {code:java}org.jboss.tools.runtime.reddeer.requirement.RuntimeRequirement{code} * The annotation corresponding to RuntimeRequirement is used for example here [1]. * How to run tests that uses this kind of annotation is shown here [2]. ** Notice there is maven goal over the *server-installer* repository ** Explore content of *server-installer* modules that are built ** Notice the usage of the system property *rd.config* like [3]. The property is described on the reddeer wiki [4]. [1] https://github.com/jbosstools/jbosstools-integration-stack-tests/blob/mas... [2] https://jbdsis-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Drools/job... [3] -Drd.config=$WORKSPACE/server-installer/$SERVER/target/config [4] https://github.com/jboss-reddeer/reddeer/wiki/Tests-configuration > Extend and use RuntimeRequirement annotation > -------------------------------------------- > > Key: JBTIS-1026 > URL: https://issues.jboss.org/browse/JBTIS-1026 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: BPMN2, QE > Affects Versions: 4.4.0.Alpha1 > Reporter: Jozef Marko > Assignee: Dominik Hanak > > Replace the usage of > {code:java}org.jboss.tools.bpmn2.ui.bot.test.requirements.ProcessRuntimeRequirement{code} > with > {code:java}org.jboss.tools.runtime.reddeer.requirement.RuntimeRequirement{code} > * The annotation corresponding to RuntimeRequirement is used for example here [1]. > * How to run tests that uses this kind of annotation is shown here [2]. > ** Notice there is maven goal over the *server-installer* repository > ** Explore content of *server-installer* modules that are built > ** Notice the usage of the system property *rd.config* like [3]. The property is described on the reddeer wiki [4]. > There will be needed > [1] > https://github.com/jbosstools/jbosstools-integration-stack-tests/blob/mas... > [2] > https://jbdsis-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Drools/job... > [3] > -Drd.config=$WORKSPACE/server-installer/$SERVER/target/config > [4] > https://github.com/jboss-reddeer/reddeer/wiki/Tests-configuration -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1026) Extend and use Runtime annotation

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1026?page=com.atlassian.jira.plugin... ] Jozef Marko updated JBTIS-1026: ------------------------------- Summary: Extend and use Runtime annotation (was: Extend and use RuntimeRequirement annotation) > Extend and use Runtime annotation > --------------------------------- > > Key: JBTIS-1026 > URL: https://issues.jboss.org/browse/JBTIS-1026 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: BPMN2, QE > Affects Versions: 4.4.0.Alpha1 > Reporter: Jozef Marko > Assignee: Dominik Hanak > > Replace the usage of > {code:java}org.jboss.tools.bpmn2.ui.bot.test.requirements.ProcessRuntimeRequirement{code} > with > {code:java}org.jboss.tools.runtime.reddeer.requirement.RuntimeRequirement{code} > * The annotation corresponding to RuntimeRequirement is used for example here [1]. > * How to run tests that uses this kind of annotation is shown here [2]. > ** Notice there is maven goal over the *server-installer* repository > ** Explore content of *server-installer* modules that are built > ** Notice the usage of the system property *rd.config* like [3]. The property is described on the reddeer wiki [4]. > There will be needed > [1] > https://github.com/jbosstools/jbosstools-integration-stack-tests/blob/mas... > [2] > https://jbdsis-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Drools/job... > [3] > -Drd.config=$WORKSPACE/server-installer/$SERVER/target/config > [4] > https://github.com/jboss-reddeer/reddeer/wiki/Tests-configuration -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1026) Extend and use RuntimeRequirement annotation

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1026?page=com.atlassian.jira.plugin... ] Jozef Marko updated JBTIS-1026: ------------------------------- Summary: Extend and use RuntimeRequirement annotation (was: Use RuntimeRequirement annotation) > Extend and use RuntimeRequirement annotation > -------------------------------------------- > > Key: JBTIS-1026 > URL: https://issues.jboss.org/browse/JBTIS-1026 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: BPMN2, QE > Affects Versions: 4.4.0.Alpha1 > Reporter: Jozef Marko > Assignee: Dominik Hanak > > Replace the usage of > {code:java}org.jboss.tools.bpmn2.ui.bot.test.requirements.ProcessRuntimeRequirement{code} > with > {code:java}org.jboss.tools.runtime.reddeer.requirement.RuntimeRequirement{code} > * The annotation corresponding to RuntimeRequirement is used for example here [1]. > * How to run tests that uses this kind of annotation is shown here [2]. > ** Notice there is maven goal over the *server-installer* repository > ** Explore content of *server-installer* modules that are built > ** Notice the usage of the system property *rd.config* like [3]. The property is described on the reddeer wiki [4]. > [1] > https://github.com/jbosstools/jbosstools-integration-stack-tests/blob/mas... > [2] > https://jbdsis-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Drools/job... > [3] > -Drd.config=$WORKSPACE/server-installer/$SERVER/target/config > [4] > https://github.com/jboss-reddeer/reddeer/wiki/Tests-configuration -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1026) Use RuntimeRequirement annotation

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1026?page=com.atlassian.jira.plugin... ] Jozef Marko updated JBTIS-1026: ------------------------------- Description: Replace the usage of {code:java}org.jboss.tools.bpmn2.ui.bot.test.requirements.ProcessRuntimeRequirement{code} with {code:java}org.jboss.tools.runtime.reddeer.requirement.RuntimeRequirement{code} * The annotation corresponding to RuntimeRequirement is used for example here [1]. * How to run tests that uses this kind of annotation is shown here [2]. ** Notice there is maven goal over the *server-installer* repository ** Explore content of *server-installer* modules that are built ** Notice the usage of the system property *rd.config* like [3]. The property is described on the reddeer wiki [4]. [1] https://github.com/jbosstools/jbosstools-integration-stack-tests/blob/mas... [2] https://jbdsis-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Drools/job... [3] -Drd.config=$WORKSPACE/server-installer/$SERVER/target/config [4] https://github.com/jboss-reddeer/reddeer/wiki/Tests-configuration was: Replace the usage of {code:java}org.jboss.tools.bpmn2.ui.bot.test.requirements.ProcessRuntimeRequirement{code} with {code:java}org.jboss.tools.runtime.reddeer.requirement.RuntimeRequirement{code} * The annotation corresponding to RuntimeRequirement is used for example here [1]. * How to run tests that uses this kind of annotation is shown here [2]. ** Notice there is maven goal over the *server-installer* repository ** Explore content of *server-installer* modules that are built ** Notice the usage of the system property *rd.config* like [3]. The property is described on the reddeer wiki. [1] https://github.com/jbosstools/jbosstools-integration-stack-tests/blob/mas... [2] https://jbdsis-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Drools/job... [3] -Drd.config=$WORKSPACE/server-installer/$SERVER/target/config > Use RuntimeRequirement annotation > --------------------------------- > > Key: JBTIS-1026 > URL: https://issues.jboss.org/browse/JBTIS-1026 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: BPMN2, QE > Affects Versions: 4.4.0.Alpha1 > Reporter: Jozef Marko > Assignee: Dominik Hanak > > Replace the usage of > {code:java}org.jboss.tools.bpmn2.ui.bot.test.requirements.ProcessRuntimeRequirement{code} > with > {code:java}org.jboss.tools.runtime.reddeer.requirement.RuntimeRequirement{code} > * The annotation corresponding to RuntimeRequirement is used for example here [1]. > * How to run tests that uses this kind of annotation is shown here [2]. > ** Notice there is maven goal over the *server-installer* repository > ** Explore content of *server-installer* modules that are built > ** Notice the usage of the system property *rd.config* like [3]. The property is described on the reddeer wiki [4]. > [1] > https://github.com/jbosstools/jbosstools-integration-stack-tests/blob/mas... > [2] > https://jbdsis-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Drools/job... > [3] > -Drd.config=$WORKSPACE/server-installer/$SERVER/target/config > [4] > https://github.com/jboss-reddeer/reddeer/wiki/Tests-configuration -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1026) Use RuntimeRequirement annotation

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1026?page=com.atlassian.jira.plugin... ] Jozef Marko updated JBTIS-1026: ------------------------------- Description: Replace the usage of {code:java}org.jboss.tools.bpmn2.ui.bot.test.requirements.ProcessRuntimeRequirement{code} with {code:java}org.jboss.tools.runtime.reddeer.requirement.RuntimeRequirement{code} * The annotation corresponding to RuntimeRequirement is used for example here [1]. * How to run tests that uses this kind of annotation is shown here [2]. ** Notice there is maven goal over the *server-installer* repository ** Explore content of *server-installer* modules that are built ** Notice the usage of the system property *rd.config* like [3]. The property is described on the reddeer wiki. [1] https://github.com/jbosstools/jbosstools-integration-stack-tests/blob/mas... [2] https://jbdsis-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Drools/job... [3] -Drd.config=$WORKSPACE/server-installer/$SERVER/target/config was: Replace the usage of `org.jboss.tools.bpmn2.ui.bot.test.requirements.ProcessRuntimeRequirement` with `org.jboss.tools.runtime.reddeer.requirement.RuntimeRequirement` * The annotation corresponding to RuntimeRequirement is used for example here [1]. * How to run tests that uses this kind of annotation is shown here [2]. ** Notice there is maven goal over the *server-installer* repository ** Explore content of *server-installer* modules that are built ** Notice the usage of the system property *rd.config* like [3]. The property is described on the reddeer wiki. [1] https://github.com/jbosstools/jbosstools-integration-stack-tests/blob/mas... [2] https://jbdsis-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Drools/job... [3] -Drd.config=$WORKSPACE/server-installer/$SERVER/target/config > Use RuntimeRequirement annotation > --------------------------------- > > Key: JBTIS-1026 > URL: https://issues.jboss.org/browse/JBTIS-1026 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: BPMN2, QE > Affects Versions: 4.4.0.Alpha1 > Reporter: Jozef Marko > Assignee: Dominik Hanak > > Replace the usage of > {code:java}org.jboss.tools.bpmn2.ui.bot.test.requirements.ProcessRuntimeRequirement{code} > with > {code:java}org.jboss.tools.runtime.reddeer.requirement.RuntimeRequirement{code} > * The annotation corresponding to RuntimeRequirement is used for example here [1]. > * How to run tests that uses this kind of annotation is shown here [2]. > ** Notice there is maven goal over the *server-installer* repository > ** Explore content of *server-installer* modules that are built > ** Notice the usage of the system property *rd.config* like [3]. The property is described on the reddeer wiki. > [1] > https://github.com/jbosstools/jbosstools-integration-stack-tests/blob/mas... > [2] > https://jbdsis-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Drools/job... > [3] > -Drd.config=$WORKSPACE/server-installer/$SERVER/target/config -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1026) Use RuntimeRequirement annotation

by Jozef Marko (JIRA)

Jozef Marko created JBTIS-1026: ---------------------------------- Summary: Use RuntimeRequirement annotation Key: JBTIS-1026 URL: https://issues.jboss.org/browse/JBTIS-1026 Project: JBoss Tools Integration Stack Issue Type: Sub-task Components: BPMN2, QE Affects Versions: 4.4.0.Alpha1 Reporter: Jozef Marko Assignee: Dominik Hanak Replace the usage of `org.jboss.tools.bpmn2.ui.bot.test.requirements.ProcessRuntimeRequirement` with `org.jboss.tools.runtime.reddeer.requirement.RuntimeRequirement` * The annotation corresponding to RuntimeRequirement is used for example here [1]. * How to run tests that uses this kind of annotation is shown here [2]. ** Notice there is maven goal over the *server-installer* repository ** Explore content of *server-installer* modules that are built ** Notice the usage of the system property *rd.config* like [3]. The property is described on the reddeer wiki. [1] https://github.com/jbosstools/jbosstools-integration-stack-tests/blob/mas... [2] https://jbdsis-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Drools/job... [3] -Drd.config=$WORKSPACE/server-installer/$SERVER/target/config -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23782) Server adapter: Should keep trying to start (silently) instead of erroring and giving up

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23782?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23782: ------------------------------------- Labels: openshift_v3 server_adapter (was: ) > Server adapter: Should keep trying to start (silently) instead of erroring and giving up > ---------------------------------------------------------------------------------------- > > Key: JBIDE-23782 > URL: https://issues.jboss.org/browse/JBIDE-23782 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Labels: openshift_v3, server_adapter > Fix For: 4.4.3.AM2 > > Attachments: starting-server-adapter-failed.png > > > steps to reproduce: > # EXEC: create a new eap64-basic-s2i application in OpenShift and have the jboss-kitchensink project imported to your workspace (dont use a pre-created one) > # EXEC: create a server adapter for it > Result: > The server adapter immediately tries to start and publish once you finish the server adapter wizard. This leads to the following error which is expected since the pods, that the server adapter wants to publish to, dont exist yet. The build has to finish first. Once it's finished, the pod will be ready and available for the adapter to sync to. > !starting-server-adapter-failed.png! > The adapter then turns to [Stopped] and stays stopped. > I then have to keep watching the OpenShift Explorer or the Properties to catch the moment when the build's finished and the service pod is running. > Once this is achieved I can go and start the adapter which will then successfully publish. > It would be much nicer if the adapter would do this waiting for me, it would possibly still inform me that the pod doesnt exist yet but would watch the build and start publishing once it exists. > In order for this wait not to occur endlessly we could inform the user after some timeout, that we were waiting for some pods to appear but this didnt happen in the given timeframe. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23782) Server adapter: Should keep trying to start (silently) instead of erroring and giving up

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23782?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23782: ------------------------------------- Attachment: starting-server-adapter-failed.png > Server adapter: Should keep trying to start (silently) instead of erroring and giving up > ---------------------------------------------------------------------------------------- > > Key: JBIDE-23782 > URL: https://issues.jboss.org/browse/JBIDE-23782 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Fix For: 4.4.3.AM2 > > Attachments: starting-server-adapter-failed.png > > > steps to reproduce: > # EXEC: create a new eap64-basic-s2i application in OpenShift and have the jboss-kitchensink project imported to your workspace (dont use a pre-created one) > # EXEC: create a server adapter for it > Result: > The server adapter immediately tries to start and publish once you finish the server adapter wizard. This leads to the following error which is expected since the pods, that the server adapter wants to publish to, dont exist yet. The build has to finish first. Once it's finished, the pod will be ready and available for the adapter to sync to. > !! > The adapter then turns to [Stopped] and stays stopped. > I then have to keep watching the OpenShift Explorer or the Properties to catch the moment when the build's finished and the service pod is running. > Once this is achieved I can go and start the adapter which will then successfully publish. > It would be much nicer if the adapter would do this waiting for me, it would possibly still inform me that the pod doesnt exist yet but would watch the build and start publishing once it exists. > In order for this wait not to occur endlessly we could inform the user after some timeout, that we were waiting for some pods to appear but this didnt happen in the given timeframe. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 January 2017