May 2020 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3260) On publishing a new Narayana release there should be created Quarkus PR to update Narayana version

by Thomas Jenkinson (Jira)

[ https://issues.redhat.com/browse/JBTM-3260?page=com.atlassian.jira.plugin... ] Thomas Jenkinson reopened JBTM-3260: ------------------------------------ > On publishing a new Narayana release there should be created Quarkus PR to update Narayana version > -------------------------------------------------------------------------------------------------- > > Key: JBTM-3260 > URL: https://issues.redhat.com/browse/JBTM-3260 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Affects Versions: 5.10.3.Final > Reporter: Ondrej Chaloupka > Assignee: Mayank Kunwar > Priority: Major > > As currently when a Narayana minor release is published it's usual to create a WildFly pull request which updates the Narayana version to the most up-to-date. > This functionality is automatized in the release script: > https://github.com/jbosstm/narayana/blob/5.10.4.Final/narayana-release-pr... > It would be good to have a similar functionality for the Quarkus. Narayana is the component managing JTA trasaction there and it would be good to pass there the newest version as well. > Narayana version could be updated at: > https://github.com/quarkusio/quarkus/blob/1.2.1.Final/bom/runtime/pom.xml... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3260) On publishing a new Narayana release there should be created Quarkus PR to update Narayana version

by Thomas Jenkinson (Jira)

[ https://issues.redhat.com/browse/JBTM-3260?page=com.atlassian.jira.plugin... ] Thomas Jenkinson updated JBTM-3260: ----------------------------------- Fix Version/s: (was: 5.10.5.Final) > On publishing a new Narayana release there should be created Quarkus PR to update Narayana version > -------------------------------------------------------------------------------------------------- > > Key: JBTM-3260 > URL: https://issues.redhat.com/browse/JBTM-3260 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Affects Versions: 5.10.3.Final > Reporter: Ondrej Chaloupka > Assignee: Mayank Kunwar > Priority: Major > > As currently when a Narayana minor release is published it's usual to create a WildFly pull request which updates the Narayana version to the most up-to-date. > This functionality is automatized in the release script: > https://github.com/jbosstm/narayana/blob/5.10.4.Final/narayana-release-pr... > It would be good to have a similar functionality for the Quarkus. Narayana is the component managing JTA trasaction there and it would be good to pass there the newest version as well. > Narayana version could be updated at: > https://github.com/quarkusio/quarkus/blob/1.2.1.Final/bom/runtime/pom.xml... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3300) Enable the checkstyle plugin on as many non Arjuna modules as makes sense

by Thomas Jenkinson (Jira)

[ https://issues.redhat.com/browse/JBTM-3300?page=com.atlassian.jira.plugin... ] Thomas Jenkinson closed JBTM-3300. ---------------------------------- Resolution: Rejected > Enable the checkstyle plugin on as many non Arjuna modules as makes sense > ------------------------------------------------------------------------- > > Key: JBTM-3300 > URL: https://issues.redhat.com/browse/JBTM-3300 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA, REST, TxBridge, XTS > Affects Versions: 5.10.4.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > > The checkstyle plugin is intended for use on new files but it is currently disabled. We should enable for as many of our modules as possible. > Arjuna modules should be precluded. > I am not sure if we want to enable it for STM. > Note that we use the WildFly checkstyle rule set (https://github.com/wildfly/wildfly-checkstyle-config/tree/master/src/main...). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3300) Enable the checkstyle plugin on as many non Arjuna modules as makes sense

by Thomas Jenkinson (Jira)

[ https://issues.redhat.com/browse/JBTM-3300?page=com.atlassian.jira.plugin... ] Thomas Jenkinson updated JBTM-3300: ----------------------------------- Fix Version/s: (was: 5.10.5.Final) > Enable the checkstyle plugin on as many non Arjuna modules as makes sense > ------------------------------------------------------------------------- > > Key: JBTM-3300 > URL: https://issues.redhat.com/browse/JBTM-3300 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA, REST, TxBridge, XTS > Affects Versions: 5.10.4.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > > The checkstyle plugin is intended for use on new files but it is currently disabled. We should enable for as many of our modules as possible. > Arjuna modules should be precluded. > I am not sure if we want to enable it for STM. > Note that we use the WildFly checkstyle rule set (https://github.com/wildfly/wildfly-checkstyle-config/tree/master/src/main...). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3300) Enable the checkstyle plugin on as many non Arjuna modules as makes sense

by Thomas Jenkinson (Jira)

[ https://issues.redhat.com/browse/JBTM-3300?page=com.atlassian.jira.plugin... ] Thomas Jenkinson reopened JBTM-3300: ------------------------------------ > Enable the checkstyle plugin on as many non Arjuna modules as makes sense > ------------------------------------------------------------------------- > > Key: JBTM-3300 > URL: https://issues.redhat.com/browse/JBTM-3300 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA, REST, TxBridge, XTS > Affects Versions: 5.10.4.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > > The checkstyle plugin is intended for use on new files but it is currently disabled. We should enable for as many of our modules as possible. > Arjuna modules should be precluded. > I am not sure if we want to enable it for STM. > Note that we use the WildFly checkstyle rule set (https://github.com/wildfly/wildfly-checkstyle-config/tree/master/src/main...). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3260) On publishing a new Narayana release there should be created Quarkus PR to update Narayana version

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3260?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka reopened JBTM-3260: ------------------------------------ > On publishing a new Narayana release there should be created Quarkus PR to update Narayana version > -------------------------------------------------------------------------------------------------- > > Key: JBTM-3260 > URL: https://issues.redhat.com/browse/JBTM-3260 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Affects Versions: 5.10.3.Final > Reporter: Ondrej Chaloupka > Assignee: Mayank Kunwar > Priority: Major > Fix For: 5.10.5.Final > > > As currently when a Narayana minor release is published it's usual to create a WildFly pull request which updates the Narayana version to the most up-to-date. > This functionality is automatized in the release script: > https://github.com/jbosstm/narayana/blob/5.10.4.Final/narayana-release-pr... > It would be good to have a similar functionality for the Quarkus. Narayana is the component managing JTA trasaction there and it would be good to pass there the newest version as well. > Narayana version could be updated at: > https://github.com/quarkusio/quarkus/blob/1.2.1.Final/bom/runtime/pom.xml... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3285) Reduce the number of axes on PR jobs

by Thomas Jenkinson (Jira)

[ https://issues.redhat.com/browse/JBTM-3285?page=com.atlassian.jira.plugin... ] Thomas Jenkinson reopened JBTM-3285: ------------------------------------ > Reduce the number of axes on PR jobs > ------------------------------------ > > Key: JBTM-3285 > URL: https://issues.redhat.com/browse/JBTM-3285 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: CI > Affects Versions: 5.10.4.Final > Reporter: Michael Musgrove > Priority: Major > > Our CI system runs a pull request poller which checks for new PRs by looking at the PR description to decide which Jenkins job axes to run. We have quite a few axes (QA_JTS_JACORB, QA_JTS_JDKORB, QA_JTS_OPENJDKORB, QA_JTA, XTS, CORE, BLACKTIE, RTS, mysql, postgres, db2, oracle, TOMCAT, JACOCO, LRA) and if the user, say, just wants to run the XTS axis then CI will start a job for each axis. All but the XTS axis will then check whether it needs to run and then terminate. Each axis can end up taking 20 minutes or so. It would be good to minimise this overhead. > For example, all of the QA axes could be run in one job. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3285) Reduce the number of axes on PR jobs

by Thomas Jenkinson (Jira)

[ https://issues.redhat.com/browse/JBTM-3285?page=com.atlassian.jira.plugin... ] Thomas Jenkinson closed JBTM-3285. ---------------------------------- Resolution: Rejected > Reduce the number of axes on PR jobs > ------------------------------------ > > Key: JBTM-3285 > URL: https://issues.redhat.com/browse/JBTM-3285 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: CI > Affects Versions: 5.10.4.Final > Reporter: Michael Musgrove > Priority: Major > > Our CI system runs a pull request poller which checks for new PRs by looking at the PR description to decide which Jenkins job axes to run. We have quite a few axes (QA_JTS_JACORB, QA_JTS_JDKORB, QA_JTS_OPENJDKORB, QA_JTA, XTS, CORE, BLACKTIE, RTS, mysql, postgres, db2, oracle, TOMCAT, JACOCO, LRA) and if the user, say, just wants to run the XTS axis then CI will start a job for each axis. All but the XTS axis will then check whether it needs to run and then terminate. Each axis can end up taking 20 minutes or so. It would be good to minimise this overhead. > For example, all of the QA axes could be run in one job. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3285) Reduce the number of axes on PR jobs

by Thomas Jenkinson (Jira)

[ https://issues.redhat.com/browse/JBTM-3285?page=com.atlassian.jira.plugin... ] Thomas Jenkinson updated JBTM-3285: ----------------------------------- Fix Version/s: (was: 5.10.5.Final) > Reduce the number of axes on PR jobs > ------------------------------------ > > Key: JBTM-3285 > URL: https://issues.redhat.com/browse/JBTM-3285 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: CI > Affects Versions: 5.10.4.Final > Reporter: Michael Musgrove > Priority: Major > > Our CI system runs a pull request poller which checks for new PRs by looking at the PR description to decide which Jenkins job axes to run. We have quite a few axes (QA_JTS_JACORB, QA_JTS_JDKORB, QA_JTS_OPENJDKORB, QA_JTA, XTS, CORE, BLACKTIE, RTS, mysql, postgres, db2, oracle, TOMCAT, JACOCO, LRA) and if the user, say, just wants to run the XTS axis then CI will start a job for each axis. All but the XTS axis will then check whether it needs to run and then terminate. Each axis can end up taking 20 minutes or so. It would be good to minimise this overhead. > For example, all of the QA axes could be run in one job. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3197) Include an STM quickstart running on Quarkus (including native mode)

by Thomas Jenkinson (Jira)

[ https://issues.redhat.com/browse/JBTM-3197?page=com.atlassian.jira.plugin... ] Thomas Jenkinson closed JBTM-3197. ---------------------------------- Resolution: Duplicate Issue > Include an STM quickstart running on Quarkus (including native mode) > -------------------------------------------------------------------- > > Key: JBTM-3197 > URL: https://issues.redhat.com/browse/JBTM-3197 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Demonstrator, Quickstarts, STM > Affects Versions: 5.9.8.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > > Add a quickstart that shows how to create an STM example running on Quarkus. The quickstart should also include instructions for building a native executable. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues May 2020