Bug #2742
allow easy rebuild of orchestration job
| Status: | Closed | Start date: | 10/11/2017 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | J. Moringen | % Done: | 0% | |
| Category: | Deployment | |||
| Target version: | - |
Description
Hi Jan,
we often face the issue, that an orchestration job (for toolkit deployment) doesn't complete successfully in the first run. However re-running it, recompiles all projects (also the just successfully built ones), which usually takes hours. If there is another failure, this is really time-consuming.
I modified the orchestration job such, that only failed or not recently build jobs are triggered. The meaning of recently is currently hard-coded in the beginning of the groovy script. One may want to transform that into a parameter...
diff.patch 
- patch to groovy script for toolkit orchestration
(2.16 KB)
new - full groovy script for our toolkit orchestration (28.8 KB)
History
#1 Updated by J. Moringen almost 7 years ago
- Status changed from New to In Progress
#2 Updated by J. Moringen almost 7 years ago
- Status changed from In Progress to Closed
I made template changes to this end. No generator changes needed.
#3 Updated by R. Haschke almost 7 years ago
- Tracker changed from Feature to Bug
- Status changed from Closed to In Progress
Using the new functionality, I get the following error, both with build-generator version 0.16 and 0.17:
DEPLOYMENT-ERROR:
Error during deployment of #<PROJECT orchestration {1005C9E953}> » #<VERSION orchestration:orchestration {1005C9EC33}> » #<JOB orchestration:orchestration:orchestration {1005DD2803}> Caused by:
> There is no applicable method for the generic function #<STANDARD-GENERIC-FUNCTION JENKINS.MODEL:IMPLEMENTATION (1)>when called with arguments (NIL).Any idea, where this comes from? I guess on your side it works...
#4 Updated by J. Moringen almost 7 years ago
Any idea, where this comes from? I guess on your side it works...
I can try to reproduce the issue. Is this lsp-famula-nightly in the lsp-famula branch?
#5 Updated by R. Haschke almost 7 years ago
I'm in the middle of merging. I pushed now my intermediate state exhibiting this error to branch wip-lsp-famula-merge. Please apply any fixes there ;-)
And yes, I'm considering lsp-famula-nightly.distribution.
Please note that my template unification work (branch wip-unify-templates from May) was not yet merged into master. Are you still interested in this work as we discussed that time?
#6 Updated by J. Moringen almost 7 years ago
- Status changed from In Progress to Closed
I'm in the middle of merging. I pushed now my intermediate state exhibiting this error to branch wip-lsp-famula-merge. Please apply any fixes there ;-)
Done. The error was caused by an unrelated template change that started to affect the lsp-famula branch because of the merge.
Please note that my template unification work (branch wip-unify-templates from May) was not yet merged into master. Are you still interested in this work as we discussed that time?
I think this is still relevant. I will have another look at the branch.
#7 Updated by R. Haschke almost 7 years ago
Thanks!