Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 341414 - can not run a build due to Running of build failed error
Summary: can not run a build due to Running of build failed error
Status: RESOLVED DUPLICATE of bug 355927
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: 0.7   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Mylyn Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-30 14:53 EDT by Taciano Tres CLA
Modified: 2011-08-30 17:19 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Taciano Tres CLA 2011-03-30 14:53:03 EDT 
Trying to run a build from Mylyn fails with the (meaningless) message: "Running of build failed". There's no stacktrace available ("An exception stack trace is not available."). Should the task be configured with the "Trigger builds remotely (e.g., from scripts)" setted?

Environment:
Hudson 1.380
JDK 1.6.0
Apache Tomcat 6.0.24
Comment 1 Steffen Pingel CLA 2011-04-01 21:54:24 EDT 
Thanks for the report. To help us investigate further can you verify that you have provided credentials in the server properties dialog and have the required permission to run builds? Does the build have any parameters? Do you consistently get the error every time you try to run a build?
Comment 2 Taciano Tres CLA 2011-04-04 08:46:27 EDT 
(In reply to comment #1)
> verify that you have provided credentials in the server properties dialog
Yes. The Hudson server is authenticated, and all other Mylyn actions works ok.

> and have the required permission to run builds?
Yes, the permissions are ok and builds on web interface works ok.

> Does the build have any parameters?
No.

> Do you consistently get the error every time you try to run a build?
Yes.
Comment 3 Steffen Pingel CLA 2011-05-06 10:30:47 EDT 
I have seen this in other workspaces as well when a user did not have permission to run a build. We should improve the error message accordingly.
Comment 4 Steffen Pingel CLA 2011-05-17 21:00:42 EDT 
There was a bug that caused the stack trace and hence the detailed error message not to get included in the error log. This is fixed in the current weekly build. Could you try updating and report back what the detailed error message is?
Comment 5 Steffen Pingel CLA 2011-08-30 17:19:53 EDT 
I suspect that this is same is issue as the one described on bug 355927.

*** This bug has been marked as a duplicate of bug 355927 ***