Closed InfoSec812 closed 6 years ago
@InfoSec812 running this build in OCP 3.7 on S7 I get the attached failure. I think we need update the build config, which overrides your based image to use sonarqube:latest
, which is debian based.
For some reason it is starting from the wrong base image, though I don't understand why. Did you update and existing deployment in-place? If so, I think you would have to modify the deployment beyond the defaults to change the source ImageStream (a problem I had when testing).
Deven
On Mon, Jan 15, 2018 at 11:43 PM, Justin Holmes notifications@github.com wrote:
@InfoSec812 https://github.com/infosec812 running this build in OCP 3.7 on S7 I get the attached failure
sonarqube-2.log https://github.com/rht-labs/labs-ci-cd/files/1633647/sonarqube-2.log
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/rht-labs/labs-ci-cd/pull/85#issuecomment-357852438, or mute the thread https://github.com/notifications/unsubscribe-auth/AAGFazgTsAe8K980fVvxep_l24rRnUH1ks5tLCkHgaJpZM4Re7zO .
--
Deven Phillips
Senior Consulting ENgineer, RED HAT OPEN INNOVATION LABS
Red Hat
deven.phillips@redhat.com https://red.ht/sig
@InfoSec812 I believe your last commits change this build to the nexus base image, not the sonarqube base image. This changes should be reverted.
CI fails rerunning sonarqube build. See attached. New CI job merges the PR into master and then applies that fresh. There is no manual modification of the deployed objects. sonarqube-1 (1).log
Resolves #84