ItGo.me Focus on IT Recommend

Home > github - How to make travis-ci work with a local git branch instead of a specific commit?

github - How to make travis-ci work with a local git branch instead of a specific commit?

2020腾讯云双十一活动,全年最低!!!(领取3500元代金券),
地址https://cloud.tencent.com/act/cps/redirect?redirect=1073

2020阿里云最低价产品入口,含代金券(新老用户有优惠),
入口地址https://www.aliyun.com/minisite/goods

I am using git and have configured travis-ci to build whenever someone commits to the master branch. Looking at the build log, this is what travis-ci does:

git clone --depth=50 --branch=master git@github.com:organisation/my-repo.git organisation/my-repo
cd organisation/my-repo
git checkout -qf 4f177043c790dad8298db4c47eae6893c8894e0c

However, I am using a plugin called sbt-release as part of the build and deployment process, which updates the project version and commits and pushes the version changes to the git repository. I have configured travis-ci to run this plugin as part of the build script but because travis-ci is working with a specific commit, the plugin fails:

[info] Starting release process off commit: 4f177043c790dad8298db4c47eae6893c8894e0c
fatal: ref HEAD is not a symbolic ref 

I believe the solution is to make travis-ci work with the git HEAD locally rather than the specific commit. Is there a way to achieve this with the travis build configuration?

git github version-control continuous-integration travis-ci
|
  this question
edited Dec 7 '15 at 9:55 asked Dec 7 '15 at 9:49 Josh 363 3 16

 | 

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Recommend:github - How to configure Travis CI better for auto push to git branch

the static content will be available in the following sub-directory: /<commit#>.<build#>/<payload> (e.g. /925dc3e.4/index.html) The scheme itself is simple, but I'm afraid because of security reasons. I understand, that showing the passwor

------splitte line----------------------------