D'oh! Disabling StrictHostKeyChecking made it work perfectly, thanks!
On 25 March 2016 at 23:28, Domen Kožar wrote:
> See https://github.com/peti/hydra-tutorial/issues/2
>
> On Fri, Mar 25, 2016 at 9:48 PM, Teo Klestrup Röijezon
> wrote:
>
>> For the record, it
See https://github.com/peti/hydra-tutorial/issues/2
On Fri, Mar 25, 2016 at 9:48 PM, Teo Klestrup Röijezon
wrote:
> For the record, it says something about host key verification failing. If
> I try to run `ssh g...@bitbucket.org` sudoed as either user it works and
> shows that
For the record, it says something about host key verification failing. If I
try to run `ssh g...@bitbucket.org` sudoed as either user it works and shows
that it should have access to the repo.
On 25 March 2016 at 22:47, Teo Klestrup Röijezon wrote:
> Did that for both hydra
Did that for both hydra and hydra-queue-runner, no luck. :/
On 25 March 2016 at 21:29, Oliver Charles wrote:
> I've had luck just doing `sudo -u hydra -i` on the Hydra machine and
> setting up id_rsa and friends in ~/.ssh. I think the full path is
> /var/lib/hydra/.ssh.
>
I've had luck just doing `sudo -u hydra -i` on the Hydra machine and
setting up id_rsa and friends in ~/.ssh. I think the full path is
/var/lib/hydra/.ssh.
On Fri, Mar 25, 2016 at 3:19 PM Teo Klestrup Röijezon
wrote:
> Hi,
>
> Is there any support for setting up Hydra jobs
Hi,
Is there any support for setting up Hydra jobs with private git
repositories as build inputs? I generated a SSH keypair each for hydra and
hydra-queue-runner, and added them both as deploy keys on Bitbucket, but
the authentication still seems to fail.
This was using Hydra