DevOps Playground – Exploring Metrics with Prometheus

DevOps Playground – Exploring Metrics with Prometheus

Singapore’s last DevOps Playground was exploring metrics gathering with Prometheus. The event was hosted at the Lifelong Learning Institute (LLI).

The DevOps Playground community in Singapore is growing and this was our biggest attendance in Singapore to date! Thank you to everyone who supported us.

In this playground, we provide you with a better understanding of the monitoring capabilities of Prometheus and how those statuses can be easily displayed in a Grafana dashboard.

Follow the video above and you’ll begin to see how easy it is to set up a new Prometheus Server and use it to gather metrics from several applications.

We walk you through installing and configuring a Prometheus instance to monitor the following:

  1. Server hardware and kernel related metrics
  2. Instrumenting a Go application

The steps needed to complete this playground can be found on our Github repo:

So consider the services you are responsible for maintaining and follow the video above to see if Prometheus can help you improve the visibility of the health of those services.

Furthermore, we would advise users who are seriously looking into Prometheus for production to take into consideration the following during their planning phase:

  1. Storage Capability – Understand the size and frequency of metrics to be collected and stored.
  2. Federation – Scaling Prometheus to allow a Prometheus server to scrape selected time series from another Prometheus server.


Interested in attending our next DevOps Playground in Singapore? Follow us on Meetup to receive a notification about the next event.

Check out our other DevOps Playground on Meetup too:

You can also find all the information and resources you need about DevOps Playground sessions, upcoming events and past events on our website:

Melvin ChengDevOps Playground – Exploring Metrics with Prometheus
read more
Is your master branch production ready?

Is your master branch production ready?

Delivering software in a continuous delivery capacity is something that nearly every project strives for. Problem is, not many projects are able to achieve continuous delivery because they don’t have the confidence in their applications quality, their build pipelines, their branching strategy or worst case, all of them.

A good indicator as to whether you fall into one of the above is to ask yourself: `can I confidently release master branch right now`.

If your answer is no, then how do we start to break down and resolve these problems.

Building confidence in quality

A recent project I have been working on fell into a few of the above categories. Nearly all their testing was done on a deployment to a long living environment, after a merge commit to master. Along with a lot of duplicated work throughout their pipeline.

The test strategy shown above was for a simple front-end application that reads data from an external API.

To start, we identified areas of our application that we knew were unloved, or treacherous to develop. Once identified, we put in place appropriate test automation. When writing test automation it is so important that your tests are robust, fast and deterministic.

We pushed as much of our UI automation down into the application. Ideally you want your application adhering to the testing pyramid principles. Testing elements that have particular classes with tools such as selenium are both time costly and of no value. There are better, more appropriate tools to do this.

Once our test scaffolding was in place, we started to feel more comfortable refactoring problem areas and reducing complexity.

We isolated our application by stubbing out external services or dependencies where necessary –  we didn’t want to be testing services outside our scope. Where possible, we recommend agreeing a contract with your external dependencies and using this to develop against.

We also recommend containerizing your app. Being able to deploy and run the same image of an application locally and on production is incredibly powerful. Long gone are the days of having long living application servers and the phrase of ‘well it works on my machine’.

Start failing fast 

Once we had confidence that when our tests all passed then the application could be deployed, we then looked to address where our tests were running.

Having tests run after a merge commit to master is too late in the process. Leaving it this long introduces a risk that someone pushes the release to production button before tests have been run.

We need to run tests earlier in the process.

In the past, to solve this problem you may have adopted complicated branching strategies dev, test, master which on paper seem reasonable, but in practice introduce horrendously slow unnecessary feedback loops and messy merges between multiple branches.

We decided to harness the power of pull request environments instead, to allow our tests to run on short living infrastructure before we merge to Master. With DevOps paradigms such as immutable infrastructure, infrastructure as code and containerisation, deploying a new environment becomes trivial.

This becomes even more powerful if you deploy your pull request environments in the same way as your production site, since you effectively test the deployment itself.

Having pull request environments spun up also caters for any testing requirements, such as exploratory testing or demos, and massively speeds up developer feedback loops.

The end result is a much higher confidence in your applications quality in master branch, which to any project is invaluable.


This a two-part series, with the next article focusing on how we can start to deliver master branch to production. Watch this space.

Matt LowryIs your master branch production ready?
read more
DevOps Deadlock – moving from distracted to determined

DevOps Deadlock – moving from distracted to determined

60% of European organisations now utilise DevOps*. But as this number increases, so does the performance gap between those “stuck” at the experimental stage and those that have been able to successfully adopt DevOps to achieve scale.

To lead and excel in today’s digital economy, companies must embrace a business-centric collaboration – AKA DevOps. It’s no longer a choice to adopt or not. The decision is about how to get DevOps right, so it can scale across the business.

Delivering greater security, speed and quality of output whilst driving a truly digital-native experience is what DevOps looks to advance and secure. And once adopted, business innovation is the recognised principal benefit – surpassing the allure of enhanced developer productivity.

But scaling requires going one step further. It’s not enough to have DevOps in place, you need to understand how to enable it to scale.

At this year’s IDC DevOps Conference, Jen Thomson – IDC’s Research Director – took to the stage to discuss the following three key areas:

  • Where European organisations are on their journeys to enterprise-scale DevOps; looking specifically at how they are becoming ‘unstuck’
  • New emergent challenges faced as DevOps journeys progress
  • DevOps for business agility and the KPIs for success

This talk was bookended by Andy Cureton’s – Managing Director and Founder at ECS Digital – presentation on lessons from a year of Enterprise DevOps. Cureton supported Thomson’s observations, reiterating that moving past the challenges of transformation at scale requires taking a more holistic view of technology and the business – especially when embracing technologies that are still emerging. Having a laser focus on security and architecting for future outcomes is also vital for securing long-term success.

Scaling DevOps requires progress across multiple segments of the software delivery pipeline including: planning, developing, testing, delivering, deploying, securing, operating and managing. And whilst these would have traditionally sat in one department, for DevOps to scale successfully, security and software-driven innovation needs to become everyone’s responsibility.

Determined organisations are pathing the way when it comes to moving past the “DevOps Deadlock” because they are modernising their infrastructures specifically, so they can propel DevOps further within the organisation.

Lloyds Banking Group are one such organisation. And on the 8thNovember, Dave Gore– Engineering Transformation Lead at Lloyds Banking Group – will be joining Jen Thomson and Andy Cureton to reveal how the bank is supporting their own transformation journey.

As well as this deep-dive into a customer experience of utilising DevOps to secure business innovation, this webinar looks to continue the core conversations that arose at IDC DevOps Conference, tapping into the following:

  • How to differentiate between DevOps Distracted and DevOps Determined
  • Different paths to take to getting unstuck
  • Supporting a transformation to a customer-centric software-defined business

Free to attend and with a live Q&A to follow the discussion, this is your chance to hear from the experts and have your say!

Registrations for the webinar are open now. Save your spot here.

*IDC DevOps Conference 2018

ECS DigitalDevOps Deadlock – moving from distracted to determined
read more
Jenkins World travels to Europe!

Jenkins World travels to Europe!

We’re back at DevOps World / Jenkins World, and this time; we’re in Europe! The first location for Jenkins World Europe is Nice, France and we’re really excited to be in such an amazing city. We’re here to provide official CloudBees training to attendees as well as network at the expo to hear stories from individuals about their DevOps successes and #DevOps moments.

Jenkins World

Billy Michael & Abhaya Ghatkar provided Jenkins Pipeline Intermediate training to over 40 attendees during the first two days of the event. This day long course was designed to build upon the Jenkins Pipeline Fundamentals course. It focused on declarative pipeline using blue ocean and how Jenkins can be further enhanced with the usage of shared libraries. In addition, we discussed new features, best practises and how to ensure the students can make the most out of their pipelines with the usage of new features. The training provided the students with interactive labs to complete during the course.

These training courses also allowed us to interact with students from companies of all sizes from all over the globe. This provided us with a way to hear the unique problems users are encountering on a day-to-day basis and provide advice on how the knowledge from the course can help them to resolve these issues.

The theme of this year’s Jenkins World remains the same as last year; Transform. This shows CloudBees clearly have a commitment to building a better product for the future and feel that their transformation is still ongoing. This was showcased by the keynote presentation provided by Kohsuke Kawaguchi, where he refers to the “Superpowers” CloudBees and the community have been working hard to provide for its users.

These superpowers include:

  1. Jenkins Pipeline
  2. Jenkins Evergreen
  3. Configuration as Code
  4. Cloud Native Jenkins
  5. Jenkins X

For more information about some of these topics, please refer to our blog post from Jenkins World San Francisco where we have spoken in more details about the keynote.

In addition to the keynotes there are a number of talks spread throughout the two days which are provided by CloudBees and its partners. Some of the topics which interest us are:

  • Jenkins Configuration as Code
  • DevOps performance management with DevOptics
  • DevOps at scale within the Enterprise
  • Jenkins X: Continuous Delivery for Kubernetes
  • AWS Keynote
  • 10 things we all do, but shouldn’t do with Jenkins

We’re pleased to have been a part of Jenkins World’s first trip to Europe. So far it has provided a great platform for networking, interesting talks and the ability to meet other companies who are here showcasing their latest offering.

We look forward to enjoying the rest of the event and hope to see you all again next year is Lisbon, Portugal!

Billy MichaelJenkins World travels to Europe!
read more
Our first DevOps Playground in Singapore

Our first DevOps Playground in Singapore

Our very first DevOps Playground took place in September in Singapore, at the Lifelong Learning Institute. We had fun with Amazon Connect!

At the event, we created a working solution utilising Amazon Connect, Amazon Lex, AWS Lambda, S3 and SNS. Cloudformation was used to help configure these services with the minimum of effort. Unionising these Amazon services allowed us to create an environment that enabled us to have an interactive telephone conversation through Amazon Connect, powered by Amazon Lex. Once the call was complete, the conversation was transcribed using AWS Lambda and sent via SNS to a subscribed email.

Watching the video below, you can run through the Playground from the comfort of your home!

Thank you to everyone who attended and made our very first DevOps Playground in Singapore a huge success.

Cy NichollsOur first DevOps Playground in Singapore
read more
10X developers. Does your company really need one?

10X developers. Does your company really need one?

10 average detectives versus one Sherlock Holmes – who will solve the crime faster?

The 10x developer is adeptly called so because, in theory, they bear the capabilities of 10 developers.

That’s right. Legend has it that a handful of these ‘Rockstar’ developers live and breathe in the tech space, operating at such speed that they outpace their counterparts on every level. Jessica Kerr is said to be one such developer – although her take on 10x developers is that a person will always appear to be 10x more effective than average if he/she is working on familiar code using familiar tools in a familiar environment.

While some remain sceptic, Marc Andreessen, cofounder of Netscape, agrees that “five great programmers can completely outperform 1,000 mediocre programmers.” He also believes that “the gap between what a highly productive person can do and what an average person can do is getting bigger and bigger.”

Mark Zuckerberg is another believer in the Rockstar employee. When asked why he was willing to pay $47 million to acquire FriendFeed – a price that translated to about $4 million per employee – Zuckerberg replied “someone who is exceptional in their role is not just a little better than someone who is pretty good.” And in Zuckerberg’s eyes, FriendFeed were “100 times better” than their counterparts.

Whilst we don’t doubt the plausibility of a Rockstar developer, we feel there are some faults to the logic.

We are also not convinced that businesses should be spending time and money (millions in some cases) trying to hunt these Rockstars down. Not only does it feed into the allure of the lone wolves, rogue elephants and the socially aloof, we believe businesses will have greater success if they focus on attracting the best talent possible to create a well-assembled team that overwhelms with collective capabilities.

Here’s why:

Complete creative freedom is a rare treat

Programming is not a manual labour, but a creative profession. How fast you write code should therefore not be a measure of productivity. What separates an average developer with an experienced one is the knowledge, recognition of redundant parts, and coding abilities that allow them to write the correct code first time, every time.

Programming is also a choices game.

One great programmer will make “great” decisions at every stage whereas an average programmer, you guessed it, will make “average” quality choices. The costs or benefits of these decisions will multiply through the business, for better or worst. And this is just one reason why businesses would look to investment in the ‘rare but great’.

Combine the ability to architecturally design a program with the sub-design of implementing the strategy and this is where a Rockstar developer can really come into their own. The more ‘goal-oriented’ the task, the greater opportunity a 10x developer has to flex their abilities to creatively create a solution with a lot less effort.

However, when the task becomes more rigid in nature – including dictations about what tools to use and an expected process – this opportunity is weakened. Whilst developers can exploit ‘local’ design possibilities, they do not have the freedom to fundamentally change the course of action or actively tweak the specification of the project to allow the same goal to be reached with a fraction of the effort.

What this tells us is that certain projects have the potential for more skilled developers to shine. But when the majority of your work is dictated by guidelines set by clients, you’re unlikely to get a good return on a ‘Rockstar’ investment.

For every one Rockstar, there are ten developers clearing up the mess

The morecommon way for 10x programmers to exist is by generating enough technical debt to keep ten other developers busy in the trail blaze. One developer ends up looking more productive because work is being produced (at a questionable standard but impressive rate), whilst the rest of the team becomes less productive as a result.

The irony is, management will often direct more resources to this superstar based on their ability to ‘get things done’, including jobs where writing new code is required. And yet, as I’m sure any developer will tell you, writing five lines of code in an existing code base is fundamentally more taxing than producing hundreds of lines of new code.

We spoke earlier about coding speed not being an appropriate measure for productivity. But we’d like to go further and support Dave Nicolette’s view that productivity itself can’t be a measure either, since it does not take into consideration the value or quality of the output. He instead looks to effectivenessas a fairer judge:

“effectiveness implies more than just delivering the customer-defined business value of the work items in our backlog”.

If your Rockstar develops quickly but leaves behind enough technical tech to keep your other developers from producing value-add work, it might be time to put them on the bench.

Don’t let perfect be the enemy of good

Avichal Garg notes that start-ups lean more towards individual Rockstars, while larger companies tend to recruit for individuals who possess specific technical skills. There are a couple of reasons for this difference in approach:

For start-ups:
  • There simply isn’t a need, or the budget to fill a room full of engineers
  • Because managing engineering teams is incredibly hard, it’s easier to think about hiring a few “10x” engineers than it is to think about designing processes that create 10x teams
  • When initiating a start-up, people often wear a variety of hats until resources allow these to live across different teams/roles in the business – as seen in larger organisations
For larger companies:
  • Rockstar engineers may actually be counter to business goals
  • A business’s unit of productivity is a team – you need to maximise the output across a broad set of people

If you’ve ever watched Moneyball (2011 film featuring Brad Pitt), you’d probably agree with how larger companies address their recruitment. There is also a strong consensus within the Agile community that the formation of cross-functional teams is of greater benefit than separate work groups.

There is also concern that team context isn’t considered when identifying individual 10x developers. If an individual appears to function at 10x while a member of a high-performing team, they may not function the same in a different environment, and their perfo

rmance will certainly suffer if they work with no team support at all – especially when considering the section above.

It is about creating a 10x team, rather than fielding one 10x engineer.

And to create a 10x team, it is no longer enough for an engineer to be good at their job. You need individuals that consistently compliment each other, are good communicators and can comfortably work with others. They need to be able to up-skill their team, up-skill their client’s teams and scale quickly when a business grows – which will be a hard task if you’re waiting for a unicorn to knock on your door.


At this point we would like to reiterate that like star musicians, athletes, scientists, and political leaders, star developers are exceedingly rare. If you create a hiring strategy focused solely on hiring ‘Rockstars’, your business, and Dev team, will end up looking lonely. And whilst a one-man-band may be good for space saving, culture and agile working could be hampered.

Whilst we don’t deny that there are some incredibly talented developers out there, don’t let perfect be the enemy of good. Hire the best engineers you can get and give them ample opportunity to develop into a 10x team that is going to best support your business goals. And remember:

  • A bargain is only a bargain if you can afford it.
  • A genius whose abilities cannot be leveraged in your organisational context is no longer a genius.
  • As engineers we know never to engineer a single points of failure into a service. A developer as a core element of delivering and supporting a service is no different.


Andy Cureton10X developers. Does your company really need one?
read more
Succeeding in Enterprise Scale Transformation

Succeeding in Enterprise Scale Transformation

Enterprise Scale Transformation affects more than just technology.

More so than ever, business growers and revenue enablers are sitting external of companies. Valuable time is being spent waiting for system access, and companies are realising that reworking/upgrading systems isn’t delivering the results they need for tomorrow.

And yet, revenue is being realised in ridiculously short spaces of time with magnifying effects on the rest of the business. Legacy systems are delivering transformational benefits, and communication channels are driving business-wide change at an accelerated rate of adoption.

Andy Cureton will be reviewing six learnings from a year of Enterprise Scale DevOps programmes at this year’s IDC conference, drawing on the experiences of ECS Digital’s experienced digital transformation consultants. You can have a sneak peak of his speech here:

Andy CuretonSucceeding in Enterprise Scale Transformation
read more
Alexa: Building Skills for the World of Tomorrow

Alexa: Building Skills for the World of Tomorrow

We have all seen the TV Ads with someone asking Alexa (Amazons personal assistant AI) to dim the lights or start playing ‘The Grand Tour’ on Prime Video, and this technology is growing larger and faster every day.

Most commercial technologies like computers and internet started their lives in the hands of big businesses and large institutes that could afford the large initial RnD costs. In light of this, the Amazon team have taken a reverse approach and employed a small scale, iterative expansion of the product.

By providing developers access to the Alexa development kit and opening the voice service to the public, Amazon have made Alexa development a straightforward, painless and rewarding process.

Amazon incentivises its cult following of open source developers by rewarding those who create great skills that others want to use. Amazon announced:

“Publish a new skill this month and get an Alexa water bottle to help you stay hydrated during your coding sessions. If more than 75 customers use your skill in its first 30 days in the Alexa Skills Store, you can also qualify to receive an Echo Dot to help you make Alexa even smarter. The skill with the most unique users within its first 30 days after publishing in February will also earn an Echo Spot.”

Vocal Skills Revolution

We should all remember the mobile app revolution along with the tremendous increase in the number of smartphone users  experienced in global mobile app markets . A massive increase in the user base drove innovation, producing better mobile phones. An organised marketplace for app download, timely updates, advanced app development platforms became the norm. Most significantly, the development of some very useful and revolutionary apps have become part of our everyday lives. With the number of users almost doubling over the last 5 years, mobile app developers can reach more consumers than ever.

At ECS Digital, we believe Voice will experience the same type of growth as mobile applications did.

While consumers command more of their day to day life using voice-controlled technologies, from smart TVs to Alexa enabled electric cars, we can be safe in the knowledge that the voice revolution is coming and will change the way future generations interact with technology.

Alexa for Business

What is Alexa for Business?

Alexa for Business makes it easy for you to use Alexa in your organisation. Alexa for Business provides tools to manage Alexa devices, enrol users and configure skills across those devices. You can build your own context-aware voice skills using the Alexa Skills Kit (ASK) and conferencing device APIs, and you can make them available as private skills for your organisation.

What is an Alexa Skill?

Alexa is Amazon’s voice service and the brain behind tens of millions of devices like the Amazon Echo, Echo Dot, and Echo Show. It provides capabilities, or skills, that enable customers to create a more personalised experience. There are now tens of thousands of skills from companies like Starbucks, Uber, and Capital One as well as other innovative designers and developers.

Alexa Voice Service

The Alexa Voice Service (AVS) enables you to integrate Alexa directly into your products. We provide you with access to a suite of resources to quickly and easily build Alexa-enabled products, including APIs, hardware and software development tools, and documentation. With AVS, you can add a new intelligent interface to your products and offer your customers access to a growing number of Alexa features, smart home integrations, and skills.

What is the Alexa Skills Kit?

The Alexa Skills Kit (ASK) is a collection of self-service APIs, tools, documentation, and code samples that makes it fast and easy for you to add skills. ASK enables designers, developers, and brands to build engaging skills and reach customers through tens of millions of Alexa-enabled devices. With ASK, you can leverage Amazon’s knowledge and pioneering work in the field of voice design.

ECS Digital and Amazon Alexa

With Alexa for business being released in the US and coming to the rest of the world soon, we at ECS Digital have been using her to increase productivity and enable innovation within the office. We have been working on a few different initiatives coining the term OfficeOps.

Here are some of them:

Booking a meeting room

Working in a large consultancy,  it can be difficult to know if a meeting room is free. Moreover, booking said room can be a complicated and confusing process. The answer: create an internal/Dev skill to track the availability of a room, who has it and for how long. This skill also allows users to book a room on the spot, allowing our colleagues to interact with the booking process by literally asking the room for a booking slot .

Interactive Training

As a fast-moving DevOps consultancy, ECS Digital are always looking for innovative ways to improve our skills. For a long time now, we have been using Alexa to learn new skills and brush up on existing ones by using her as a pop quiz master. Colleagues located in our London Bridge office can ask Alexa to test their knowledge about a technology, helping them to maintain a high level of competency.


All evidence suggests that voice is here to stay, and will drive the next wave of technical innovation, both in business and at home, making those laborious, everyday tasks a little easier and futuristic. However, our assessment comes with a note: work still needs to be done in order make voice the standard, but we are confident that changes will be made swiftly.

Visit our services to explore how we enable organisations to transform their internal cultures, to make it easier for teams to collaborate, and adopt practices such as Continuous Integration, Continuous Delivery, and Continuous Testing. 

Morgan AtkinsAlexa: Building Skills for the World of Tomorrow
read more
Puppet Feature highlight: Puppet Discovery

Puppet Feature highlight: Puppet Discovery

In May, Puppet released Lumogon, a tool used to help discover your infrastructure.

Today at PuppetConf, Puppet announced Puppet Discovery, which allows you to quickly and easily discover your resources, no matter what they are, traditional, cloud and container resources, it does them all, and is built on top of Lumogon.From PuppetConf, here are few key-points about Puppet Discovery:

  • Agentless service discovery for AWS EC2, containers, and physical hosts
  • Actionable intuitive views across your hybrid landscape
  • The ability to instantly bring your unmanaged resources under Puppet management
  • Delivered as turnkey and auto-updating experience

Read here for more information about Puppet Discovery.


Michel LebeauPuppet Feature highlight: Puppet Discovery
read more
ECS Digital Acquires QAWorks

ECS Digital Acquires QAWorks

London-based ECS Digital, the specialist DevOps division of the ECS Group, has acquired QAWorks, the UK’s leading technical software testing organisation.  

QAWorks is recognised in the industry as the home of the Software Development Engineer in Test (SDET). Studies suggest that 31% of IT budgets are being spent on testing1 which is set to rise over the coming years as a result of growing demands on organisations to increase innovation and time to market and reduce associated cost.

This acquisition is part of ECS Digital’s strategy to reduce the time and cost of delivering software and software-related services by including practices such as Behaviour Driven Development (BDD) and Acceptance Test Driven Development (ATDD) as core elements of all DevOps transformations.

The combined company will be known as ECS Digital and have a turnover approaching £10 million which is expected to continue to grow over 100% year on year.

The combination of specialist testing expertise with proven – and rare – DevOps experience will ensure that the company’s customers – who are across all sectors, with the majority in finance and retail, can realise even greater outcomes from digital transformation. DevOps is a methodology that helps companies create software and software-related services such as internet banking, faster, at lower cost and with improved quality.

Andy Cureton, Founder and Managing Director, ECS Digital, commented:

“This is, as far as we are aware, the first time that a specialist DevOps company has integrated to this extent with a specialist testing company.  We believe the deal will make ECS Digital unique as we will be the only consultancy to offer specialist testing practices as a foundation element of our DevOps offerings as well as in their own right. This acquisition is driven by the need for greater levels of innovation and customer engagement within many companies, and the ever-rising benchmark of high performance. By combining testing and DevOps, companies can ensure that software is designed with how the customer is going to use it in mind and tested on that basis. Development and delivery will be accelerated as testing is done as part of development rather than separately.”

He added “With over 14 years’ experience in DevOps and digital transformation (ECS Digital) we could not have found a more experienced software testing team (17 years) than QAWorks. Combining the rare skillset of the SDET with the equally rare DevOps skillset, will enable us to meet our customers’ growing demands and further our position as a leader in DevOps and Digital Transformation.“

ECS Digital is part of ECS Group, headquartered in Scotland.  The ECS Group delivers an extensive range of services, from Cloud adoption to cyber-security to DevOps for many FTSE 100 companies.  With the acquisition of QAWorks, ECS Digital will have one of the largest pools of SDET and DevOps engineers in the UK.

QAWorks develops testing software as well as providing agile testing consultancy and implementation.

Jason Westhorpe, MD, QAWorks, said:

“The services offered by ECS Digital complement and enhance the services we currently offer our customers. For true DevOps to be successful it is essential that continuous testing / test automation is in place, likewise for the benefits of test automation to be realised we need an effective DevOps strategy. With the integration of two of the UK’s leaders in these fields, both the existing QAWorks customers and ECS Digital customers will gain the greater benefit from the adoption of DevOps.”

He continued, “Continuous Delivery and DevOps has seen the once independent disciplines of infrastructure automation, continuous integration, deployment automation and so on, merge into software delivery pipelines. Businesses that are increasingly reorganising around products or customer journeys and adopting DevOps and Continuous Delivery practices, are now benefitting the most. It’s no longer enough to be a specialist in one discipline such as testing.   It is rare to find companies with the skills to provide DevOps to large corporations, so we are delighted to be teaming up with a company of the calibre of ECS Digital.”

According to Gartner, by 2020, DevOps initiatives will cause 50% of enterprises to implement continuous testing using frameworks and open-source quality tools.2


Andy CuretonECS Digital Acquires QAWorks
read more