> On 30 Apr 2017, at 2:49 am, Allen Wittenauer <a...@effectivemachines.com> > wrote: > > >> On Apr 29, 2017, at 9:28 AM, Chris Lambertus <c...@apache.org> wrote: >> >> I’m not able to reproduce this on any browser.. I don’t seem to have any >> broken links either in Opera or Firefox on OSX. Strangely, I do see in the >> page source the reference to https://builds.apache.org:80 but can’t find it >> as an active link on the rendered page anywhere. > > It’s easy to find on this page, since it only runs once a day, only a > few builds are kept, etc. > > https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc > > Click the lock next to job #299. (which, interestingly enough, > randomly disappears if you keep the page open long enough… probably another > bug)
Yes I can see it. Wondering if it has anything to do with the recent upgrade of the job config history plugin. The last plugin upgrade did this:- https://github.com/jenkinsci/jobConfigHistory-plugin/commit/080ac3820a27cc604e2bf6b8e972336470ef10b4 <https://github.com/jenkinsci/jobConfigHistory-plugin/commit/080ac3820a27cc604e2bf6b8e972336470ef10b4> https://issues.jenkins-ci.org/browse/JENKINS-42464 <https://issues.jenkins-ci.org/browse/JENKINS-42464> Now I haven’t dug any further as to the implications of that change. But it is possible this has affected us. Still no idea where it might be picking up port 80 from, we do not specify it in the global config at all. A revert of the plugin will likely tell us if this is what did it. But I’d like to know if someone knows about about the changes made before I schedule downtime for it. Gav…
