Since everything but standard retrigger/cancellation is now handled
client-side by tcactions, making the backend parts that provided pulse
messages to pulse_actions redundant (since it was decommissioned in
bug 1379172).
Now that no submissions are using revision_hash, it can be removed.
This removes everything but the model field, which will be handled
later.
I've removed revision_hash from the Pulse jobs schema without bumping
the version, which wouldn't normally be ok, but no one is still using
it, and I'd rather have explicit failures later than if we left the
schema unchanged.
Change of new environment variable `PULSE_PUSH_SOURCES`.
Keep old `publish-resultset-runnable-job-action` task name by creating a
method that points to `publish_push_runnable_job_action`.
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.
* Bug 1254325 - Adding support to download all_tasks.json
* Adding support to send task ID of gecko decision via Pulse
* Fixing a few problems
* Adding UTC timestamp in pulse message
* Fixing nits, adding restriction to block ui changes
* Updating URL for full tasks file
* Renaming buildernames to requested_jobs
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
This adds a "Add new jobs" button that shows all buildbot jobs
that can be added as normal treeherder jobs (with a new CSS class).
After logged in users click on the jobs they want to trigger, they
can click on "Trigger new jobs" to send a pulse message that will
trigger the jobs.
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.
Ed Morley
Cameron Dawson
Max Chehab
Dave Hunt
William Lachance
glenn124f
William Lachance
Ed Morley
Kalpesh Krishna
Alice Scarpa
Vaibhav Agrawal
James Lal
Greg Arndt
Jonas Finnemann Jensen