bitbucket

Atlassian Bamboo: Handling git-Flow hotfix-branch

半城伤御伤魂 提交于 2019-12-06 12:47:33
问题 At our company we use Jira, Bitbucket and Bamboo. Our repository is organized in the git-flow schema: develop-branch = Application code for testing (aka Release Candidate) master-branch = Application code running live feature-branches = new components based on actual dev-branch merged via pull-request hotfix-branches = new hotfixes based on master-branch merged into develop and master via pull-request Our versioning system works like the following: Now I'm trying to integrate our structure

Using BitBucket repo in Github App (Mac OSX)

走远了吗. 提交于 2019-12-06 11:29:07
问题 I´m new to mac osx system and in windows i have set a repository from bitbucket in github app successfuly. Now in Mac OSX i can´t drag the url from the BitBucket page (and i pull the commits locally to bb). Is there a way to do this?? Sorry for my bad english! Thanks for the future responses! 回答1: You can clone the repository locally and add it like they explain here. Alternatively, you can clone it directly from GitHub for Mac like in here. 来源: https://stackoverflow.com/questions/18281164

Bitbucket issues section useless when connected to JIRA?

时间秒杀一切 提交于 2019-12-06 11:09:54
I have connected Bitbucket repo with JIRA project. Now when I commit to Bitbucket, I can reference JIRA issues or I can create branches in Bitbucket repo from JIRA and view commits from JIRA. However, when I create an issue in JIRA or an issue in Bitbucket, they are not being synced. I have not found any tutorial about this. Does this mean that Issues section in Bitbucket is useless when we connect it to JIRA? Is Issues section on Bitbucket only for repos that are not connected to JIRA (and I should turn it off in repos that have JIRA connection? I am sure this is easy answer for someone who's

Getting an SSL error with Mercurial on Bitbucket due to TLS

纵饮孤独 提交于 2019-12-06 10:48:14
It seems that Bitbucket has now blocked TLS 1.0 and 1.1. I am working in Eclipse on Mac OSx 10.12.6 using the MercurialEclipse (hg) 2.2 plugin. I was receiving SSL handshake errors whenever I tried to pull from the remote Bitbucket repository. I tried updating the plugin and doing a fresh install, but it still gave the same error. Then I tried downloading and installing the latest Mercurial package (4.8) from the mercurial web site. After doing this the error changed to this: warning: connecting to bitbucket.org using legacy security technology (TLS 1.0); see https://mercurial-scm.org/wiki

How to specify version with git smart commits?

被刻印的时光 ゝ 提交于 2019-12-06 10:02:10
I'm using BitBucket and Attlasian Jira. They are linked between each other so i can resolve an issues just with git comment: git commit -m "BUG-123 #resolve #comment My comment" My question is. Is it possible to specify fix version with smart commit feature? According to the JIRA DVCS plugin API documentation , there are three commands you can use: #time #comment #<transition> There is no direct command to use to select the fix version, but you could likely set up a trigger or a hook in the JIRA system that will select a fix version for you upon transition, but there's no way to do it using

TeamCity with BitBucket Cloud Commit Status Publisher. 404 Errors

筅森魡賤 提交于 2019-12-06 09:34:42
问题 I'm having problems getting the commit status publisher to work. Details: TeamCity 9.1 Commit Status Publisher Plugin version: snapshot-20160523141816 Bitbucket Cloud git repository type on bitbucket.org VCS Settings: Configured to use the private key auth (w/ uploaded key) Multiple branches configured. Not using VCS Labeling No PUSH URL specified (should be failing back to FETCH URL, right?) Commit Status Publisher Settings: I've experimented with these settings, neither email addresses nor

Git - End of line characters causing fake diffs

我怕爱的太早我们不能终老 提交于 2019-12-06 09:09:56
I have a git repository which is hosted in bit bucket. I use source tree to work with git. I have a pull request in which some files appear as modified, but the contents of the file are essentially unchanged. I noticed that when I compared the two branches in bit bucket and source tree. This is what the diff looks like in those tools : -j1 -j2 -j3 +j1 +j2 +j3 This is very confusing because (1) it makes it appear as though there are many changes, even though there are no real changes, and (2) any changes to a particular line could be missed if you have a huge file (unlike the small one I showed

Is it possible to download ONLY files changed in a commit/revision using git archive

℡╲_俬逩灬. 提交于 2019-12-06 08:20:41
问题 Using git archive commmand is it possible to download only the changed/affected files from a repository for a particular commit id ? Is it possible using the web interface @ bitbucket ? 回答1: List the files changed in a commit with git diff-tree and pass them to the command line of git archive . git archive --format=zip --output=commit_files.zip <tree-ish> `git diff-tree --no-commit-id --name-only -r <tree-ish> | sed ':a;N;$!ba;s/\n/ /g'` 回答2: You can create an archive file focused on a

Jenkins pipeline, bitbucket hook and maven release plugin infinite loop

可紊 提交于 2019-12-06 07:15:57
I haven't been able to find any info about this, so i hope you guys can help me on this one I've a maven project hosted in bitbucket that has a BitBucket WebHook pointing to someurl/bitbucket-hook/ , this hooks triggers the build of my project that is defined by a pipeline that has this structure: node { stage 'Checkout' git url: 'https:...' def mvnHome = tool 'M3' #Various stages here ... stage 'Release' sh "${mvnHome}/bin/mvn -B clean install release:prepare release:perform release:clean" } the problem is that maven release plugin pushes changes to BitBucket, and this triggers again the

Jenkins Pipeline and stash Pull Request Builder not working on PR create/update

大兔子大兔子 提交于 2019-12-06 06:57:14
问题 Below is the requirement needed to achieve using the Jenkins Pipeline and i am new bee into Jenkins Pipeline. After completing development work and pushing his changes to Bitbucket the user creates a pull request. In order to approve a pull request we require at least one successful Jenkins build. Thereby we would like to get only the build result of the code checked in for the pull request. When a pull request is created/updated Jenkins shall be triggered automatically for real continuous