March 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-8996) Multi-pipeline Jenkins build

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8996?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8996: ---------------------------------- Description: We should have multiple pipelines so that we can build with different setups: * different JDKs (JDK 8, JDK 10, JDK 11, OpenJ9) * Different profiles (e.g. with code coverage reports, unstable) was: We should have multiple pipelines so that we can build with different setups: * different JDKs (JDK 8, JDK 10, JDK 11, OpenJ9) * Different profiles (e.g. with code coverage reports) > Multi-pipeline Jenkins build > ---------------------------- > > Key: ISPN-8996 > URL: https://issues.jboss.org/browse/ISPN-8996 > Project: Infinispan > Issue Type: Bug > Components: Build, CI > Reporter: Tristan Tarrant > Fix For: 9.3.0.Alpha1 > > > We should have multiple pipelines so that we can build with different setups: > * different JDKs (JDK 8, JDK 10, JDK 11, OpenJ9) > * Different profiles (e.g. with code coverage reports, unstable) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8993) LocalTopologyManager should not install a reset topology before conflict resolution

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-8993?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-8993: ------------------------------- Description: When the coordinator changes, either because the old one left or because there was a merge, the new coordinator first resets any ongoing rebalance, and then starts a rebalance with the new members. But some nodes could see the post-merge rebalance before the post-merge reset, and they need to reset any old data or inbound transfers first. [LocalTopologyManagerImpl|https://github.com/infinispan/infinispan/blob/22...] is responsible for faking that reset topology update, in order to keep StateConsumerImpl simpler. The problem is that LocalTopologyManagerImpl also creates a reset topology update if the new coordinator started conflict resolution, and that topology update clears all the segments not owned by the local node in the preferred topology. was: When the coordinator changes, either because the old one left or because there was a merge, the new coordinator first resets any ongoing rebalance, and then starts a rebalance with the new members. But some nodes could see the post-merge rebalance before the post-merge reset, and they need to reset any old data or inbound transfers first. [LocalTopologyManagerImpl|https://github.com/infinispan/infinispan/blob/22...] is responsible for faking that reset topology update, in order to keep StateConsumerImpl simpler. The problem is that LocalTopologyManagerImpl also creates a reset topology update if the new coordinator started conflict resolution. > LocalTopologyManager should not install a reset topology before conflict resolution > ----------------------------------------------------------------------------------- > > Key: ISPN-8993 > URL: https://issues.jboss.org/browse/ISPN-8993 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.2.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.2.1.Final > > > When the coordinator changes, either because the old one left or because there was a merge, the new coordinator first resets any ongoing rebalance, and then starts a rebalance with the new members. But some nodes could see the post-merge rebalance before the post-merge reset, and they need to reset any old data or inbound transfers first. > [LocalTopologyManagerImpl|https://github.com/infinispan/infinispan/blob/22...] is responsible for faking that reset topology update, in order to keep StateConsumerImpl simpler. The problem is that LocalTopologyManagerImpl also creates a reset topology update if the new coordinator started conflict resolution, and that topology update clears all the segments not owned by the local node in the preferred topology. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5823) Send Infinispan events to Hawkular

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5823?page=com.atlassian.jira.plugin.... ] Tristan Tarrant closed ISPN-5823. --------------------------------- Resolution: Out of Date > Send Infinispan events to Hawkular > ---------------------------------- > > Key: ISPN-5823 > URL: https://issues.jboss.org/browse/ISPN-5823 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Reporter: Pedro Zapata > Priority: Minor > Labels: jdg7 > > Create integration to optionally log Infinispan events to Hawkular -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-9000) Send e-mails for nightly builds to Infinispan CI mailing list

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9000?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9000: ---------------------------------- Description: The branch builds (master, stable, etc) should send results to the infinispan ci mailing list > Send e-mails for nightly builds to Infinispan CI mailing list > ------------------------------------------------------------- > > Key: ISPN-9000 > URL: https://issues.jboss.org/browse/ISPN-9000 > Project: Infinispan > Issue Type: Bug > Reporter: Tristan Tarrant > > The branch builds (master, stable, etc) should send results to the infinispan ci mailing list -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-9000) Send e-mails for nightly builds to Infinispan CI mailing list

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9000?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9000: ---------------------------------- Component/s: CI > Send e-mails for nightly builds to Infinispan CI mailing list > ------------------------------------------------------------- > > Key: ISPN-9000 > URL: https://issues.jboss.org/browse/ISPN-9000 > Project: Infinispan > Issue Type: Bug > Components: CI > Reporter: Tristan Tarrant > > The branch builds (master, stable, etc) should send results to the infinispan ci mailing list -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8999) Automatically publish website from CI

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8999?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8999: ---------------------------------- Description: Add a CI job to publish the current HEAD of the develop branch of infinispan.github.io > Automatically publish website from CI > ------------------------------------- > > Key: ISPN-8999 > URL: https://issues.jboss.org/browse/ISPN-8999 > Project: Infinispan > Issue Type: Bug > Components: CI, Website > Reporter: Tristan Tarrant > > Add a CI job to publish the current HEAD of the develop branch of infinispan.github.io -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-9000) Send e-mails for nightly builds to Infinispan CI mailing list

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-9000: ------------------------------------- Summary: Send e-mails for nightly builds to Infinispan CI mailing list Key: ISPN-9000 URL: https://issues.jboss.org/browse/ISPN-9000 Project: Infinispan Issue Type: Bug Reporter: Tristan Tarrant -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8999) Automatically publish website from CI

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8999?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8999: ---------------------------------- Component/s: Website CI > Automatically publish website from CI > ------------------------------------- > > Key: ISPN-8999 > URL: https://issues.jboss.org/browse/ISPN-8999 > Project: Infinispan > Issue Type: Bug > Components: CI, Website > Reporter: Tristan Tarrant > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8999) Automatically publish website from CI

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-8999: ------------------------------------- Summary: Automatically publish website from CI Key: ISPN-8999 URL: https://issues.jboss.org/browse/ISPN-8999 Project: Infinispan Issue Type: Bug Reporter: Tristan Tarrant -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8998) Automatically release from CI

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8998?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8998: ---------------------------------- Description: The releases should happen via a Jenkins job: * versioning, build and stage to nexus * reversion and build of simple tutorials against stage repository to ensure that all artifacts are correctly published * release and drop of nexus staging repo * push tag and bump version to next snapshot on master branch > Automatically release from CI > ----------------------------- > > Key: ISPN-8998 > URL: https://issues.jboss.org/browse/ISPN-8998 > Project: Infinispan > Issue Type: Bug > Components: Build, CI > Reporter: Tristan Tarrant > > The releases should happen via a Jenkins job: > * versioning, build and stage to nexus > * reversion and build of simple tutorials against stage repository to ensure that all artifacts are correctly published > * release and drop of nexus staging repo > * push tag and bump version to next snapshot on master branch -- 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

infinispan-issues March 2018