| Summary: | Attach aarch64 build machine to releng jipp | ||
|---|---|---|---|
| Product: | Community | Reporter: | Alexander Kurtakov <akurtakov> |
| Component: | CI-Jenkins | Assignee: | CI Admin Inbox <ci.admin-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | christian.dietrich.opensource, daniel_megert, frederic.gurr, sravankumarl, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 565419 | ||
|
Description
Alexander Kurtakov
Machine is ready and compiles swt fine. What are the steps to get it added to releng jipp? Please create a "genie.releng" account on the machine. I will send you the public SSH key of the genie.releng user that needs to be added to the .ssh/authorized_keys file. We will need the IP address of the new server as well. Does it have to be "genie.releng" ? `adduser genie.releng`: adduser: Please enter a username matching the regular expression configured via the NAME_REGEX configuration variable. Use the `--force-badname' option to relax this check or reconfigure NAME_REGEX. I just don't feel comfortable to use "--force-badname". If you don't want to give releng a "bad name" and use the force, "genie_releng" is also possible. ;) Lets do it via websocket Lets connect via websocket similar to ppcle machines working dir is "/home/swtbuild/build" please name the executor as "aarch64-swt" java -jar agent.jar -jnlpUrl https://ci.eclipse.org/releng/computer/aarch64-swt/slave-agent.jnlp -secret @secret-file -workDir "/home/swtbuild/build" I've sent instructions to set up the secret-file via email. Hit sent too fast: The above command needs to be executed on the agent to start the websocket connection. Please set up the secret first. The machine is connected and available. Thanks for quick response Ok. Closing. |