You may want to watch or modify the queue of JIRA tickets. If you have a JIRA login then it's best to look at the real JIRA task filter which shows Go-related tickets.
You can get a login here. Alternatively, the Wiki assembls this report from JIRA right here in the Wikito the JIRA and/or Confluence infrastructure by checking the instructions on the right hand side of the Wiki starting page.
Go Agents are what other systems might call "build slaves". They do the actual compilation Jobs assigned by the Go Server.
List of Go Agents and maintainers:
(This list needs continuous maintenance - please notify the administrator if you see a mismatch)
|Agent Name||Location, Company and Maintainer contact||Operating system & setup||Comments|
Custom, temporarily unavailable
Specialized agent for Vagrant/VirtualBox jobs
|genivi-builder||Standard Docker setup|
Agent running on docs.projects.genivi.org machine to handle automated testing preparation and Lava integration
Run by GENIVI IT (→ AWS)
This is a special purpose agent used to deploy files on the "docs" local disk (to be able to put them into web serving directories, and another storage location where lava.genivi.org can fetch test artifacts.
|Standard Docker setup + install custom credentials for lava.genivi.org|
N.B. The credentials to log into lava.genivi.org are manually
Temporary. Machine is run by Gunnar Andersson
|Standard Docker setup||64 GB RAM, modern CPU & fast SSD|
|Resource Name||Purpose and explanation|
Example of Pipeline
|Example of Agent |
having this resource
This signifies an agent machine that has been entrusted to keep a copy of licensed binary drivers for Renesas hardware, typically graphics drivers. Without those binaries the build would fail but since they are only distributed after user license acceptance, there is no opportunity for an Agent to download them as part of the pipeline input material.
Special build steps are included to copy the binaries from a predefined location on an agent machine carrying this resource.
|All GDP / Baseline builds for Renesas Hardware|
Most Yocto_build enabled agents – please refer to the actual agent list on server (might need admin credentials)
This is used to indicate the agent is capable of running full Yocto builds of GDP size.
This might go away if all agents are capable of doing that, or if those that are not (for example on-target test agents) are instead placed in a unique Environment (see below).
|Full GDP / baseline builds using Yocto.|
Most agents, unless they are known to be small (slow, or with little disk space).
|deploy_genivi||This means the agent is colocated or otherwise has the ability to copy files directly to the disks involved in other parts of GENIVI infrastructure - most notably to copy files to the web server area so that they show up on https://docs.projects.genivi.org/releases||Single special-purpose agent.|
This resource is specified on an agent dedicated to control a board farm for <architecture>, i.e. testing jobs can be assigned to run on it.
|GDP & Baseline automated tests|
|arm (N/A)||This is an agent machine that runs an ARM processor appropriate for native compilation/execution on ARM.|