action #51410
closed
Enable automatic test deployment on o3 again once it is deployed with the newest os-autoinst package
Added by nicksinger almost 5 years ago.
Updated almost 5 years ago.
Description
OSD was deployed with the breaking API changes for assert_and_click. To not break tests (we have to merge the test-code changes now for the new API) on either instance we have to disable the cron-job pulling the test-code changes from github.
This ticket exists to make sure we don't forget to enable it again once everything is deployed/merged.
- Copied from action #50951: Enable transactional updates on all o3 workers again once OBS published the most recent os-autoinst version added
- Copied from deleted (action #50951: Enable transactional updates on all o3 workers again once OBS published the most recent os-autoinst version )
- Related to action #50951: Enable transactional updates on all o3 workers again once OBS published the most recent os-autoinst version added
I've commented out:
ariel:/etc # cat cron.d/openqa-update-git
#-7 * * * * geekotest (cd /var/lib/openqa/share/tests/openqa && git pull --rebase origin master)
remove the preceding # to enable the cron again.
- Status changed from Blocked to Resolved
- Assignee set to nicksinger
Also available in: Atom
PDF