So I just pushed to the ORM master branch, which has caused the following
jobs to be queued up:
- hibernate-orm-5.0-h2
- hibernate-orm-5.1-h2
- hibernate-orm-master-h2-main
Only one of those jobs is configured to "watch" master. So why do these
other jobs keep getting triggered?
I see the same exact thing on my personal fork as well. At the same time I
pushed to my fork's 5.3 branch, which triggered the 6.0 job to be queued.
On Tue, Jan 2, 2018 at 1:54 PM Steve Ebersole <steve(a)hibernate.org> wrote:
The legacy ORM jobs (5.1-based ones at least) are getting triggered
when
they should not be. Generally they all show they the run is triggered by a
"SCM change", but it does not show any changes. The underlying problem
(although I am at a loss as to why) is that there has indeed been SCM
changes pushed to Github, but against completely different branches. As
far as I can tell these job's Github setting are correct. Any ideas what
is going on?
This would not be such a big deal if the CI environment did not throttle
all waiting jobs down to one active job. So the jobs I am actually
interested in are forced to wait (sometimes over an hour) for these jobs
that should not even be running.