CI remains broken #572

New Issue

noerw · 2022-03-10T16:06:14Z

noerw commented

2022-03-10 16:06:14 +00:00

Even with #569 CI is broken with the error:

Could not resolve host: gitea

I have no idea what's causing this, any drone wizards can chime in? @techknowlogick

Even with #569 CI is broken with the error: `Could not resolve host: gitea` I have no idea what's causing this, any drone wizards can chime in? @techknowlogick

noerw added the

kind/build

label 2022-03-10 16:06:14 +00:00

noerw referenced this issue

2022-03-28 10:37:01 +00:00

add mirror_updated field to Repository struct #565

noerw commented

2022-03-28 10:37:43 +00:00

@gitea/Owners any chance someone finds the time to resolve this?
Or pointers how I can reproduce this locally, then I could try to fix it myself..

@gitea/Owners any chance someone finds the time to resolve this? Or pointers how I can reproduce this locally, then I could try to fix it myself..

petergardfjall referenced this issue

2022-03-28 11:00:55 +00:00

add mirror_updated field to Repository struct #565

lunny self-assigned this 2022-03-28 13:03:55 +00:00

lunny referenced a pull request that will close this issue

2022-03-28 13:33:16 +00:00

Use goproxy.io instead of goproxy.cn #574

zeripath closed this issue

2022-03-28 23:09:58 +00:00

zeripath referenced this issue from a commit

2022-03-28 23:09:58 +00:00

Use goproxy.io instead of goproxy.cn (#574)

zeripath commented

2022-03-28 23:13:21 +00:00

I think there's still the broken test that needs to be sorted too.

Sign in to join this conversation.

No Milestone

No Assignees

2 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: gitea/go-sdk#572