Community
Participate
Working Groups
Collect UI nits to fix in the builds framework and Hudson connector.
* Open Builds view after creating a build repository * Add option to navigate to Builds view from build server in Team Repositories view
* Add popup menu to Team Repositories view
* Add options to disable automatic refresh to Builds view menu
The builds framework should use consistent naming. Any thoughts on that? Suggestions: * Build Server * Build Repository * Continuous Integration Server * CI Server
* Do not enable actions in Builds view when nothing is selected (e.g. workspace is empty)
* use UTF-8 to persists builds model
* Move categories to team.ui * Gradient for categories * Remove icon for categories * Subscribe to Hudson Views * Move Status icon into summary
(In reply to comment #1) * -Open Builds view after creating a build repository- * -Add option to navigate to Builds view from build server in Team Repositories view- (In reply to comment #2) * -Add popup menu to Team Repositories view- (In reply to comment #3) * -Add options to disable automatic refresh to Builds view menu- (In reply to comment #5) * -Do not enable actions in Builds view when nothing is selected (e.g. wokspace is empty)- (In reply to comment #6) * -use UTF8 to persists builds model- (In reply to comment #7) * Move categories to team.ui * Gradient for categories * Remove icon for categories -> bug 323313 * Subscribe to Hudson Views -> bug 323314 * -Move Status icon into summary-
Created attachment 177166 [details] mylyn/context/zip
I'll mark this as resolved. Please feel free to reopen if other issues arrise.
Is a minor thing, but I was confused about the "last built" column, as I thought it show the time the build finished. I know it's according to the Hudson web UI, but maybe the connector should be more clear on what this value means. Also the time seems to get updated multiple times during a sync (probably multiple API calls), which most of the time lead to seeing the seconds move twice. Maybe just remove the seconds so this issue would only happen 1/60 of the current occurrences? And should the built time be auto updated continuously, instead of only each sync? If no seconds, it wouldn't be too costly to just have a job scheduled for once a minute.
Yes, that an oddness in the UI. Please file a separate bug for that as we need to figure out the best refresh policy for the view.
(In reply to comment #12) > Yes, that an oddness in the UI. Please file a separate bug for that as we need > to figure out the best refresh policy for the view. 327160: [build] Last built refresh oddness https://bugs.eclipse.org/bugs/show_bug.cgi?id=327160