I have two Jira instances (both are Jira Cloud) and the same project in both.
Historically one Jira is used by dev team and second Jira is used by ops.
However, some dev tasks have to be considered by ops team.
So the question: is it possible to sync issues from one Jira to other Jira?
Yes, it is possible to sync issues from one Jira to another, however, this will require you to install additional add-ons to your Jira instances.
In the marketplace you have several available solutions:
Backbone Issue Sync for Jira
Exalate Jira Issue Sync & more
Issue SYNC - Synchronization for Jira
You can trial all of them and pick one that suits you the most. Or in extreme case, if you have some programming skills you could develop such add-on yourself, however, if you include maintenance and hosting costs it's probably cheaper to buys an existing solution.
I'm sure you are aware that you don't have that much flexibility in Cloud. However, check if Backbone Issue Sync plugin can help you or not. In Server it's possible to do it via Issue Sync Plugin.
In a Devops context, Who is the responsible for the automation tasks ?
more exactly in the case of "pipeline as a code" in jenkins . who is supposed to do this task ? the devoloper or the operator ?
who is the actor ?
"The key to DevOps is greater collaboration between engineering and operations."
Roles : DEVOPS
Responsibilities :
1. Management : The DevOps Engineer ensures compliance to standards by monitoring the enterprise software and online websites. The engineer also regulates tools and processes in the engineering department and catalyses their simultaneous enhancement and evolution.
2 Design and Development : Design and Development of enterprise infrastructure and its architecture is one of the major responsibilities that DevOps Engineers are tasked with. Such Engineers are highly skilled coders which enable them to script tools aimed at enhancing developer productivity.
3 Collaboration and Support : The DevOps’ Modus Operandi is to collaborate extensively and yield results in all aspects of their work. Everything ranging from technical analyses to deployment and monitoring is handled, with the focus to enhance overall system reliability and scalability. The diagram below gives one a clear picture of the values that define DevOps.
4 Knowledge : DevOps staff and Engineers aid in promotion of knowledge sharing and overall DevOps culture throughout the engineering department
5 Versatile Duties : DevOps staff and Engineers also take on work delegated by IT director, CTO, DevOps head and more. They will also perform similar duties to the designations mentioned above.
Standard Definition :
DevOps is an IT mindset that encourages communication, collaboration, integration and automation among software developers and IT operations in order to improve the speed and quality of delivering software.
Layman's Definition :
Any kind of automation that enables the opportunity for smoother Development, Operations, Support and delivery of the product is DevOps.
Indrustry's View :
There usually are two prominent area's where DevOps mindset is applied across industry :
a) Primary functionaries of DevOps like
• Continuous Integration,
• Continuous Delivery,
• Continuous Deployment,
• Infrastructure as an code or infrastructure Automation,
• CI/CD Pipeline Orchestration,
• Configuration Management and
• Cloud Management (AWS, Azure or GCP)
b) Secondary functionaries of DevOps like
• SCM tool Support,
• Code Quality tech support like Sonar, Veracode, Nexus etc.
• Middleware tech support for tools like NPM, Kafka, Redis, NGIMX, API Gateway, etc
• Infrastructure tech support for components like F5, DNS, Web Servers, Build Server Management etc
• OS Level support for miscellaneous activities lke Server Patching, Scripting for automation of server level tasks etc.
There is no exact answer to this. It depends on many factors.
The development team will most likely want more ownership over the pipeline, and therefore would want to own the templates / code required to achieve the end goal of automation.
The opposite side of this is also completely valid. An operations team could be the custodians of a pipeline and mandate a development team must meet certain standards and use their automation pipelines to be able to get into an environment or onto a platform.
If an environment is an island, and development teams are trying to get to that island. Each development team can build their own bridge to get there. Or the operations team can build a bridge and ask the development teams to use it. Both are valid and the end result is the same either way.
If the end result is the same, then the only thing that matters is how you apply it in the context of the organization, team(s) and the people you are working with to achieve that common goal.
The assigned developer (and scrum team) should be responsible for the complete delivery of all aspects of development through final deployment into production. This fosters the notions of ownership and empowerment, and focuses responsibility for the full life cycle delivery of the service (application).
DevOps engineering should be responsible for providing an optimal tool chain and environments for rapid and quality delivery. I see DevOps role as the development focused precedent to SRE. If SRE's maintain high performance, stable production environments, then DevOps team maintains optimal development and testing environments. In theory, DevOps should extend into the realm of SRE, conforming into a single team supporting the environments for rapid innovation with quality to meet the business needs.
Everything from committing of the code to production. This includes
Automation
Production Support
Writing automation scripts
Debugging Production Infrastructure
In short Devops = Infrastructure + Automation + Support
We are using Jira to manage the flow of development of a single application in a Scrum development team.
We want to extend the usage of Jira to include the other applications and micro-services on which the main application relies.
They run with the same development team and monthly release cycle, so we'd like to share the Versions and Epics, having them affect multiple services.
We use Bamboo and Bitbucket and would like to make sure that the requirements for making a particular release is clear in Jira (tracking the links between the stories, software versions and services that need to be released).
If find it hard to see clear advice from Atlassian that points to a particular design, though suspect that components give us what we need.
Has anyone else implemented something similar.
Are components the way forward? Or is something more bespoke / a plug-in a better route?
I'm trying to make an application that will allow a user to initiate builds, see build info etc, and just general TFS based actions.
I've found a few guides on how to use the SDK... http://msdn.microsoft.com/en-us/library/bb286958.aspx
But I can't use the TeamFoundation.*.dll's in the metro/win8 app... http://msdn.microsoft.com/en-us/library/windows/apps/br230302(v=vs.110).aspx
so, is there an alternative? Do they have a separate api? (you can access a tfs project via the web access, providing a web based alternative from doing it all in visual studio).
Thanks,
james.
Windows RT is an ARM based surface and the TFS SDK/OM is only available compiled for x86. So, it will not work.
Windows Surface PRO available later will be x86 based.
The closest you could probably get is if you coded directly to the SOAP web service layer directly. The TFS team is also starting to create RESTful http APIs with light http clients but that's a work in progress that's just starting. That would be the long term approach available someday.
If you're creating a Windows store app, you should note that it's sandboxed. The TFS team is looking into that as we transition toward REST and a more modern REST client.
My company are imposing Jira and Zephyr on us for defect tracking and test management. We're quite happily using TFS 2008 for both these jobs at the moment, but management have never let the fact that something isn't broken stop them from trying to fix it.
Are there any tools/plug-ins that will allow us to synchronise between the remotely hosted repositories and our in-house TFS server?
Probably too late, but the company might want to look at the new features for bug tracking and manual tests coming in the 2010 release. Nice as Jira is, I doubt it will integrate well with the historical debugger and the ability to include a video of the test, as well as information on the test environment, and have it all be part of the work item.