Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
L
lvalert
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 14
    • Issues 14
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 4
    • Merge Requests 4
  • Requirements
    • Requirements
    • List
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • lscsoft
  • lvalert
  • Issues
  • #6

Closed
Open
Created Aug 24, 2018 by Alexander Pace@alexander.paceMaintainer

incorporate lvalertMP into standard LVAlert packaging

This is a migration of Redmine issue #4685.

Original Description (2015-09-27):

An extension to LVAlert has been developed in a personal github repository for a while now. However, the code is stable enough that it should be reviewed and migrated into the existing default packaging.

The lvalertMP repo can be found here: https://github.com/reedessick/lvalertMP

Update:

lvalertMP and event_supervisor have been (as far as I can tell) depreciated in favor of GWCelery. I think it's safe to close this ticket.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None