Eventually, we want to write unit tests for our API that interact with GitLab and eventually more involved integration tests that run parts of the main arena buisness logic.
We need to be able to communicate with GitLab without human interaction. This NEEDS to be investigated early so we can decide if we stick with this or move to another solution
Currently the easiest way to interact is to create a personal access token and pass it like
GET gitlab.example.com/api/v3/users?private_token=asblksajdfoi32894790
The issue here is to create this access token, you must first navigate to GitLab's web interface and manually configure it
russleyshaw
commented
7 years ago
Eventually, we want to write unit tests for our API that interact with GitLab and eventually more involved integration tests that run parts of the main arena buisness logic.
We need to be able to communicate with GitLab without human interaction. This NEEDS to be investigated early so we can decide if we stick with this or move to another solution
Currently the easiest way to interact is to create a personal access token and pass it like
GET gitlab.example.com/api/v3/users?private_token=asblksajdfoi32894790The issue here is to create this access token, you must first navigate to GitLab's web interface and manually configure it