This is counterpart of . While that ticket deals with giving access to new Arm’s OpenCI server to automated systems like LAVA and Tux, this tickets is about getting developer access to it.

Step-by-step access instructions.

The URL of the new Arm OpenCI server is https://jenkins.openci-dev.arm.com/ , but it’s accessible only from select IP addresses. We’re going to setup such access for user’s browser using ci.trustedfirmware.org as an SSH proxy host (which has its IP whitelisted to access the Arm server).

1. Have SSH access to ci.trustedfirmware.org

2. Run: ssh -v -N -D localhost:9090 user.name@ci.trustedfirmware.org

3. You can now configure your browser to use localhost:9090 as SOCK5 server to access https://jenkins.openci-dev.arm.com/ https://jenkins.openci-test.arm.com/

4. As you probably want to keep accessing all other sites directly, it makes sense to configure either dedicated browser with the SOCKS proxy, or create a new profile in existing browser and use that.

5. For Firefox, following may work:

6. Run firefox -P to create a new profile, say “arm-socks”. You probably want to not specify “Use the selected profile without asking at startup“ (to keep using normal profile by default).

7. Then open standalone Firefox process with this profile: firefox -no-remote -p arm-socks .

8. Go to Menu → Settings → Network Settings. Choose “Manual proxy configuration”, SOCKS host, port, SOCKS v5 protocol, “Proxy DNS when using SOCKS v5”.

9. Use the same command (firefox -no-remote -p arm-socks) later to start a new session.

References:

(Just using a command-line switch to set proxy, e.g. with Chrome may be complicated, as that still requires a separate profile dir (or doesn’t work), and e.g. on Ubuntu Chrome is shipped as snap with restricted filesystem access to specify a standalone profile dir. YMMV)