Early Access Deployment tracking requires version
1.26.0 or later of the Nightwatch package and is currently limited to early access users. Contact us to enable access for your organization.Resolve issues on next deploy
Setting up deployment tracking unlocks the Resolve on next deploy workflow, which is one of the most effective ways to manage issues in Nightwatch. Instead of resolving an issue manually, you can mark it to resolve automatically when the next deployment is detected. The issue stays open while your fix is waiting to reach your live environment and then automatically closes once the new release ships.Mark an issue for resolution
1
Open the issue
Navigate to the issue you want to resolve.
2
Open the status menu
Click the Status dropdown in the sidebar or at the bottom of the page.
3
Choose the resolution
Select Resolve on next deploy.
4
Select the environment
Choose which environment should trigger the resolution, such as
production.5
Confirm
Optionally leave a comment, then click Resolve on next deploy.
The issue resolves when the next deployment is detected. If a deployment is already in progress, the issue resolves on the subsequent deployment.
Automatic Setup
If you deploy with Laravel Cloud, Nightwatch handles deployment tracking automatically. This integration sends deployment details such as the release reference, name, and URL without extra configuration.Manual Setup
If you are not using a platform with built-in Nightwatch integration, you can set up deployment tracking manually. Start by setting theNIGHTWATCH_DEPLOY environment variable as part of your deployment process. Once this value is present, Nightwatch detects new deployments from incoming application activity.
Common values include:
- A git commit SHA:
NIGHTWATCH_DEPLOY=$(git rev-parse HEAD) - A version tag:
NIGHTWATCH_DEPLOY=v1.2.3 - A release timestamp:
NIGHTWATCH_DEPLOY=$(date +%Y%m%d%H%M%S)
nightwatch:deploy Artisan command at the appropriate point in your deployment pipeline.
Examples
Use the configuredNIGHTWATCH_DEPLOY value: