Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Revision as of 15:58, 19 February 2012

Hudson Continuous Integration Server
Website
Download
Community
Mailing List • Forums • IRC • mattermost
Issues
Open • Help Wanted • Bug Day
Contribute
Browse Source

	Community Meeting 20-Feb-2012

Add or comment on agenda items here, just prefix the item with your name so we can identify you on the call:

3.0.0
- [susan] M2/M3 Release
- [susan] Website and wiki
- [susan] Initial Code Contribution
- [susan] Issues migration

[Winston] Hudson performance in a enterprise installation, defining best practice, dedicating a release for performance analysis.

[Henrik] What are the core team's priorities besides the eclipse migration? upcoming features?
[Henrik] Out approach to scripting Hudson seems half-hearted at best, how do we improve this? (We need a unified way that plugins can easily attach themselves to)
- CLI works: but is limited in its API plus requires special access through firewalls etc.
- old "REST" api: I can configure a project, but it generally lacks in api
- new "REST" api, I personally find it confusing, eg. there is a difference bewteen project/<id> and projects/<name> in the latter I can get the config, nodes doesn't support configuration at all.

@@ Line 19: / Line 19: @@
 ** CLI works: but is limited in its API plus requires special access through firewalls etc.
 ** old "REST" api: I can configure a project, but it generally lacks in api
-** new "REST" api, I can get state but I cannot seem to figure out how to configure project, nodes etc. e.g. can't find url for projects config.xml, nodes doesn't support configuration at all.
+** new "REST" api, I personally find it confusing, eg. there is a difference bewteen project/<id> and projects/<name> in the latter I can get the config, nodes doesn't support configuration at all.