I am evaluating Stash, JIRA, Jenkins, Confluence integration for Continuous Integration. Part of which, need to list of the various functionalities can be achieved through this integration.
Can anyone provide these details.
That's an essay question - you can do all sorts of things with those systems, and we don't know what you are actually looking for - we could give you hundreds of things they could do and not tell you anything that's relevant.
What do you want to do?
If it's simply "everything for Continuous Integration", then the answer here is simply "Yes, it does it" (Although I'd seriously look at Bamboo instead of Jenkins)
I've seen several DevOps world and the most common way I've seen so far is:
You start with planning, designing in JIRA (issue tracking, use JSW for Agile), begin your development with Stash (source code repository), use JIRA for test cases (natively, you can do that if you want more optimized test case handling and have some money to burn, evaulate JIRA Capture or Zephyr add-on). Build/Deploy your codes to different environments using Jenkins. Document and/or display JIRA issues (per version, per sprint), display charts/gadgest in Confluence.
There's an add-on for Jenkins to JIRA on which Jenkins will update the JIRA issue for the status of the build (FAIL, SUCCESS, WARNING). Stash will update the Development section for the source code changes. So on this setup, you can see everything on a JIRA issue.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs