Confirm
4,971
edits
Changes
→How to move a VCS Sync job
The keys are the same as the keys on vcs2vcs@gd{0..4}, and has been shared on Google Drive to various RelEngers... except the passphrase has been stripped from them: <code>ssh-keygen -p -f FILE</code>
=== How to move a VCS Sync job process === * pause the cron job* move the work dir (or rsync, if across machines).** You need to move build/conversion or you'll start from scratch, which is definitely a no-no for mozilla-central based repos (see https://wiki.mozilla.org/ReleaseEngineering/VCSSync/HowTo#How_to_start_a_mozilla-central_based_repo_conversion_from_scratch)** Moving build/stage_source will save a lot of cloning time, especially for processes with a lot of large repos like the project-branches process.** If the path changes, you need to delete (or not move) build/venv.** If you're trying to move it cleanly, don't move build/target or build/upload. If you want to preserve the old history, move them.* If you're on a new machine, you need to make sure it's set up properly. (Should be easier once it's puppetized)* make sure the cron job script is pointing at the right location* restart the cron job
=== How to start a mozilla-central based repo conversion from scratch ===
