1198668 - delivery: post_upload handles mar-tools differently to the python script

Status: RESOLVED FIXED

(Cloud Services :: Operations: Miscellaneous, task)

Description

[Nick Thomas [:nthomas] (UTC+12)]

When the python script is given   (eg on windows)
  <tmpdir>/host/bin/mar.exe
  <tmpdir>/host/bin/mbsdiff.exe
it puts them them in the candidates directory at
  .../build<buildNumber>/mar-tools/win32/mar.exe
  .../build<buildNumber>/mar-tools/win32/mbsdiff.exe

The go script puts it at
  .../build<buildNumber>/mar-tools/win32/host/bin/mar.exe
  .../build<buildNumber>/mar-tools/win32/host/bin/mbsdiff.exe
which breaks the jobs which consume the utilities.

The other platforms are macosx64, linux, and linux64 (with no .exe on the filenames). eg see http://stage.mozilla.org/pub/mozilla.org/firefox/candidates/40.0.2-candidates/build1/mar-tools/. See http://hg.mozilla.org/build/tools/file/default/stage/post_upload.py#l319 for the code. Note that it does nothing if tinderbox_builds_dir is not defined.

This is needed for parity with post_upload.py, definitely by the time we swap firefox/thunderbird/mobile over to the new system. It doesn't block testing though.

Comment 1

[Jeremy Orem [:oremj]]

https://github.com/mozilla-services/product-delivery-tools/pull/33

r?

Comment 2

[Nick Thomas [:nthomas] (UTC+12)]

This merged last week. I'll close and reopen if a retest reveals any issues.