Skip to content

SDKQE-2411: Dotnet combination test pipeline matrix improvements#28

Open
willbroadbelt wants to merge 1 commit into
masterfrom
dotnetPipelineCombiMatrix
Open

SDKQE-2411: Dotnet combination test pipeline matrix improvements#28
willbroadbelt wants to merge 1 commit into
masterfrom
dotnetPipelineCombiMatrix

Conversation

@willbroadbelt
Copy link
Copy Markdown
Contributor

Motivations:
The combination pipeline does not run all the server versions when
they are run, only the first version will run. Also the combination
tests are always skipped and will not run unless replayed.

Modifications:

  • Introduce a matrix for the combination tests so that all the
    versions will be run in parallel
  • Fix logic of when the combination tests will be skipped/run
  • Made combination test script more resilient to errors during
    setup that may prevent tests from running

Motivations:
The combination pipeline does not run all the server versions when
they are run, only the first version will run. Also the combination
tests are always skipped and will not run unless replayed.

Modifications:
- Introduce a matrix for the combination tests so that all the
  versions will be run in parallel
- Fix logic of when the combination tests will be skipped/run
- Made combination test script more resilient to errors during
  setup that may prevent tests from running
@willbroadbelt
Copy link
Copy Markdown
Contributor Author

FYI Here's this script being run on jenkins: http://sdk.jenkins.couchbase.com/job/dotnet/job/sdk/job/couchbase-net-scripted-build-pipeline-wip/33/
The "skip" and "gerrit trigger" options will still cause the combination tests to be skipped as before, and the tests will now actually be run during every nightly trigger.

About ~2/3rds of the test failures are fixed in this patch https://review.couchbase.org/c/couchbase-net-client/+/171117
The remaining failing tests I am working on fixing/stabilising.

Copy link
Copy Markdown
Contributor

@jeffrymorris jeffrymorris left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, but @RiPont should take as look as he has been working on Jenkins more than myself.

Jeff

@avsej avsej force-pushed the master branch 12 times, most recently from 8a4c1d1 to 55e217f Compare May 11, 2022 06:58
@avsej avsej force-pushed the master branch 4 times, most recently from eb289ec to 4ee748c Compare October 19, 2022 06:24
@avsej avsej force-pushed the master branch 2 times, most recently from 24bcbaf to ab7ac0c Compare February 8, 2023 12:58
@avsej avsej force-pushed the master branch 4 times, most recently from a5a2f84 to 7bba9f5 Compare March 9, 2023 09:13
@avsej avsej force-pushed the master branch 3 times, most recently from 8d7e48b to fb53f2d Compare May 9, 2023 12:30
@avsej avsej force-pushed the master branch 8 times, most recently from b8095ff to b3282a6 Compare September 25, 2023 15:34
@avsej avsej force-pushed the master branch 2 times, most recently from 684cd7e to e5bccc5 Compare October 4, 2023 16:21
@avsej avsej force-pushed the master branch 5 times, most recently from aecef86 to 0c99d2b Compare February 7, 2024 23:54
@avsej avsej force-pushed the master branch 3 times, most recently from 59c46f3 to c8f24e6 Compare March 2, 2024 04:54
@avsej avsej force-pushed the master branch 3 times, most recently from cb3084f to d12bcf0 Compare September 14, 2024 05:51
@avsej avsej force-pushed the master branch 4 times, most recently from 1648340 to 52c1732 Compare March 7, 2025 19:31
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.

2 participants