Closed rhawalsh closed 4 months ago
While public testing is running, it occurs to me that perhaps we need to modify the public environment to ensure that the hostname 'jenkins' also resolves to the RSVP host. Otherwise, it's going to try to use 'jenkins' which doesn't otherwise exist until it reaches private testing.
259 tests 258 :heavy_check_mark: 1m 0s :stopwatch: 84 suites 0 :zzz: 2 files 0 :x: 1 :fire:
For more details on these errors, see this check.
Results for commit 0545ad25.
While public testing is running, it occurs to me that perhaps we need to modify the public environment to ensure that the hostname 'jenkins' also resolves to the RSVP host. Otherwise, it's going to try to use 'jenkins' which doesn't otherwise exist until it reaches private testing.
Sounds like that needs to happen before this change goes in?
While public testing is running, it occurs to me that perhaps we need to modify the public environment to ensure that the hostname 'jenkins' also resolves to the RSVP host. Otherwise, it's going to try to use 'jenkins' which doesn't otherwise exist until it reaches private testing.
Sounds like that needs to happen before this change goes in?
Yes. Will need to make the tweaks. The environment gets reimaged tomorrow, so it shouldn't be too long.
To prevent resource starvation while nightly is in process, automated CI testing should use the jenkins resources by default, which are not utilized by nightly.