starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

[PR #14393] [MERGED] Closes #14365: Introduce job_start and job_end signals #14382

New Issue
Closed
opened 2025-12-29 23:24:10 +01:00 by adam · 0 comments
adam commented 2025-12-29 23:24:10 +01:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/netbox-community/netbox/pull/14393
Author: @jeremystretch
Created: 11/30/2023
Status: ✅ Merged
Merged: 12/1/2023
Merged by: @jeremystretch

Base: feature ← Head: 14365-job-signals

📝 Commits (2)

  • f830968 Introduce job_start and job_end signals, and receivers to process event rules
  • 877ec30 Complete signals documentation

📊 Changes

4 files changed (+61 additions, -20 deletions)

View changed files

📝 docs/development/signals.md (+24 -0)
📝 netbox/core/models/jobs.py (+5 -20)
📝 netbox/core/signals.py (+6 -0)
📝 netbox/extras/signals.py (+26 -0)

📄 Description

Closes: #14365

  • Introduce two new signals in core: job_start and job_end
  • Move Job.process_event() logic for EventRule processing to receiver functions under extras

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/netbox-community/netbox/pull/14393 **Author:** [@jeremystretch](https://github.com/jeremystretch) **Created:** 11/30/2023 **Status:** ✅ Merged **Merged:** 12/1/2023 **Merged by:** [@jeremystretch](https://github.com/jeremystretch) **Base:** `feature` ← **Head:** `14365-job-signals` --- ### 📝 Commits (2) - [`f830968`](https://github.com/netbox-community/netbox/commit/f830968d1e1a055878130c246cce31c862eaf8a5) Introduce job_start and job_end signals, and receivers to process event rules - [`877ec30`](https://github.com/netbox-community/netbox/commit/877ec30a5a34b44b00d8fa79a8583e9da95d74bf) Complete signals documentation ### 📊 Changes **4 files changed** (+61 additions, -20 deletions) <details> <summary>View changed files</summary> 📝 `docs/development/signals.md` (+24 -0) 📝 `netbox/core/models/jobs.py` (+5 -20) 📝 `netbox/core/signals.py` (+6 -0) 📝 `netbox/extras/signals.py` (+26 -0) </details> ### 📄 Description ### Closes: #14365 - Introduce two new signals in `core`: `job_start` and `job_end` - Move `Job.process_event()` logic for EventRule processing to receiver functions under `extras` --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
adam added the pull-request label 2025-12-29 23:24:10 +01:00
adam closed this issue 2025-12-29 23:24:10 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#14382
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?