Make SFTP for maven repository use pkey. #11751

Activity

1. offtherailz

   added this to the 2026.01.00 milestone on Dec 1, 2025
2. offtherailz

   assigned

   randomorder

   on Dec 1, 2025
3. offtherailz

   added the

   Task

   issue type on Dec 1, 2025
4. offtherailz

   added

   enhancement

   on Dec 1, 2025
5. tdipisa

   added

   DevOps

   on Dec 1, 2025
6. tdipisa

   added

   MapStore

   on Dec 9, 2025
7. tdipisa

   modified the milestones: 2026.01.00, 2026.01.01 on Mar 2, 2026
8. tdipisa

   modified the milestones: 2026.01.01, 2026.02.00 on Apr 8, 2026
9. tdipisa

   linked a pull request that will close this issuebuild: add support for ssh key for publishing artifacts #85on Jun 17, 2026
10. tdipisa

    linked a pull request that will close this issueconfig: add ssh-key support with wagon-ssh-external plugin #554on Jun 17, 2026
11. offtherailz commented on Jul 17, 2026

    

    offtherailz

    on Jul 17, 2026

    Last edited by offtherailz

    MemberAuthor

    More actions

    Error:  Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:3.1.4:deploy (default-deploy) on project mapstore-java: Failed to deploy artifacts: Could not transfer artifact it.geosolutions.mapstore:mapstore-java:pom:1.12-20260717.100624-279 from/to geosolutions (scpexe://maven.geo-solutions.it/): Error executing command for transfer: Exit code 255 - exec request failed on channel 0 -> [Help 1]
    Error:  
    Error:  To see the full stack trace of the errors, re-run Maven with the -e switch.
    Error:  Re-run Maven using the -X switch to enable full debug logging.
    Error:  
    Error:  For more information about the errors and possible solutions, please read the following articles:
    Error:  [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
    Error: Process completed with exit code 1.
    

    it is ok to do a quick check to exclude server side problems, and it is ok you re-run the publish task.
    If @mahesh-wor don't have a quick solution in next hours, I think that at this point, we postpone this at least to 2026.03.00. Can you :
    revert the PR (button revert on the old PR)
    close the backport PR with a comment (reverted and moved task to 2026.03.00
    Move the issues linked to 2026.03.00 milestone
12. mahesh-wor

    modified the milestones: 2026.02.00, 2026.03.00 on Jul 17, 2026
13. randomorder

    assigned

    mahesh-wor

    on Jul 27, 2026
14. tdipisa

    modified the milestones: 2026.03.00, 2027.01.00 on Sep 17, 2026