Auto-tools/Projects/Pulse actions

• Source code: https://github.com/adusca/pulse_actions
• Running on: Heroku
• Logs on:
  • For corp access -> https://papertrailapp.com/systems/pulse-actions/events
  • For communit access:
    • https://dashboard.heroku.com/apps/pulse-actions/resources
    • Click on PaperTrail icon

Alerts

• Papertrail alerts sent to armenzg and others - https://papertrailapp.com/alerts
  • Memory issues
  • Worker1: Errors
  • Worker1: crashed
  • Worker2: Errors
  • Worker2: crashed

Accounts

• Papertrail:
  • For employees, you can request a corp account to all Papertrail apps
  • For contributors, speak with armenzg to add you to the Papertrail add-on

Credentials

For pulse_actions to work we need set these environment variables:

• Buildapi - LDAP credentials (LDAP_PW/LDAP_USER)
• TaskCluster - TaskCluster client credentials (TASKCLUSTER_CLIENT_ID/TASKCLUSTER_ACCESS_TOKEN)
• Pulse - Pulse user credentials (PULSE_PW/PULSE_USER)
• Papertrail - API Token (PAPERTRAIL_API_TOKEN)

To run locally you will need to set all up as env variables. You won't need to add the Papertail token.

Workflow

This workflow was created with Gliffy: http://www.gliffy.com/go/publish/8686299

Support

In case the service is causing issues:

• Point of contact: armenzg
• Team alias address: auto-tools
• Brief description:
  • Pulse_actions listens to various pulse exchanges and takes various scheduling actions through BuildApi.
• What to do in case of issues: Send an email to auto-tools and ask someone to stop it until point of contact can look into it.
• Impact: If you disable pulse_actions:
  • sheriffs will not be able to backfill jobs (and other actions) from Treeherder
    • Re-opening trees would take longer
  • We will not have automated backfilling
    • Re-opening trees would take longer