facebook/sapling
1
1
Fork 0
mirror of https://github.com/facebook/sapling.git synced 2024-10-12 09:48:05 +03:00
Code Issues Projects Releases Wiki Activity
30549a98dd
sapling/tests/test-commitcloud-background-logging-perms.t

29 lines
625 B
Perl
Raw Normal View History

infinitepush: better client-side logging Summary: New logging will have rotation and will separate different users and repos Test Plan: arc unit Reviewers: #mercurial, durham Reviewed By: durham Subscribers: durham, mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4689191 Tasks: 16474976 Signature: t1:4689191:1489172091:d304d4b19ae6cf52f86c11f442fa760b50d1fdf9
2017-03-14 12:13:16 +03:00
$ . "$TESTDIR/library.sh"
infinitepush: move library-infinitepush.sh to infinitepush/library.sh Summary: Makes more sense to have this structure after D6691821. Test Plan: Ran all the tests. Reviewers: quark, #mercurial, #sourcecontrol Reviewed By: quark Differential Revision: https://phabricator.intern.facebook.com/D6694171 Signature: 6694171:1515609818:1142419346e3458db7674b1b69036d88e82a1903
2018-01-10 21:44:15 +03:00
$ . "$TESTDIR/infinitepush/library.sh"
infinitepush: better client-side logging Summary: New logging will have rotation and will separate different users and repos Test Plan: arc unit Reviewers: #mercurial, durham Reviewed By: durham Subscribers: durham, mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4689191 Tasks: 16474976 Signature: t1:4689191:1489172091:d304d4b19ae6cf52f86c11f442fa760b50d1fdf9
2017-03-14 12:13:16 +03:00
$ setupcommon
Setup server
$ hg init repo
$ cd repo
$ setupserver
$ cd ..
Clone
$ hg clone ssh://user@dummy/repo client -q
$ cd client
Create log dir
$ mkdir $TESTTMP/logs
infinitepush: do not expose word 'infinitepush' to users and make it clear that all that messages are about autobackup (in background) Summary: Make it clear that all that messages are about autobackup (in background) Even if it is disabled, manual `hg pushbackup` works Also, since we announced publicly about renaming infinitepush we should not use it in user facing messages. Also, that commands enable/disable background cloudsync, probably later we should check if cloudsync is enabled and improve messages to be more precise. Reviewed By: StanislavGlebik Differential Revision: D7635640 fbshipit-source-id: 2461b1b45e181c6e24b59f707a17f2fd60d4bb0e
2018-04-16 14:49:45 +03:00
Setup background backup logging
commitcloud: incorporate infinitepush backups into commitcloud Summary: Merge the functionality of the infinitepushbackup extension (backing up commits to commit cloud) into the commitcloud extension. These two extensions are highly coupled, and the commitcloud extension monkey-patches the infinitepushbackup extension for a lot of its functionality. There is also a lot of code duplication between the two extensions which we can remove if they are part of the same extension. The infinitepushbackup commands (`hg pushbackup`, ...) are moved to subcommands of the `hg cloud` command, e.g. `hg cloud backup`. Each feature of the infinitepushbackup extension is moved to a new module in the commit cloud extension: The `background` module controls background execution of `hg cloud backup` and `hg cloud sync`. The `backupbookmarks` module tracks and updates scratch bookmarks for backups. This will be deprecated in the future. The `backupstate` module tracks whether or not a commit has been backed up. This is now tracked separately from backup bookmarks in a new file: `.hg/commitcloud/backedupheads.<remote-identifier>`. This also covers hidden commits, preventing a re-backup of previously backed up commits when they are unhidden. Previously the commitcloud extension customized the smartlog annotations: `Backing up` became `Syncing`, etc. This is now removed for consistency. Previously the infinitepushbackup extension disabled background backup by injecting an `infinitepushbackup.disableduntil` config entry into the user's config. This is now replaced with a state file at `.hg/commitcloud/autobackup`. Either option can be set to disable auto backup. Commit cloud will wait until both have expired before starting to run background backups again. Reviewed By: DurhamG Differential Revision: D15276939 fbshipit-source-id: 1d28989a157286e47d3dd97ca9c70b27f692dda1
2019-05-20 16:11:59 +03:00
$ setconfig infinitepushbackup.logdir=$TESTTMP/logs
infinitepush: better client-side logging Summary: New logging will have rotation and will separate different users and repos Test Plan: arc unit Reviewers: #mercurial, durham Reviewed By: durham Subscribers: durham, mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4689191 Tasks: 16474976 Signature: t1:4689191:1489172091:d304d4b19ae6cf52f86c11f442fa760b50d1fdf9
2017-03-14 12:13:16 +03:00
$ mkcommit first
infinitepush: fix security concern Summary: Check owner of a log file before writing to it. See comments for details Test Plan: arc unit Reviewers: #mercurial, simpkins Reviewed By: simpkins Subscribers: net-systems-diffs@fb.com, mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4842933 Tasks: 17155924 Signature: t1:4842933:1491861137:e8a027fb7a930c0c5f553c75cb84214d24f66ce3
2017-04-12 11:12:23 +03:00
Check that logging fails because of wrong permissions
commitcloud: incorporate infinitepush backups into commitcloud Summary: Merge the functionality of the infinitepushbackup extension (backing up commits to commit cloud) into the commitcloud extension. These two extensions are highly coupled, and the commitcloud extension monkey-patches the infinitepushbackup extension for a lot of its functionality. There is also a lot of code duplication between the two extensions which we can remove if they are part of the same extension. The infinitepushbackup commands (`hg pushbackup`, ...) are moved to subcommands of the `hg cloud` command, e.g. `hg cloud backup`. Each feature of the infinitepushbackup extension is moved to a new module in the commit cloud extension: The `background` module controls background execution of `hg cloud backup` and `hg cloud sync`. The `backupbookmarks` module tracks and updates scratch bookmarks for backups. This will be deprecated in the future. The `backupstate` module tracks whether or not a commit has been backed up. This is now tracked separately from backup bookmarks in a new file: `.hg/commitcloud/backedupheads.<remote-identifier>`. This also covers hidden commits, preventing a re-backup of previously backed up commits when they are unhidden. Previously the commitcloud extension customized the smartlog annotations: `Backing up` became `Syncing`, etc. This is now removed for consistency. Previously the infinitepushbackup extension disabled background backup by injecting an `infinitepushbackup.disableduntil` config entry into the user's config. This is now replaced with a state file at `.hg/commitcloud/autobackup`. Either option can be set to disable auto backup. Commit cloud will wait until both have expired before starting to run background backups again. Reviewed By: DurhamG Differential Revision: D15276939 fbshipit-source-id: 1d28989a157286e47d3dd97ca9c70b27f692dda1
2019-05-20 16:11:59 +03:00
$ hg cloud backup --background
infinitepush: use ui.debug() instead of ui.warn() Summary: To avoid spamming users Test Plan: Run tests Reviewers: #mercurial, rmcelroy Reviewed By: rmcelroy Subscribers: mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4883447 Signature: t1:4883447:1492088221:3649b14ff514957d2f412aae2647ca1b20ef5fea
2017-04-18 09:44:26 +03:00
$ waitbgbackup
commitcloud: incorporate infinitepush backups into commitcloud Summary: Merge the functionality of the infinitepushbackup extension (backing up commits to commit cloud) into the commitcloud extension. These two extensions are highly coupled, and the commitcloud extension monkey-patches the infinitepushbackup extension for a lot of its functionality. There is also a lot of code duplication between the two extensions which we can remove if they are part of the same extension. The infinitepushbackup commands (`hg pushbackup`, ...) are moved to subcommands of the `hg cloud` command, e.g. `hg cloud backup`. Each feature of the infinitepushbackup extension is moved to a new module in the commit cloud extension: The `background` module controls background execution of `hg cloud backup` and `hg cloud sync`. The `backupbookmarks` module tracks and updates scratch bookmarks for backups. This will be deprecated in the future. The `backupstate` module tracks whether or not a commit has been backed up. This is now tracked separately from backup bookmarks in a new file: `.hg/commitcloud/backedupheads.<remote-identifier>`. This also covers hidden commits, preventing a re-backup of previously backed up commits when they are unhidden. Previously the commitcloud extension customized the smartlog annotations: `Backing up` became `Syncing`, etc. This is now removed for consistency. Previously the infinitepushbackup extension disabled background backup by injecting an `infinitepushbackup.disableduntil` config entry into the user's config. This is now replaced with a state file at `.hg/commitcloud/autobackup`. Either option can be set to disable auto backup. Commit cloud will wait until both have expired before starting to run background backups again. Reviewed By: DurhamG Differential Revision: D15276939 fbshipit-source-id: 1d28989a157286e47d3dd97ca9c70b27f692dda1
2019-05-20 16:11:59 +03:00
$ hg cloud backup --background --debug
infinitepush: do not expose word 'infinitepush' to users and make it clear that all that messages are about autobackup (in background) Summary: Make it clear that all that messages are about autobackup (in background) Even if it is disabled, manual `hg pushbackup` works Also, since we announced publicly about renaming infinitepush we should not use it in user facing messages. Also, that commands enable/disable background cloudsync, probably later we should check if cloudsync is enabled and improve messages to be more precise. Reviewed By: StanislavGlebik Differential Revision: D7635640 fbshipit-source-id: 2461b1b45e181c6e24b59f707a17f2fd60d4bb0e
2018-04-16 14:49:45 +03:00
$TESTTMP/logs directory has incorrect permission, background backup logging will be disabled
infinitepush: better client-side logging Summary: New logging will have rotation and will separate different users and repos Test Plan: arc unit Reviewers: #mercurial, durham Reviewed By: durham Subscribers: durham, mjpieters, #sourcecontrol Differential Revision: https://phabricator.intern.facebook.com/D4689191 Tasks: 16474976 Signature: t1:4689191:1489172091:d304d4b19ae6cf52f86c11f442fa760b50d1fdf9
2017-03-14 12:13:16 +03:00
$ waitbgbackup
Reference in New Issue Copy Permalink