BitBucket’s Pipelines are for “Integrating CI/CD for Bitbucket Cloud,” and are “trivial to set up” using a YAML file for describing actions.
Here’s an example of a pipeline file:
pipelines: default: - step: caches: - dotnetcore script: # Modify the comma`nds below to build your repository. - export PROJECT_NAME=hello.csproj - export TEST_NAME=hello-tests.csproj - dotnet restore - dotnet build $PROJECT_NAME - dotnet test $TEST_NAME
Pretty simple, right? Yep, nice and simple. Executing the pipeline is pretty easy, too. The problem is that this pipeline will fail, and the failure has little to do with the code.
Bitbucket Pipelines only accepts the JUnit XML format for test output. Since your standard .NET project does not use JUnit tooling, the Bitbucket Pipeline doesn’t find any test results.