Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cross-project-issues-dev] Linux Tools build cannot write to standard output location


Something has changed in the build infrastructure since last week and our Linux Tools master build pipeline is failing when it tries to write to the standard updates-nightly output directory we use.

Is there something we can do or is this a new infrastructure issue?  I didn't see any posting about anything other than the removal of git protocol which I had fixed last week and the jar signer plug-in version which we exceed.

-- Jeff J.

[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Deploy)
[Pipeline] sshagent
[ssh-agent] Using credentials genie.linuxtools (ssh://genie.linuxtools@xxxxxxxxxxxxxxxxxxxxxxxxxxxx)
[ssh-agent] Looking for ssh-agent implementation...
[ssh-agent]   Exec ssh-agent (binary ssh-agent on a remote machine)
$ ssh-agent
Running ssh-add (command line suppressed)
Identity added: /home/jenkins/agent/workspace/linuxtools-master@tmp/private_key_13458881067364320014.key (/home/jenkins/agent/workspace/linuxtools-master@tmp/private_key_13458881067364320014.key)
[ssh-agent] Started.
[Pipeline] {
[Pipeline] sh
+ ssh genie.linuxtools@xxxxxxxxxxxxxxxxxxxxxxxxxxxx rm -rf '/home/data/httpd/*'
Permission denied, please try again.
Permission denied, please try again.
genie.linuxtools@xxxxxxxxxxxxxxxxxxxxxxxxxxxx: Permission denied (publickey,password).

Back to the top