search

Shippable / support

Shippable SaaS customers can report issues and feature requests in this repository
101 stars 28 forks source link

Missing recipe for committing tag from CI build #3683

Open sdlarsen opened 7 years ago

sdlarsen commented 7 years ago

Using BitBucket it's not (easily) possible to git push tags or version changes to the repository. Could you provide a small write-up on how to do that?

ambarish2012 commented 7 years ago

@sdlarsen we will add this recipe. Please can you elaborate on the not easily part - what is difficult?

sdlarsen commented 7 years ago

What would be nice to accomplish was to get a git commit with the user causing the build, not just a "CI-User". I haven't found a way to do that, so maybe the question should be rephrased "How to commit from CI with the user causing the build?" Could you come up with a recipe for doing that?

sscarduzio commented 7 years ago

I have a similar issue, I need a successful build to tag the git repository and upload the zip to S3. This enables me to have reproducible builds.

I managed to achieve everything except pushing the git tag to Bitbucket because Shippable has cloned the repo in read only.

I have no idea how to enable write access to the bitbucket repo for Shippable. Any advice?

[core]
    repositoryformatversion = 0
    filemode = true
    bare = false
    logallrefupdates = true
[remote "origin"]
    url = ssh://git@bitbucket.org/xxxxx/yyyy.git
    fetch = +refs/heads/*:refs/remotes/origin/*
[branch "master"]
    remote = origin
    merge = refs/heads/master
[user]
    name = Shippable Build
    email = build@shippable.com

 git tag v1.16.9-pre4_es5.5.0 -a -m 'Auto-tagging from build system'
 git push origin v1.16.9-pre4_es5.5.0

Warning: Permanently added the RSA host key for IP address '104.192.143.2' to the list of known hosts.
repository access denied. access via a deployment key is read-only.
fatal: Could not read from remote repository.