ReleaseEngineering/Applications/Tooltool: Difference between revisions

ReleaseEngineering/Applications/Tooltool (view source)

1,095 bytes added , 10 June 2014

no edit summary

Confirmed users

107

edits

@@ Line 124: / Line 124: @@
 Use /tooltool/uploads/<your_username>/pub to upload to the public download server
 Use /tooltool/uploads/<your_username>/pvt to upload to the private download server
+= Tooltool uploads: the old school =
+''This is the old school, deprecated, manual way to upload artifacts to tooltool.
+Please use the official procedure described above whenever possible.''
+If you don't want to upload from your own laptop (because, eg, you have a slow uplink) you can do this from cruncher.
+Access cruncher with your credentials:
+ ME="your_short_ldap_username" # or `whoami`
+ ssh -A $ME@cruncher.build.mozilla.org
+Download the file and then:
+ scp filename.tar.xz $ME@relengwebadm.private.scl3.mozilla.com:
+Login to relengwebadmn:
+ ssh $ME@relengwebadm.private.scl3.mozilla.com
+And deploy the file to tooltool:
+<pre>
+FILE=~/emulator.zip # or whatever you're uploading
+export SHA512=`openssl sha512 $FILE | cut -d' ' -f2`
+sudo mv -i $FILE /mnt/netapp/relengweb/tooltool/pvt/build/sha512/${SHA512}
+sudo chmod 644  /mnt/netapp/relengweb/tooltool/pvt/build/sha512/${SHA512}
+ls -l  /mnt/netapp/relengweb/tooltool/pvt/build/sha512/${SHA512}
+</pre>
+* Add the filename, filesize, and sha512 digest to the bug you are working on.  These can be added to the tooltool manifests later.