One of the most commonly asked questions these days is “Should all our source code be in one repository?” This is a complex question and leads to a somewhat interesting set of answers.
Before we get to that lets try and understand the question a little more and find out why customers asking this? In IT we like to centralize and optimize. Gathering all the code in one place is seen as the next logical set of distributed data ripe for centralization and optimization. All in one place meansRead More
In the next few weeks Serena is going to be announcing important new versions of our ALM, Release and Deploy solutions.
Ever since Serena’s CEO, Greg Hughes, introduced the concept of “Move Fast Without Breaking Things” at our User Conference in Washington DC in February, we have seen an overwhelming acknowledgement from our customers and partners that this is the perfect encapsulation of what modern application development and deployment means to them.
For Highly Regulated Large Enterprises (we callRead More
As the leader in deployment automation, Serena is a proud sponsor of the Jenkins User Conference 2015 World Tour. Come visit us at our booth and meet our experts in DevOps, CI/CD and enterprise release management.
Network Learn Explore @ the largest gathering of Continuous Integration and Continuous Delivery experts on the planet.
Want to tap the collective knowledge of a vibrant community of CI/CD practitioners? How aboutRead More
DevOps turned five last October, and while five years seems like a long time in terms of the technology adoption lifecycle, DevOps and Continuous Delivery still seem perched on the Enterprise IT chasm. The Pragmatists get it. They are under pressure from the business to deliver business value faster, better and more cheaply and the Visionaries and Early Adopters have proven that Continuous Delivery fits the bill.
The problem is that Enterprise IT canRead More
Greg Hughes talked about the need to “Move Fast Without Breaking Things” and his first love … a 128k RAM, twin 320kb floppy, 32lb “portable” computer. He drove home the critical need of modern organizations to create an infrastructure environment that supports dev teamsRead More
We were joined by one of our early adopters of the innovative Dimensions CM 14 release, Carmelette Benson of Health Care Service Corporation. The VUG was treated to an exceptional upgrade story that engaged the free Upgrade Lab to advance their planning and readiness, and worked collaboratively withRead More
Well! We’re all set to go! We have a great agenda, a fantastic lineup of speakers and some fun activities planned. If you haven’t registered yet there is still time – you can register here.
Let’s take a quick tour of the highlights …
Once the developer checks in a change, how long does it take your organization to deliver it to the customer? The path to production can take many turns, have many dips, and fall short in terms of quality and expectations. IT organizations struggle with major process and toolchain gaps between develop, build, deploy, and release. Come join us at the December Serena DevOps Drive-in as JulianRead More
This blog is a follow up to a topic presented at xChange2015. It presents a 3rd solution to the dilemma of how to use native SBM reports to show listings of items alongside current SLA data. While the two solutions offered in previous blog entry (How can I do SLA Reporting via Standard SBM listing Reports?) offered viable solutions, there were some limitations to both.
In Release Control 6.0 Timeline: Part 1 we learned the basic anatomy of the timeline view and how to access and use the timeline editor. The first post focused on customizing the out of the box Release Train timeline. In this post I will show you how to create a new timeline and add it to work center. The end result of this tutorial will be a new timeline which you can access by URL that is added to a dashboard in work center.
Serena Release Control 6.0 comes with a new and powerful gantt report that we call the timeline. Starting with RLC 6.0 it is decoupled from the processes that we ship with and fully configurable. In order to be successful in customizing the timeline or even creating new ones from scratch (details coming in part 2) it is important to understand the anatomy of the timeline and the terminology we use in the editor.
SBM Application Repository exposes web services which can imported into Composer to perform repository operations. These SOAP web services can be used in orchestrations to automate deployment and promotion operations. I would like to present a small process application with orchestrations which provides a way to retrieve all process application and snapshots from an SBM Application Repository instance.
We recently released a brand new version of Release Control (RLC), version 6. One of the many things we added in this release is a new Provider Interface that makes it much easier to integrate with any tool, including Serena tools. Along with the release, we provided out of the box providers for SBM, SDA and Dimensions CM with more to come.
In this blog post, I am going to show you how to leverage the SBM Provider to be able to reference Changes from Serena Service Manager (SSM), which is our ITSM product built on SBM, in a Release Package.
SBM Patch Context can often confuse SBM users, so I have put together a slide and this blog to explain. The slide may look busy but please look at it as a story and timeline, working from the top left across and then down through time.
Pulse has gone through some major functional enhancements in 14.2. In 14.1 it was only possible to trigger a Jenkins Build from a delivery. In 14.2 there is a whole range of experts that call various development tools that report on and help control the quality of deliveries made into the CM repository.
The PMD Expert
In the first of a series of articles we are going to look at the PMD development tool and how you can harness this technology from within Pulse.
The PMD expert is used to analyse primarily Java source but also code from various languages and detects common coding flaws such as unused variables, empty catch blocks etc. PMD is bundled with Pulse, which means it comes pre-installed and ready to use within a Pulse Expert Chain.
Serena Release Control 6.0 introduces us to request providers and request collections. These features give much more flexibility in being able to relate requests, especially 3rd party requests, to SBM items. You are able to relate requests from multiple sources - SBM requests, Dimensions Requests, ServiceNow tickets, and JIRA issues - and view this list of items in one place.
To view the related requests, you must add the Request Collection widget to your application. By default, only the Release Package application has the Request Collection widget, but you can easily add the widget to other of your SBM applications, such as Release Trains or Application Releases. The only requirement is that you have Release Control 6.0 installed.
Some pilots will have installed the default Derby database. As part of going into production implementers may want to migrate what has been implemented into the production database.
Note: Derby is to be used for prototyping/testing/evaluation purposes only.
Many of the most common questions about new releases revolve around the platform matrix. What operating systems will be supported? Will it support the latest browsers? When will the older versions of the database be dropped from the matrix? These questions are important because you need time to plan for any changes that are happening - either with your own environment or due to changing support within the product. To help with any such decisions, I'd like to share our current thoughts about what is changing in the next major release of Version Manager. The next major release is tentatively planned for release summer 2016.
Deploying applications is often as much about "updating configuration" as it is about deploying the files of the application itself. Configuration is often used at runtime by application servers, it is stored in files (property files, XML files etc) and needs to be updated based on the environment in which the application is running. One nice feature of SDA to support this is Configuration Templates. In this blog we will look at how to make use of them.
Many SBM Composer users are familiar with the REST Grid, a widget that permits you to return iterating results from a REST service on a custom form. For more information about this feature, take a look at the SBM documentation and these blog posts:
Application Variables are variables that can be administratively modified to change the behavior of a rule. For example, you might have a threshold value for escalation of an issue that you want to be able to change without modifying the underlying design. An item might be routed differently in a workflow if a severity value exceeds that threshold. Rules that reference application variables can also be used in the condition portion of a form action. On a form, you might want to highlight a field if the value exceeds a threshold.
***We have this working currently in 10.1.3.1 with SSM 5. However I have tested it in the 10.1.5.2 with the latest version of SSM and it is working.***
The MoreActions menu was originally included with the SSM install. All of the "out of the box" applications for SSM like the CMDB, CRM, Incidents, and Service Requests use this menu style to display actions and transitions. However, there was no native way to include it in your custom forms. So, I spent some time pulling it apart and found out that it is actually pretty easy to include. There are some key dependencies and elements that your form will need to include that I will explain below.
In this article, we'll drill down into the use of Custom Endpoints for REST Grids. As discussed in another blog post, custom endpoints are process app endpoints defined explicitly in Composer as opposed to endpoints created automatically for an imported WSDL or by a REST Grid widget configured with an URL.
The Java API provides an extensive client interface to Dimensions CM allowing users to create and manipulate versioning, change management, and process modelling data while under the control of the permissions of Dimensions CM and the change management rules framework.
Have you ever been in a situation where a fix applied to one stream was urgently required in another?
This often happens when a bug fixed in a future release is escalated and needs to be included in a patch release. Each patch typically has its own stream so you need to merge the fix from the feature or mainline stream to the patch. To restrict the merged code to the exact bug-fix you need to cherrypick the changes carefully.
Dimensions CM 14.1.x and earlier supports regular request merge but not cherrypicking.
The REST Grid can easily display flat lists of data returned from a REST Service, but what do you do when the service doesn't cooperate? This blog post will describe a new feature in SBM 11.0 that let's you do something about it.
With every release of SBM, the Composer team works to provide new features that make your life as a developer easier, or empower you to provide superior applications for your end users. SBM 11.0 is no exception. In this blog post, I'll preview some of the new Form features for Composer in the SBM 11.0 release.