You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My org has a mercurial repo, and what happens right now is the backup script just fails to clone or update.
I cannot access the admin panel for that repo, because bitbucket has disabled mercurial repos.
I'm working with bitbucket support to get it deleted, but in the meantime, I've modified my local copy of the script to just not try to update or clone mercurial repos.
I figure that maybe the script should do that, or maybe try mercurial repos $retry times, and then not fail?
Actually, why does the entire script fail if one repo fails?
Seems like it would be better to report the issues on stderr, continue backing up things, and then return an error at the end.
The text was updated successfully, but these errors were encountered:
https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket
My org has a mercurial repo, and what happens right now is the backup script just fails to clone or update.
I cannot access the admin panel for that repo, because bitbucket has disabled mercurial repos.
I'm working with bitbucket support to get it deleted, but in the meantime, I've modified my local copy of the script to just not try to update or clone mercurial repos.
I figure that maybe the script should do that, or maybe try mercurial repos $retry times, and then not fail?
Actually, why does the entire script fail if one repo fails?
Seems like it would be better to report the issues on stderr, continue backing up things, and then return an error at the end.
The text was updated successfully, but these errors were encountered: