-
Notifications
You must be signed in to change notification settings - Fork 9
Troubleshooting
For collections that were migrated (and existed on the testing server before it was converted to singularity-hub.org
) the webhooks need to be updated for the different server address. The first obvious thing to try is logging out, and back in again. You can also navigate to the Settings --> Applications --> OAuth applications page and look at the configuration and response for the hook to better understand any issues. If you have no legacy images and don't mind rebuilding, then just delete the collection, log out and back in, and authenticate again. If you have legacy images (and don't want to delete the collection) then you can either make a second collection to work from, or wait for @vsoch to carefully update the webhooks.
If you are ever confused about why a build seems to be over-writing another, remember that the default behavior is to do this *unless you specify to freeze an image. Also be careful to check your build trigger settings. For example, if you are set to build manually, builds will not happen when you commit.
Don't worry! All images and metadata are still happily existing on their original server, and @vsoch will soon get working a legacy domain for this. The legacy domain will be available until the end of the calendar year.
Need help? submit an issue and let us know!