Message-ID: <1659073800.9137.1711720020168.JavaMail.confluence@host3.pipelinefx.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_9136_220251883.1711720020168" ------=_Part_9136_220251883.1711720020168 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
It's possible to submit a job that will remain in a "blocke= d" state until a certain time on a specific day, at which time it will= then automatically go into a "pending" state and be the next job= dispatched to the farm
This in an example of how to submit a job that will start at a later tim= e.
Lines of interest are:
#!/usr/bin/env python import sys import os import time sys.path.append(os.environ['QBDIR']) import qb task =3D [] agenda =3D qb.genframes('1-2') now =3D int(time.time()) later =3D now + 3600 - qb.QB_TIME_EPOCH_OFFSET job =3D { 'prototype': 'cmdrange', 'name': 'wait time test', 'status': 'blocked', 'package': {'cmdline': 'sleep 30'}, 'agenda': agenda, 'callbacks': [], 'hosts': 'rhel52-64,rhel53-64,rhel54-64' } cb =3D { 'language': 'qube', 'triggers': 'dummy-time-self-%d' % later, 'code': 'unblock-self' } job['callbacks'].append(cb) task.append(job) submitted =3D qb.submit(task) for job in submitted: print 'submitted job %(id)s: %(name)s' % job=20