Skip to content

Update Server-Release-Tests.md #65

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 21, 2025
Merged

Update Server-Release-Tests.md #65

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion doc/deployment/deploy/Server-Release-Tests.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ These are tests/checks that should be performed on the IBEX server after a relea
1. `git status`
1. Ensure that the message says `up-to-date with 'origin/<Instrument Name>'`.
1. Ensure that a block PV is being logged. Do this by right-clicking a PV (one which would be expected to change a little) and select `Display block history -> create a new plot`. There should be data on the plot from after the instrument was upgraded.
1. Confirm that the web dashboard is working for the specific instrument (http://dataweb.isis.rl.ac.uk/)
1. Confirm that the web dashboard is working for the specific instrument (https://isiscomputinggroup.github.io/WebDashboard/instruments & http://dataweb.isis.rl.ac.uk/)

### Instruments which are having their first IBEX installation
1. Setup or find a block which is logging itself. Ensure that a log file with this block value in appears in `c:\data\*.log`. If this doesn't happen see [DAE troubleshooting](/specific_iocs/dae/DAE-Trouble-Shooting)
Loading