Skip to content
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

Support github release #135

Open
wants to merge 15 commits into
base: master
Choose a base branch
from
Open

Conversation

luckyrandom
Copy link

This pull request add support for github release, which was requested in #124. Please feel free to move the following doc to any place such as wiki. You may check https://travis-ci.org/luckyrandom/r-travis-test/builds for a working example.

Release package on github release

Set up

travis encrypt GH_TOKEN=your_token_created_on_github
  • Add the following sections to .travis.yml
-env:
  global:
    # GITHUB_TOKEN
    - secure: "your_encrypted_token"
after_success:
  - ./travis-tool.sh deploy ./packagename*.tar.gz

Recommend workflow

When a package is ready, bump the version, and put [try deploy github] in a single line of commit comment. Then the deploy script will create release and upload pkg automatically. In detail, the deploy script will create a release on github if the build pass, which will trigger another build on Travis-CI, in which the deploy script will upload the package.

Alternatively, you can also trigger the deploy script to upload package by,

  • Create release on github manually
  • Push a tag to github, with the tag name similar to v2.3.2

@@ -266,6 +266,26 @@ RunTests() {
fi
}

BootstrapDeploy() {
if [[ -z ${BOOTSTRAP_DEPLOY_COMPLETE} ]]; then
curl -OL http://raw.github.com/luckyrandom/r-travis/master/scripts/github-release.rb
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably luckyrandom should be changed to craigcitro here, at least after merging.

As suggested by krlmlr, environment will not be propagated to the
calling shell.

Since deploy script should be called only once, we don't really need to
protect  BootstrapDeploy from multiple running.
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.

None yet

2 participants