Skip to content

Add CI target and workflow for RavenDb (GH-2558)#2561

Merged
jeremydmiller merged 3 commits intomainfrom
feature/2558-ravendb-ci
Apr 22, 2026
Merged

Add CI target and workflow for RavenDb (GH-2558)#2561
jeremydmiller merged 3 commits intomainfrom
feature/2558-ravendb-ci

Conversation

@jeremydmiller
Copy link
Copy Markdown
Member

Summary

  • New CIRavenDb Nuke target + .github/workflows/ravendb.yml workflow covering RavenDbTests and RavenDbTests.LeaderElection (no docker — uses embedded RavenDB.TestDriver)
  • Fix DiscoverTestMethods in build/TestAllPersistence.cs so inherited [Fact] methods on compliance base classes (e.g. LeadershipElectionCompliance) are attributed to the concrete derived class — previously leader-election projects silently discovered zero methods
  • Incorporates merged community bug fixes Fix RavenDb scheduled messages not being delivered when using a durable transport #2554 (scheduled-job lock) and Fix NRE in RavenDb durability recovery #2555 (NRE on orphaned listener URIs) via a main merge

Closes #2558

Test plan

🤖 Generated with Claude Code

jeremydmiller and others added 2 commits April 21, 2026 12:47
Adds a CIRavenDb Nuke target that builds and exercises both RavenDbTests
and RavenDbTests.LeaderElection one class (or one method, for leader
election) at a time with retry, plus a dedicated GitHub Actions workflow.
RavenDb tests use the embedded RavenDB.TestDriver, so no docker services
are required.

Also fixes DiscoverTestMethods so inherited [Fact] methods on a compliance
base class (e.g. LeadershipElectionCompliance) are attributed to the
concrete derived class — previously leader-election projects discovered
zero methods, silently running nothing.

Includes the merged community fixes (#2554, #2555) which repair RavenDb
scheduled-job locking and guard RavenDb durability recovery against
orphaned listener URIs; both ship with regression tests.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Copy link
Copy Markdown
Contributor

I checked why this is blocked: the PR is behind main and conflicts with the newer CIGrpc target in build/CITargets.cs.

I could not push directly to feature/2558-ravendb-ci because my GitHub token does not have write access to JasperFx/wolverine, so I opened #2564 against this PR branch with the merge conflict resolved. The resolution keeps both targets:

  • CIRavenDb from this PR
  • CIGrpc from current main

Local verification on that branch: dotnet build build/build.csproj --nologo passes, with existing package/nullability warnings only.

Resolve merge conflict for RavenDb CI PR
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add a CI Target for RavenDb

2 participants