-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Usage - commitLock with ssh #123
Comments
if you're setup to git clone over ssh without getting a prompt. commitLock
should also work without prompting.
If you have a passphrase on the key you'll need to setup ssh-agent / use
ssh-add.
…On Wed, Jun 21, 2017 at 3:27 PM vivsrivastav ***@***.***> wrote:
I wonder if gradlew commitLock works with SSH?
Am trying to automate the process of generating the lock file, build and
test the application with upgraded dependencies. This works fine. I can
commit the files by running gradlew commitLock from command prompt. But i
want to commit the lock file with human intervention. Wonder if this is
possible with nebula.gradle-git-scm and commitLock?
Is there any documentation for SSH usage?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#123>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAvvFtANHJKqhFnWWslVAFU3Ud5b1Ww_ks5sGZjpgaJpZM4OBmH_>
.
|
Yes i can clone git over ssh without a prompt. In fact i am using ssh_auth_sock. I was able to make it work by invoking git commands directly (ssh_auth_sock git add, ssh_auth_sock git commit, ssh_auth_sock git push). Not sure if ssh_auth_sock ./gradlew commitLock will propagate the auth sock variable to every git command executed by commitLock. |
i do not know how jgit would interact with ssh_auth_sock
…On Sun, Jun 25, 2017 at 10:44 PM vivsrivastav ***@***.***> wrote:
Yes i can clone git over ssh without a prompt. In fact i am using
ssh_auth_sock. I was able to make it work by invoking git commands directly
(ssh_auth_sock git add, ssh_auth_sock git commit, ssh_auth_sock git push).
Not sure if ssh_auth_sock ./gradlew commitLock will propagate the auth sock
variable to every git command executed by commitLock.
I will give a try
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#123 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAvvFnfIl2h-C5aVv373lLFYs75eMVM9ks5sH0VSgaJpZM4OBmH_>
.
|
closing due to lack of activity |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I wonder if gradlew commitLock works with ssh keys
Am trying to automate the process of generating the lock file, build and test the application with upgraded dependencies. I can manually commit the files by executing gradlew commitLock from command prompt.
But my use case is to commit the lock file without any human intervention. Wonder if this is possible with nebula.gradle-git-scm and commitLock for a git repository that is configured to use SSH keys for commits?
Let me know if there is any documentation for SSH usage of commitLock ?
The text was updated successfully, but these errors were encountered: