Recognizing the benefits of automating application release and moving to Continuous Delivery in the enterprise, Network World named Deployit as its Product of the Week.
Today XebiaLabs announced the latest version of Deployit. Deployit 3.9 adds out-of-the-box support for additional middleware stacks and automates the self-service creation of on-demand cloud environments with a single click, accelerating development and testing and freeing up Operations resources.
Major highlights include:
- New Self-Service Cloud Pack Available
- .NET Continuous Delivery
- Expert Mode Operations Control with Plan Analyzer
- Updated & Enhanced User Interface
Part of the strength of Deployit is our growing community of deployment experts. We always want to encourage users to learn, share and connect! In this week's community blog, IT Architect Jan Vermeir walks through how he created a clean up script to sweep out the Deployit repository in one go...
Our good friends over at CloudBees have just launched a valuable series of learning resources around Continuous Cloud Delivery, explaining the elements and benefits of Continuous Delivery and helping to make an appropriate choice of technologies for your implementation.
Obviously, given our full-time focus on helping our customers introduce Continuous Delivery and Deployment Automation, we're keenly aware of the need for automated deployments as part of a CD strategy. So we fully agree on an "Integrated Deployment Process" being an essential Cloud Continuous Delivery element.
Over the past several months, XebiaLabs conducted a survey to unveil the drivers behind changes in the Application Release process and the results are in. The overarching results reveal organizations regard their current Application Release processes as deficient and are actively seeking to automate “the last mile” of their release process as they look to automate their enterprise application release management to a greater degree.
The survey also shows that organizations are actively looking to implement solutions that help them move away from expensive, error-prone “big bang” releases and towards a Continuous Delivery approach.
Deployment Packages are usually created outside of Deployit. For example, packages are built by tools like Maven or Jenkins and then imported using a Deployit plugin. (See documentation of the Maven Deployit Plugin and Jenkins Deployit Plugin). Or you manually write a Manifest.MF file for the Deployit Archive format (DAR format) and import the package using the Deployit UI.
The growth of cloud services for business has been a hot topic for years now, but 2012 was the year when the cloud went from market hype to mainstream deployment. Most organizations have now adopted a private cloud of some kind, but caution is preventing them from taking full advantage.
Recent Gartner research highlights the importance of digital technologies for CIOs in the coming year. Gartner's Mark McDonald, described the problem succinctly, "IT needs new tools if it hopes to hunt for technology-intensive innovation and harvest raised business performance from transformed IT infrastructure, operations and applications. Without change, CIOs and IT consign themselves to tending a garden of legacy assets and responsibilities."
Exploring the potential benefits of new tools is vital if IT departments hope to see real performance gains, writes Andrew Phillips in Tools Journal. The article examines the challenges, why PaaS may fall short, the goals and how to work toward automation.
Together with Puppet Labs and CloudBees, XebiaLabs is hosting a webinar January 30. Register and learn how you can enhance and extend your existing infrastructure to create an automated, end-to-end IT platform supporting on-demand middleware and application environments, application release pipelines, Continuous Delivery, Private/ hybrid development platform and PaaS and more.
The first Jenkins User Event was held in London last week. Jenkins experts Kohsuke Kawaguchi and Andrew Phillips presented several continuous integration topics to a packed crowd. The principal software engineer at NDS Limited (now part of Cisco) and the author of the M2Release Jenkins plugin also presented about maintaining Jenkins installations within NDS. Some great Jenkins Enterprise information is now available from the event.
For most organizations, software delivery is time-consuming, stressful and costly. As soon as applications go live, issues arise - forcing IT into another costly release cycle. Businesses thus need a process that enables the addition of new online features in a matter of hours instead of days - faster, better and at a lower cost.
As an article by Andrew Phillips from XebiaLabs published this week in .NET Developer's Journal notes, one way that many businesses overcome the challenge of promptly delivering software updates is to adopt the Continuous Delivery approach - a strategy that moves ideas into production as fast and as efficiently as possible. This iterative approach also allows you to validate business assumptions at an early stage of the delivery process and adjust when required.
Continuous Delivery lowers costs since deployments run reliably on a daily basis, and the number of deployments does not significantly impact the overall cost. Once a deployment pipeline is configured, subsequent deployments occur automatically so the maximum number of deployments is not bound to any limit. Read the full article >