search

juju-solutions / bundle-cwr-ci

Deploy the Juju Charm CI system
Other
2 stars 6 forks source link

The bundle-build job never runs #11

Open mbruzek opened 7 years ago

mbruzek commented 7 years ago

I ran the bundle-build action on cwr-ci and I see the job created in jenkins. The job looks to be scheduled to run every 10 minutes but does not ever seem to run.

$ juju run-action cwr/0 build-bundle repo=http://github.com/juju-solutions/bundle-kubernetes-e2e bundle-name=kubernetes-e2e
Action queued with id: 2d798c50-0487-419b-8e0a-15f2e6ec6a21
$ juju show-action-output --wait 0 2d798c50-0487-419b-8e0a-15f2e6ec6a21                              
status: completed
timing:
  completed: 2017-02-14 22:20:59 +0000 UTC
  enqueued: 2017-02-14 22:20:57 +0000 UTC
  started: 2017-02-14 22:20:58 +0000 UTC

I watched the jenkins job for the first 10 minute increment and it passed without attempting to run the job. Here is the relevant information from the Schedule section of the build-bundle-kuberentes-e2e job.

Would last have run at Tuesday, February 14, 2017 10:40:28 PM UTC; would next run at Tuesday, February 14, 2017 10:50:28 PM UTC.

ktsakalozos commented 7 years ago

Your build-bundle-kuberentes-e2e jenkins job should include a ScriptTrigger entry under Build Triggers. There you will see we do a check for updates on the bundle via:

 python3 -u /var/lib/juju/agents/unit-cwr6-0/charm/scripts/bundlebuilder.py check http://github.com/juju-solutions/bundle-kubernetes-e2e master

If the above script returns 0 we proceed with grabbing the bundle, updating and testing it.

To see if the ScriptTrigger actually checked for updates you should be looking in the ScriptTrigger logs eg https://ibin.co/3CSWNrsS0Tnf.png

Can you please, double check that there are entries there?

Thank you for your input. Do you think we should have a wiki describing this kind of esoteric information?