I don’t think it’s a permissions issue in my case. I can run git commands in windows powershell (as the same user) on the command line and push / pull / fetch from the remote with no issues. The issue more seems to be with RDi not using my private key, or not connecting with the right protocol.
Also I was reminded that there is an install option for GIT tooling during the RDi install process – so that is probably the preferred method of getting the egit plugin installed.
From: Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>
Sent: Wednesday, March 22, 2023 10:17 AM
To: Rational Developer for IBM i <wdsci-l@xxxxxxxxxxxxxxxxxx>
Cc: Weirich, John <John.Weirich@xxxxxxxxxx>
Subject: **EXTERNAL** Re: [WDSCI-L] Git in RDi 18.104.22.168
When I did that there was a security issue with the .ssh directory. the user profile tying to set up the SSH communications was unable to use the keys. I don't have the solution at my fingertips, and I doubt I saved the emails anyway. On my MAC I set that directory to 700 and it worked.
Chief Technical Architect
Agile Technology Architects
On Wed, Mar 22, 2023 at 10:02 AM Weirich, John via WDSCI-L <wdsci-l@xxxxxxxxxxxxxxxxxx<mailto:wdsci-l@xxxxxxxxxxxxxxxxxx>> wrote:
I am trying to get a workable eGIT extension in my version of RDi, which is 22.214.171.124 20210819_0803.
What is the correct way to install the eGIT extension? I did not find eGIT in the eclipse marketplace (I recall it being there in prior versions of RDi). The way I eventually ended up installing was downloading and installing V126.96.36.19971140-r from https://wiki.eclipse.org/EGit/FAQ#Where_can_I_find_older_releases_of_EGit.3F
> based on the information in the 'What versions of Eclipse does EGit target?' which indicates this version for 'Eclipse 4.4 + (Luna) and thinking that my 9.6.011 version of RDi is based upon eclipse 4.6.3. I'm not even sure that 4.6.3 is the version of eclipse that my RDi is based upon - how can I find this info? Is there a newer version of egit that will work with my RDi version?
I'm having issues setting up an ssh connection to our corporate gitlab. I have generated SSH keys in powershell and registered them in gitlab, and command line interface in windows and WSL both work with these keys. HOWEVER, RDi doesn't seem to want to use my private key.
My private key is in the standard windows location: C:\Users\jweirich\.ssh\id_rsa
In RDi I have gone to window > preferences > General > Network Connections > SSH2 > General and confirmed that SSH2 home: is the correct directory and Private keys: has id_rsa
eGIT seems to work fine with my local GIT repo, I can stage and commit just fine.
I used command line to add the gitlab project remote repo as origin and confirmed I can fetch / pull, etc from command line.
The origin remote shows correctly in the Git Repositories view.
But when I stage, then, commit and push using the Git Staging view, the SSH welcome message set up by my organization will appear several times, and I hit OK each time, but after 3 or 4 tries eventually I get:
Can't connect to any repository: git@path/to/gitlab/project.git<mailto:git@path<mailto:git@path>/to/gitlab/project.git> (git@path/to/gitlab/project.git<mailto:git@path<mailto:git@path>/to/gitlab/project.git>: Auth fail)
(obfuscated the path in the error message above)
With push towards devops and ci/cd, Will future versions of RDi have git capabilities built in without having to jump through these hoops?
The information contained in this message is confidential proprietary property of Nelnet, Inc. and its affiliated companies (Nelnet) and is intended for the recipient only. Any reproduction, forwarding, or copying without the express permission of Nelnet is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to this e-mail.
This is the Rational Developer for IBM i (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx<mailto:WDSCI-L@xxxxxxxxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx<mailto:WDSCI-L-request@xxxxxxxxxxxxxxxxxx>
Before posting, please take a moment to review the archives
As an Amazon Associate we earn from qualifying purchases.