git,maven,svn,jenkins,atlassian-stash
You can setup different jobs to build different projects, even though all of them will checkout your full repository on master branch with all other projects. If you put your whole repo in config, it doesn't mean that Jenkins will build ALL projects. The only issue is disk space, every...
maven,atlassian,atlassian-stash
Aswani, Looks like you've overwritten the default maven repositories for the atlas-* commands with your own local Nexus server. As Artem pointed out, Atlassian has it's own Maven repositories that you would have to add: https://developer.atlassian.com/docs/advanced-topics/working-with-maven/atlassian-maven-repositories Also I suspect there is some etiquette around raising the same question more than...
After looking in to this a bit more, I've realized that you can't really just stop using Stash and continue to access the same repo on the same origin. The origin of a repo checked out from a Stash server points to that Stash server which is what manages access...
I think the commit messages (as opposed to pull request descriptions) are not stored separately in Stash, they are retrieved from git as needed. The Stash documentation lists the available Java APIs to access Git from within Stash plugins.
If it's the last commit, it's easy: git commit --amend This brings up the editor with the last commit message and lets you edit the message. (You can use -m if you want to wipe out the old message and use a new one.) And then when you push, do...
osx,git,ssl,osx-mavericks,atlassian-stash
Solved it! (With a little help from this question, but a slightly different solution.) Browse to the repository in Stash. Click the little 'https' icon in the address bar. Click Show Certificate. Drag the little certificate icon onto the desktop. Open the Keychain Access utility (type it into Finder). In...
The problem was a malformed URL: it should be https://[email protected]/scm/~username/project.git instead of [email protected]
python,git,python-3.4,atlassian-stash,gitpython
Instead of using http use ssh. Once you set up your ssh keys the authentication is done "silently" with the ssh keys and there will be no need to enter password ever again. Generating ssh keys: ssh-keygen -t rsa -C '[email protected]' Once you create your keys add them to the...
git,email,jira,atlassian-stash
In general the work flow you use requires Git Integration Plugin for JIRA or JIRA DVCS Connector (if you are using Bitbucket or Github) so I assume you use that. An alternative is to use the JIRA REST API to handle your tickets with git hooks - this should trigger...
git,git-merge,merge-conflict-resolution,atlassian-stash
Normally you don't create a new branch to resolve conflicts. Instead you merge the target branch into your pull requests's branch: git fetch origin git checkout my_pr_branch git merge origin/master <resolve conflicts and commit the resolution> git push origin my_pr_branch` If you keep seeing conflicts at stash – someone else...
As of version Stash 3.11.x This not possible. If you want you can create a plugin which would allow you to do this - there are none on the market currently. More on plugins: https://developer.atlassian.com/stash/docs/latest/how-tos/creating-a-stash-plugin.html...
git,git-merge,git-push,git-pull,atlassian-stash
You can merge both branches with git merge. I don't recommend using git rebase on this case since you said both branches have already been published to the repository server. I've created the following situation (described on your post): $ git co A $ git lg --all * 4df39d7 -...
git,github,jenkins,atlassian-stash
The Post-build "Git Publisher" step will push the current HEAD to a designated remote on a git repository specified among your "Git Repositories". To configure: add both your private and the stash repository to Git Repositories, specify the "branch to build" to the target branch from your private re. Create...
git,ssh,ssh-keys,atlassian-stash
Check /var/log/auth.log or journalctl -u sshd for any information, such as invalid permissions on keyfiles. Another usual mistake is also to have a typo on authorized_keys.
code-review,sonarqube,static-analysis,atlassian,atlassian-stash
Try Sonar for Stash addon (evaluation licence). I am currently testing it on the same workflow as yours: Create a pull request A Jenkins build is triggered If the build succeeds and the thresholds on the static analysis are met, the pull request is authorized Need SonarQube 4.4+ to get...
jenkins,git-stash,atlassian-stash
On your Jenkins master, you need to generate a public key for the jenkins user (or the owner of the jenkins process): ssh-keygen -t rsa (with no paraphrase) Next, go to ssh folder ~/.ssh and copy the content of the id_rsa.pub file. With Stash, go on the relevant project/settings/Access keys....
svn,iptables,atlassian-stash,subgit
iptables -A INPUT -i lo -j ACCEPT iptables -A OUTPUT -o lo -j ACCEPT Did it....
ant,scp,bamboo,atlassian-stash
Ok I figured out a way to complete what I was looking to do. Basically, I ended up creating a few more targets in my ant build file that (re)moved files to achieve the structure that I wanted.
To recover: Use git reflog to find SHA1, then use git checkout <sha>. To track down: Use git log to see all commmit logs - http://git-scm.com/docs/git-log...
git,ssh,git-pull,atlassian-stash
Firstly you have to add ssh://[email protected]****.net:7999/project/project.git as your remote origin: git remote add originSSH ssh://[email protected]****.net:7999/project/project.git And next call git pull originSSH name_branch And then you can checkout on your branch git checkout originSSH/name_branch -b name_branch ...
git,github,git-stash,atlassian-stash
When you set-url the URL for the origin remote, you removed the original location, which is that of the GitHub repository. In Git, you can have many remotes, and the default name for the one you cloned from is origin. You should add another remote (I usually call it upstream)...
git,selenium,automated-tests,build-automation,atlassian-stash
You're looking for a Continuous Integration product - this will allow you to do what you're asking. Some popular names are: https://www.atlassian.com/software/bamboo https://jenkins-ci.org/ You can define a build plan there, which will watch your repo for changes and kick off a build when there are changes. Your tests can be...
seems i had a mis match in java versions. setting JAVA_HOME to the right version helped
atlassian-stash,atlassian-plugin-sdk
Ok so even though the CommitsBetweenRequest page on the Atlassian stach api documentation is one of the few pages with an explanation it took some trial and error to figure this out. GetCommitsBetween works but heres the trick... set the CommitsBetweenRequest.exclude to the starting commit in the change set and...
Just use its last merged commit id in place of the branch name, branch names are just repo-local synonyms for commit ids anyway, plus some local notes for defaults and such. merge=$(git log --merges --format=%H --grep="Merge branch '$branchname'" | sed q) will get that commit unless you're integrating commits to...
linux,git,git-stash,atlassian-stash
Go to current working directory to your local project and run following commands: Step 1 : Initializes a new Git repository. Until you run this command inside a repository or directory, it’s just a regular folder. Only after you input this does it accept further Git commands. git init Step...
git,ssh,capistrano,capistrano3,atlassian-stash
A simplistic answer, but I would guess that Capistrano is picking up the wrong key. I'd suggest that you check the default ssh key for the deployment user. So, if capistrano is set to log into the server using deployuser, see what key deployuser picks up. It can be helpful...
Yep you can do it by using hooks. Go to your setting section, hooks and search for the suitable hook for you, install it form the market (or write your own hook if you know how to) and set the required permissions. How to do it? Add code to the...