Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "BuildServerPorts"
(updated some info, added orbit) |
|||
| Line 28: | Line 28: | ||
Some of our unit tests use ports the range 20000 to 29999. | Some of our unit tests use ports the range 20000 to 29999. | ||
| + | |||
| + | FYI, need to find whole list, but Serves currently assigned: 22100-22200 | ||
| + | (and currently only use 22150) | ||
| + | |||
| + | |||
== Orbit == | == Orbit == | ||
Revision as of 14:20, 6 December 2006
This page is to document ports that are used on the build.eclipse.org server by teams that are doing build or Unit tests there.
In the following, '"well known"' means it is given to others to access some function, so should be relatively long term, and needs to be open to the public in the firewall. Whereas '"internal"' means a port that needs to be distinct from other processes running on the util node, it does not need to be open to the public, and would likely be feasible to change, if need be. For example, those used in unit tests.
Contents
WTP
well known
WTP build uses CruiseControl, and our instance uses ports
7000, 7777 (cruiseconsole console and status page, respectively)
I believe we no longer need or use the following
7070, 7077 ( build tools)
internal
Some of our unit tests use ports the range 20000 to 29999.
FYI, need to find whole list, but Serves currently assigned: 22100-22200 (and currently only use 22150)
Orbit
Orbit build uses CruiseControl, and our instance uses ports
9000, 9777 (cruiseconsole console and status page, respectively)