Pipelines: using pipes inside parallel blocks

[Paul Hicks]

Is it possible to invoke pipes from within parallel blocks? I haven't managed to find the correct syntax yet, and the error messages are pretty good at protecting me from learning anything. My current effort is:

pipelines:
  pull-requests:
    "**":
      - parallel:
          steps:
            - step:
                name: Run Bitbucket's native secret checks (Gitleaks)
                script:
                  - pipe: atlassian/git-secrets-scan:3.2.0
            - step:
                name: Run Bitbucket's native dependency scanner
                script:
                  - pipe: atlassian/dependency-scanner:0.3.0
              artifacts:
                - dependency-check-report.json
            - step:
                name: Run Bitbucket's native IaC checks (KICS)
                script:
                  - pipe: atlassian/bitbucket-iac-scan:0.5.2

This is being called but it's erroring instantly with message:

---

Configuration error

No matching pipeline definition in the Pipelines configuration.

---

Is there a syntax that works for this?

I have tried a selection of other options, including child pipelines and shared configuration. They all work fine until they reach this block, then instant error.

Any insights would be appreciated!

[Paul Hicks · Accepted solution]

It looks like "no matching pipeline definition" means "pipe atlassian/dependency-scanner is broken". Error messages, eh? I tried the newest version (0.8.0) and it still doesn't work. The problem is in that one pipe; the other two from the example above work fine. I tried it non-parallel, and the same error occurs. The problem is definitely in atlassian/dependency-scanner.

I'd raise an issue against the pipe, but they're using Bitbucket to host it, and there's no Bitbucket Issues. :facepalm:

[Paul Hicks]

Further to this: it turns out that the reason dependency-scanner is broken is that it doesn't exist. The correct name is bitbucket-dependency-scanner  Mea culpa. Though the hopeless error message doesn't help: there's no hint that's the problem. Atlasssian support spotted mistake and raised this issue: vote for it!

https://jira.atlassian.com/browse/BCLOUD-24167