-
Suggestion
-
Resolution: Unresolved
-
None
Issue Summary
Currently, when a build has multiple variables configured (including Repository Variables, Workspace Variables, and Deployment Variables) and has a total of 120K characters combined, it could cause the pipelines build to be in a hung state.
This could be misleading as the actual error message isn't displayed nor informative.
A suggestion is to :
- Include an informative message indicating that pipelines build failed for the reason.
- Instead of allowing the build to be hung indefinitely until timeout, it's better if builds could be stopped / marked as failed.
- Allow increase of variable length limit above 120k.
- mentioned in
-
Page Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[BCLOUD-20105] Provide informative error when pipelines build is hung caused by variable length
| Description |
Original:
h3. Issue Summary
Currently, when a build has multiple variables configured (including Repository Variables, Account Variables, Deployment Variables) and has a total of 120K characters combined, it could cause the pipelines build to be in a hung state. This could be misleading as the actual error message isn't displayed nor informative. A suggestion is to : # Include an informative message indicating that pipelines build failed for the reason. # Instead of allowing the build to be hung indefinitely until timeout, it's better if builds could be stopped / marked as failed. # Allow increase of variable length limit above 120k. |
New:
h3. Issue Summary
Currently, when a build has multiple variables configured (including Repository Variables, Workspace Variables, and Deployment Variables) and has a total of 120K characters combined, it could cause the pipelines build to be in a hung state. This could be misleading as the actual error message isn't displayed nor informative. A suggestion is to : # Include an informative message indicating that pipelines build failed for the reason. # Instead of allowing the build to be hung indefinitely until timeout, it's better if builds could be stopped / marked as failed. # Allow increase of variable length limit above 120k. |
We initially stumbled across this issue in June 2022 and had to resort to opening a support ticket to get it resolved. Back then, we were pointed at this feature request.
Fast forward to May 2023, we came across this issue again and while doing excessive pipeline refactoring in one of our projects. After 2-3 hours of trying to find the mistake, we remembered this issue and variable length really was the root cause of our issue.
This feature request is a must. Non-descriptive error messages are an absolute no-go and this really does not strengthen our engineer's trust in Bitbucket Pipelines as a CI/CD solution.
| Remote Link | New: This issue links to "Page (Confluence)" [ 743503 ] |
I experienced what the description for the item states. It would have been tremendously helpful to have had at least a descriptive message on the Pipelines screen telling me why the Queued state was persistent up until I allowed it to error out. I had to reach out to a Support Engineer, Bruno, for him to tell me that his internal logs showed the excessive character length in a variable. Resolution took 5-6 business days, which I cannot have if I am to reliably use Bitbucket as our cloud repository. Thank you.
| Remote Link | Original: This issue links to "Page (Confluence)" [ 643226 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 643226 ] |
| Description |
Original:
h3. Issue Summary
Currently, when a build has multiple variables configured (including Repository Variables, Account Variables, Deployment Variables) and has a total of 120K characters combined, it could cause the pipelines build to be in a hung state. This could be misleading as the actual error message isn't displayed nor informative. A suggestion is to : # Include an informative message indicating that pipelines build failed for the reason. # Instead of allowing the build to be hung indefinitely until timeout, it's better if builds could be stopped / marked as failed. |
New:
h3. Issue Summary
Currently, when a build has multiple variables configured (including Repository Variables, Account Variables, Deployment Variables) and has a total of 120K characters combined, it could cause the pipelines build to be in a hung state. This could be misleading as the actual error message isn't displayed nor informative. A suggestion is to : # Include an informative message indicating that pipelines build failed for the reason. # Instead of allowing the build to be hung indefinitely until timeout, it's better if builds could be stopped / marked as failed. # Allow increase of variable length limit above 120k. |
This also affected us and took many days to get an appropriate answer from support. Adding some checks to the initial build setup would seem surely appropriate.