Contributor
Contributor

vRLCM 1.2 not passing GitLab access token on check-in

When capturing new content with "check-in" enabled, I get an error on the Content Pipeline

Error: Service https://gitlabs.xxx.yyy/api/v4/projects/133/repository/tree?ref=master&recursive=true&page=1 returned error 404 for GET. id 260813240 message 404 Tree Not Found]

I have verified the access token configured in vRLCM is correct and working by using a browser and going to https://gitlabs.xxx.yyy/api/v4/projects/133?private_token=gJ9oxcaKuFujpxn2CNdz 

From the error above it doesn't look like vRLCM is passing the access token when trying to access GitLab.

Ideas?

Tags (3)
0 Kudos
1 Reply
Contributor
Contributor

I ended up opening a SR on this, got the answer from Jay...

This is typical of one of two things...

  1. There is no master branch present in GitLab for the project.

  2. The access token is wrong or otherwise invalid.

My issue was #1. While I created the group and project, I did not touch it with git, so no master branch to start off with. A quick "readme.md" file and wham master branch created and content capture is working.

0 Kudos