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.
Difference between revisions of "Platform-releng/e4Build Build Id"
(initial) |
(initial) |
||
| Line 5: | Line 5: | ||
1. The ID has been given the right accesses and permissions to sign and commit/push tags to git, and it can push changes to the maps project. (See {{bug|374248}}) | 1. The ID has been given the right accesses and permissions to sign and commit/push tags to git, and it can push changes to the maps project. (See {{bug|374248}}) | ||
| − | 2. As a general rule, nothing should be changed or stored in e4Build $HOME. Some things, such as .cvspass, .bashrc would in principle change how other "shared builds" run. So, please | + | 2. As a general rule, nothing should be changed or stored in e4Build $HOME. Some things, such as .cvspass, .bashrc would in principle change how other "shared builds" run. So, please note any special cases or changes here on this page. |
3. One implication of the above "rule" is that during builds, if people use Eclipse to do something during the build, they should be sure to point to a "workspace" in their own build area, or else the default is ${user.home}/workspace. For example, you might use -data /shared/eclipse/e4/workspace-orion when invoking your eclipse instance. | 3. One implication of the above "rule" is that during builds, if people use Eclipse to do something during the build, they should be sure to point to a "workspace" in their own build area, or else the default is ${user.home}/workspace. For example, you might use -data /shared/eclipse/e4/workspace-orion when invoking your eclipse instance. | ||
| + | |||
| + | 4. As a general rule, e4Build should only be used literally "for building" and if a "build user" needed to edit things, create directories, etc., in the /shared/eclipse area, they should work with their own committer ID. That directory (/shared/eclipse) has been set up so that the "group owner" should always be 'eclipse.platform.releng' so any committer that is a member of that linux group should be able to add, write, and delete files at will (no matter who created them ... which is desirable, since it is, after all, a shared area for shared work. | ||
Revision as of 12:16, 8 April 2012
This page is to capture a few notes on e4Build build Id.
This id is "owned" by Paul Webster and at this time is "shared" by David Williams, John Arthorne, and Bogdan Gheorghe (at at times others) to do the various builds for the Eclipse Project; the Eclipse SDK, Orion, e4 Incubator, etc. Usually once a "build user" is given initial access they set up access via SSH certificates so they don't require the password any longer (this allows Paul to change and safeguard the password at any time he'd like).
1. The ID has been given the right accesses and permissions to sign and commit/push tags to git, and it can push changes to the maps project. (See bug 374248)
2. As a general rule, nothing should be changed or stored in e4Build $HOME. Some things, such as .cvspass, .bashrc would in principle change how other "shared builds" run. So, please note any special cases or changes here on this page.
3. One implication of the above "rule" is that during builds, if people use Eclipse to do something during the build, they should be sure to point to a "workspace" in their own build area, or else the default is ${user.home}/workspace. For example, you might use -data /shared/eclipse/e4/workspace-orion when invoking your eclipse instance.
4. As a general rule, e4Build should only be used literally "for building" and if a "build user" needed to edit things, create directories, etc., in the /shared/eclipse area, they should work with their own committer ID. That directory (/shared/eclipse) has been set up so that the "group owner" should always be 'eclipse.platform.releng' so any committer that is a member of that linux group should be able to add, write, and delete files at will (no matter who created them ... which is desirable, since it is, after all, a shared area for shared work.