Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • beat.web beat.web
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 54
    • Issues 54
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • beatbeat
  • beat.webbeat.web
  • Issues
  • #430
Closed
Open
Issue created Jun 24, 2016 by André Anjos@andre.anjos💬Owner

[backend] Result.syserr is not useful any longer

Given the whole system is now based on the Django framework, we can immediately use the e-mailing capabilities of Django to send e-mail to administrators in case a problem is perceived anywhere in the code, making the use of this field on Results a bit useless.

Currently, on our base deployment system every error message emitted by the code is sent via e-mail to system administrators. We can use this to ship the error messages instead of moving it around in an object.

Assignee
Assign to
Time tracking