Creation of external feed with Gitlab is failing

Integration
, ,
1

We are trying to integrate with Gitlab. Using the steps mentioned in the below blog.

we are running on below versions:

Octopus Deploy version: V2022.3
Gitlab Version: 15.3

We have followed all the steps and mentioned in the document. We have our own maven Package registry within Gitlab and providing the correct configuration parameters within the Octopus external feed configuration of the same. However, we are getting an error while testing the external feed. The screenshot of the error is attached herewith.
Can anyone please help with the same?

octopus issues
octopus issues1408×207 161 KB

3

Hi @manjunatha.karekal,

Thanks for reaching out.

I’m able to reproduce the error if I have a typo in my test for the group:artifact. Can you please copy paste the string you’re searching in the feed as well as a screenshot of the artifact in the repo please? if there is information you can’t share, please feel free to DM me the screenshots/string.

Best,
Jeremy

4

@jeremy.miller Thanks Jeremy for the response.

Attached is the string which I am trying to search. Encircled in “Red”

octopus-issues-2
octopus-issues-21486×648 130 KB

5

Hi @manjunatha.karekal,

Thank you for that.

Can you also please send me a screenshot of the package inside of the maven feed so I can see that?

Best,

6

Hi Jeremy,
attached is the screenshot of the maven package

octopus-issues-3
octopus-issues-31516×749 167 KB

7

Hey @manjunatha.karekal,

Thanks for the screenshot. The setup looks correct to me, but I don’t have much experience with gitlab so I’m going to reach out to my colleague who does and get back to you asap.

Best,
Jeremy

8

Thanks Jeremy,
This is really important integration for us to be able to proceed further.

9

Hi @manjunatha.karekal,

I spoke with my colleague and he said it also looks okay to him.

Is the project set to public? Have you confirmed the credentials are correct in the Octopus setup portion?

Best,
Jeremy

10

Hi Jeremy,
The project is set as Private and not public. Do we need to set the project as public?

The credentials are correct.

11

Hi,

My colleague’s is set to public but if you can’t test that we can try to tinker on our side by making ours private and see if we get the same issues.

Please let me know what you think.

Best,
Jeremy

12

Hi,
Yes, that’s a good idea. Can you pls try and let me know how it goes.

13

Hi,

We’ve set it to private and have the same issue. We’re going to do some testing and see if we can figure out what’s causing it.

Please feel free to reach out in the meantime.

Best,
Jeremy

14

Hi Jeremy,
Thanks. I made the project public and its working. However, we need to understand how can we integrate this with the private project.

15

Hi,

That’s awesome news. I definitely understand that need and we’re going to dig in and figure out what’s going on for you.

Best,
Jeremy

16

Hi @manjunatha.karekal,

We had some discussions and did some investigation last night and we think there will need to be some code changes to get this to work with private projects so we’ve opened an issue you can follow here: Gitlab Maven feeds do not work if the project is set to private · Issue #7810 · OctopusDeploy/Issues · GitHub

While that is being implemented I believe the only workaround will be to have a public project.

I’m sorry I don’t have better news for you but please let me know if there are any other questions or concerns.

Best,
Jeremy

17

@jeremy.miller
Ok, I will follow up on this . Thanks for your support on this issue.

1 Like
18

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.