Closed danielwagn3r closed 1 year ago
Some questions to try to narrow it down:
Here's something you could try:
I've already reproduced the issue with a freshly imported model on which I did a single change. Import worked fine, so communication with Git Server (Atlassian Bitbucket) should be fine.
I've seen that already the commit doesn't work apparently so there is no push tried after all, at least it seems so.
I've already reproduced the issue with a freshly imported model on which I did a single change. Import worked fine, so communication with Git Server (Atlassian Bitbucket) should be fine.
Could you please detail you plugin configuration? If you use SSH key, then please try with alternate methode (HTTPS with user/password or token).
This is a Bouncy Castle error. This is used internally by JGit for encrypting and signing with GPG keys. Is there some unusual configuration going on here?
Hm, the problem seem's originate from the the global (per user) .gitconfig
[commit]
gpgsign = true
[gpg]
program = C:\\Program Files (x86)\\GnuPG\\bin\\gpg.exe
which wasn't honored by JGit as far as I know. Was there a change in JGit regarding this?
I don't know if there is an issue with JGit 5.3 and Bouncy Castle that could cause this. I searched but couldn't find anything. It may be that JGit 5,5 fixes this.
In the meanwhile I've disabled signed commits.
I couldn't even get my GPG key to work with JGit. I think it's this:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=545673
When JGit 5.6 is released I'll try that.
I've tested this with JGit 5.6 and there is a more fundamental issue to using GPG signed commits - we have to implement a specific credentials provider to ask the user for a pass phrase to the GPG store (or get it from somewhere) when committing.
I've created some POC code to do this but needs more work, refactoring and testing so we have to say that, right now, GPG signing of commits is unsupported.
Notes to self:
Create a GPG key:
gpg --list-keys
gpg --gen-key
Add to .gitconfig the public key and gpgsign:
[user]
signingkey = 1CCF1FC43907B95A18251F68E51AF52E2E2F12F1
[commit]
gpgsign = true
POC code in branch "gpg"
There are times when coArchi does an automatic commit (when first cloning, when creating a new repo from a model, merging, refresh (pull) and restore commit). It might be inconvenient to ask the user for the pass-phrase at these points. We need to think about whether GPG signing is desirable or not and, if it is, how to deal with these types of commit. At any rate, my assessment is that implementing it would take some work.
just ran into this, womp womp
just ran into this, womp womp
Signed commits won't be implemented in coArchi, so this should be disabled in .gitconfig
which stinks cuz 99% of my work with git is on the command line so having gpg signing on by default isn't worth giving up for the 1% of the time i have to push from archi. rock. hard place. womp womp.
which stinks cuz 99% of my work with git is on the command line so having gpg signing on by default isn't worth giving up for the 1% of the time i have to push from archi. rock. hard place. womp womp.
But as explained several times here and on Archi's forum, nobody should use git command on a coArchi maintained repository, unless you want to loose your work of course (git is not able to do merge in a way that guarantee that the model won't be corrupted, coArchi does).
which stinks cuz 99% of my work with git is on the command line so having gpg signing on by default isn't worth giving up for the 1% of the time i have to push from archi. rock. hard place. womp womp.
You can manually add this to the local config
file in the archi repository in the .git
directory.
[commit]
gpgSign = false
But please feel free to implement GPG signing as a pull request. It's all free and open source.
For the next version of coArchi I'll add the following as default to each new repo's config
file:
[commit]
gpgSign = false
@Phillipus oooh. good idea. thanks.
For the next version of coArchi I'll add the following as default to each new repo's config file
This is now in coArchi 0.8.5
wow. amazing. i assumed "next version" would be like a year from now. my heros!
I'm currrently facing a problem where I'm unable to refresh or commit my model anymore without any user-visible failure. In the Archi logfile I found the following exception:
Versions: Archi 4.6.0.201911111111 Archi Model Repository 0.5.3.201910181308