I need to automatically create multiple branches on a Bitbucket repo when a developer creates a branch from a Jira Issue.
The branching pattern is this:
feature/SAx
feature/SAx-FE
feature/SAx-BE
So I would need to automatically create the feature/SAx branch and then split this new branch into the FE and BE branches.
How can I do this?
Thanks!
Related
I'm wondering if there is a way to create a single shortcut in IntelliJ that does multiple consecutive actions.
For example, the following actions are needed to deploy a service:
check out the master branch
pull changes
check out the production branch
pull changes
merge the master branch into the production branch
push changes
Each of these actions can be done with a shortcut (and a bit of typing/selection in the case of the checking out), but I would like to do all of these in this order with a single shortcut.
I want to create a trigger like this, when a specific branch pattern is created in codecommit it must invoke codebuild project , eg : prod/myapp-{version} (We will create release branch like this always, like prod/myapp-V1.2 , This was easy in jenkins as it has branch filter regex like '/prod/' and it will checkout latest branch starting with prod/myapp-{version} and start build) , the same way I need to implement in codecommit + codebuild. How can I do that ? Am not seeing the option for branch pattern in codebuild , only static branch name (like master, or tagname) .So it will checkout only the static branch(eg: master) . What I want is how I can pass branch pattern to codebuild as ${Version} is always dynamic . I am new to AWS devops. Any help will be appreciated
Thanks
We use JIRA in our organisation. I am unable to find the branch tag/commit-id against particular feature. Is there something I'm missing?
To understand a feature I want to understand all the changes that were made for this feature. How do I go about finding them?
Assuming your JIRA is connected to some kind of source code management (Bitbucket or Github). The branch / commit name must contain the JIRA issue key.
Jira: assign an existing git branch to an issue
Creating the branch though the UI is just a convenience. The important thing is that the name contains the JIRA key. If only one developer is working on the branch, it's fairly easy to just rename (delete + add) a branch with the appropriate name.
To find all branches / commits related to an issue, there's the Development Panel on the sidebar right.
The jira key in the git commit message we found needs to be in uppsercase, well case senstive depending on what you set in the integration.
I'm having different project structure in each branch, is it possible configure different jobs/ tasks for each branch in bamboo? If not please suggest me any alternatives.
It's not possible to configure different tasks per branch in Bamboo. I can suggest 2 alternative ways:
You can use branch "Variables", use the Script task and have different manipulations based on the branch variable.
And if your project structure is really different per branch, I would suggest you to create a new plan for it.
Lets say there exists a MASTER repository with 2 different branches(branch A and branch B) already created for it. I've already cloned master and have a local version of that on my machine. If I pull branch A, checkout to branch B, and do another pull with branch B, do the codes from branch A and branch B get "merged" together? Meaning at since I pulled both of them once already, at any one point in time that I am working on a particular branch, am I working on code that is a combination of both branches? I would not think so. I would think that each branch that I'm working on has its own particular instance and is independent of other branches correct?
If you do the following sequence while in a repository containing two branches A and B, A and B should be independent
git checkout A
git pull MASTER A
git checkout B
git pull MASTER B
However, if you do something like this you'll end up merging A into B
git checkout B
git pull MASTER A
I think this might shed some light on what a branch is and how to do various workflows, as well as a lot of tips/tricks for using Git in general.
http://git-scm.com/book/en/Git-Branching-What-a-Branch-Is
As a best pratice when working with branches, I always set the target branch for a pull.
git checkout branchB
git pull origin branchB
You can if you like pull from branchA and merge with it too
git checkout branchB
git pull origin branchA
Depends in what you want to do. But pulling and merging another branch fron the server blindly is not the best thing to do. In this case you want to fetch look what branchA has to offer and merge after that with git merge or rebase.