[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
[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
[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