[JBoss JIRA] (WFCORE-3751) DefaultCapabilityReferenceRecorder cannot be used with capabilities that use 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 cannot be used with capabilities that use a dynamic name mapper (was: DefaultCapabilityReference cannot be used with capabilities that use a dynamic name mapper)
> DefaultCapabilityReferenceRecorder cannot be used with capabilities that use 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
[JBoss JIRA] (SWSQE-145) Modularize CI/CD Pipline
by Michael Foley (JIRA)
[ https://issues.jboss.org/browse/SWSQE-145?page=com.atlassian.jira.plugin.... ]
Michael Foley updated SWSQE-145:
--------------------------------
Attachment: 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: Story
> Reporter: Matt Mahoney
> Assignee: Guilherme Baufaker Rêgo
> Attachments: Kiali QE CD Pipeline - Pro.pdf
>
>
> 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-163) Create sub-tasks ... and move a few discrete sub-tasks from this story to sprint #4
by Michael Foley (JIRA)
[ https://issues.jboss.org/browse/SWSQE-163?page=com.atlassian.jira.plugin.... ]
Michael Foley updated SWSQE-163:
--------------------------------
Description:
The modularization of the CI/CD pipeline is a large topic ... epic or user story. The first step is to do task breakdown into more discrete units of work.
[~mmahoney] has a slide or google doc outlining, at a high-level, some thoughts (Matt, please attach your slide to this Jira). Using this document as input, I would like to ask [~gbaufake] to work with [~hhovsepy] to create a set of sub-tasks that represent the planned modularization work in some detail. Each unit of work should be around 1 or 2 days of work, at most. And taken together, these sub-tasks will represent the improvements.
Once the sub-tasks are created:
* move this epic out of sprint 4
* move in the specific discrete sub-tasks that are needed for sprint #4
was:
The modularization of the CI/CD pipeline is a large topic ... epic or user story. The first step is to do task breakdown into more discrete units of work.
[~mmahoney] has a slide or google doc outlining, at a high-level, some thoughts (Matt, please attach your slide to this Jira). Using this document as input, I would like to ask [~gbaufake] to work with [~hhovsepy] to create a set of sub-tasks that represent the planned modularization work in some detail. Each unit of work should be around 1 or 2 days of work, at most. And taken together, these sub-tasks will represent the improvements.
Once the sub-tasks are created:
* move this epic out of sprint 4
* move in the specific tasks that are needed for sprint #4
Team: (was: Infrastructure)
> Create sub-tasks ... and move a few discrete sub-tasks from this story to sprint #4
> ------------------------------------------------------------------------------------
>
> Key: SWSQE-163
> URL: https://issues.jboss.org/browse/SWSQE-163
> Project: Kiali QE
> Issue Type: Sub-task
> Reporter: Michael Foley
> Assignee: Guilherme Baufaker Rêgo
>
> The modularization of the CI/CD pipeline is a large topic ... epic or user story. The first step is to do task breakdown into more discrete units of work.
> [~mmahoney] has a slide or google doc outlining, at a high-level, some thoughts (Matt, please attach your slide to this Jira). Using this document as input, I would like to ask [~gbaufake] to work with [~hhovsepy] to create a set of sub-tasks that represent the planned modularization work in some detail. Each unit of work should be around 1 or 2 days of work, at most. And taken together, these sub-tasks will represent the improvements.
> Once the sub-tasks are created:
> * move this epic out of sprint 4
> * move in the specific discrete sub-tasks that are needed for sprint #4
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (SWSQE-163) Create sub-tasks ... and move a few discrete sub-tasks from this story to sprint #4
by Michael Foley (JIRA)
[ https://issues.jboss.org/browse/SWSQE-163?page=com.atlassian.jira.plugin.... ]
Michael Foley updated SWSQE-163:
--------------------------------
Description:
The modularization of the CI/CD pipeline is a large topic ... epic or user story. The first step is to do task breakdown into more discrete units of work.
[~mmahoney] has a slide or google doc outlining, at a high-level, some thoughts (Matt, please attach your slide to this Jira). Using this document as input, I would like to ask [~gbaufake] to work with [~hhovsepy] to create a set of sub-tasks that represent the planned modularization work in some detail. Each unit of work should be around 1 or 2 days of work, at most. And taken together, these sub-tasks will represent the improvements.
Once the sub-tasks are created:
* move this epic out of sprint 4
* move in the specific tasks that are needed for sprint #4
was:
The modularization of the CI/CD pipeline is a large topic ... epic or user story. The first step is to do task breakdown into more discrete units of work.
[~mmahoney] has a slide or google doc outlining, at a high-level, some thoughts. Using this document as input, I would like to ask [~gbaufake] to work with [~hhovsepy] to create a set of sub-tasks that represent the planned modularization work in some detail. Each unit of work should be around 1 or 2 days of work, at most. And taken together, these sub-tasks will represent the improvements.
Once the sub-tasks are created:
* move this epic out of sprint 4
* move in the specific tasks that are needed for sprint #4
Team: (was: Infrastructure)
> Create sub-tasks ... and move a few discrete sub-tasks from this story to sprint #4
> ------------------------------------------------------------------------------------
>
> Key: SWSQE-163
> URL: https://issues.jboss.org/browse/SWSQE-163
> Project: Kiali QE
> Issue Type: Sub-task
> Reporter: Michael Foley
> Assignee: Guilherme Baufaker Rêgo
>
> The modularization of the CI/CD pipeline is a large topic ... epic or user story. The first step is to do task breakdown into more discrete units of work.
> [~mmahoney] has a slide or google doc outlining, at a high-level, some thoughts (Matt, please attach your slide to this Jira). Using this document as input, I would like to ask [~gbaufake] to work with [~hhovsepy] to create a set of sub-tasks that represent the planned modularization work in some detail. Each unit of work should be around 1 or 2 days of work, at most. And taken together, these sub-tasks will represent the improvements.
> Once the sub-tasks are created:
> * move this epic out of sprint 4
> * move in the specific tasks that are needed for sprint #4
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFLY-10255) Swagger Integration does not honor JAXB @XmlTransient annotation (and possibly more)
by Jonathan Fisher (JIRA)
Jonathan Fisher created WFLY-10255:
--------------------------------------
Summary: Swagger Integration does not honor JAXB @XmlTransient annotation (and possibly more)
Key: WFLY-10255
URL: https://issues.jboss.org/browse/WFLY-10255
Project: WildFly
Issue Type: Bug
Components: JAXR
Affects Versions: 12.0.0.Final
Reporter: Jonathan Fisher
Assignee: Kurt Stam
Swagger does not honor JAXB annotations. If you mark a field on an Object as @XmlTransient, it will not be rendered in the XML or JSON output to the client. However, if will still be shown in the swagger.json. If you annotate the field with @JsonIgnore (jackson annotation), it will be omitted from the swagger.json as expected.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (SWSQE-163) Create sub-tasks ... and move a few discrete sub-tasks from this story to sprint #4
by Michael Foley (JIRA)
Michael Foley created SWSQE-163:
-----------------------------------
Summary: Create sub-tasks ... and move a few discrete sub-tasks from this story to sprint #4
Key: SWSQE-163
URL: https://issues.jboss.org/browse/SWSQE-163
Project: Kiali QE
Issue Type: Sub-task
Reporter: Michael Foley
Assignee: Guilherme Baufaker Rêgo
The modularization of the CI/CD pipeline is a large topic ... epic or user story. The first step is to do task breakdown into more discrete units of work.
[~mmahoney] has a slide or google doc outlining, at a high-level, some thoughts. Using this document as input, I would like to ask [~gbaufake] to work with [~hhovsepy] to create a set of sub-tasks that represent the planned modularization work in some detail. Each unit of work should be around 1 or 2 days of work, at most. And taken together, these sub-tasks will represent the improvements.
Once the sub-tasks are created:
* move this epic out of sprint 4
* move in the specific tasks that are needed for sprint #4
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (SWSQE-145) Modularize CI/CD Pipline
by Michael Foley (JIRA)
[ https://issues.jboss.org/browse/SWSQE-145?page=com.atlassian.jira.plugin.... ]
Michael Foley reassigned SWSQE-145:
-----------------------------------
Assignee: Guilherme Baufaker Rêgo (was: Michael Foley)
> 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: 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-10229) org.jboss.as.txn.service.internal.tsr.TransactionSynchronizationRegistryWrapper.getStatus() should use org.wildfly.transaction.client.ContextTransactionManager.getStatus()
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-10229?page=com.atlassian.jira.plugin... ]
David Lloyd commented on WFLY-10229:
------------------------------------
bq. David Lloyd if the transaction has been marked for rollback then Narayana won't call before completion:
Okay, so much for that hypothesis :)
bq. Scott Marlow why is ContextTransactionManager maintaining its own transaction status code - that is the role of the transaction manager to determine the transaction status.
You're definitely asking the wrong person. :) The answer though is, it doesn't: it passes the status through. I think what's happening is that the wrong transaction is being resumed during the synchronization (because the special TSR wrapper is bypassing the WFTC API). So WFTC thinks transaction A is resumed but Narayana thinks it's B.
I'm working on a fix which involves putting this TSR ordering logic into WFTC (so that it works even when executing in a remote transaction for example).
> org.jboss.as.txn.service.internal.tsr.TransactionSynchronizationRegistryWrapper.getStatus() should use org.wildfly.transaction.client.ContextTransactionManager.getStatus()
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-10229
> URL: https://issues.jboss.org/browse/WFLY-10229
> Project: WildFly
> Issue Type: Task
> Components: Transactions
> Reporter: Scott Marlow
> Assignee: David Lloyd
> Fix For: 13.0.0.Beta1
>
>
> org.jboss.as.txn.service.internal.tsr.TransactionSynchronizationRegistryWrapper.getStatus() is currently using com.arjuna.ats.jta.TransactionManager, instead it should use org.wildfly.transaction.client.ContextTransactionManager.getStatus().
> I'm seeing a case in Hibernate ORM 5.3, where org.wildfly.transaction.client.ContextTransactionManager.getStatus() returns 4 but TransactionSynchronizationRegistryWrapper.getStatus() returns 1.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years