Issue Details (XML | Word | Printable)

Key: BAM-196
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Mark Chaimungkalanont [Atlassian]
Reporter: MattyJ
Votes: 0
Watchers: 0
Operations

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

Adding VisualStudio as builder launches IDE when built

Created: 06/Sep/06 03:59 PM   Updated: 06/Sep/06 08:09 PM
Component/s: Builders (Other)
Affects Version/s: 0.3
Fix Version/s: 0.4

Time Tracking:
Not Specified

Environment: Windows server 2003

Participants: Mark Chaimungkalanont [Atlassian] and MattyJ
Since last comment: 2 years, 17 weeks, 6 days ago
Number of comments: 1
Labels:


 Description  « Hide
When I add Visual Studio 2003 to the builder list with a long commandline, it puts extraneous quotes around everything which causes the IDE to launch on the remote build machine, locking up the build until I log in and close the IDE. The build script says it is doing this:

... running command line: ""c:\program files\Microsoft Visual Studio .NET 2003\Common7\IDE\devenv.com" '"C:\localdev\DotNet\Source\DataAccess\DataAccess.sln /rebuild Release /project DataAccessInstaller"'"

All the quotes around the second part of this commandline shouldn't be there, or we should be given the opportunity to leave them out. My paramaters for the builder and project in question have no quotes, so it looks like Bamboo is adding all of them itself. This commandline would work in this case:

"c:\program files\Microsoft Visual Studio .NET 2003\Common7\IDE\devenv.com" C:\localdev\DotNet\Source\DataAccess\DataAccess.sln /rebuild Release /project DataAccessInstaller



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Mark Chaimungkalanont [Atlassian] added a comment - 06/Sep/06 08:08 PM
Matty,

Thanks for the detailed report! Really appreciate it.

I don't have Visual studio setup, but I've reproduced the problem using a Maven Custom Command and have now fixed it. We'll release as part of 0.3.1 soon.

Cheers

Mark C