| Push command did not fail due to insufficient privileges [message #1863549] |
Thu, 08 February 2024 11:44  |
Eclipse User |
|
|
|
Hello everyone,
Recently a bug was reported at JReleaser (consumer of JGit 5.13.x) which states the following https://github.com/jreleaser/jreleaser/issues/1582
Basically the code either clones an existing repository (asdf-*) or creates a new one, adds files to it, creates a commit, and pushes. However, given that the repository is different than the one where the release occurs GitHub requires that the access token have additional permissions. In the case of the reporter said permission is missing. I'm able to reproduce the problem with a token configured in the same way as the reporter explained.
Now, JReleaser must remain Java8 compatible for the time being, this is why it consumes JGit 5.13.x. I wonder. If this issue has been observed before and hopefully fixed in the 6.x series? If that's the case then we'll have to wait til JReleaser can move past Java 11 to perform an upgrade.
If this issue has not been observed then the problem may lie in the execution of the push command, as an exception or error should have been caught and propagated to the caller. Right now nothing happens as the operation appears to complete successfully. Matter of fact, it leaves the remote repository in either a freshly created state (when new) or unmodified (when previously existing).
Finally, if by any chance there were to be a workaround in 5.13.x to further inspect the execution of the push command to get to the bottom of the problem, that would be appreciated, thank you.
|
|
|
| Re: Push command did not fail due to insufficient privileges [message #1863771 is a reply to message #1863549] |
Mon, 26 February 2024 04:55  |
| Eclipse User |
|
|
|
Maybe you can try with latest jgit master if you compile JReleaser yourself using Java 11+ and check if it fixes your problem ?
Otherwise your best bet is debugging what's going wrong. If you are contributing a fix I can review it.
Otherwise I consider 5.13 pretty much EOL, we can't maintain umpteen old releases, instead we better work on
bumping the minimum Java version in JGit to a more recent LTS of Java (17 or 21) and make progress on master.
|
|
|
Powered by
FUDForum. Page generated in 0.27545 seconds
Home