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
  • #538
Closed
Open
Issue created Oct 28, 2019 by André Anjos@andre.anjos💬Owner

Moving cronjobs in beat.web to systemd

I get repeated e-mails every day concerning our BEAT jobs in beat.web. After more than a year, these scripts are pretty stable and it would be nice if we managed to make them not report unless there is a problem (exit status != 0).

In our internal webserver, I managed to implement this using systemd (report on failure only).

Could we do the same here? That would avoid the continuous torrent of "successful run" e-mails.

Assignee
Assign to
Time tracking