Skip to main content

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

BuildServerPorts

Revision as of 13:55, 6 December 2006 by David williams.acm.org (Talk | contribs) (updated some info, added orbit)

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.


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.

Orbit

Orbit build uses CruiseControl, and our instance uses ports

9000, 9777 (cruiseconsole console and status page, respectively)

Back to the top