AcdntlPoet 2700019V2G Visits (675)
Back in January we posted about Ralph Schoon's RTC command line... since then he has continued his work and made a few updated revisions to the tool! Check out the two blog posts below noting the deprecation of version one, and the most recently updated version 2.2!
An RTC WorkItem Command Line V1.0 – Deprecated- Version 1.0 is now Deprecated. Please refer to the new Version 2.2 of the RTC WorkItem Command Line . The code has been enhanced and received a lot of testing and will be the basis for future efforts.
An RTC WorkItem Command Line Version 2.2- Creating links is not easy. Many things can go wrong. Testing by a user showed that there was an issue with links between work items and build results. I found that I got the link direction wrong. I fixed that. Here is the updated source code.
License and Getting Started
The post contains published code, so our lawyers reminded me to state that the code in this post is derived from examples from Jazz.net as well as the RTC SDK. The usage of code from that example source code is governed by this license. Therefore this code is governed by this license. I found a section relevant to source code at the and of the license.
Incremental publish & remote debug help accelerate IBM Bluemix app development using Rational Application Developer V9.5 Beta
AcdntlPoet 2700019V2G Visits (559)
The IBM Rational Application Developer v9.5 Beta bundles the latest version of the IBM Eclipse Tools for Bluemix which includes 4 new features and bug fixes.
With the new support for incremental publish and remote debug of applications, we now only need to publish the delta code changes instead of redeploying the entire application, significantly reducing the deployment time and making application development targeting Bluemix easier than ever.
To try the new features check out Cesar Orozco's blog post with all the steps you need in the Rational Community here: Incremental publish & remote debug help accelerate IBM Bluemix app development using Rational Application Developer V9.5 Beta
AcdntlPoet 2700019V2G Visits (913)
In this 7 part blog series surrounding the DevOps culture, Adrian Cho (Program Director, Continuous Delivery Evangelist, and Author of The Jazz Process: Collaboration, Innovation, and Agility) tackles some of the less tangible issues as they relate to the connection between delivery logistics, development culture, and continuous delivery.
DevOps Culture – Retrospectives and continuous improvement: In the Collaborative Lifecycle Management (CLM) project we have declared three imperatives for improvement in order to increase our agility with a goal of continuous delivery: culture, process, and tools. Of these three things, culture is, in my opinion, the most difficult thing to change because it’s less tangible than processes and tools and because culture is often deeply ingrained in an organization and a team. [Read More...]
DevOps Culture – Enabling continuous improvement with IBM’s DevOps Maturity Model and Rational Team Concert: In my last post about retrospectives I discussed the way we have been tracking pain points and associated improvement actions to address those pain points. In this post I want to discuss how we’ve taken this even further by using Rational Team Concert to help track our continuous improvement and how we’re using IBM’s DevOps Maturity Model. [Read More...]
DevOps Culture – Increasing shared awareness: The ability of any team to execute with agility is predicated on a shared awareness of important team elements such as the team’s strategy, plans, and current status. A measure of shared awareness is easily gained when team members work alongside one another. You can’t help but notice what your teammate is doing when she is sitting right next to you or in the same room and that can be invaluable if you are working together. However, when teams are spread across physical locations and time-zones, a more conscious effort must be made to create shared awareness. [Read More...]
DevOps Culture – Teaming up: In a previous post Sreerupa Sen wrote about run teams and feature teams and how they are helping to make our continuous delivery successful. I want to expand on that in this post and talk a bit about the culture that enables such fluid organizational constructs to work successfully. [Read More...]
DevOps Culture – Managing friction: In a previous post about retrospectives and continuous improvement I described how we track “pain points” which are issues that block or hinder our ability to develop a specific development capability. Another way to think of pain points is that they are sources of friction. [Read More...]
DevOps Culture – Building robust teams: When it comes to managing projects and teams, the natural inclination for many people is to try to predict and control everything while taking comfort in tools and technology and processes and practices. This happens frequently in software development despite the fact that other, far more mature, domains learned long ago that this approach doesn’t work, especially in a world of constant change. [Read More...]
DevOps Culture – Thriving at the edge of chaos: In my previous post on building robust teams, I mentioned the need to have some people in a team with an appetite for risk and some who are risk-averse. Some people take risks because they are too inexperienced to know better but some experienced people know that it’s important to take risks. [Read More...]
AcdntlPoet 2700019V2G Visits (1172)
Stéphane Leroy (Unleash the Labs CLM, IBM Software Engineer) has created a wonderfully simple table to outline the Test Lab mana
And don't miss Stéphane's most recent posts surrounding his expertise in RTC and enterprise modernization!
AcdntlPoet 2700019V2G Visits (1286)
Ralph Schoon (Unleash The Labs, Leading Technical Sales Professional ) provides two great no-nonsense views into starting up with projects in IBM BlueMix on his external blog rsja
Getting started with BlueMix - Ralph blogs about his experiences with BlueMix and provides some detailed information to help you get started as well: "Recently everyone has their heads in the clouds and I decided to have a peek to find out what it is all about. So I started looking into it. This post is a summary of my first experiences with the IBM BlueMix Cloud Computing offering and how I got started with developing my first applications for it..."
Using RTC to Work with DevOps Services and With Bluemix - Ralph blogs again with a deeper dive into BlueMix and Eclipse that builds upon the post above: "I recently had a look into Bluemix and how to use it with Eclipse to develop cloud applications. The blog post also mentions that there is an integration to DevOps Services that enables to use work items for planning. It also allows to use GIT or Jazz SCM to manage the source code. Recently I had a look into how that works and I would like to share here what I learned. This post assumes you have performed the first steps to setup your environment following the Getting started With Bluemix post already...."