search

researchgate / gradle-release

gradle-release is a plugin for providing a Maven-like release process for projects using Gradle
MIT License
860 stars 223 forks source link

where to provide scm info in gradle-release plugin? #167

Open tulachana opened 8 years ago

tulachana commented 8 years ago

HI ,

I am getting this error.

FAILURE: Build failed with an exception.

I don't know where to provide the Repo URL and the credentials to push to repository. Please help.

arvind-das commented 7 years ago

any updates , having same issue. I even set up git with ssh access, but it does not seem to work.

arvind-das commented 7 years ago

actually I just fixed it here, after configuring connection with ssh, I also changed remote from https to ssh and that did the trick. Just remove origin

git rm origin

and then add ssh one using

git remote add origin 'git@github.com:username/myrepo.git

Hillkorn commented 7 years ago

By default the plugin tries to push to origin which should work. It executes the "git push" like you would on the command line.

diegobmd commented 7 years ago

Any body solved this? I have the same problem with jenkins ci The username doesn't on url when clone

Hillkorn commented 7 years ago

You have to use ssh and Jenkins needs to be authorized with its key

diegobmd notifications@github.com schrieb am Fr., 3. März 2017, 23:10:

Any body solved this? I have the same problem with jenkins ci The username doesn't on url when clone

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/researchgate/gradle-release/issues/167#issuecomment-284084215, or mute the thread https://github.com/notifications/unsubscribe-auth/ABsepFcrATG1Z4mvkFcHJRebnOtHy77Jks5riI_kgaJpZM4IFkh2 .

Poeschl commented 6 years ago

So there is no way to push over https?

jeffwysong commented 6 years ago

I struggled with this plugin and Jenkins as well. I solved the issue by adding a .netrc file to the Jenkins Agent, which I do not think is the best solution, but was the only way I could get things working.

I have found the problem to be that credentials used from the checkout stage are not used in the release stage. I could not get the git credential.helper to work for me either.

jonnybot0 commented 5 years ago

This problem also crops up if you have an SSH key passphrase configured. https://www.ssh.com/ssh/passphrase

aarmistead-chwy commented 1 year ago

Here we are 2023, same problem