Releases are not built - Travis deployment bug

[roborourke]

Bug Report

Looking at the Travis CI config it appears that the deploy section is intended to update the released tags on Github with the built version. Fetching the plugin via composer right now requires an additional build step.

deploy:
  provider: releases
  overwrite: true
  skip_cleanup: true
  file_glob: true
  file: build/**/*
  on:
    tags: true

# Pull requests are built by default.
branches:
  only:
  - master
  - develop

The problem is that by using branches: only builds only happen on these branches, tags are excluded so by setting deploy: on: tags: true this effectively means the deploy step can never run.

I would recommend either removing the branches section entirely or adding a regex to match your tag structure to that list.

Expected Behavior

Travis should build and deploy when the repo is tagged.

Actual Behavior

Travis does nothing, tag represents unbuilt commit.

[kasparsd]

Thank you for opening the issue!

Looks like we never got the Travis CI to create the plugin bundles and upload them to GitHub releases. I'm not even sure the current deploy workflow for releases would work because it doesn't create a ZIP file which is expected by that deploy workflow.

We would probably want to add a dedicated release command to scripts in package.json which does the build and creates a zip file out of that directory. This would also need a dedicated Grunt task to zip it.

[roborourke]

Ah I see, I thought it maybe just pushed the built directory to the tag. Thanks @kasparsd !