Hi, when I pushed a new branch to my fork of the JLDAP repo, this triggered the Auto DevOps CI/CD pipeline. Is that supposed to work on git.openldap.org?
From the error messages it seems to me, that it cannot resolve the host "docker":
error during connect: Post http://docker:2375/v1.40/auth: dial tcp: lookup docker on 173.255.199.5:53: no such host
error during connect: Post http://docker:2375/v1.40/images/create?fromImage=registry.gitlab.com%2Fgitla...: dial tcp: lookup docker on 173.255.199.5:53: no such host
Regards Norbert
-------- Forwarded Message -------- Subject: JLDAP | Pipeline #1219 has failed for maven | 6795ebdf Date: Fri, 30 Oct 2020 08:02:31 +0000 From: GitLab gitlab@git.openldap.org Reply-To: GitLab noreply@git.openldap.org
JLDAP | Pipeline #1219 has failed for maven | 6795ebdf GitLab โ Your pipeline has failed.
Project Norbert Klasen https://git.openldap.org/klasen / JLDAP https://git.openldap.org/klasen/jldap Branch maven https://git.openldap.org/klasen/jldap/-/commits/maven
Commit 6795ebdf https://git.openldap.org/klasen/jldap/-/commit/6795ebdf4f091ff4135cb5a671b97e554300e21f
Delete .gitlab-ci.yml. Re-enable Auto DevOps pi... Commit Author Norbert Klasen https://git.openldap.org/klasen
Pipeline #1219 https://git.openldap.org/klasen/jldap/-/pipelines/1219 triggered by Norbert Klasen https://git.openldap.org/klasen
had 2 failed builds. Failed builds โ test
code_quality https://git.openldap.org/klasen/jldap/-/jobs/2594 โ build
build https://git.openldap.org/klasen/jldap/-/jobs/2592
GitLab You're receiving this email because of your account on git.openldap.org. Manage all notifications https://git.openldap.org/profile/notifications ยท Help https://git.openldap.org/help
--On Friday, October 30, 2020 10:17 AM +0100 Norbert Klasen klasen@gmx.net wrote:
Hi, when I pushed a new branch to my fork of the JLDAP repo, this triggered the Auto DevOps CI/CD pipeline. Is that supposed to work on git.openldap.org?
From the error messages it seems to me, that it cannot resolve the host "docker":
error during connect: Post http://docker:2375/v1.40/auth: dial tcp: lookup docker on 173.255.199.5:53: no such host
error during connect: Post http://docker:2375/v1.40/images/create?fromImage=registry.gitlab.com%2Fgi tlab-org%2Fci-cd%2Fcodequality&tag=0.85.10-gitlab.1: dial tcp: lookup docker on 173.255.199.5:53: no such host
Hi Norbert,
I've disabled CI/CD for the repo.
Regards, Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
--On Friday, October 30, 2020 9:32 AM -0700 Quanah Gibson-Mount quanah@symas.com wrote:
Hi Norbert,
I've disabled CI/CD for the repo.
Or, to be clear, for the main JLDAP repo. You'll likely need to disable it for your own fork. Gitlab defaults to automatically enabling CI/CD and will run jobs even if no configuration is found.
--Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com