DevOps Day 1 and DevOps Day 2 - Both are about saving time (and that saves cost)
DevOps Day 1 and DevOps Day 2 are terms used to talk about the big phases of DevOps maturity. DevOps Day 1 competency means that the DevOps team has automated continuous integration builds (with Jenkins, for example) and are doing automated, continuous deployments to dev and test, maybe even prod (with UrbanCode Deploy, for example). Automated tests are run during the continuous integration builds to check for security vulnerabilities and code flaws. Many, if not most IBM customers have DevOps Day 1 down and are either onboarding new applications to their DevOps pipeline or covering new platforms like IBM Z or IBM i or container platforms. Learn more about a DevOps Day 1 tool, UrbanCode Deploy here
DevOps teams who have entered DevOps Day 2 are looking to optimize the DevOps processes they have in place. These teams are looking for ways to improve delivery time and to understand the value stream that goes from an idea (captured in an Epic for a sprint) all the way to production when it becomes available to customers. How can I go faster? What can I do better? UrbanCode Velocity provides the visibility into the delivery pipeline, data analytics and value stream management needed to optimize a decently running DevOps pipeline. Learn more about a DevOps Day 2 tool, UrbanCode Velocity here
Both products released new versions this month.
New in UrbanCode Deploy 7.2 - Available June 25
UrbanCode Deploy is an application-release solution that combines continuous delivery and deployment automation with robust visibility, traceability, and auditing capabilities. Newest updates:
- API Changes for Delete Application Process. Support for a Command Line Interface (CLI) API that enables the deletion of application processes.
- New Artifact Cleanup Permission. A new permission setting that separates cleanup permission field editing from the other basic settings. This feature enables strict enforcement of cleanup policy while still providing UrbanCode Deploy teams with the capability to modify the other fields in their components and environments.
- Option to specify JAVA_OPTS for Source Control / Non-Groovy Scripts
- Documentation on how to silently install UrbanCode Deploy agents.
- UCD Containers updates
- UrbanCode Deploy plug-in for MuleSoft third-party integration software for connecting applications, data, and devices.
- Z/OS deployments
- z/OS component v2 comparison report plugin. Usehis new plug-in to compare z/OS components, providing the capability to compare two UrbanCode Deploy component versions (in the new component format) with a textual output of the differences
- Artifactory/Nexus plugin enhancements
- Publish runbooks / videos for zOS deployment features using newer plugin improvements
- With version 7.2 of UrbanCode Deploy, the previous server-agent communication model, JMS, is no longer shipped with the UrbanCode Deploy product. The JMS agents will continue to be supported. However, to upgrade to UrbanCode Deploy 7.2, or later, the JMS agents must be converted to Web agents. For information about how to migrate your agents, see the IBM UrbanCode Deploy website.
- With version 7.2, the Blueprint Designer ends support for OpenStack Heat. Blueprint Designer will continue to support the use of Terraform.
- IBM UrbanCode Deploy will no longer support Java™ 8 starting June, 2022. Additional information about alternative Java platforms will be communicated later. For information about IBM UrbanCode Deploy on the z/OS platform, see the IBM Statement of Direction.
Statements by IBM regarding its plans, directions, and intent are subject to change or withdrawal without notice at the sole discretion of IBM. Information regarding potential future products is intended to outline general product direction and should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for IBM products remain at the sole discretion of IBM.
New in UrbanCode Velocity 2.4 - available June 22
UrbanCode Velocity enables value stream management, pipeline orchestration, and near real-time analytics to help DevOps teams visualize work and the creation of value as development proceeds from idea to client.
- Deployment orchestration support for open pipeline and application mapping to unify existing applications between the VSM and Pipeline. When a CI/CD tool other than UrbanCode Deploy or Jenkins (which are integrated with UrbanCode Velocity), integrates with UrbanCode Velocity through its open pipeline API, it can now be orchestrated by UrbanCode Velocity.
- New Plugins: Acunetix, Rapid7, Sonatype, GitLab (Build), BMC Remedy
- Expanded Git branching support for more complex merge and release strategies
- New and improved reports for IBM UrbanCode Deploy
- API-driven Capability to join any release capability (scheduled, in progress, or complete)
- Automatically generate user access keys during integration configuration
- IBM CloudPak changes and requirements.
- Defect, performance, and security fixes.