Custom pipeline suddenly failing after running properly for years

[Michael Melvin]

Good morning, 

Hoping to get some help here.  We have a custom pipeline that builds a parent Maven module, waits for the artifact to be uploaded, and then runs parallel steps to build child Maven modules.

It has been working fine for years, and suddenly stopped working with failures last weekend.  I looks like it no longer is waiting for (or is unable to detect) the status of the parent build status:

Currently the output of the failure is:

---

Status: Downloaded newer image for bitbucketpipelines/trigger-pipeline:4.3.1

WARNING: New version available: atlassian/trigger-pipeline '4.3.1' to '5.5.1'

✔ Build started successfully. Build number: 9832.

Follow build logs at the following URL: https://bitbucket.org/XXXXXXXXX/microservices-clients/addon/pipelines/home#!/results/9832

INFO: Waiting for pipeline to finish

INFO: Attempt number 1: Getting build info.

Traceback (most recent call last):

File "/usr/bin/main.py", line 192, in <module>

pipe.run()

File "/usr/bin/main.py", line 172, in run

success, message = self._check_build(build_number, auth)

TypeError: cannot unpack non-iterable NoneType object

Previously, the build output looked like:

Status: Downloaded newer image for bitbucketpipelines/trigger-pipeline:4.3.1

WARNING: New version available: atlassian/trigger-pipeline '4.3.1' to '5.5.1'

✔ Build started successfully. Build number: 9801.

Follow build logs at the following URL: https://bitbucket.org/pointchain/XXXXXXXXX/addon/pipelines/home#!/results/9801

INFO: Waiting for pipeline to finish

INFO: Attempt number 1: Getting build info.

INFO: Build number 9801 for XXXXXXXXX is PENDING, waiting for pipeline to finish...

INFO: Attempt number 2: Getting build info.

INFO: Build number 9801 for XXXXXXXXX is IN_PROGRESS, waiting for pipeline to finish...

...

INFO: Build number 9801 for XXXXXXXXX is IN_PROGRESS, waiting for pipeline to finish...

INFO: Attempt number 26: Getting build info.

✔ Build number 9801 for XXXXXXXXX@YYYYYYYYYYY finished successfully.

✔ Pipe finished successfully.

[Michael Melvin · Accepted solution]

I have updated the triggers to 5.5.1 as well as changed BRANCH_NAME to REF_NAME and everything seems to be working fine in case anyone else hits this issue.

[Rafael Pereira]

Done the same here, just upgrading from 5.1.0' to '5.7.0' in my bitbucket-pipelines.yml and worked fine!