- 05 Jul, 2017 15 commits
-
-
Shinya Maeda authored
-
Shinya Maeda authored
This reverts commit 8f0a2b6d.
-
Lin Jen-Shin authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
- 05 Jun, 2017 1 commit
-
-
Lin Jen-Shin authored
So that we could use it for the schedule before trying to use CreatePipelineService
-
- 30 May, 2017 4 commits
-
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
- 29 May, 2017 1 commit
-
-
Shinya Maeda authored
-
- 15 May, 2017 1 commit
-
-
Z.J. van de Weg authored
When the owner of a pipelines schedule was either blocked or was removed from the project, the pipeline schedular would still schedule the pipeline. This would than fail however, given the user had no access to the project and it contents. However, a better way to handle it would be to not schedule it at all. Furthermore, from now on, such schedules will be deactivated so the schedule worker can ignore it on the next runs.
-
- 07 May, 2017 1 commit
-
-
Zeger-Jan van de Weg authored
-
- 07 Apr, 2017 6 commits
-
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
- 06 Apr, 2017 11 commits
-
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-