|
|
| Line 43: |
Line 43: |
|
| |
|
| = How to add a new version = | | = How to add a new version = |
| * Manifests should be attached to the bug by a developer
| | See [https://wiki.mozilla.org/ReleaseEngineering/Applications/Tooltool#How_To_Upload_To_Tooltool How To Upload To Tooltool] |
| * ssh to relengwebadm.private.scl3.mozilla.com
| |
| * Download files
| |
| mkdir ~/tooltool
| |
| cd ~/tooltool
| |
| rm -i *
| |
| # get latest setup.sh if its manifest was changed
| |
| wget https://hg.mozilla.org/mozilla-central/raw-file/default/build/unix/build-clang/setup.sh
| |
| # download new clang packages
| |
| wget http://people.mozilla.org/~user/clang-linux.tar.bz2
| |
| wget http://people.mozilla.org/~user/clang-linux64.tar.bz2
| |
| wget http://people.mozilla.org/~user/clang-osx.tar.bz2
| |
| # Fix permissions
| |
| chmod 644 *
| |
| * Copy files to the tooltool directory. Use the "digest" field from the generated manifests as target file name:
| |
| for f in clang-*.tar.bz2; do
| |
| ls -l $f
| |
| sudo cp -vi $f /var/www/html/runtime-binaries/tooltool/sha512/$(sha512sum $f | cut -f1 -d " ")
| |
| done
| |
| * repeat the same step for setup.sh if needed
| |
|
| |
|
| = See Also = | | = See Also = |
| * [[ReleaseEngineering/Applications/Tooltool]] | | * [[ReleaseEngineering/Applications/Tooltool]] |
| * https://github.com/mozilla/build-tooltool | | * https://github.com/mozilla/build-tooltool |