Skip to content

Fix #75: Fix Travis CI deployments from branches other than master #134

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 5, 2020

Conversation

MaximeKjaer
Copy link
Contributor

The previous deployment failed with the following message:

Skipping a deployment with the releases provider because this branch is not permitted: 0.4.2

It turns out that the previous config only allowed deployments from master. According to the Travis CI docs:

branch: name of the branch. If omitted, this defaults to the app-specific branch, or master. If the branch name is not known ahead of time, you can specify all_branches: true instead of branch: and use other conditions to control your deployment.

In our case, we already only deploy if a tag is present, so all_branches: true should be fine.

Hopefully it'll work this time 🤞

@nicolasstucki nicolasstucki merged commit 076a74a into scala:master Aug 5, 2020
@MaximeKjaer MaximeKjaer deleted the fix-travis-ci-releases branch August 5, 2020 13:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants