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

Bug 379533

Summary:	Newly-created plans initially incorrectly appear as disabled
Product:	z_Archived	Reporter:	Robin Green <greenrd>
Component:	Mylyn	Assignee:	Project Inbox <mylyn-triaged>
Status:	CLOSED MOVED	QA Contact:
Severity:	enhancement
Priority:	P3	Keywords:	helpwanted
Version:	1.0
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Robin Green

2012-05-15 08:13:38 EDT

Create a new build plan on Jenkins, and don't disable it. Right-click on the server in the Builds view, and choose Properties. Click Refresh, Select All, OK. A notification appears saying that the build is disabled.

However, the build is not in fact disabled, as can be seen from the fact that it can be run successfully.

Comment 1 Steffen Pingel

2012-06-10 13:34:55 EDT

Does the build appear with the expected status after a refresh?

Comment 2 Robin Green

2012-06-11 13:48:00 EDT

(In reply to comment #1)
> Does the build appear with the expected status after a refresh?

Yes.

Comment 3 Steffen Pingel

2012-06-14 11:47:34 EDT

I was able to reproduce the problem. HudsonServerBehavior.updateStateAndStatus() does indeed not differentiate between HudsonModelBallColor.DISABLED and HudsonModelBallColor.GREY. I'm not entirely sure what generic status we would best map GREY to, maybe something like NEVER_RUN.

I have put this on the backlog and added the helpwanted flag to indicate that we would be happy to resolve this through a community contribution.

Comment 4 Steffen Pingel

2012-06-14 11:48:21 EDT

BTW, thanks for the bug report!

Comment 5 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