Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


The bitbucket-pipe-release pipe does not support an empty list of files to update

I am using version 5.1.0 of the Atlassian bitbucket-pipe-release within my own pipe repository. I am providing a version number manually and I do not want any of the built-in version number handling.

If I try to provide an empty string to the UPDATE_VERSION_IN_FILES argument, the pipe fails with the following output:

Traceback (most recent call last):
File "/", line 184, in <module>
File "/", line 180, in main
File "/", line 59, in run
version = self.version_bump()
File "/", line 121, in version_bump
f'{repo_slug}:[0-9]*\.[0-9]*\.[0-9]*(@sha256:[a-fA-F0-9]*)?') # noqa
File "/", line 37, in replace_content_by_pattern
with open(filename) as f:
FileNotFoundError: [Errno 2] No such file or directory: ''

This issue is caused by an incorrect check on line 115 of The code will exit when the filenames_to_update variable is equal to "". However, the .split() function has already been applied to this variable, so it will never be equal to "", but would instead be equal to [""]. Please fix.

1 answer

1 vote
Igor Stoyanov
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Mar 10, 2023

@oobug hi. Thank you for investigating this bug.

We will notify you when new pipe version with fix will become available.

Regards, Igor

I have created a pull request with a fix for this issue:

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events