Commit 0349a02
committed
Timer triggered pipelines are not scheduled on a standby server
* This commit fixes an issue with
#5220 which expected the server to be
active before scheduling the timer triggered pipelines. With BC addon
remains active on startup and on TimerSchduler initialization and
later turns inactive on load of the BC jar.
* Turning of scheduling timer triggered pipelines for standby server by relying
on the SystemEnvironment 'go.server.mode'.1 parent 6d7320c commit 0349a02
File tree
4 files changed
+19
-3
lines changed- base/src/main/java/com/thoughtworks/go/util
- common/src/test/java/com/thoughtworks/go/util
- server/src
- main/java/com/thoughtworks/go/server/service
- test-fast/java/com/thoughtworks/go/server/service
4 files changed
+19
-3
lines changedLines changed: 4 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
857 | 857 | | |
858 | 858 | | |
859 | 859 | | |
| 860 | + | |
| 861 | + | |
| 862 | + | |
| 863 | + | |
860 | 864 | | |
861 | 865 | | |
862 | 866 | | |
| |||
Lines changed: 9 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
522 | 522 | | |
523 | 523 | | |
524 | 524 | | |
| 525 | + | |
| 526 | + | |
| 527 | + | |
| 528 | + | |
| 529 | + | |
| 530 | + | |
| 531 | + | |
| 532 | + | |
| 533 | + | |
525 | 534 | | |
Lines changed: 4 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
74 | 74 | | |
75 | 75 | | |
76 | 76 | | |
77 | | - | |
| 77 | + | |
| 78 | + | |
| 79 | + | |
| 80 | + | |
78 | 81 | | |
79 | 82 | | |
80 | 83 | | |
| |||
Lines changed: 2 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
188 | 188 | | |
189 | 189 | | |
190 | 190 | | |
191 | | - | |
| 191 | + | |
192 | 192 | | |
193 | 193 | | |
194 | | - | |
| 194 | + | |
195 | 195 | | |
196 | 196 | | |
197 | 197 | | |
| |||
0 commit comments