Error: server error: 404 Not Found

[sdebruyn]

I always get the following error message:

| (2) gitlab-status                                                            |
+------------------------------------------------------------------------------+
| id: gitlab-status                                                            |
| version: 0.10.0                                                              |
| collection: https://github.com/bitrise-io/bitrise-steplib.git                |
| toolkit: go                                                                  |
| time: 2019-12-02T14:23:27Z                                                   |
+------------------------------------------------------------------------------+
|                                                                              |
Config:
- PrivateToken: [REDACTED]
- RepositoryURL: ssh://git@gitlab.redacted.be:12345/redacted/redacted.git
- CommitHash: 6c59d3896d5b1f68250dce1e294ed50b0422735e
- APIURL: https://gitlab.redacted.be/api/v4
- Status: auto
- TargetURL: https://app.bitrise.io/build/redacted
- Context: Bitrise
- Description: 
- Coverage: 0
Error: server error: 404 Not Found

The API works (when I go to https://gitlab.redacted.be/api/v4/projects in my browser). The documentation mentions that you need a project ID instead of the repository URL, so why is this step using the repository URL?

[bitce]

Hey @SamuelDebruyn, can you please initially include a build URL that would allow us to check out the details of said build along your report? 🙂

[sdebruyn]

Hi @bitce this app has a lot of attempts to get it working with Gitlab: https://app.bitrise.io/app/c85987f824d78d30#/builds

[bitce]

Thanks, @sdebruyn! Can you perhaps direct us to an older attempt with our actual as the latest builds seem to be using your own forked version of the step 🤔

[bitrise-coresteps-bot]

Hello there, I'm a bot. On behalf of the community I thank you for opening this issue.

To help our human contributors focus on the most relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 90 days, so I marked it as stale.

The community would appreciate if you could check if the issue still persists. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me".

If no comment left within 21 days, this issue will be closed.

[bitrise-coresteps-bot]

I'll close this issue as it doesn't seem to be relevant anymore. We believe an old issue probably has a bunch of context that's no longer relevant, therefore, if the problem still persists, please open a new issue.