Well, I just verified my ssh-agent is running and my key is loaded, but the same error as above persists. The error says connection attempted to timeout, wouldn't I be getting an authentication error if there was something wrong with my key? And again, straight *git push *works, it's only failing when I run through maven... The "connection timeout" message leads me to believe this has something to do with the proxy but I can't fathom why Git would be ignoring my proxy settings when called by Maven.
On Friday, April 13, 2018 at 12:41:50 PM UTC-7, Emory Penney wrote: > > Yes I did, that resulted in the error indicating my username was an > invalid hostname. I'd be happy to try to figure that method out if it would > work better... > > On Fri, Apr 13, 2018, 12:38 Slide <[email protected]> wrote: > >> Just to be clear, you did -Dusername=<something> -Dpassword=<something> >> correct? >> >> On Fri, Apr 13, 2018 at 12:34 PM Emory Penney <[email protected]> >> wrote: >> >>> I know there are a bunch of threads on this but I haven't found any >>> feedback in any of the existing threads that helped me resolve this at >>> all. Releases fail to push to GIT during prepare: >>> >>> [INFO] Working directory: >>> C:\Users\ejpenney\Desktop\startup-trigger-plugin >>> [INFO] Executing: cmd.exe /X /C "git push >>> [email protected]:jenkinsci/startup-trigger-plugin.git >>> refs/heads/master:refs/heads/master" >>> [INFO] Working directory: >>> C:\Users\ejpenney\Desktop\startup-trigger-plugin >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] BUILD FAILURE >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] Total time: 02:55 min >>> [INFO] Finished at: 2018-04-13T12:21:00-07:00 >>> [INFO] >>> ------------------------------------------------------------------------ >>> [ERROR] Failed to execute goal >>> org.apache.maven.plugins:maven-release-plugin:2.5.3:prepare (default-cli) >>> on project startup-trigger-plugin: Unable to commit files >>> [ERROR] Provider message: >>> [ERROR] The git-push command failed. >>> [ERROR] Command output: >>> >>> *[ERROR] ssh: connect to host github.com <http://github.com> port 22: >>> Connection timed out[ERROR] fatal: Could not read from remote repository.* >>> [ERROR] >>> [ERROR] Please make sure you have the correct access rights >>> [ERROR] and the repository exists. >>> [ERROR] >>> [ERROR] -> [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/MojoFailureException >>> >>> I'm running Maven 3.5.3 on Windows 10, with Git for Windows (MSYS >>> 2.16.2-windows.1). The Jenkins Support Wiki >>> <https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins>indicates this >>> could be a problem with Tortoise GIT, which I do not have installed, so I >>> can't utilize the documented work around. If I specify -*Dusername *and >>> -*Dpassword *on the command line then I get the error where it says my >>> username is not a valid hostname so I've set my username and password in >>> the Maven settings.xml. >>> >>> I'm running behind an http_proxy (that does not require >>> authentication). I've set all the usual environment variables to point at >>> my proxy (ALL_PROXY, HTTPS_PROXY, HTTP_PROXY, FTP_PROXY). I've configured >>> maven to use the proxy in settings.xml. I've set git config --system >>> http.proxy as well as --global. As a matter of fact, *mvn install* and >>> *git >>> push* work just fine. It only fails during release:prepare. Read that >>> again: Git pulls and pushes work fine UNLESS they're happening from inside >>> Maven. >>> >>> What the heck am I missing? Why can't GIT connect? >>> >>> Thanks >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Developers" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/34afdb62-a0ea-4ce9-bdb3-f0bbf0c9d7fc%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/jenkinsci-dev/34afdb62-a0ea-4ce9-bdb3-f0bbf0c9d7fc%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Jenkins Developers" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/jenkinsci-dev/1FDdo2h2wug/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVf2YUiX67br2xg%3DzPW9v0fEPDaq3Y705DYiAhD6eLW6cg%40mail.gmail.com >> >> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVf2YUiX67br2xg%3DzPW9v0fEPDaq3Y705DYiAhD6eLW6cg%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/c62f81bd-e094-4b7f-900e-378c1cfeed60%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
