Production tryjob issue on uploading build artifacts |
||||
Issue descriptionReported via email previously. Assigning to Charles for now. === Hi Don, Charles, Not sure if you can help, but we are trying to build firmware that needs to be qualified with cros tryjob --production --branch=firmware-fizz-10139.117.B fizz-firmware-tryjob https://ci.chromium.org/p/chromeos/builds/b8946805663810150976 Everything looks OK other than there's no build artifacts available. I noticed from the log https://logs.chromium.org/v/?s=chromeos%2Fbuildbucket%2Fcr-buildbucket.appspot.com%2F8946805663810150976%2F%2B%2Fsteps%2FArchive%2F0%2Fstdout which says, "11:59:45: INFO: DRY RUN MODE ACTIVE: NOTHING WILL BE UPLOADED" Just wondering if that's the reason for the absence of artifacts, and if so how to get the artifacts uploaded? Thanks for the helps, YH
,
May 14 2018
Bumping the priority as we need the firmware for pre-FSI qualification. Thanks.
,
May 14 2018
Per email thread, try without -tryjob suffix.
,
May 16 2018
Thanks. That works. Just wondering what the rule is, cros tryjob --branch=firmware-fizz-10139.117.B fizz-firmware-tryjob for a tryjob, and cros tryjob --production --branch=firmware-fizz-10139.117.B fizz-firmware for a production build?
,
May 16 2018
Yep. Except.... on older branches, <foo>-firmware-tryjob won't exist. In that case use <foo>-firmware. We are hoping to have cros tryjob give better feedback in both cases in future.
,
May 16 2018
Thanks Don. I am marking the bug fixed. Please re-open if in need. |
||||
►
Sign in to add a comment |
||||
Comment 1 by shapiroc@chromium.org
, May 11 2018