You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I'm using Bitbucket Cloud to run the tests of an nx project.
When `max-parallel` is set to a value higher than 1, the pipeline times out. It seems as if Bitbucket doesn't notice that the command has finished. When I set max-parallel to 1, it works.
Here's my yml file:
max-time: 20 # configure default 20 minute timeout
name: 'Lint, test, and build'
- npm ci
- npx nx workspace-lint
- npx nx format:check
- npx nx affected --target=lint --base=origin/master --parallel --max-parallel=3
- npx nx affected --target=test --base=origin/master --parallel --max-parallel=1 --ci --code-coverage
- npx nx affected --target=build --base=origin/master --head=HEAD --parallel --max-parallel=3
When changing `max-parallel` in the second to last line to "3", the pipeline won't finish. When running it locally on my machine, it finishes just fine. Any thoughts?
One possibility is that step may need more than 20 minutes to finish.
When `max-parallel` is set to a value higher than 1, is there any indication in the command's output that the command has finished doing what it is doing?
Is there an option to add verbose output to the command (that may show additional output about what is happening)?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.