worker

package

v0.1.1 Latest Latest Go to latest Published: May 5, 2017 License: MPL-2.0 Imports: 24 Imported by: 0

Details

Package worker is responsible for managing the claiming, executing, and resolution of tasks.

This section is empty.

View Source

var ErrWorkerStoppedNow = errors.New("worker was interrupted by StopNow")

ErrWorkerStoppedNow is used to communicate that the worker was forcefully stopped. This could also be triggered by a plugin or engine.

func ConfigSchema() schematypes.Object

ConfigSchema returns the schema for configuration.

type Worker struct {
	// contains filtered or unexported fields
}

A Worker processes tasks

func New(config interface{}) (w *Worker, err error)

New creates a new Worker

func (w *Worker) PayloadSchema() schematypes.Schema

PayloadSchema returns the schema for task.payload

func (w *Worker) Start() error

Start process tasks, returns ErrWorkerStoppedNow if not stopped gracefully.

func (w *Worker) StopGracefully()

StopGracefully stops claiming new tasks and returns nil from Work() when all currently running tasks are done.

func (w *Worker) StopNow()

StopNow aborts current tasks resolving worker-shutdown, and causes Work() to return an error.

Path	Synopsis
taskrun Package taskrun provides abstractions to execute a run of a task given a task, engine, plugin, and other runtime objects required by plugin and engine.	Package taskrun provides abstractions to execute a run of a task given a task, engine, plugin, and other runtime objects required by plugin and engine.
workertest Package workertest provides a framework for declarative definition of worker integration tests.	Package workertest provides a framework for declarative definition of worker integration tests.
fakequeue Package fakequeue provides a fake implementation of taskcluster-queue in golang, The FakeQueue server stores tasks in-memory, it doesn't validate authentication, but implements most end-points correctly.	Package fakequeue provides a fake implementation of taskcluster-queue in golang, The FakeQueue server stores tasks in-memory, it doesn't validate authentication, but implements most end-points correctly.