[MXS-888] unexpected "started by SCM change" Jenkins job executions Created: 2016-10-12 Updated: 2016-11-14 Resolved: 2016-11-14 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | test |
| Affects Version/s: | None |
| Fix Version/s: | 2.1.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | Timofey Turenko | Assignee: | Timofey Turenko |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Description |
|
Example http://max-tst-01.mariadb.com:8089/view/env/job/create_env/194/console probably cause: Jenikins bug in processing of SCM changes when 'branches" set to '*' or to any non-existing branch |
| Comments |
| Comment by Timofey Turenko [ 2016-11-14 ] |
|
fixed by FRUCT by moving from GitHub hooks to SCM pooloing + adding default branch to all Jenkins jobs |