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

Standardizing data for testing #111

New Issue
Closed
opened 2025-12-29 15:33:25 +01:00 by adam · 1 comment
adam commented 2025-12-29 15:33:25 +01:00
Owner
Copy Link

Originally created by @ryanmerolle on GitHub (Jun 30, 2016).

It might be helpful to setup some process(es) to git clone the master or search for the latest stable release, deploy and run the upgrade process on a demo page (digital ocean or packetlife) on a daily basis. Obviously this would be limited given that not all testers would have access to a remote console for troubleshooting. It would also help give new users a view of the most recent version of the tool before installing.

This would allow for some cross collaboration when testing. Another option would be to develop a standard test data set for distribution with these releases so we can all test using similar data sets. A simple sql file could be used for this. We could probably package up an export of the current db on the demo site with some tweaks here and there.

Originally created by @ryanmerolle on GitHub (Jun 30, 2016). It might be helpful to setup some process(es) to git clone the master or search for the latest stable release, deploy and run the upgrade process on a demo page (digital ocean or packetlife) on a daily basis. Obviously this would be limited given that not all testers would have access to a remote console for troubleshooting. It would also help give new users a view of the most recent version of the tool before installing. This would allow for some cross collaboration when testing. Another option would be to develop a standard test data set for distribution with these releases so we can all test using similar data sets. A simple sql file could be used for this. We could probably package up an export of the current db on the demo site with some tweaks here and there.
adam closed this issue 2025-12-29 15:33:25 +01:00
adam commented 2025-12-29 15:33:25 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 22, 2016):

In an effort to clean up the issues backlog, I'm closing all issues labelled as "discussion." If there is interest in continuing this topic, please start a thread on the NetBox subreddit. Thanks!

@jeremystretch commented on GitHub (Jul 22, 2016): In an effort to clean up the issues backlog, I'm closing all issues labelled as "discussion." If there is interest in continuing this topic, please start a thread on the [NetBox subreddit](https://www.reddit.com/r/netbox). Thanks!
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
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#111
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?