Declaring maven as pipeline top-level tool breaks sshagent step in Eclipse I-builds
Summary
If one declares maven as Jenkins pipeline top-level tool in https://ci.eclipse.org/releng/job/Builds/job/I-build-4.31, i.e. with
tools {
maven 'apache-maven-latest'
}
instead of adding it to the PATH environment variable with:
environment {
PATH = "$PATH:/opt/tools/apache-maven/latest/bin"
}
the sshagent step fails in mysterious ways to find a suitable ssh-agent provider
:
19:06:34 [ssh-agent] Using credentials eclipse-releng-bot (GitHub bot (SSH))
19:06:34 [ssh-agent] Looking for ssh-agent implementation...
19:06:35 [ssh-agent] FATAL: Could not find a suitable ssh-agent provider
19:06:35 [ssh-agent] Diagnostic report
For context please see the following issue and Jenkins build
- https://github.com/eclipse-platform/eclipse.platform.releng.aggregator/issues/1724#issuecomment-1892602584
- https://ci.eclipse.org/releng/job/Builds/job/I-build-4.31/95/
Priority
-
Urgent -
High -
Medium -
Low
Severity
-
Blocker -
Major -
Normal -
Low