The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

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

oobug
March 7, 2023

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 "/pipe.py", line 184, in <module>
main()
File "/pipe.py", line 180, in main
release.run()
File "/pipe.py", line 59, in run
version = self.version_bump()
File "/pipe.py", line 121, in version_bump
f'{repo_slug}:[0-9]*\.[0-9]*\.[0-9]*(@sha256:[a-fA-F0-9]*)?') # noqa
File "/pipe.py", 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 pipe.py. 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 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

1 vote
Answer accepted
Igor Stoyanov
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 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

oobug
March 17, 2023

I have created a pull request with a fix for this issue: https://bitbucket.org/atlassian/bitbucket-pipe-release/pull-requests/16

oobug
July 23, 2024

This was ultimately fixed in PR https://bitbucket.org/atlassian/bitbucket-pipe-release/pull-requests/19, producing release 5.3.2.

DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events