I removed the doc exclusion for Git polling on the geoserver-master Jenkins job. Something appears to be horribly wrong with it. The symptoms are that polling *always* detects changes, so there is always a geoserver-master in the queue. Hopefully this will stop the flood of unnecessary builds.
Kind regards,
--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/>
New Zealand
I removed the doc exclusion for Git polling on the geoserver-master
Jenkins job. Something appears to be horribly wrong with it. The
symptoms are that polling *always* detects changes, so there is always a
geoserver-master in the queue. Hopefully this will stop the flood of
unnecessary builds.
Kind regards,
--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/>
New Zealand
I have removed the doc and geogig Git polling exclusions on geoserver-master Jenkins. As discussed last year (see below), Git polling exclusions are broken: they cause continual retriggering of the geoserver-master build, waste resources, and delay other builds. Please do not add Git polling exclusions on any Jenkins build.
I removed the doc exclusion for Git polling on the geoserver-master Jenkins job. Something appears to be horribly wrong with it. The symptoms are that polling *always* detects changes, so there is always a geoserver-master in the queue. Hopefully this will stop the flood of unnecessary builds.
Kind regards,
--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/>
New Zealand
Thanks for the info, I wasn’t aware of the issues.
It seems the exclusions are still in place for the other builds (2.11.x, 2.10.x and 2.9.x). I can remove them on those builds too, unless it is desired to keep them.
···
On Sun, Apr 9, 2017 at 7:56 PM, Ben Caradoc-Davies <ben@anonymised.com> wrote:
I have removed the doc and geogig Git polling exclusions on geoserver-master Jenkins. As discussed last year (see below), Git polling exclusions are broken: they cause continual retriggering of the geoserver-master build, waste resources, and delay other builds. Please do not add Git polling exclusions on any Jenkins build.
I removed the doc exclusion for Git polling on the geoserver-master Jenkins job. Something appears to be horribly wrong with it. The symptoms are that polling always detects changes, so there is always a geoserver-master in the queue. Hopefully this will stop the flood of unnecessary builds.
Is this something fixed with newer versions of Jenkins?
···
On 9 April 2017 at 17:56, Ben Caradoc-Davies <ben@anonymised.com> wrote:
I have removed the doc and geogig Git polling exclusions on geoserver-master Jenkins. As discussed last year (see below), Git polling exclusions are broken: they cause continual retriggering of the geoserver-master build, waste resources, and delay other builds. Please do not add Git polling exclusions on any Jenkins build.
I removed the doc exclusion for Git polling on the geoserver-master Jenkins job. Something appears to be horribly wrong with it. The symptoms are that polling always detects changes, so there is always a geoserver-master in the queue. Hopefully this will stop the flood of unnecessary builds.
thanks for pointing that out. I have removed the exclusions for 2.11.x and 2.10.x, even though they have not yet caused trouble. This gives us consistency between the builds.
Also, I see no reason to exclude docs and geogig as developers may be building them locally. Leaving them included will allow Jenkins to detect breakage.
Kind regards,
Ben.
On 11/04/17 03:38, Erik Merkle wrote:
Ben,
Thanks for the info, I wasn't aware of the issues.
It seems the exclusions are still in place for the other builds (2.11.x,
2.10.x and 2.9.x). I can remove them on those builds too, unless it is
desired to keep them.
On Sun, Apr 9, 2017 at 7:56 PM, Ben Caradoc-Davies <ben@anonymised.com> wrote:
I have removed the doc and geogig Git polling exclusions on
geoserver-master Jenkins. As discussed last year (see below), Git polling
exclusions are broken: they cause continual retriggering of the
geoserver-master build, waste resources, and delay other builds. Please do
not add Git polling exclusions on any Jenkins build.
I removed the doc exclusion for Git polling on the geoserver-master
Jenkins job. Something appears to be horribly wrong with it. The symptoms
are that polling *always* detects changes, so there is always a
geoserver-master in the queue. Hopefully this will stop the flood of
unnecessary builds.
Kind regards,
--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/>
New Zealand
--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/>
New Zealand
Unknown. I have not found a bug report that matches our situation. As I mentioned in my previous email, I do not see why we are excluding commits to docs and geogig in the first place. Shall we just leave them in?
Kind regards,
Ben.
On 11/04/17 08:53, Jody Garnett wrote:
Is this something fixed with newer versions of Jenkins?
--
Jody Garnett
On 9 April 2017 at 17:56, Ben Caradoc-Davies <ben@anonymised.com> wrote:
I have removed the doc and geogig Git polling exclusions on
geoserver-master Jenkins. As discussed last year (see below), Git polling
exclusions are broken: they cause continual retriggering of the
geoserver-master build, waste resources, and delay other builds. Please do
not add Git polling exclusions on any Jenkins build.
I removed the doc exclusion for Git polling on the geoserver-master
Jenkins job. Something appears to be horribly wrong with it. The symptoms
are that polling *always* detects changes, so there is always a
geoserver-master in the queue. Hopefully this will stop the flood of
unnecessary builds.
Kind regards,
--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/>
New Zealand
--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/>
New Zealand
For docs at least, there was an effort to separate the doc build and the code build so if a doc change was made we would only build the docs, and if a code change was made we would only build the code. Consequently, the docs are excluded from the polling for the main builds.
See the *-live-docs builds for the doc portion of this.