CI for labs-ci-cd is broken
pcarney8 opened this issue · comments
it looks like pact-broker needs Bundler 2 for it's build
Cloning "https://github.com/DiUS/pact_broker-docker.git " ...
Commit: 5e0c16c7c0ee0b8612c035a62030f4efd82f9797 (feat(gems): update pact_broker gem to version 2.35.0)
Author: Beth Skurrie <beth@bethesque.com>
Date: Fri Aug 9 09:14:23 2019 +1000
Using docker-registry.default.svc:5000/openshift/ruby@sha256:3f0a0dd6ccf6d6749cf274e8e55d96789818db3cd72f6a1a4ccfc0e86e9fa867 as the s2i builder image
---> Installing application source ...
---> Building your Ruby application from source ...
---> Running 'bundle install --retry 2 --deployment --without development:test' ...
You must use Bundler 2 or greater with this lockfile.
error: build error: non-zero (13) exit code from docker-registry.default.svc:5000/openshift/ruby@sha256:3f0a0dd6ccf6d6749cf274e8e55d96789818db3cd72f6a1a4ccfc0e86e9fa867
AND
sonarqube deployment is failing because it's taking too long?
--> Scaling sonarqube-1 to 1
--
| error: update acceptor rejected sonarqube-1: pods for rc 'labs-ci-cd-pr-285/sonarqube-1' took longer than 600 seconds to become available
I have some updates to pact deployment to use secrets for auth and such but also not have to build it from source. Their upsteam project has now got a non-root container so we can just pull it.
@springdo Sweet, I think I saw those docs on the dockerhub image they have out there, but either way, it appears to deploy correctly with the new repo. Going to run ci-for-ci to test that things are working again, and then feel free to migrate over to that