SOLVED: Windows release deploy artifact missing in github after (apparent) successful windows job

BanzaiMan · March 28, 2019, 2:00pm

My initial guess is that on Windows, $TRAVIS_BUILD_DIR is not properly resolved by Ruby.

tombech/sesam-py/blob/bd0b36f67df7321a98213485d32b77f0706a8241/.travis.yml#L30


script:
- bash test.sh
before_deploy:
- bash deploy.sh
deploy:
  - provider: releases
    skip_cleanup: true
    api_key:
      secure: cLkxJ8KdmjpUw/UAsRTfUsrqpB5NOUs9nY9FaiN7+c4ky71cgycCiKNxeun5TS0ygH/6gENub+oye4vzdFR3cCUHxclDm6QyTMWeSnyhbAcowlO83OuiR+BCuKSoG9sgoWBQ4hxHP6i57XlSBcHA4PqVFfr+fT2fDwDSY0jaTkRn46+7ffbVcEkBcSL5QFevt6664UGcZdbtrKKrpYKYw/LAQ53D3MvkWD89tqLrUAZeR9mxrfS0sQTTQZvtEjl0DOKn0hnml53j5stiz+yPl8qBfXgudW1MHoMd2ZgtBSvIpJ/Oar5YmJe3GUQOaCasuVu2wYSch0M6zV1ruRddijj4wFXQMZ65YiNLwGhlP4DuYWdoC5/zjEXJQi3+yX5t9zgMwPDB8kfnJDC070gMdoxybKdMarTx0D7wiOq/oi53pTGJwyv7/AjMX7MONeYwb/t7iwWlb7yI68k9PMF9IvSKvkslWUCFtPKj7AA2+fOFUVxc2okIWj5SdRcUGWfCYi1CNhwkRd8aaH57k7Y7bcRUz3adgzFkm/2oIybOCm0MFXwH0LqlskCHH+GZdux1gXTh+JEahxoyiwRr0WSDTJpRZJjzL76sQEEF6frmDKBD8CHYfSwizJCs0eNGgMed6ODyzR5kw+Wh6rWvlPh6HIGEvWR3P06/V0IxCwW7ipA=
    file_glob: true
    file: $TRAVIS_BUILD_DIR/artifact/*
    on:
      tags: true
      repo: tombech/sesam-py

So there is no file to upload. If you are certain that you are in $TRAVIS_BUILD_DIR during the deployment, perhaps dropping it from the file value would result in successful upload.

Topic		Replies	Views
No windows asset file found after deploy to Github release success Windows	4	1732	March 30, 2019
Builds are not tagged properly on GitHub releases on Windows Deployment build-env , github-integration	8	1358	November 6, 2019
Add artifacts built on different operating systems to a single release Deployment java	1	1025	April 1, 2021
Build artifacts aren't found on deployment Deployment python	2	896	January 19, 2020
Artifact uploader binary not found Windows	3	695	November 21, 2019

SOLVED: Windows release deploy artifact missing in github after (apparent) successful windows job

Related topics