This sets the field lengths to what they will be in a later PR for
the job_details model. But these are still within the constraints
of the current field lengths for that table.
Several existing jobs are already out of compliance with these patterns
and there is no existing way to tell task definition developers how to
comply with our required patterns.
created bug 1283866 in Taskcluster for that tool/workflow
This removes the pattern requirements. If we ever decide that we DO
need these patterns, we can create that tool and then fix old task
definitions to comply.
Some repos are longer-lived and do not yet have the Task Cluster
code that allows them to submit tasks with a revision. They only
have the older code to submit revision_hash. This prevents the
jobs from being ingested via Pulse. This commit adds support
for revision_hash until a time when it's no longer needed.
This contains several tweaks and fixes that allow us to ingest data from
a real Task Cluster owned exchange.
One of the main fixes is the way I was binding to the exchange and
routing keys with the same Queue. Before, it was re-creating the Queue,
so would miss some of the bindings.
This will also prune the durable queue if the config has removed some
exchanges and/or routing keys.
These changes were discovered to be needed after direct testing
against Task Cluster Pulse exchanges.
-Made some JSON/YML schema changes to be more precise for several fields
-Modified to job_loader to be more resilient to optional data being
missing
We store both long and short, but only utilize the short (as before). We
need to populate all the short and long revision records before we can
start using them. So after this commit, we will begin backfilling the
old records that don't yet have those values populated. Once they all
are, we can move to using the long_revision primarily in Bug 1199364.
camd