I have integrated ServiceNow DevOps with Git, Jenkins, or Jira in my development process for several customers. We integrate directly with the tools in some cases, and in other cases we use something in the middle, for example, making an integration using email systems to open tickets or something similar. We manage integrations of customer tools with our tools across all of them. I used a different solution for the same use cases before ServiceNow DevOps. Internal ones from here and other tools were tested and implemented, such as Jira, for example. We were working with our internal own scripts with automation for our products, with our internal management products such as HP compute management and HP server management that are now integrated with ServiceNow DevOps, but previously were separate. We also worked with our Salesforce.com environment for ticketing. There were different tools that we managed in the past. I work daily with cloud backup, cloud management, or software-defined storage solutions during these weeks. At this moment, I am not using ServiceNow DevOps's machine learning capabilities to predict and prevent failures. However, this is part of our improved ideas to pursue in the future. In this case, I am using a tool called HP Hybrid Operation Console, which is based on several tools, but the central one is ServiceNow DevOps.
My company is in the process of integrating Azure DevOps with ServiceNow. The solution is mainly used for deployment purposes with change requests whenever there is a need to do production, deployments, or staging, depending on the environment. My company mostly uses the solution for the functionality known as CMDB that it provides, especially to handle whatever resources we create in our company and to take care of the storage related to its Azure part.
Head of business transformation and digitalization at Apple
MSP
Feb 9, 2022
We use this solution for operation and support. If we develop a certain project, we use ServiceNow for the ops side. That's why it's DevOps, meaning development. Ops is the operations wherein users can file tickets, or we can create tickets for a change management. For example, a change ticket or a request ticket for enhancement or for incidents that are bugs, et cetera. Our team is DevOps, so we develop and are also part of operations. If there's a problem with the application, they log a ticket in ServiceNow. A ticket is assigned to us. Then we work on the ticket. We do the documentation and resolve it. There are times we transfer that ticket, so we are using the ServiceNow system to do all of that. We also use it for Power BI. I connect Power BI directly to ServiceNow using Dash API.
ServiceNow DevOps enables IT teams to automate change management tasks such as planning, development, testing, deployment and operations via a single dashboard surfacing a common set of metrics, he said.
I have integrated ServiceNow DevOps with Git, Jenkins, or Jira in my development process for several customers. We integrate directly with the tools in some cases, and in other cases we use something in the middle, for example, making an integration using email systems to open tickets or something similar. We manage integrations of customer tools with our tools across all of them. I used a different solution for the same use cases before ServiceNow DevOps. Internal ones from here and other tools were tested and implemented, such as Jira, for example. We were working with our internal own scripts with automation for our products, with our internal management products such as HP compute management and HP server management that are now integrated with ServiceNow DevOps, but previously were separate. We also worked with our Salesforce.com environment for ticketing. There were different tools that we managed in the past. I work daily with cloud backup, cloud management, or software-defined storage solutions during these weeks. At this moment, I am not using ServiceNow DevOps's machine learning capabilities to predict and prevent failures. However, this is part of our improved ideas to pursue in the future. In this case, I am using a tool called HP Hybrid Operation Console, which is based on several tools, but the central one is ServiceNow DevOps.
My company is in the process of integrating Azure DevOps with ServiceNow. The solution is mainly used for deployment purposes with change requests whenever there is a need to do production, deployments, or staging, depending on the environment. My company mostly uses the solution for the functionality known as CMDB that it provides, especially to handle whatever resources we create in our company and to take care of the storage related to its Azure part.
We use this solution for operation and support. If we develop a certain project, we use ServiceNow for the ops side. That's why it's DevOps, meaning development. Ops is the operations wherein users can file tickets, or we can create tickets for a change management. For example, a change ticket or a request ticket for enhancement or for incidents that are bugs, et cetera. Our team is DevOps, so we develop and are also part of operations. If there's a problem with the application, they log a ticket in ServiceNow. A ticket is assigned to us. Then we work on the ticket. We do the documentation and resolve it. There are times we transfer that ticket, so we are using the ServiceNow system to do all of that. We also use it for Power BI. I connect Power BI directly to ServiceNow using Dash API.
We use the solution for our entire internal idea simulator, with new feature functionality, ID, and product management development.
We use it for ITIL. It is our everyday tool for ITIL.