[JIRA] [publish-over-ssh-plugin] (JENKINS-29360) Bump jsch to fix "Algorithm negotiation failed"
Title: Message Title Raúl Wegmann commented on JENKINS-29360 Re: Bump jsch to fix "Algorithm negotiation failed" We have have the same problem after hardening our SSH server configuration. As mentioned above, updating the jsch dependency to the latest version fixes this problem. Please consider merging the following (one line) pull request: https://github.com/jenkinsci/publish-over-ssh-plugin/pull/11 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven2] (JENKINS-4861) Post-build deployment of Maven artifacts does not work with scpexe-type repository
Raúl Wegmann updated JENKINS-4861 Post-build deployment of Maven artifacts does not work with scpexe-type repository We are seeing this problem again when using any Jenkins version greater than 1.559 so that we have been stuck for the last few months with that version. Apparently some CLI escaping issues have been fixed in the plexus-utils library since version 3.0.10, which is the one included in the maven-plugin, and I believe that this bug may have been fixed since 3.0.16 (https://jira.codehaus.org/browse/PLXUTILS-161). Please consider including the changes of the following pull request that fixes this error by bumping the plexus-utils version to the most recent one (3.0.17): https://github.com/jenkinsci/maven-plugin/pull/28 Change By: Raúl Wegmann (22/Aug/14 4:30 PM) Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-4861) Post-build deployment of Maven artifacts does not work with scpexe-type repository
Raúl Wegmann reopened JENKINS-4861 Post-build deployment of Maven artifacts does not work with scpexe-type repository We can reproduce this error with Jenkins ver. 1.505 (using Maven 3). Please ask if you need further information. Change By: Raúl Wegmann (13/Mar/13 3:58 PM) Resolution: CannotReproduce Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-4861) Post-build deployment of Maven artifacts does not work with scpexe-type repository
Raúl Wegmann commented on JENKINS-4861 Post-build deployment of Maven artifacts does not work with scpexe-type repository Here is the current stack trace: ERROR: Failed to deploy artifacts: Could not transfer artifact com.example.util:lib-util-core:jar:2.0.0.0.0-20130313.100035-11 from/to lib-deploy-snapshots (scpexe://maven.example.com/maven/snapshots/): Exit code: 2 - /bin/sh: 1: cd: can't cd to /srv/jenkins/jobs/libj-util_trunk_ci/modules/com.example.util-util-core/builds/2013-03-13_10-58-15/archive/com.example.util/lib-util-core/2.0.0.0.0-SNAPSHOT org.apache.maven.artifact.deployer.ArtifactDeploymentException: Failed to deploy artifacts: Could not transfer artifact com.example.util:lib-util-core:jar:2.0.0.0.0-20130313.100035-11 from/to lib-deploy-snapshots (scpexe://maven.example.com/maven/snapshots/): Exit code: 2 - /bin/sh: 1: cd: can't cd to /srv/jenkins/jobs/libj-util_trunk_ci/modules/com.example.util-util-core/builds/2013-03-13_10-58-15/archive/com.example.util/lib-util-core/2.0.0.0.0-SNAPSHOT at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:141) at hudson.maven.reporters.MavenArtifactRecord.deploy(MavenArtifactRecord.java:190) at hudson.maven.RedeployPublisher.perform(RedeployPublisher.java:176) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:814) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:786) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:947) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:733) at hudson.model.Run.execute(Run.java:1592) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Caused by: org.sonatype.aether.deployment.DeploymentException: Failed to deploy artifacts: Could not transfer artifact com.example.util:lib-util-core:jar:2.0.0.0.0-20130313.100035-11 from/to lib-deploy-snapshots (scpexe://maven.example.com/maven/snapshots/): Exit code: 2 - /bin/sh: 1: cd: can't cd to /srv/jenkins/jobs/libj-util_trunk_ci/modules/com.example.util-util-core/builds/2013-03-13_10-58-15/archive/com.example.util/lib-util-core/2.0.0.0.0-SNAPSHOT at org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:280) at org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:211) at org.sonatype.aether.impl.internal.DefaultRepositorySystem.deploy(DefaultRepositorySystem.java:443) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:137) ... 11 more Caused by: org.sonatype.aether.transfer.ArtifactTransferException: Could not transfer artifact com.example.util:lib-util-core:jar:2.0.0.0.0-20130313.100035-11 from/to lib-deploy-snapshots (scpexe://maven.example.com/maven/snapshots/): Exit code: 2 - /bin/sh: 1: cd: can't cd to /srv/jenkins/jobs/libj-util_trunk_ci/modules/com.example.util-util-core/builds/2013-03-13_10-58-15/archive/com.example.util/lib-util-core/2.0.0.0.0-SNAPSHOT at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$4.wrap(WagonRepositoryConnector.java:951) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$4.wrap(WagonRepositoryConnector.java:941) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.run(WagonRepositoryConnector.java:837) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector.put(WagonRepositoryConnector.java:467) at org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:274) ... 14 more Caused by: org.apache.maven.wagon.TransferFailedException: Exit code: 2 - /bin/sh: 1: cd: can't cd to /srv/jenkins/jobs/libj-util_trunk_ci/modules/com.example.util-util-core/builds/2013-03-13_10-58-15/archive/com.example.util/lib-util-core/2.0.0.0.0-SNAPSHOT at org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.executeScpCommand(ScpExternalWagon.java:321) at org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.put(ScpExternalWagon.java:403) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.run(WagonRepositoryConnector.java:811) ... 16 more It is trying to cd into /srv/jenkins/jobs/libj-util_trunk_ci/modules/com.example.util-util-core/, while the
