Continuous Integration checks (travis/gitlab-CI/drone/...) #4322

GiteaMirror commented

@nogweii commented on GitHub (Oct 24, 2019):

We may want to consider an alternative if we want to seriously consider self-hosting this project as well. (See https://github.com/awesome-selfhosted/awesome-selfhosted/issues/89#issuecomment-526728253 and surrounding comments for that conversation.) Though, the best-in-class self-hosted CI is Gitlab's IMO but that's a hefty lift considering it doesn't integrate with anything other than Gitlab.

@nogweii commented on GitHub (Oct 24, 2019): We may want to consider an alternative if we want to seriously consider self-hosting this project as well. (See https://github.com/awesome-selfhosted/awesome-selfhosted/issues/89#issuecomment-526728253 and surrounding comments for that conversation.) Though, the best-in-class self-hosted CI is Gitlab's IMO but that's a hefty lift considering it doesn't integrate with anything other than Gitlab.

GiteaMirror commented

@SuperSandro2000 commented on GitHub (Oct 24, 2019):

Drone + Gitea?

@SuperSandro2000 commented on GitHub (Oct 24, 2019): Drone + Gitea?

GiteaMirror commented

@nodiscc commented on GitHub (Oct 25, 2019):

stick with Travis

We already have a travis config so it makes sense to go with this for the time being. I will set it up this weekend.

move to github actions

Tying our work with proprietary, non self-hostable software even more is not the way to go IMHO. I understand it's convenient.

best-in-class self-hosted CI is Gitlab's IMO but that's a hefty lift considering it doesn't integrate with anything other than Gitlab

True. I have been using it for some time (both SaaS and self-hosted) and it works great and is slowly becoming industry standard. I will set it up for our current mirror and the repo can contain both .travis.yml and .gitlab-ci.yml without problems. We'll see if it's possible to integrate with our Github repo somehow.

Drone + Gitea?

I have a personal Gitea instance but did not have time to set up drone yet. @SuperSandro2000 if you have a (public) drone instance we can interact with this would be a great addition, and it gives us another option.

Any suggestions are welcome.

@nodiscc commented on GitHub (Oct 25, 2019): > stick with Travis We already have a travis config so it makes sense to go with this for the time being. I will set it up this weekend. > move to github actions Tying our work with proprietary, non self-hostable software even more is not the way to go IMHO. I understand it's convenient. > best-in-class self-hosted CI is Gitlab's IMO but that's a hefty lift considering it doesn't integrate with anything other than Gitlab True. I have been using it for some time (both SaaS and self-hosted) and it works great and is slowly becoming industry standard. I will set it up for our current [mirror](https://gitlab.com/awesome-selfhosted/awesome-selfhosted) and the repo can contain both `.travis.yml` and `.gitlab-ci.yml` without problems. We'll see if it's possible to integrate with our Github repo somehow. > Drone + Gitea? I have a personal Gitea instance but did not have time to set up drone yet. @SuperSandro2000 if you have a (public) drone instance we can interact with this would be a great addition, and it gives us another option. Any suggestions are welcome.

GiteaMirror commented

@SuperSandro2000 commented on GitHub (Oct 25, 2019):

I have a personal Gitea instance but did not have time to set up drone yet. @SuperSandro2000 if you have a (public) drone instance we can interact with this would be a great addition, and it gives us another option.

no, it was on my todo to try out later but I didn't get to it yet and wouldn#t count on it. Way to much other stuff to do currently.

@SuperSandro2000 commented on GitHub (Oct 25, 2019): > I have a personal Gitea instance but did not have time to set up drone yet. @SuperSandro2000 if you have a (public) drone instance we can interact with this would be a great addition, and it gives us another option. no, it was on my todo to try out later but I didn't get to it yet and wouldn#t count on it. Way to much other stuff to do currently.

GiteaMirror commented

@nodiscc commented on GitHub (Oct 27, 2019):

I have restored Travis checks as they were before, and updated all URLs to reflect the change of ownership (2c6e7ab9d2). (also edited issues that contained the old URL)

Let's keep this issue open to keep track of work on other CI systems.

@nodiscc commented on GitHub (Oct 27, 2019): I have restored Travis checks as they were before, and updated all URLs to reflect the change of ownership (https://github.com/awesome-selfhosted/awesome-selfhosted/commit/2c6e7ab9d2b6c4b44a6bb8f6b2a6a4371950a1c0). (also edited issues that contained the old URL) Let's keep this issue open to keep track of work on other CI systems.

GiteaMirror commented

@SuperSandro2000 commented on GitHub (Oct 27, 2019):

You could have made some of those links relative.

@SuperSandro2000 commented on GitHub (Oct 27, 2019): You could have made some of those links relative.

GiteaMirror commented

From https://github.com/awesome-selfhosted/awesome-selfhosted/issues/2266#issuecomment-751400333:

@nodiscc commented on GitHub (Dec 26, 2020):

We also need to change our CI provider (travis CI) who will soon start enforcing severe job time limits for free projects (let's move that topic to #1852). Similar problem mentioned at shaarli/Shaarli#1649 in which we evaluated other CI systems (Gitlab CI, Drone, GH actions...). Not an excuse for not optimizing our checks runtime/bandwidth consumption :)

@nodiscc commented on GitHub (Dec 26, 2020): From https://github.com/awesome-selfhosted/awesome-selfhosted/issues/2266#issuecomment-751400333: > We also need to change our CI provider (travis CI) who will soon start enforcing severe job time limits for free projects (let's move that topic to #1852). Similar problem mentioned at shaarli/Shaarli#1649 in which we evaluated other CI systems (Gitlab CI, Drone, GH actions...). Not an excuse for not optimizing our checks runtime/bandwidth consumption :)

GiteaMirror commented

https://travis-ci.org/github/awesome-selfhosted/awesome-selfhosted/builds

@nodiscc commented on GitHub (Jun 15, 2021):

Since June 15th, 2021, the building on travis-ci.org is ceased. Please use travis-ci.com from now on.

@nodiscc commented on GitHub (Jun 15, 2021): https://travis-ci.org/github/awesome-selfhosted/awesome-selfhosted/builds > Since June 15th, 2021, the building on travis-ci.org is ceased. Please use travis-ci.com from now on.

GiteaMirror commented

-> https://github.com/awesome-selfhosted/awesome-selfhosted/issues?q=is%3Aissue+is%3Aopen+label%3Atools

@nodiscc commented on GitHub (Jun 15, 2021):

I will be moving awesome-selfhosted's CI pipeline to Github Actions soon (it is not self-hosted but Travis was not either). The only satisfying FOSS CI service I have worked so far is Gitlab CI (I have been running into instablilities with Drone, have not tried many others, check https://github.com/ligurio/awesome-ci). We can setup Gitlab<->Github<->other integrations later if needed, but for now let's just move to GH Actions and cleanup/improve the tooling a bit.

@nodiscc commented on GitHub (Jun 15, 2021): I will be moving awesome-selfhosted's CI pipeline to [Github Actions](https://github.com/awesome-selfhosted/awesome-selfhosted/actions/) soon (it is not self-hosted but Travis was not either). The only satisfying FOSS CI service I have worked so far is Gitlab CI (I have been running into instablilities with Drone, have not tried many others, check https://github.com/ligurio/awesome-ci). We can setup Gitlab<->Github<->other integrations later if needed, but for now let's just move to GH Actions and cleanup/improve the tooling a bit. -> https://github.com/awesome-selfhosted/awesome-selfhosted/issues?q=is%3Aissue+is%3Aopen+label%3Atools

GiteaMirror commented

@n8225 commented on GitHub (Jun 16, 2021):

I've got a little free time today I'll see if I can get started on this.

@n8225 commented on GitHub (Jun 16, 2021): I've got a little free time today I'll see if I can get started on this.

GiteaMirror commented

@nodiscc commented on GitHub (Sep 2, 2021):

https://github.com/nodiscc/hecat will handle URL checks, and enrich the list with automatically gathered data, as part of https://github.com/awesome-selfhosted/awesome-selfhosted/issues/1038.

Our CI pipeline should run on GH actions and rely on hecat and https://github.com/awesome-selfhosted/awesome-selfhosted-data as much as possible. In fact there is no point in having a CI pipeline on https://github.com/awesome-selfhosted/awesome-selfhosted itself since this will just be an automatically generated file/repository.

@nodiscc commented on GitHub (Sep 2, 2021): https://github.com/nodiscc/hecat will handle URL checks, and enrich the list with automatically gathered data, as part of https://github.com/awesome-selfhosted/awesome-selfhosted/issues/1038. Our CI pipeline should run on GH actions and rely on `hecat` and https://github.com/awesome-selfhosted/awesome-selfhosted-data as much as possible. In fact there is no point in having a CI pipeline on https://github.com/awesome-selfhosted/awesome-selfhosted itself since this will just be an automatically generated file/repository.

GiteaMirror commented