-
Type:
Task
-
Status: Closed
-
Priority:
Major
-
Resolution: Cannot Reproduce
-
Fix Version/s: None
-
Component/s: Jenkins
-
Labels:None
-
Project:Infrastructure
I just configured the Celix site job to run using the 'git-websites' label. However, it takes a long time (~10 minutes) to get assigned to ci-builds even when it showed as "Available for lease" on jenkins-ccos.
Then after being assigned to ci-builds it first fails to launch. It seems to retry and automagically restore itself.
Would be nice to check:
- Whether there is a setting to lower the treshold of available nodes being assigned to e.g. the ci-builds master (aiming at websites2)
- Check why the error in attached image pops up (seen this 3 times already)
Temporary job used while converting our bash script to a Jenkins pipeline script: https://ci-builds.apache.org/job/Celix/job/test/2/ (echoing 'Hello World' took 11 minutes)
Then after being assigned to ci-builds it first fails to launch. It seems to retry and automagically restore itself.
Would be nice to check:
- Whether there is a setting to lower the treshold of available nodes being assigned to e.g. the ci-builds master (aiming at websites2)
- Check why the error in attached image pops up (seen this 3 times already)
Temporary job used while converting our bash script to a Jenkins pipeline script: https://ci-builds.apache.org/job/Celix/job/test/2/ (echoing 'Hello World' took 11 minutes)
