Skip to main content
K
kiran21-Visitor
1-Visitor
September 23, 2019
Solved

Unable to push files into Git using GitBackup extension

  • September 23, 2019
  • 4 replies
  • 2743 views

Hi Guys,

 

I have imported the Git Backup extension 2.0.2 into the ThingWorx composer. And created the Git Backup thing made necessary git configurations in the configuration tab. Accessed the GitBackupMainMashup and performed the push operation, i can see that files has been added in the mashup.

But when viewing the git repo, i cannot see any newly pushed files in that git repository.

In the application logs, i got this error org.eclipse.jgit.api.errors.TransportException: https://gitlab: not authorized__ at org.eclipse.jgit.api.PushCommand.call(PushCommand.java:180)__ at gb.GitBackupTemplate.Push(GitBackupTemplate.java:156)

 

I'm not sure whether it's the issue with GitBackupTemplate or am i missing any of the steps.

 

Can someone please help me on this.

 

Thanks in advance.

Best answer by kiran2

@vangne 

 

It's working now. Yes, it's the issue with GIT credentials. Instead of configuring GitLab password in the thingworx Gitthing, i have generated the Access token in my GitLab account and configured this Access token in the GitThing at password field. It got worked after doing this. And now i'm able to push the files into GitLab. But i'm still curious why it didn't worked out with the GitLab password even though it's correct.

 

And one more doubt is that if i add a property or service to that Gitthing, how could we know those changes?Where exactly i can see the newly added property in the mashup that this particular property has been added?

 

Thanks in advance

Kiran.

 

4 replies

V
vangne16-Pearl
16-Pearl
September 24, 2019

@kiran2 

1. What is the Thingworx version you are using?

 

May be caused due to the improper configuration of GIT credentials.

 

Please try below resolution and let us know if this works for you.

Azure DevOps requires separate credentials to authenticate against GIT vs DevOps

  1. Log into Azure DevOps and navigate to your project
  2. Click on the 'Repos' menu to the left
  3. Make sure the correct repository is selected in the breadcrumb at the top of the page
  4. Click the 'Clone' button
  5. In the popup that displays, click the 'Generate GIT Credentials' button
    • User Name should be populated automatically
  6. Enter a password in the password field, and again in the confirm password field
  7. Click the 'Save Credentials' button
  8. Return to ThingWorx and update the GIT Thing's configuration with the new credentials
  9. Click the Pull button to retrieve the files from the repository

Thanks,

Vibhuti

 
K
kiran21-VisitorAuthor
1-Visitor
September 24, 2019

@vangne 

Thank you for the response.

I didn't understand why Azure Devops is required for this issue. I have been using GitLab.

And even before push in Git extension mashup it's checking for the GitLab credentials. So i don't think it's the issue with GitLab credentials.

 

Thanks,

Kiran

 

Terms & ConditionsAccessibility statement