Skip to content
This repository was archived by the owner on Jan 18, 2021. It is now read-only.

Suggested implementation / design for simplifying release configuration#102

Closed
mockitoguy wants to merge 1 commit intomasterfrom
simplify-configuration
Closed

Suggested implementation / design for simplifying release configuration#102
mockitoguy wants to merge 1 commit intomasterfrom
simplify-configuration

Conversation

@mockitoguy
Copy link
Copy Markdown
Member

See motivation at #101

We should be able to to simplify release configuration
and get rid of ‘releasing.build.branch’ completely.

Workflow:

1. travisReleasePrepare task ensures that TRAVIS_BRANCH is checked out.
2. in other workflows (non-travis), for example local testing,
deployment from local, we don’t read/require the TRAVIS_BRANCH at all.
@epeee
Copy link
Copy Markdown
Contributor

epeee commented Apr 30, 2017

👍

@mockitoguy
Copy link
Copy Markdown
Member Author

This has been implemented / fixed. Thank you!

@mockitoguy mockitoguy closed this May 10, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants