Issue #6668: taiga.fedorainfracloud.org and gitlab module failure - fedora-infrastructure

When trying to integrate taiga with gitlab, in the URI presented to copy to gitlab, the hostname shown is 'localhost'.

Workflow according to
https://tree.taiga.io/support/integrations/gitlab-integration/

Go to Admin > Integrations > GitLab
Fill secret key or use the auto generated one
Copy the payload URL input

It should be a hostname that a gitlab instance is able to connect.

Replacing localhost with taiga.fedoraincloud.org is not sufficient as the API port 8000 doesn't answer.

Edited Feb 2, 2018 by nmav

We don't actually officially support this instance... instead it's handled by @ralph and @kellin

Perhaps they have some ideas here?

What does officially support mean? Is there a web page describing what is supported and for how long?

Well, we are working on formalizing that in https://fedoraproject.org/wiki/Infrastructure/ServiceLevelExpectations

This service is a community run one, and support is subject to whatever the people running it are willing to provide.

Well, we are working on formalizing that in https://fedoraproject.org/wiki/Infrastructure/ServiceLevelExpectations

This service is a community run one, and support is subject to whatever the people running it are willing to provide.

Metadata Update from @kevin:
- Issue assigned to kellin
- Issue priority set to: Waiting on Asignee

Apr 20, 2018

It's been 6 months without reply form instance owner - @kellin. Since this is not an infra issue, can we close this as wontfix?

It makes sense to me as I've given up on it already. I have no permissions to close it.

As said earlier, there is nothing for Fedora Infrastructure to fix here, so I'm closing this issue.

Metadata Update from @mizdebsk:
- Issue close_status updated to: Will Not/Can Not fix
- Issue status updated to: Closed (was: Open)

Aug 20, 2018

Assignee

kellin

Tags

None

Blocking

None

Depending on

None

Priority

Normal