Trigger tap release on CI deployment

[theofidry]

Hello,

I would like to make use of Tap Release for Box. The issue I have is that the artefact I would like to publish is not attached to the release at the moment of tagging: it is uploaded via the Travis CI. So the workflow is:

• Tag a release
• The previous point triggers a Travis build for the release
• One of the build upload the built artefact to the release

Is there any way to achieve that?

[toolmantim]

Tagging shouldn't automatically create a full-blown release, we only listen to the release event: https://github.com/toolmantim/tap-release/blob/master/index.js#L6

I wonder what's happening here? 🤔

[theofidry]

Hm I think that this events is triggered as soon as the release is created. Only after that the build is triggered and upon success the artefact is published.

Maybe what is needed would be a way to trigger tap to say "hey, please check that release again"

[toolmantim]

Do you know if there's a GitHub event for that? https://developer.github.com/webhooks/ Because from what I can tell, there isn't! 🤔

Is there a way to rejig your flow?

[theofidry]

Maybe the deployment or deployment status event? In the end it's what is used to upload the additional artefacts to the release.

[toolmantim]

Are you creating a deployment / deployment status? Mind linking me to the scripts where this workflow is run, so I can get my head around it.

[theofidry]

Sure: https://github.com/humbug/box/blob/master/.travis.yml#L69

[brunolemos]

I have the same travis workflow. Any solution?

Maybe if we make travis mark as draft or pre_release?
Not sure if a new webhook would be sent after changing it to release, but probably yes.

[theofidry]

@toolmantim would there actually be a way to use this as a GitHub action step? This would allow one to configure the exact conditions upon which the step needs to be executed solving this timing issue.