Issue Details (XML | Word | Printable)

Key: BAM-272
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Edwin Wong [Atlassian]
Reporter: Gwyn Evans
Votes: 0
Watchers: 1
Operations

Add/Edit UI Mockup to this issue
If you were logged in you would be able to see more operations.
Bamboo

start-bamboo.bat fails to run when the folder name has a . and a _ in it

Created: 28/Sep/06 08:03 PM   Updated: 12/Oct/06 08:28 AM
Component/s: Installation
Affects Version/s: 0.4
Fix Version/s: 0.5.1

Time Tracking:
Original Estimate: 2 hours
Original Estimate - 2 hours
Remaining Estimate: 2 hours
Remaining Estimate - 2 hours
Time Spent: Not Specified
Remaining Estimate - 2 hours

Issue Links:
Reference
 

Participants: Edwin Wong [Atlassian] and Gwyn Evans
Since last comment: 2 years, 12 weeks, 5 days ago
Number of comments: 4
Internal Priority: 2. High
Labels:


 Description  « Hide
From http://forums.atlassian.com/message.jspa?messageID=257234648#257234648

Hi,
It looks as if there's an installation name issue...

I first installed the Windows standalone, specifing my own root of D:\Java\Continuous_Integration\Bamboo but keeping the default suffix of _0.4. I also specified an alternative BambooHome outside the app directory.

When I came to run it, I found that nothing happened, so I downloaded the .zip version, unzipped that to \Bamboo, set the BambooHome (in fact, copied it from the previous install) and run that, whereupon it ran up correctly.

I compared the two trees and was surprised to see that apart from the .install4j folder (surely not needed in the .zip archive?) they were identical, and was even more surprised to see the following behaviour!

D:\Java\Continuous_Integration\Bamboo_0.4>start-bamboo.bat
Press any key to continue . . .
D:\Java\Continuous_Integration\Bamboo_0.4>cd ..

D:\Java\Continuous_Integration>mv Bamboo_0.4 Bamboo04

D:\Java\Continuous_Integration>cd Bamboo04

D:\Java\Continuous_Integration\Bamboo04>start-bamboo.bat
2006-09-28 09:44:41,946 INFO [main] [HttpServer] Version Jetty/5.1.4
2006-09-28 09:44:41,977 INFO [main] [Credential] Checking Resource aliases
2006-09-28 09:44:42,587 INFO [main] [Container] Started org.mortbay.jetty.servlet.WebApplicationHandler@1abab88
Terminate batch job (Y/N)? y

D:\Java\Continuous_Integration\Bamboo04>cd ..

D:\Java\Continuous_Integration>mv Bamboo04 Bamboo_0.4

D:\Java\Continuous_Integration>cd Bamboo_0.4

D:\Java\Continuous_Integration\Bamboo_0.4>start-bamboo.bat
Press any key to continue . . .
D:\Java\Continuous_Integration\Bamboo_0.4>cd ..

D:\Java\Continuous_Integration>mv Bamboo_0.4 Bamboo04

D:\Java\Continuous_Integration>cd Bamboo04

D:\Java\Continuous_Integration\Bamboo04>start-bamboo.bat
2006-09-28 09:46:04,916 INFO [main] [HttpServer] Version Jetty/5.1.4
2006-09-28 09:46:04,956 INFO [main] [Credential] Checking Resource aliases
Terminate batch job (Y/N)? y

D:\Java\Continuous_Integration\Bamboo04>

Just to continue, Bamboo_04 & Bamboo0.4 are OK, but not Bamboo_0.4 !

/Gwyn



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Gwyn Evans added a comment - 29/Sep/06 03:04 AM
Misleading title: Note the last line, it's OK with either '.' or '_' but the combination fails!

Edwin Wong [Atlassian] added a comment - 09/Oct/06 01:15 AM
Hi Gwyn,

This is a truely interesting bug indeed. I have spent some time investigating why you had the problem with this and the results were rather confusing:

c:\Continuous_Integration\Bamboo_0.4 - worked
c:\java\Continuous_Integration\Bamboo1234 - worked
c:\java\Continuous_Integration\Bamboo_0_4 - worked
c:\java\Continuous_Integration\B_0.4 - worked.
c:\java\Continuous_Integration\Bam_0.4 - worked.
c:\reallyreallyreallylongfolder\Continuous_Integration\B_0.4 - worked

c:\java\Continuous_Integration\Bamboo_0.4 - didn't work
c:\java\Continuous_Integration\Bamboox0.4 - didn't work
c:\reallyreallyreallylongfolder\Continuous_Integration\Bamboo_0.4 - didn't work
c:\reallyreallyreallylongfolder\Continuous_Integration\Bamboox0y4 - didnt' work

The problem occurs when trying to fire the .exe launcher, which somehow fails with a error. This .exe launcher is generated by Install4J, and at this stage, I am trying to chase them down to the root cause of the problem.

For now, I have updated the recommended build directory to not include the version number.


Edwin Wong [Atlassian] added a comment - 09/Oct/06 01:30 AM
Both issue seems to be caused by the same underlying problem.

Edwin Wong [Atlassian] added a comment - 12/Oct/06 08:28 AM
This has been confirmed to be an issue with the installation package and launcher creator we were using.

This problem has been fixed.