-
Bug
-
Resolution: Timed out
-
Medium
-
None
-
2.1.3
-
2
-
Severity 2 - Major
-
If the p4 changelist looks like
p4 describe -s 123
Change 321 by remoteuser@newClient on 2009/01/08 16:51:07 Bug Fixing (No jira #) Changed link on usable jug FF Change 97885 by yannis_brown@YBROWN1 on 2008/12/08 19:09:23 FIX to WWise Event error on Goblin Skulker Play_goblinskulker_effort_heavy - were just wrong audio tag links in QED data - now using correct ones. Affected files ... ... //depot/TWN/Resource/PropertyClassSpecs/Audio_CharacterSoundLookupDatasetInstances.xml#75 edit Bug Fixing (No jira #) Changed link on usable jug FF Affected files ... ... //depot/BankPrj/build.sh#7 edit
The 'Affected files ...' in the descriptive part will switch the p4 parser into file mode and out of description mode. The line
Bug Fixing (No jira #) Changed link on usable jug
will kill the parser as it interprets the # as a file related action
- relates to
-
-
- Closed
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[BAM-3410] Perforce changelist parser dies if 'Affected files..." is in the descriptive part of the changelist
David Aldridge
added a comment - Good catch! Luckily, 'p4 describe' appears to indent the description with preceding tabs, so you could probably search for "line that begins with 'Affected files ...' without preceding whitespace". Or maybe search for that, plus a following empty line and a line beginning with "..." without preceding whitespace..
David Aldridge
added a comment - Good catch! Luckily, 'p4 describe' appears to indent the description with preceding tabs, so you could probably search for "line that begins with 'Affected files ...' without preceding whitespace". Or maybe search for that, plus a following empty line and a line beginning with "..." without preceding whitespace.. 
Ulrich Kuhnhardt [Atlassian]
added a comment - https://support.atlassian.com/browse/BSP-1443 
Hi everyone,
We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collected votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Time Out.
Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Bamboo team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.
We understand how disappointing this decision may be but we want to be fully transparent when communicating with our users.
Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.
Thank you,
Syed Masood
Bamboo Product Manager