Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 351888

Summary:	Build Job history view should refresh when job is refreshed
Product:	z_Archived	Reporter:	Lucas Panjer <lucas.panjer>
Component:	Mylyn	Assignee:	Project Inbox <mylyn-triaged>
Status:	CLOSED MOVED	QA Contact:
Severity:	normal
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	Macintosh
OS:	Mac OS X
Whiteboard:

Description Lucas Panjer

2011-07-12 15:04:44 EDT

Hudson/Jenkins supports parallel execution of multiple builds of the same job if the job is configured to run parallel builds. The Run Build command should trigger another build execution if the job is configured for parallel execution.

Comment 1 Lucas Panjer

2011-07-12 15:07:00 EDT

Never mind. This appears to work.

Comment 2 Lucas Panjer

2011-07-14 13:47:31 EDT

This originally came up because I had the a job's history shown in the history view (and linked with selection) and the history doesn't update when the job is refreshed from the builds view.

This caused me to think that the Hudson connector failed to launch a parallel build as noted in the original description.

I expect the history view to refresh when the build server and/or jobs are refreshed, either manually or automatically.

Updated summary accordingly.

Comment 3 Steffen Pingel

2011-07-19 16:37:51 EDT

Thanks for the update Lucas. I agree that the History view should be refreshed automatically.

Comment 4 Eclipse Webmaster

2022-11-15 11:45:08 EST

Mylyn has been restructured, and our issue tracking has moved to GitHub [1].

We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub.

[1] https://github.com/orgs/eclipse-mylyn