[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:
------------------------------------------
Epic Name: Pipeline
Team: Infrastructure (was: Infrastructure)
> Modularize CI/CD Pipline
> ------------------------
>
> Key: SWSQE-145
> URL: https://issues.jboss.org/browse/SWSQE-145
> Project: Kiali QE
> Issue Type: Epic
> Reporter: Matt Mahoney
> Assignee: Guilherme Baufaker Rêgo
> Attachments: pipeline proposal.png
>
>
> 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
[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:
------------------------------------------
Attachment: pipeline proposal.png
> Modularize CI/CD Pipline
> ------------------------
>
> Key: SWSQE-145
> URL: https://issues.jboss.org/browse/SWSQE-145
> Project: Kiali QE
> Issue Type: Epic
> Reporter: Matt Mahoney
> Assignee: Guilherme Baufaker Rêgo
> Attachments: pipeline proposal.png
>
>
> 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
[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:
------------------------------------------
Issue Type: Epic (was: Story)
> Modularize CI/CD Pipline
> ------------------------
>
> Key: SWSQE-145
> URL: https://issues.jboss.org/browse/SWSQE-145
> Project: Kiali QE
> Issue Type: Epic
> Reporter: Matt Mahoney
> Assignee: Guilherme Baufaker Rêgo
>
> 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
[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:
------------------------------------------
Attachment: (was: Kiali QE CD Pipeline - Pro.pdf)
> Modularize CI/CD Pipline
> ------------------------
>
> Key: SWSQE-145
> URL: https://issues.jboss.org/browse/SWSQE-145
> Project: Kiali QE
> Issue Type: Epic
> Reporter: Matt Mahoney
> Assignee: Guilherme Baufaker Rêgo
>
> 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
[JBoss JIRA] (WFLY-10238) Wsprovide tool doesn't generate/keep class files on JDK10
by R Searls (JIRA)
[ https://issues.jboss.org/browse/WFLY-10238?page=com.atlassian.jira.plugin... ]
R Searls edited comment on WFLY-10238 at 4/17/18 4:06 PM:
----------------------------------------------------------
To resolve this, an enhancement is required to apache CXF.
https://issues.apache.org/jira/browse/CXF-7711 was filed
Submitted PR: https://github.com/apache/cxf/pull/406
That PR will need to be back ported to cxf-3.2.4 which is the version wfly-13 and jbossws is using.
A PR will be needed for jbossws to use the change to CXF.
JBWS-4113 was filed. PR is pending CXF merge or a redhat specific cxf archive build.
was (Author: rsearls):
To resolve this, an enhancement is required to apache CXF.
https://issues.apache.org/jira/browse/CXF-7711 was filed
Submitted PR: https://github.com/jboss/cxf/pull/19
That PR will need to be back ported to cxf-3.2.4 which is the version wfly-13 and jbossws is using.
A PR will be needed for jbossws to use the change to CXF.
JBWS-4113 was filed. PR is pending CXF merge or a redhat specific cxf archive build.
> Wsprovide tool doesn't generate/keep class files on JDK10
> ---------------------------------------------------------
>
> Key: WFLY-10238
> URL: https://issues.jboss.org/browse/WFLY-10238
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Reporter: Marek Kopecký
> Assignee: R Searls
> Priority: Blocker
> Fix For: 13.0.0.Beta1
>
> Attachments: classes.zip
>
>
> Wsprovide tool doesn't keep class files on JDK10
> Example:
> {noformat}
> [mkopecky@localhost bin]$ jdk8
> [mkopecky@localhost bin]$ java -version
> java version "1.8.0_111"
> Java(TM) SE Runtime Environment (build 1.8.0_111-b14)
> Java HotSpot(TM) 64-Bit Server VM (build 25.111-b14, mixed mode)
> [mkopecky@localhost bin]$ ./wsprovide.sh -k -c ~/erase10/classes -o out org.jboss.as.testsuite.integration.scripts.test.tools.Echo1Impl
> Could not find log4j.properties or log4j.xml configuration, logging to console.
> java2ws -s /home/mkopecky/playground/wf/wfly.22/wfly.22/bin/out -classdir /home/mkopecky/playground/wf/wfly.22/wfly.22/bin/out -d /home/mkopecky/playground/wf/wfly.22/wfly.22/bin/out -verbose -cp /home/mkopecky/erase10/classes/: -wrapperbean -createxsdimports org.jboss.as.testsuite.integration.scripts.test.tools.Echo1Impl
> java2ws - Apache CXF 3.2.4
> [mkopecky@localhost bin]$ find out/ | grep class
> out/org/jboss/as/testsuite/integration/scripts/test/tools/jaxws/EchoPlus1.class
> out/org/jboss/as/testsuite/integration/scripts/test/tools/jaxws/EchoPlus1Response.class
> [mkopecky@localhost bin]$ jdk10
> [mkopecky@localhost bin]$ rm -rf out
> [mkopecky@localhost bin]$ java -version
> java version "10" 2018-03-20
> Java(TM) SE Runtime Environment 18.3 (build 10+46)
> Java HotSpot(TM) 64-Bit Server VM 18.3 (build 10+46, mixed mode)
> [mkopecky@localhost bin]$ ./wsprovide.sh -k -c ~/erase10/classes -o out org.jboss.as.testsuite.integration.scripts.test.tools.Echo1Impl
> Could not find log4j.properties or log4j.xml configuration, logging to console.
> java2ws -s /home/mkopecky/playground/wf/wfly.22/wfly.22/bin/out -classdir /home/mkopecky/playground/wf/wfly.22/wfly.22/bin/out -d /home/mkopecky/playground/wf/wfly.22/wfly.22/bin/out -verbose -cp /home/mkopecky/erase10/classes/: -wrapperbean -createxsdimports org.jboss.as.testsuite.integration.scripts.test.tools.Echo1Impl
> java2ws - Apache CXF 3.2.4
> [mkopecky@localhost bin]$ find out/ | grep class
> [mkopecky@localhost bin]$
> {noformat}
> I attached input class files. I see this issue on WF with latest WS.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFCORE-3751) DefaultCapabilityReferenceRecorder generates wrong dependent name if corresponding RuntimeCapability uses a dynamic name mapper
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3751?page=com.atlassian.jira.plugi... ]
Paul Ferraro updated WFCORE-3751:
---------------------------------
Summary: DefaultCapabilityReferenceRecorder generates wrong dependent name if corresponding RuntimeCapability uses a dynamic name mapper (was: DefaultCapabilityReferenceRecorder cannot be used with capabilities that use a dynamic name mapper)
> DefaultCapabilityReferenceRecorder generates wrong dependent name if corresponding RuntimeCapability uses a dynamic name mapper
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-3751
> URL: https://issues.jboss.org/browse/WFCORE-3751
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 5.0.0.Alpha2
> Reporter: Paul Ferraro
> Assignee: Brian Stansberry
>
> CapabilityReferenceRecorder.DefaultCapabilityReferenceRecorder should be generalized to handle capabilities that use a dynamic name mapper.
> While most users can workaround the problem by using ContextDependencyRecorder instead - this is limited to resources that define a single capability.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years