[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: Kiali 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: Kiali 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
--
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: 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: Kiali 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
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2250) Align Engine hints in Decision Table column wizard with BAPL-708
by Stetson Robinson (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2250?page=com.atlassian.jira.plugi... ]
Stetson Robinson commented on DROOLS-2250:
------------------------------------------
[~jomarko], please delete that reference. With our new user-based doc set, we no longer have a Dev Guide, User Guide, etc., and as of now, Truth Maintenance is not documented anywhere for DM/PAM. All other references in the UI to the legacy doc set (Dev Guide, User Guide, Admin Guide, blabla Guide) need to be removed also going forward, if you encounter them (there shouldn't be many, I suspect).
> Align Engine hints in Decision Table column wizard with BAPL-708
> ----------------------------------------------------------------
>
> Key: DROOLS-2250
> URL: https://issues.jboss.org/browse/DROOLS-2250
> Project: Drools
> Issue Type: Task
> Components: Guided Decision Table Editor
> Affects Versions: 7.6.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Fix For: 7.6.0.Final
>
> Attachments: Screenshot from 2018-01-17 13-49-51.png, Screenshot from 2018-01-17 13-50-37.png, Screenshot from 2018-01-19 14-35-50.png
>
>
> Due to the BAPL-708 and the [doc|https://docs.google.com/spreadsheets/d/1kmK92hY3JJp7gZTvLzd0CawaZzvI2...] with new product terminology, we should update the Engine hint shown in the attached screenshots. We should use *decision engine* or *process / engine* instad of *inference engine*, *rules engine* etc.
> [edited]
> Also the Data Object designer affected, see the role hint.
> !Screenshot from 2018-01-19 14-35-50.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2250) Align Engine hints in Decision Table column wizard with BAPL-708
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2250?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-2250:
-------------------------------------
Jira is reopened because the engine hint is not correct. I agree that is my fail I didn't realize during filing that two parts of the hint have to be updated however I don't see reason to file separate jira, thanks Michael, will create PRs.
> Align Engine hints in Decision Table column wizard with BAPL-708
> ----------------------------------------------------------------
>
> Key: DROOLS-2250
> URL: https://issues.jboss.org/browse/DROOLS-2250
> Project: Drools
> Issue Type: Task
> Components: Guided Decision Table Editor
> Affects Versions: 7.6.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Fix For: 7.6.0.Final
>
> Attachments: Screenshot from 2018-01-17 13-49-51.png, Screenshot from 2018-01-17 13-50-37.png, Screenshot from 2018-01-19 14-35-50.png
>
>
> Due to the BAPL-708 and the [doc|https://docs.google.com/spreadsheets/d/1kmK92hY3JJp7gZTvLzd0CawaZzvI2...] with new product terminology, we should update the Engine hint shown in the attached screenshots. We should use *decision engine* or *process / engine* instad of *inference engine*, *rules engine* etc.
> [edited]
> Also the Data Object designer affected, see the role hint.
> !Screenshot from 2018-01-19 14-35-50.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2250) Align Engine hints in Decision Table column wizard with BAPL-708
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2250?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-2250:
----------------------------------------
[~jomarko] I am confused why this is re-opened.
The PRs making the original fix did not touch upon "Red Hat X, Y or Z".
The line in the {{Constants}} file (containing "Red Hat JBoss BPM Suite Development Guide") was added for https://issues.jboss.org/browse/GUVNOR-3462
Personally, whatever JIRA is re-opened, I'd prefer to re-phrase to something more generic like "... For more details, see Truth Maintenance in the User Guide".
> Align Engine hints in Decision Table column wizard with BAPL-708
> ----------------------------------------------------------------
>
> Key: DROOLS-2250
> URL: https://issues.jboss.org/browse/DROOLS-2250
> Project: Drools
> Issue Type: Task
> Components: Guided Decision Table Editor
> Affects Versions: 7.6.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Fix For: 7.6.0.Final
>
> Attachments: Screenshot from 2018-01-17 13-49-51.png, Screenshot from 2018-01-17 13-50-37.png, Screenshot from 2018-01-19 14-35-50.png
>
>
> Due to the BAPL-708 and the [doc|https://docs.google.com/spreadsheets/d/1kmK92hY3JJp7gZTvLzd0CawaZzvI2...] with new product terminology, we should update the Engine hint shown in the attached screenshots. We should use *decision engine* or *process / engine* instad of *inference engine*, *rules engine* etc.
> [edited]
> Also the Data Object designer affected, see the role hint.
> !Screenshot from 2018-01-19 14-35-50.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2251) Align Test Scenario KIE configuration with BAPL-708
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2251?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2251:
--------------------------------
Attachment: scenario-after-fix.png
> Align Test Scenario KIE configuration with BAPL-708
> ---------------------------------------------------
>
> Key: DROOLS-2251
> URL: https://issues.jboss.org/browse/DROOLS-2251
> Project: Drools
> Issue Type: Task
> Components: Test Scenarios Editor
> Affects Versions: 7.6.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Fix For: 7.7.0.Final, 7.8.0.Final
>
> Attachments: Screenshot from 2018-04-06 11-19-22.png, scenario-after-fix.png
>
>
> Test Scenario designer KIE configuration part should be updated to use terms *KIE base* and *KIE session* instead of the *knowledge base* and *knowledge session*.
> h2. Acceptance test
> - Changes applied in the screen from attachment
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFLY-8217) ActiveMQ leaks connections if a JMS message is sent from an MDB
by Michael Auß (JIRA)
[ https://issues.jboss.org/browse/WFLY-8217?page=com.atlassian.jira.plugin.... ]
Michael Auß commented on WFLY-8217:
-----------------------------------
any update on this issue?
> ActiveMQ leaks connections if a JMS message is sent from an MDB
> ---------------------------------------------------------------
>
> Key: WFLY-8217
> URL: https://issues.jboss.org/browse/WFLY-8217
> Project: WildFly
> Issue Type: Bug
> Components: JMS, Transactions
> Affects Versions: 10.1.0.Final
> Environment: Running on Windows 10. Java(TM) SE Runtime Environment (build 1.8.0_92-b14)
> Reporter: Scott Van Wart
> Assignee: Jeff Mesnil
> Priority: Minor
> Attachments: leak.zip, leak.zip, log.txt, log.txt, server.log
>
>
> If an MDB causes a JMS message to be sent during the call to onMessage(), ActiveMQ won't close its connection. I'm using JMS2 through an @Inject'ed JMSContext. My sample project is an EAR with an EJB JAR (containing a service and an MDB) and a JAX-RS endpoint (entry point for the test).
> 1) Build the EAR
> 2) Run wildfly with the standalone-full.xml configuration:
> {{standalone.bat --server-config=standalone-full.xml}}
> 3) Enable debug and error reporting for leaked connections with ActiveMQ/CCM:
> {{jboss-cli.bat -c}}
> {{/subsystem=jca/cached-connection-manager=cached-connection-manager:write-attribute(name=debug,value=true)}}
> {{/subsystem=jca/cached-connection-manager=cached-connection-manager:write-attribute(name=error,value=true)}}
> 4) Deploy the EAR.
> 5) Access http://localhost:8080/leak-web/rest/test?message=Hi
> The REST endpoint will send a message to the test topic (Defined in leak-ejb/src/main/java/test/mdb/TestTopic.java). TestTopicListener (in the same package as TestTopic) will receive the message and send a second message to the topic. Upon returning from TestTopicListener.onMessage(), the message is sent, but this shows up in the logs
> (see attached log.txt)
> I have no idea why JIRA attached each file twice.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFLY-10256) WildFly Common and shaded jars with MR overlays do not have defined Multi-Release in Manifest
by Rostislav Svoboda (JIRA)
Rostislav Svoboda created WFLY-10256:
----------------------------------------
Summary: WildFly Common and shaded jars with MR overlays do not have defined Multi-Release in Manifest
Key: WFLY-10256
URL: https://issues.jboss.org/browse/WFLY-10256
Project: WildFly
Issue Type: Bug
Components: Server
Affects Versions: 12.0.0.Final
Reporter: Rostislav Svoboda
Assignee: David Lloyd
Priority: Critical
Several jars with MR overlays do not have defined Multi-Release in Manifest
Results with WildFly master from 2018-04-18:
{code}
DistributionTestCase.checkOverlayDirectoryAndManifestEntryForExpectedMRJars:93
The following 4 assertions failed:
1) [Artifact /Users/rsvoboda/git/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/bin/wildfly-elytron-tool.jar is expected to be Multi-Release JAR, jar.isMultiReleaseJar() returns false] expected:<[tru]e> but was:<[fals]e>
at DistributionTestCase.lambda$checkOverlayDirectoryAndManifestEntryForExpectedMRJars$8(DistributionTestCase.java:90) expected:<[tru]e> but was:<[fals]e>
2) [Artifact /Users/rsvoboda/git/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/bin/client/jboss-cli-client.jar is expected to be Multi-Release JAR, jar.isMultiReleaseJar() returns false] expected:<[tru]e> but was:<[fals]e>
at DistributionTestCase.lambda$checkOverlayDirectoryAndManifestEntryForExpectedMRJars$8(DistributionTestCase.java:90) expected:<[tru]e> but was:<[fals]e>
3) [Artifact /Users/rsvoboda/git/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/bin/client/jboss-client.jar is expected to be Multi-Release JAR, jar.isMultiReleaseJar() returns false] expected:<[tru]e> but was:<[fals]e>
at DistributionTestCase.lambda$checkOverlayDirectoryAndManifestEntryForExpectedMRJars$8(DistributionTestCase.java:90) expected:<[tru]e> but was:<[fals]e>
4) [Artifact /Users/rsvoboda/git/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/wildfly/common/main/wildfly-common-1.3.1.Final.jar is expected to be Multi-Release JAR, jar.isMultiReleaseJar() returns false] expected:<[tru]e> but was:<[fals]e>
at DistributionTestCase.lambda$checkOverlayDirectoryAndManifestEntryForExpectedMRJars$8(DistributionTestCase.java:90) expected:<[tru]e> but was:<[fals]e>
{code}
According MR JAR Support in JBoss Parent proposal WildFly Common should have Manifest entry
* modules/system/layers/base/org/wildfly/common/main/wildfly-common-1.3.1.Final.jar
I believe shaded jars should also have Manifest entry
* bin/wildfly-elytron-tool.jar
* bin/client/jboss-cli-client.jar
* bin/client/jboss-client.jar
Using https://github.com/jboss-eap-qe/jarest/pull/3/files ++ mvn test -Djarest.input.dir=/Users/rsvoboda/git/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years