Extract #generate_compile_tasks into CompileTaskGenerator

Signed-off-by: caleb miles <cmiles@pivotallabs.com>
prefer single quotes for non-interpolated strings

Signed-off-by: caleb miles <cmiles@pivotallabs.com>
Allow injection of event log

Signed-off-by: Rob Day-Reynolds <rdayreynolds@pivotallabs.com>
Obtain release version from job template rather than job

Signed-off-by: Rob Day-Reynolds <rdayreynolds@pivotallabs.com>
integration test for cross release collocation

Signed-off-by: Matthew Boedicker <mboedicker@pivotallabs.com>
Move job-centric logging to template-centric

Previously we assumed that each job instance has a release associated.
This will no longer be true after we enable cross release collocation
(WIP). This commit removes that assumption.

Signed-off-by: Matthew Boedicker <mboedicker@pivotallabs.com>
inflate the tests by avoiding re-lets

Signed-off-by: Yulia Tolskaya <ytolskaya@pivotallabs.com>
back fill tests for #spec of a job

Signed-off-by: Yulia Tolskaya <ytolskaya@pivotallabs.com>
job spec should not contain a release

Signed-off-by: Yulia Tolskaya <ytolskaya@pivotallabs.com>
assembler no longer sets release for a job instance

Signed-off-by: Yulia Tolskaya <ytolskaya@pivotallabs.com>
Clear out release from current state of agents

In addition to stopping setting the top level "release" key, we also
need to migrate existing agents by removing that information when we
update the VM's because we will otherwise still send out the older
"release" out as part of an apply spec.

Signed-off-by: Yulia Tolskaya <ytolskaya@pivotallabs.com>
Stop sending "release" in apply specs

This commit removes the top level "release" in the apply spec to the
agent.

Historically, there was only one release per job. And when collocation
was introduced, we happened to have the restriction that templates come
fromn the same release.  When we start collocating templates from
different releases, the "release of the job" will stop making sense.

The agent does not consume this release information, but it passes it to
the ERB templates, which means that we have a slim chance of breaking a
release that actually makes use of `spec.release` but such uses should
be discouraged.

Signed-off-by: Yulia Tolskaya <ytolskaya@pivotallabs.com>
more explicit and stricter assertion on the apply_spec when updating resource pools

Signed-off-by: Yulia Tolskaya <ytolskaya@pivotallabs.com>
Stop sending release in the apply spec when updating resource pool

Signed-off-by: Yulia Tolskaya <ytolskaya@pivotallabs.com>