On 04.04.2015 05:45 PM, Michael DePaulo wrote:
I figured I would setup my Raspberry Pi 2 at my apartment as a Jenkins slave. However, it appears that I would need to upload the packages to code.x2go.org with dupload, which would in turn call scp in batch mode. That means setting up SSH public key authentication.
We would also have to figure out package signing.
So before I continue, I want to know:
- Should I continue setting this up, or should we try to use qemubuilder on japsand with a Raspberry Pi version of QEMU?
Really not sure what makes more sense. Qemu is really slow for non-native arches (naturally, due to the emulation.) A raspberry pi might even be faster than that, but I don't know this for sure.
- If I continue setting this up, how should we setup the SSH and GPG keys?
I believe GPG signing should be done on the server after uploading the files. Transferring the general private key to your RasPi machine isn't a good idea.
I'm also wary to having your RasPi machine log in to ymir as x2go-admin, for that would it basically give it complete access to everything, including git repos.
Uploading files into a staging area to which x2go-admin has access with a new, unprivileged user and having a cron job for x2go-admin move the files in place seems to be a saner solution.
Mihai