Closed amaddio closed 1 month ago
Thanks for the bug report @amaddio.
I can reproduce the issue with your sample so no worries there. The problem is the condition:
bit, which I don't support yet. I will push a fix for that today. In the meantime, if you remove the condition
s, it should work.
You are a gun @mathieu-lemay. Just tried it. I can confirm that the pipeline-runner list
cmd works, when the condition part is removed entirely
2024-08-20 16:47:04.798 pipeline_runner.cli: Available pipelines:
branches.main
Happy to hear that!
I've added partial support for the condition block, meaning they will be parsed, but ignored with a warning when running a step. That way, it will work and the user will be made aware that the condition are explicitly ignored my the tool.
Version 0.4.4 has been released to fix this issue. Please re-open the issue if you still encounter a problem!
I stumbled over the pipeline-runner project today. The tool looks exactly what I was looking for. It seams that this tool fills the gap as Atlassian does not provide a feature to properly lint nor test the pipeline prior to pushing it.
Unfortunately my complex
bitbucket-pipelines.yml
is considered invalid even though the pipeline works well when run on bitbucket cloud.The command I use was
pipeline-runner list
. My pipeline configuration is quite complex but basically it is a repetition of steps in theparallel
section. It looks like this with the repetitions removed:I receive a ton of errors:
I know that debugging this issue is impossible if I don't provide the full
yml
file. Unfortunately I can't. I would be already happy to be advised how to fix the yml problems or ignore the errors and run thepipeline-runner run <pipelinename>
command without failing on syntax errors.