On Tue, Mar 19, 2019 at 03:08:48PM -0400, Eric S. Raymond wrote: > Matthew Selsky <[email protected]>: > > On Mon, Mar 18, 2019 at 08:13:27PM -0400, Eric S. Raymond via devel wrote: > > > Coverity scan builds are busted for me. Log enclosed. Are the ones > > > triggered by the CI system working? > > > > Yes, the CI triggered coverity builds are working. See > > https://secure-web.cisco.com/1vwrdWkJJ8wOhfp3pdW20_KLCAJj-iCT892_7bjgZyb_1HOyqd4IOUoYSdMt4YeTbyiBk4s2uiJi0RyaefzpvxN5gCgUEyOeY_B4lBZ9KRH7imo2NMA8ivRi_QOpl_7uKFiLTINpHgGWKMVPGh4iaPAhedFcsMmT_aKprder7so4WmUi4ldCBD-rakbT8ZZ_QFuKgexqbrSwhoV5C1B3atW0EtmWCS30NWL2PwpNAsj1wavBi0o8wj83s7pO4Lo3Z15B54zl3GYOju-JucV0KQA/https%3A%2F%2Fgitlab.com%2FNTPsec%2Fntpsec%2Fpipelines%2F52498442 > > Arrgh. Now I need to figure out how the CI enviroment is different from > coverity-submit's. Is the CI enviroment described by a Docker file? > If so, where is it?
No, the CI environment for Coverity runs on one of our VMs. The commands are documented at https://gitlab.com/NTPsec/ntpsec/blob/master/.gitlab-ci.yml#L579 If you can find a docker image that has coverity, I would be happy to switch over to that. I wasn't able to find one that last time I checked docker hub. Thanks, -Matt _______________________________________________ devel mailing list [email protected] http://lists.ntpsec.org/mailman/listinfo/devel
