Permalink
Commits on Feb 9, 2017
  1. Bug 1319246 - Allow login with plain email from Auth0 (#2011)

    This will also  migrate the username of existing users logging 
    in with LDAP to be the ``clientId`` we get from the login.
    camd committed on GitHub Feb 9, 2017
Commits on Jan 11, 2017
Commits on Dec 2, 2016
Commits on Nov 22, 2016
  1. Revert "Bug 1207460 - Split retrigger menu into separate btns (#1960)"

    The retrigger and backfill buttons don't work after this change.  I think
    an ng-click was forgotten in the PR.
    
    This reverts commit 86235ae.
    camd committed Nov 22, 2016
Commits on Nov 21, 2016
Commits on Nov 18, 2016
  1. Bug 1273034 - Transition to Taskcluster Auth from Persona (#1922)

    In this commit, Sheriff access is still maintained in the
    Treeherder DB, rather than using the scopes derived from
    LDAP.
    
    For local usage with Vagrant, this requires accessing
    Treeherder with localhost instead of
    local.treeherder.mozilla.org
    
    Loggin in to the Django Admin is not enabled in this
    branch.  Do use the admin, you must first login through
    the normal Treeherder front-end.  Then the admin will
    be accessible if the user has the privileges to do so.
    
    Persona login will still be technically possible through the
    login.taskcluster.net site.  But that choice will go away
    shortly.
    camd committed on GitHub Nov 18, 2016
Commits on Nov 8, 2016
Commits on Oct 27, 2016
Commits on Oct 7, 2016
  1. Bug 1308328 - Add Treeherder test cases to docs (#1902)

    * Bug 1308328 - Add Treeherder test cases to docs
    camd committed on GitHub Oct 7, 2016
Commits on Oct 6, 2016
Commits on Oct 3, 2016
  1. Bug 1306578 - Use retryable_task for pulse job ingestion

    Was calling retry manually, but that was causing repeated
    retries that were blowing up the celery queue.  This just
    uses our normal retryable_task for retries and adds some
    extra logging in new relic to help identify the product
    of a pulse job that failed.
    camd committed with camd Oct 3, 2016
  2. Bug 1306578 - Better handling for unknown project repo

    Raises a DatasetNotfoundError if the repo isn't found
    camd committed with camd Oct 3, 2016
Commits on Sep 30, 2016
Commits on Sep 29, 2016
  1. Revert "Bug 1305507 - Save whatever's typed into the bug field before…

    … seeing if we can save the classification (#1875) r=camd"
    
    This reverts commit 3092f0b.
    camd committed Sep 29, 2016
  2. Bug 1286578 - Retry job task if resultset doesn't exist (#1872)

    * Bug 1286578 - Retry job task if resultset doesn't exist
    
    This removes the logic which creates `skeleton resultsets`
    when a job is ingested that we don't have a resultset for yet.
    The new approach is to fail and wait for the task to retry.
    
    The buildbot job ingestion already skips and retries later if
    it encounters a job for which it has no resultset.
    
    This adds a similar check to the Pulse Job ingestion.  If
    a job comes in with a revision that doesn't have a resultset
    yet, then this will raise a ValueError.  That will invoke the
    retryable_task actions which will wait a bit, then retry.  Each
    time it will wait a little longer to retry.  After 9 retries it
    waits something like 3900 seconds which should be plenty of time
    for the resultset ingestion to complete.
    camd committed on GitHub Sep 29, 2016
Commits on Sep 16, 2016
  1. Bug 1303215 - Fix UI test failure due to lack of es6 support (#1860)

    The admin.js file has es6 templating syntax which is not considered
    valid in our Karma tests.  This moves the admin controller to the
    /admin folder where it should be anyway, so that the UI tests stop
    failing.
    camd committed on GitHub Sep 16, 2016
Commits on Sep 15, 2016
  1. Bug 1266116 - Add the Admin page: Full-page exclusion editor

    This moves the Sheriff panel out to a full-page app.  The functionality
    is basically the same, however.  Much of the logic and HTML were just
    copied from the Sheriff panel.
    
    This also introduces ReactJS to the repo.  This was used to speed up
    the rendering of the reference data lists in the Exclusions detail
    editor.  The ``reactselect`` component is defined as normal JavaScript.
    We decided not to introduce using JSX at this time.
    camd committed Sep 15, 2016
Commits on Sep 13, 2016
  1. Bug 1302529 - Add store_pulse_resultsets to bin script

    camd committed Sep 13, 2016
Commits on Sep 9, 2016
  1. Bug 1301739 - Fix Github repo urls so pulse data ingestion will work

    camd committed Sep 9, 2016
Commits on Aug 30, 2016
Commits on Aug 22, 2016
  1. Bug 1264074 - Use Pulse for creation of Github resultsets (#1692)

    * Bug 1264074 - Move to_timestamp function to a reusable location
    
    * Bug 1264074 - Refactor JobConsumer to have a PulseConsumer super class
    
    Much of what was in the JobConsumer is reusable by the upcoming
    ResultsetConsumer.  So refactor those parts out so that each specific
    consumer can reuse code as much as possible.
    
    * Bug 1264074 - Add ability to ingest Github Resultsets via Pulse
    
    This introduces a ResultsetConsumer and a read_pulse_resultsets
    management command to ingest resultsets from the TaskCluster
    github exchanges.
    
    When a supported Github repo has a Pull Request created or
    updated, or a push is made to master, then it will kick off a
    Pulse message.  We will receive it and then fetch any additional
    information we need from github's API and store the Resultset.
    
    This follows a very similar pattern to the Job Pulse ingestion.
    
    * Bug 1264074 - Old code/comments cleanup
    
    * Bug 1264074 - Tests for the Github resultset pulse loader
    camd committed on GitHub Aug 22, 2016
Commits on Aug 8, 2016
Commits on Aug 5, 2016
  1. Bug 1278711 - Lower field lengths in job_detail table (#1666)

    This is required in order to create a unique index on title,
    value and job_id to prevent duplicates.  The index will be
    created in a later PR.
    
    This also uses update_or_create instead of get_or_create as
    this will be the mechanism going forward to prevent duplicates.
    camd committed on GitHub Aug 5, 2016
Commits on Aug 4, 2016
  1. Bug 1291882 - Add unique_together index on build_platform table (#1759)

    Also to the machine_platform table.
    
    This is necessary because we use a get_or_create() on these
    tables, but without the unique index, we can (and did) get
    duplicates which then blocked data ingestion of jobs on try.
    camd committed on GitHub Aug 4, 2016
Commits on Aug 2, 2016
  1. Bug 1291010 - Add branch field to Repository model/table (#1755)

    We need a 'branch' field on the repository so that we can determine
    which repo to use for incoming resultsets from pulse exchanges. In
    the past, projects like gaia-taskcluster have had their own maps of
    github repositories/names/branches to Treeherder projects.  But
    Treeherder should be the one owning that mapping.  The only thing on
    this table was the branch that's used.  So here it is.
    
    The "branch" field will default to "master" which is appropriate for
    several of the repos.  But a few will need more custom values set.
    These are laid out in the fixtures/repository.json file.  But they
    will need to be manually entered into the databases on Prod/Stage
    and Heroku.
    camd committed on GitHub Aug 2, 2016
Commits on Jul 22, 2016
  1. Bug 1288181 - Handle empty changeset list from json-pushes (#1717)

    If a pushlog contains hidden changesets (changesets that are
    obsolete) then the call to json-pushes will return a push
    with no changesets.  This was changed in bug 1286426.
    For us, if `changesets` is empty, we will not be able to get
    a revision, which is required for a resultset.  So we
    need to just skip the push.
    camd committed on GitHub Jul 22, 2016
Commits on Jul 21, 2016
  1. Bug 1287501 - Fix /jobs/ endpoint to preserve `last_modified` param (#…

    …1704)
    
    A prior commit removed the ability to use "-Infinity" for the last_modified
    query param.  However, the fix accidentally stripped the param entirely.
    This change ensures that the value is a valid date string.  The range is
    not limited.
    
    This also adds some new tests to ensure the param of `last_modified` is
    working correctly when included.
    camd committed on GitHub Jul 21, 2016
Commits on Jul 18, 2016
  1. Bug 1287501 - Restrict jobs query last_modified to within last 30 min… (

    #1702)
    
    * Bug 1287501 - Restrict jobs query last_modified to within last 30 minutes
    camd committed on GitHub Jul 18, 2016
Commits on Jul 8, 2016
  1. Bug 1278711 - Set pulse schema jobdetails field lengths higher (#1665)

    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.
    camd committed on GitHub Jul 8, 2016
Commits on Jul 6, 2016
Commits on Jul 1, 2016
  1. Bug 1283865 - remove pattern requirements for pulse job display fields (

    #1639)
    
    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.
    camd committed on GitHub Jul 1, 2016