April 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-79) Report jenkins CI result back to the community(github PR's)

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-79?page=com.atlassian.jira.plugin.s... ] Matt Mahoney updated SWSQE-79: ------------------------------ Sprint: SWS QE Sprint 2 (was: SWS QE Sprint 2, Kiali QE Sprint 4) > Report jenkins CI result back to the community(github PR's) > ----------------------------------------------------------- > > Key: SWSQE-79 > URL: https://issues.jboss.org/browse/SWSQE-79 > Project: Kiali QE > Issue Type: Task > Reporter: Jeeva Kandasamy > Assignee: Jeeva Kandasamy > > Currently, we show only pass or fail status of the suite to PR. There is no failure reason for PR from internal Jenkins job. > Sample: https://github.com/jaegertracing/jaeger-openshift/tree/master/jenkins-ci -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-138) Add kiali-client-python to the Jenkins Python/Selenium Slave Image

by Filip Brychta (JIRA)

[ https://issues.jboss.org/browse/SWSQE-138?page=com.atlassian.jira.plugin.... ] Filip Brychta reassigned SWSQE-138: ----------------------------------- Assignee: Filip Brychta (was: Michael Foley) > Add kiali-client-python to the Jenkins Python/Selenium Slave Image > ------------------------------------------------------------------ > > Key: SWSQE-138 > URL: https://issues.jboss.org/browse/SWSQE-138 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Matt Mahoney > Assignee: Filip Brychta > > Add the Kiali-Client python module to the Jenkins Python/Selenium Slave image. > [Kiali-Client|https://github.com/Kiali-QE/kiali-client-python] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-103) Create internal docker registry in our production openshift

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-103?page=com.atlassian.jira.plugin.... ] Matt Mahoney updated SWSQE-103: ------------------------------- Priority: Minor (was: Major) > Create internal docker registry in our production openshift > ----------------------------------------------------------- > > Key: SWSQE-103 > URL: https://issues.jboss.org/browse/SWSQE-103 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Minor > > It would be good to use our internal docker registry for: > * jenkins docker slaves > * internal qe images of kiali > * other external images not to pulling them from internet > This registry should be accessible from outside too. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10248) write to jgroups-channel throws IllegalStateException

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-10248?page=com.atlassian.jira.plugin... ] Paul Ferraro commented on WFLY-10248: ------------------------------------- Ah - you're absolutely right. This is a bug. The value "ejb" should indeed be acceptable (I forgot that we create aliases for each Infinispan cache-container). However, the bug is not with the clustering capability, or the messaging write handler, but with the capability reference itself. The capability in question defines a dynamic name mapper, however, the CapabilityReferenceRecorder implementation does not use it to construct the dependent name. So, while this really ought to be fixed in wildfly-core, in the meantime, messaging can use a custom CapabilityReferenceRecorder implementation (e.g. the one in wildfly-clustering-common). > write to jgroups-channel throws IllegalStateException > ----------------------------------------------------- > > Key: WFLY-10248 > URL: https://issues.jboss.org/browse/WFLY-10248 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Claudio Miranda > Assignee: Jeff Mesnil > > {code} > /profile=full-ha/subsystem=messaging-activemq/server=default/discovery-group=my_disco:add(jgroups-channel=ee,jgroups-cluster=disco) > { > "outcome" => "success", > "result" => undefined, > "server-groups" => {"other-server-group" => {"host" => {"master" => {"server-three" => {"response" => { > "outcome" => "success", > "response-headers" => { > "operation-requires-reload" => true, > "process-state" => "reload-required" > } > }}}}}} > } > [domain@uranus-0:9990 /] reload --host=master > {code} > reload host master, success > Then, try to replace jgroups-channel value "ee" to "ejb", as its suggested by capability-reference > {code} > /profile=full-ha/subsystem=messaging-activemq/server=default/discovery-group=my_disco:write-attribute(name=jgroups-channel,value=ejb) > { > "outcome" => "failed", > "failure-description" => {"domain-failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalStateException: WFLYCTL0365: Capability 'org.wildfly.messaging.activemq.discovery-group.my_disco' is unknown in context 'profile=full-ha'."}, > "rolled-back" => true > } > {code} > {code} > 2018-04-16 16:10:31,044 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("write-attribute") failed - address: ([ > ("profile" => "full-ha"), > ("subsystem" => "messaging-activemq"), > ("server" => "default"), > ("discovery-group" => "my_disco") > ]): java.lang.IllegalStateException: WFLYCTL0365: Capability 'org.wildfly.messaging.activemq.discovery-group.my_disco' is unknown in context 'profile=full-ha'. > at org.jboss.as.controller.CapabilityRegistry.registerRequirement(CapabilityRegistry.java:212) > at org.jboss.as.controller.CapabilityRegistry.registerAdditionalCapabilityRequirement(CapabilityRegistry.java:198) > at org.jboss.as.controller.OperationContextImpl.registerAdditionalCapabilityRequirement(OperationContextImpl.java:1520) > at org.jboss.as.controller.OperationContextImpl.registerAdditionalCapabilityRequirement(OperationContextImpl.java:1512) > at org.jboss.as.controller.CapabilityReferenceRecorder$DefaultCapabilityReferenceRecorder.processCapabilityRequirement(CapabilityReferenceRecorder.java:137) > at org.jboss.as.controller.CapabilityReferenceRecorder$DefaultCapabilityReferenceRecorder.addCapabilityRequirements(CapabilityReferenceRecorder.java:114) > at org.jboss.as.controller.AttributeDefinition.addCapabilityRequirements(AttributeDefinition.java:1066) > at org.jboss.as.controller.AbstractWriteAttributeHandler.recordCapabilitiesAndRequirements(AbstractWriteAttributeHandler.java:191) > at org.jboss.as.controller.AbstractWriteAttributeHandler.execute(AbstractWriteAttributeHandler.java:89) > at org.jboss.as.controller.operations.global.WriteAttributeHandler.doExecuteInternal(WriteAttributeHandler.java:194) > at org.jboss.as.controller.operations.global.WriteAttributeHandler.execute(WriteAttributeHandler.java:115) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:982) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:726) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:450) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1408) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:423) > at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:263) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:229) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:240) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:138) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:162) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:158) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:287) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:244) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:158) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.lang.Thread.run(Thread.java:748) > at org.jboss.threads.JBossThread.run(JBossThread.java:485) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-99) Why are tests running against zalenim in VM faster then zalenium in OS

by Filip Brychta (JIRA)

[ https://issues.jboss.org/browse/SWSQE-99?page=com.atlassian.jira.plugin.s... ] Filip Brychta updated SWSQE-99: ------------------------------- Sprint: (was: Kiali QE Sprint 4) > Why are tests running against zalenim in VM faster then zalenium in OS > ---------------------------------------------------------------------- > > Key: SWSQE-99 > URL: https://issues.jboss.org/browse/SWSQE-99 > Project: Kiali QE > Issue Type: Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Minor > > Tests running against http://zalenium.bc.jonqe.lab.eng.bos.redhat.com:4444 are faster then http://zalenium-fbr-zal-test.openshift.jonqe.lab.eng.bos.redhat.com/ > Why? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-90) Remove b24 and b25 from hawkular performace cluster

by Filip Brychta (JIRA)

[ https://issues.jboss.org/browse/SWSQE-90?page=com.atlassian.jira.plugin.s... ] Filip Brychta updated SWSQE-90: ------------------------------- Priority: Minor (was: Major) > Remove b24 and b25 from hawkular performace cluster > --------------------------------------------------- > > Key: SWSQE-90 > URL: https://issues.jboss.org/browse/SWSQE-90 > Project: Kiali QE > Issue Type: Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Minor > > Those 2 blades are used for hawkular performance testing. We agreed to drop that testing so those can be cleaned. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-90) Remove b24 and b25 from hawkular performace cluster

by Filip Brychta (JIRA)

[ https://issues.jboss.org/browse/SWSQE-90?page=com.atlassian.jira.plugin.s... ] Filip Brychta updated SWSQE-90: ------------------------------- Sprint: (was: Kiali QE Sprint 4) > Remove b24 and b25 from hawkular performace cluster > --------------------------------------------------- > > Key: SWSQE-90 > URL: https://issues.jboss.org/browse/SWSQE-90 > Project: Kiali QE > Issue Type: Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Minor > > Those 2 blades are used for hawkular performance testing. We agreed to drop that testing so those can be cleaned. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-99) Why are tests running against zalenim in VM faster then zalenium in OS

by Filip Brychta (JIRA)

[ https://issues.jboss.org/browse/SWSQE-99?page=com.atlassian.jira.plugin.s... ] Filip Brychta updated SWSQE-99: ------------------------------- Priority: Minor (was: Major) > Why are tests running against zalenim in VM faster then zalenium in OS > ---------------------------------------------------------------------- > > Key: SWSQE-99 > URL: https://issues.jboss.org/browse/SWSQE-99 > Project: Kiali QE > Issue Type: Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Minor > > Tests running against http://zalenium.bc.jonqe.lab.eng.bos.redhat.com:4444 are faster then http://zalenium-fbr-zal-test.openshift.jonqe.lab.eng.bos.redhat.com/ > Why? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-138) Add kiali-client-python to the Jenkins Python/Selenium Slave Image

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-138?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-138: ------------------------------------------ Parent: SWSQE-127 Issue Type: Sub-task (was: Task) > Add kiali-client-python to the Jenkins Python/Selenium Slave Image > ------------------------------------------------------------------ > > Key: SWSQE-138 > URL: https://issues.jboss.org/browse/SWSQE-138 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Matt Mahoney > Assignee: Michael Foley > > Add the Kiali-Client python module to the Jenkins Python/Selenium Slave image. > [Kiali-Client|https://github.com/Kiali-QE/kiali-client-python] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-145) Modularize CI/CD Pipline

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-145?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-145: ------------------------------------------ Team: Infrastructure (was: Infrastructure) Sprint: Kiali QE Sprint 4 > Modularize CI/CD Pipline > ------------------------ > > Key: SWSQE-145 > URL: https://issues.jboss.org/browse/SWSQE-145 > Project: Kiali QE > Issue Type: Story > Reporter: Matt Mahoney > Assignee: Michael Foley > > The CI/CD pipeline has become more complex and challenging with which to build CI/CD usage-cases and to add new functionality: > Use Case Examples: > 1) Deploy Istio -> Deploy&build-kiali -> Deploy All Service Meshes -> Deploy Traffic Generator on all Service Meshes -> Run all test suites > 2) Deploy built Kiali -> Run REST suite > 3) Build and Deploy Kiali -> Run all test suites > 4) Run UI suite on any Openshift Cluster > Exc, etc, lots of scenarios which would be built by modules. > Modularize into self-contained Jenkins jobs that can by themselves can do the following: > - Install Istio + Book Info > - Build Kiali > - Deploy Kiali > - Deploy Service Mesh's (all or subset there-of) > - Deploy Traffic Generator > - Run test suites + Report results to Community -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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

jboss-jira April 2018