Hello,
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.linuxto...@projects-storage.eclipse.org)
[ssh-agent] Looking for ssh-agent implementation...
[ssh-agent] Exec ssh-agent (binary ssh-agent on a remote machine)
$ ssh-agent
SSH_AUTH_SOCK=/tmp/ssh-JKaxH65G7Ffd/agent.1134
SSH_AGENT_PID=1136
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.linuxto...@projects-storage.eclipse.org rm -rf
'/home/data/httpd/download.eclipse.org/linuxtools/updates-nightly/*'
Permission denied, please try again.
Permission denied, please try
again.genie.linuxto...@projects-storage.eclipse.org: Permission denied
(publickey,password).
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
