What Exactly Does a DevOps Architect Do?

According to Wikipedia, "an Architect is a person who plans, designs, and reviews the construction of buildings."

Times have changed. Now we have a DevOps Architect. No, don’t think of it as a replacement. In fact, we need both. We are talking about the web world. We are trying to make you understand the roles and responsibility of a DevOps Architect with this post.

Original Link

What We Learned About Flutter by Analyzing CI/CD Builds

Our previous post about mobile builds on Nevercode CI/CD servers took the mobile app development world by the storm. Therefore, we decided to take a deeper look at the new kid on the block — Flutter.

Flutter is Google’s mobile SDK, introduced in 2017, and is expected to release a stable version soon. The rising popularity of Flutter is illustrated by more than 40k GitHub stars and more than 15k StackOverflow questions.

Original Link

DevOps Trends 2019 — What You Need to Know

DevOps has evolved big time since many of us thought it was just a buzzword. Now we know that is a myth. DevOps has become a main focus and has been shaping the world of software for the last few years. Experts say that DevOps is going to be the mainstream and its popularity is going to reach its peak in 2019.

Below is the Google trend shown for the term “DevOps” and a hypothesis of its projected growth in 2019.

Original Link

How to Build a CI/CD Pipeline for Your Enterprise Middleware Platform

Continuous integration and continuous deployment (or delivery) a.k.a CI/CD is one of the most talked-about ideas in enterprise software development. With the rise of microservice architecture (MSA), it has become a mainstream process within enterprises. If you are familiar with microservice architecture, you should have heard about greenfield and brownfield integrations, where you start your microservices journey from scratch or from an existing enterprise architecture (which is the case 80% of the time). According to this survey, there are more and more organizations moving ahead with microservices architecture even though they accept that it is really hard to maintain and monitor (of course, there are tools coming up to cover these aspects). This survey showcases that the advantages of MSA are outweighing the disadvantages I mentioned above. CI/CD is a tightly-coupled concept along with MSA and DevOps culture. Due to the dominance of MSA within enterprises, CI/CD has also become an essential part of each and every software development lifecycle within the enterprise.

With this shift in the enterprise towards MSA, DevOps and CI/CD culture, the other parts of the brownfield, cannot stay out of these waves. These “other parts,” consist of

Original Link

DevOps in 2019 (Part 3)

Given how fast technology is changing, we thought it would be interesting to ask IT executives to share their predictions about the future of DevOps in 2019. Here’s more of what they told us:

Bill Peterson, VP, Industry Solutions, MapR

Original Link

How to Leverage Infrastructure-as-Code With DevOps Best Practices

Infrastructure-as-Code (IAC) remains a relatively trending topic in the field of computing. IAC refers to a method of managing virtualization using automation. By defining infrastructure entirely using code, developers can reuse and refine their approach to continuously improve their systems. For as long as DevOps has been around, IAC has grown alongside. In fact, there are many people who would argue that DevOps wouldn’t be possible without the use of IAC.

Implementing IAC

In order to understand how to best implement IAC, and why it’s necessary to adhere to certain best practices, a refresher in IAC is helpful to understand why it is held in such high regard by so many. The driving concept behind IAC is that virtual machines can be deployed and managed in the same way that software applications can be. By defining system architecture—and the configuration of individual components—purely as code, developers are able to tweak their virtual systems to remove bugs and infrastructure imperfections.

Original Link

How to Leverage Infrastructure-as-Code With DevOps Best Practices

Infrastructure-as-Code (IAC) remains a relatively trending topic in the field of computing. IAC refers to a method of managing virtualization using automation. By defining infrastructure entirely using code, developers can reuse and refine their approach to continuously improve their systems. For as long as DevOps has been around, IAC has grown alongside. In fact, there are many people who would argue that DevOps wouldn’t be possible without the use of IAC.

Implementing IAC

In order to understand how to best implement IAC, and why it’s necessary to adhere to certain best practices, a refresher in IAC is helpful to understand why it is held in such high regard by so many. The driving concept behind IAC is that virtual machines can be deployed and managed in the same way that software applications can be. By defining system architecture—and the configuration of individual components—purely as code, developers are able to tweak their virtual systems to remove bugs and infrastructure imperfections.

Original Link

DevOps in 2019 (Part 2)

Given the speed with which technology is evolving, we asked IT professionals to share their thoughts about how the agile methodology would evolve in 2019. 

Here’s what they told us about agile and DevOps:

Original Link

DevOps’ 2018 Surprises and 2019 Predictions

Given how fast technology is changing, we thought it would be interesting to ask IT executives to share their thoughts on the biggest surprises in 2018 and their predictions for 2019. Here’s what they told us regarding DevOps:

Michael Schweighofer, Product Manager for Webtestit, Ranorex (a division of Idera, Inc.)

Original Link

Intro to Jenkins Pipelines and Publishing Over SSH

In many projects, things that seem very small come to be decisive factors to continue on the current path or find a better one. Starting from simple text editors to tools used for a long period of time, we all have different flavors for each tool in hand. Merging these ideas sometimes comes to be a to-do, and while this happens for any kind of work done in a group, there are also some other factors that shape the path to it.

This time, we came across an issue which let us think about how to proceed. Our project is being developed as an integration of many standalone microservices. This led us to use different resource files for our remote development and production environments. After considering different options, we finally decided to deploy these files through SSH (from our build server to where the application server is). Since we are using Jenkins for CI/CD, we had to use an ssh plugin.

Original Link

DevOps: Principles, Practices, and the DevOps Engineer Role

For a long time, development and operations were isolated modules. Developers wrote code; the system administrators were responsible for its deployment and integration. As there was limited communication between these two silos, specialists worked mostly separately within a project. That was fine when Waterfall development dominated. But since Agile and continuous workflow have taken over the world of software development, this model is out of the game. Short sprints and frequent releases occurring every two weeks or even every day require a new approach and new team roles.

Today, DevOps is one of the most discussed software development approaches. It is applied in Facebook, Netflix, Amazon, Etsy, and many other industry-leading companies. So, if you are considering embracing DevOps for the sake of better performance, business success, and competitiveness, you take the first step and hire a DevOps engineer. But first, let’s look at what DevOps is all about and how it helps improve product delivery.

Original Link

Continuous Documentation With Antora and Travis

Antora is a documentation pipeline that enables docs, product, and engineering teams to create, manage, remix, and publish documentation sites composed in AsciiDoc and sourced from multiple versioned content repositories.

You can see several examples out there from Couchbase documentation to Fedora documentation. And of course, Antora documentation is used to generate Antora documentation. You can see it here.

Original Link

How to Create GitOps Pipelines With GitHub Actions and Weave Cloud

GitHub Actions will become a major player in the CI SaaS market. It can easily replace most CI tools out there especially if you ship code as container images. With GitHub Actions, you can do more than CI/CD. Most tasks performed today with bots (code sign validations, issue management, notifications, etc) can be made into workflows and run solely by GitHub.

Why would you give up your current CI SaaS and self-hosted bots for GitHub Actions? For one, GitHub Actions simplifies automation tasks by offering a serverless platform that is capable of handling most development tasks. As a developer, you don’t want to jump from one SaaS to another in order to diagnose a build error. The fewer environments you have to use on a regular basis, the more productive you’ll be. Not to mention that as a developer you probably spend most of your time on GitHub anyway.

Original Link

Putting the Dev in DevOps

“If only the rest of IT moved as fast as we developers do!”

As applications and runtime platforms become more cloud native, the pace of development necessarily becomes faster. IT departments have sold the transition to the cloud as a self-service haven where development teams no longer suffer from the multi-day-ticket hell of days past and are freed to move at their own pace. Developers have long opined, “If only the rest of IT moved as fast as we do!” Well, be careful what you wish for. Now that developers have self-service infrastructure provisioning and runtime platforms with real APIs, they are realizing that their new reality is not quite the utopia they made it out to be. As Stan Lee taught us via Spider-Man, “With great power, there must also come great responsibility,” but that is only half the story. The other half being, “With great responsibility there must also come a great deal of work.” Such are the realities of utopias.

Original Link

What Is Continuous Integration?

It’s hard to find terms getting more attention in the software world in the last few years than the closely related practices of Continuous Integration (CI) and Continuous Delivery or Continuous Deployment (CD), often referred to in tandem as CI/CD. Organizations across the world, from one-person development shops to multinational corporations, are implementing CI and CD for their software products.

In this article, we will describe CI, briefly mention CD, and see how you can use them effectively. We will evaluate some of the popular tools and systems available in the space that allow you to get up and running quickly with your development workflow.

Original Link

Using Jenkins-X UpdateBot

Jenkins-X UpdateBot is a tool for automating the update of dependency versions within project source code. Say you’re building two projects, A and B, such that B uses A as a dependency. The release process for A could use UpdateBot to update the source for project B to use a new version of A. With UpdateBot this would result in a pull request so that the change could be tested and reviewed or automatically merged.

Within pipelines on the Jenkins-X platform, UpdateBot is automatically present and invoked by updatebot commands in Jenkinsfiles. But UpdateBot can also be used outside of Jenkins-X and running it alone can help to understand what it can do and test out version replacements. So let’s try it out with a simple tester project.

Original Link

The DevOps Road Map — A Guide for Programmers

DevOps is really hot at the moment and most of my friends, colleagues, and senior developers I know are working hard to become a DevOps engineer and project themselves as DevOps champion in their organization.

While I truly acknowledge the benefits of DevOps, which is directly linked to improved software development and deployment, from my limited experience I can say that it’s not an easy job. It’s very difficult to choose the right path in the middle of so many tools and practices.

Original Link

How to Deploy a Jenkins Cluster on AWS in a Fully Automated CI/CD Platform

A few months ago, I gave a talk at Nexus User Conference 2018 on how to build a fully automated CI/CD platform on AWS using Terraform, Packer, and Ansible.

The session illustrated how concepts like infrastructure as code, immutable infrastructure, serverless, cluster discovery, etc. can be used to build a highly available and cost-effective pipeline.

Original Link

The Journey to Kubernetes

Have you wondered why Kubernetes is so popular? Discover why Kubernetes is the clear market leader in the container orchestration space in our latest addition to the Weaveworks Kubernetes library.

On this page, we provide an overview of what Kubernetes is and how it enables fast-growing applications to quickly scale. The different installation options available, as well as a summary on how companies are running it today with many hand-curated links to more in-depth information are all discussed in these pages.

Original Link

DevOps Concerns

To understand the current and future state of DevOps, we spoke to 40 IT executives from 37 organizations. We asked them, "Do you have any concerns regarding the current state of DevOps?" Here’s what they said:

Organization Change

  • Don’t over-engineer. Ideal DevOps situation is a company building with as little friction as possible in the best fashion. Copy the culture not what’s been deployed. 
  • As I mentioned earlier, a lot of tools are being spun as DevOps, but if those tools don’t focus on building the culture—on bringing people closer together—and on increasing value creation, then they’re not really doing DevOps. 
  • We still have too many organizations not focused on systems thinking. People are hyper-focused on automation when they don’t have a great culture. Automation helps companies fail faster. Be value-stream minded. Plan backward. Most bottlenecks are at the very end. Plan backward to get to the bottleneck more quickly. Focus on reliability versus resilience. 
  • Not sure. See where it goes in a year or two. Getting too far away from culture drivers and getting too lost in the technology. Success is breaking down silos between dev and operations. 
  • I think there are many concerns and challenges with the current state of DevOps.  The hype and expectations are high.  Implementing and scaling DevOps in large enterprises is difficult.  It’s a transformational experience, not a project.  Many companies will jump on the DevOps bandwagon without understanding the primary business objectives, and they will also not be willing to make the cultural changes necessary to create an organization that is focused on continuous improvement.  They will meet failure with regression and revert back to the old way of doing business which will put their business at a disadvantage.


  • There are so many tools in the DevOps space that all claim to solve DevOps challenges. It is becoming a very crowded space and many vendors are claiming to have the silver bullet to solve DevOps. My concern is for companies that are just starting to test the DevOps waters. It can be very confusing and overwhelming, given the broad array of choices and methodologies. 
  • One concern I have is that as we continue to use more layers of abstraction on top of the underlying computer system to simplify building automated and complex distributed systems, that the next generation of engineers may lack the fundamental system knowledge necessary to truly understand what their applications are doing. I see things potentially headed this way with the emphasis on fully abstracting compute through concepts like Functions as a Service, which, while a powerful tool, could potentially lead to engineers who are unaware of the realities happening behind the scenes. A person is only capable of holding so many layers of abstraction in their mind at once and still working at that top layer. Building a robust, high-performance, scalable, and secure system relies on fundamental systems understanding. It creates a catch-22 for the next generation of DevOps engineers.


  • Not enough practitioners, more expensive to hire, not taught in school. As more people adopt it becomes a more expensive labor proposition. It affects what a developer is.
  • How do we move this faster especially on the people side? This is a giant transition for the industry and a different way of getting the software to the market. Significant skillset needs. How do we get people to evolve their skillsets?
  • It seems like there are fewer and fewer people in the field capable of doing the job. This may have to do with the fact that people don’t want to be ‘on call’.


  • People are still not buying into full testing with a repeatable baseline. Still a few cutting corners. Do it right the first time or you’ll have to do it again. If you get failures that’s good data, you can fix it before too late. Data tells you whether it’s good or bad. Don’t have fear of getting a bad result. Security tends to be overlooked. Multi and hybrid-cloud need to be paying more attention to security.
  • It’s still early in maturity. Part of the problem is people promising silver bullets. Gartner hype cycle – multi-year journey, organizational change, here’s the value you can realize. Set reasonable expectation. Don’t leave a bad taste in people’s mouth. It’s a three to seven-year process, not six months. It took 12 years to go to VMware, how long do you think it will take to move to microservices? 
  • The level of maturity is growing but some things are still unknown with regards to tooling and deployment environments. The notion is that people who have done DevOps to-date were very forward thinking. The next batch will do DevOps because its fashionable or trendy but they don’t do it well – they will be less successful. 
  • DevOps leads people to just think dev and ops. DevSecOps is really agile with a customer feedback loop. Every company and vendor talks about DevOps in a different way. We need greater clarity and simplicity. We’re getting better but we still have different interpretations.
  • What do you do with legacy systems? How do you adapt and make sure they do not slow you down? Each organization has to deal with their legacy systems and software.
  • Need an exit plan for the technology we cannot get spare parts for in two years. Different architectures, processes, teams you need coordinated releases and deployments. Need to coordinate to release a new mobile app. Freak out shows in many ways. IT delayed set up of Chef prototype environment for two years. Need to be smart and transparent.
  • DevOps will evolve as businesses adapt and discover its greatest benefits based on their own needs. One area that we see DevOps helping tremendously is in reducing technical debt. Many development teams find themselves having to update a horribly outdated project or struggling to keep applications up to date and clean. Often, engineering finds itself at odds with business stakeholders or trying to squeeze major refactors into feature development. Paying down tech debt is never a bad thing if it helps a company grow. Companies with minimal technical debt are nimble and more competitive. DevOps is an important triage step towards paying down that tech debt. 
  • Converting (or creating a new one) the application to DevOps is only part of the challenge. One of my major issues in DevOps is databases. Databases are stateful and cannot be treated the same way as stateless applications. We cannot spin down and spin up and scale down and scale up databases easily as data has gravity and requires special caring and feeding from the team. This makes it hard for them to be adopted in a DevOps environment.
  • We have embraced a culture of diversity and team-driven innovation, which has led to great success with our products. Many of these achievements can be attributed to the fact that we enable different teams to leverage different tools in building their applications. However, this heterogeneity also brings two challenges: 1) Different levels of SDLC maturity – While some teams are pushing the envelope and using the most up-to-date DevOps solutions, there are still teams across the organization that need more help to modernize their developer workflow. 2) Change is hard – Long-standing organizational structures, culture and dynamics, as well as code pride, are often barriers to cross-team collaboration and InnerSourcing. Another challenge we have is how to set up best practices for newer DevOps tools within the organization. For example, the way Docker images are typically reused across the industry represents a risk, because it’s often hard to reproduce the sequence of steps needed to build an image. This is especially true if you’re using up-to-date versions of the depended-upon images. As people are updating their workflow to leverage tools like Docker, we need to develop a better Continuous Integration/Continuous Development (CI/CD) practice for Docker images – one that will likely require some form of mechanism to keep track of coherent sets of versions across images that are already tested.
  • Yes, as DevOps adoption increases, there is always an over reliance on tools. This tool will fix the problem! Or, that tool didn’t work, and we need to use this tool. Teams must always remember that tools are not culture. I’d hate to see DevOps viewed as a set of practices that may or may not work for a company. DevOps, when implemented well, works every time
  • 1) As with any other technology, things will evolve with time and more research. To mention one concern in particular, it seems that DevOps is typically limited to the developers and operations teams. By integrating DevOps solutions with third-party software, the DevOps scope could be extended to include other teams in the IT department. 2) DevOps should also be able to support more complex applications to better facilitate technological adaptation. Many organizations have large, complex application ecosystems, a lot of which fall outside the scope of DevOps. Support for such complex applications will allow businesses to overcome the barriers of traditional application life cycle management and adopt DevOps more willingly. Also, with increased awareness, more IT Ops teams will see the business value in DevOps and consider implementing DevOps for delivering maximum efficiency. Compared to how quickly enterprises adapt to DevOps changes, having SMBs get completely on board with DevOps seems like a challenge.

Here’s who shared their insights with us:

Original Link

Automation Replaces Tasks, Not People

There is no better example of automation than in the remake of “Charlie and Chocolate Factory.” In the movie, Charlie’s father, Mr. Bucket, loses his job at the toothpaste factory where he put caps on tubes. Because of the increase of demand for chocolate due to the contest, the toothpaste factory makes more money and decides to modernize… and Mr. Bucket loses his job. Later, the same factory rehires him, with better pay, to repair the machine that replaced him.

Sure, it’s a movie. It’s not real. However, this happens all the time in information technology, albeit without the intervening firing.

Original Link

Keep Your Automated Testing Simple and Avoid Anti-Patterns

Automated Tests That Need to Be Tested?

We are so fortunate today to have so many automated testing libraries, frameworks, and tools available that make creating automated tests quite easy. Some even allow people who do not have any coding experience to create automated tests. If you’re new to automated testing, should you just dive in with one of those tools and crank out some tests?

Or perhaps you’ve got programming experience, and you’ve automated some regression tests, but they keep sporadically failing in your continuous integration. You and your team are spending way too much time diagnosing failures to see if changes to the production code caused regression failures or if it’s just something wrong with the automated test script. If you haven’t had the time to learn good automated testing and principles, troubleshooting and maintaining automated scripts can slow your team’s ability to deliver new features.

Original Link

Problems Solved by DevOps

To understand the current and future state of DevOps, we spoke to 40 IT executives from 37 organizations. We asked them, "What problems are solved by DevOps – where is the greatest value realized?" Here’s what they said:

Deliver Value to Customers

  • DevOps minimizes the time it takes to deliver value to customers. The cycle time from developer completion of a story/defect/task to production is dramatically reduced allowing for value to be realized as quickly as possible. 
  • Getting more satisfaction from internal users. Move from a pain point to a solution. Organizations see having a strong DevOps team and tools helps you get more satisfaction for end users and internal users. DevOps aligns IT to the business. 
  • People realize in order to provide better services and stay competitive they have to change. A big driver is business time and quality to market. It’s all about how fast can provide rights things and right quality to end-users. Change the culture from delivering what someone internally wants versus delivering what customers really want and like. Continuous experimentation – engineers experiment with new things to stay ahead of the competition. Develop and deliver at a faster pace. Faster quality to market and more experimentation that leads to innovation and better service to the end user. Use technology to help determine how to make customers lives simpler and easier. 
  • The tenets are still the same – better, faster, sooner. Increase productivity and serve customers in the best way and learn quickly. Used to have to explain why you needed to go to the cloud or pursue DevOps. Not anymore, people understand the benefits. A company in denial and doesn’t want to change processes now comes under scrutiny. 
  • The greatest value realized through DevOps is that it allows IT organizations to focus on their “core” business activities.  By removing constraints within the value stream and automating deployment pipelines, teams can focus on the activities that create customer value rather than just moving bits and bytes. These activities increase the sustainable competitive advantage of a company and create better business outcomes.

Reduce Cycle Time

  • Internally DevOps only way to achieve agility to deliver secure code with insights. Have gates and a well-crafted DevOps process. When you are delivering a new version, it can run side-by-side with the current version and you can compare metrics to accomplish what you wanted to with application and performance metrics.
  • The number one thing is velocity – move quickly. It’s also about increasing the rate of success of these digital transformation projects. Need to ensure you are successful. Increasing the rate of success. Aware of the first bunch of people doing DevOps are the best experts. The teams after that are less experienced. How can we ensure the consistency of the product and the process?
  • Speed, version cycles getting shorter. The expectation of turning out releases monthly. Can’t take months for a QA test. Have to react to changes being driven by competitors.
  • Make incremental changes to apps on the fly. Test and deploy. More agile, more valuable in the market by responding to customer demands. Fast, safer to market. DevOps helps get that done. Industry culture tech workforce is young and new, and DevOps has been there, it’s the new norm. SaaS startups were nothing before DevOps.
  • DevOps drives app dev teams towards continuous improvement and faster release cycles. Done well, this iterative process allows for more focus over time on the things that really matter – things that create great experiences for users – and less time on managing “below the waterline” tools, processes, and tech.
  • DevOps and the many related ideas surrounding it are all used by enterprises to accelerate the delivery of modern applications. The benefits are many: By introducing new digital capabilities faster enterprises can respond more quickly to customers, partners, and internal users. Businesses can greatly enhance their agility to decrease time to market, increase customer satisfaction, and gain competitive advantage. Reducing cycle times can also speed innovation. New ideas can manifest more quickly. Those that fail can be sorted from those that flourish sooner, bringing more focus to the most successful innovations faster. Multiplying this effect over many interactions of experimentation and discovery can dramatically increase the ROI on advanced research and development. The process automation that underpins DevOps and enables rapid delivery at scale also improves the bottom line. Automation improves productivity, reduces errors, and greatly enhances operational efficiency.

Time to Market

  • Moving faster. A marketing group can understand what it takes to get a feature rolled out and promote it. How does moving more quickly help me own the application? Break down siloed development vs. operations vs. business.
  • Colonial Life took their biggest and most important app and worked to improve it. They felt if we could modernize this one app, user onboarding, then we’ve proven there’s no challenge we cannot address.  They’ve gone from three manual releases per year to seven automated releases. Time is saved in handoffs and in transition, build time has been reduced by one third. Eliminated 10 hours of handoff per week for DBAs. In addition to going faster on new projects, they’re able to go back to a backlog of projects and start improving them.
  • Being more agile saving cost, Save developer time. While it’s a large upfront investment, we’re lowering the negative impact of operations. We’ve accelerated the speed at which we go to market and our ability to scale. We view DevOps as a business enablement tool.
  • Speed to market. Six days versus six months. Competing on the ability to innovate. App delivery has to be front and center.
  • More secure and compliant environments, lower cost of operations due to reduced downtime and increased development velocity, and quicker time to market for new product features. The things most people associate with DevOps are tools and methods that enable these values, rather than the end target themselves.
  • The most important problem being solved is the reduction of the complexity of the process — whether it’s configuring a new cluster for existing applications or provisioning the environment for a new application. This contributes significantly to our business success by shortening our time to market, giving us fast feedback on features, and making us more responsive to our customers’ needs.

Problem Resolution

  • The greatest value of successful DevOps higher confidence in delivery, visibility, and traceability to what’s going on, so you can solve problems quicker. 
  • From the dev team perspective, the biggest gain is a different kind of velocity – a reduced level of friction. When you do have dev and ops working together there is value in problem swarming. Getting problems fixed faster and creating a level of bonding that results in better code and apps. 
  • The greatest value of DevOps is not wasting time. Aligning an organization’s people and resources enables rapid deployments and updates which allows DevOps programs to fix problems before they become disasters. DevOps creates a culture of transparency that fosters focus and collaboration among development, operations, and security teams.


  • Adoption of standards. Used to just do what you can. Today there are standards are in place. We want quantified data, metrics, and a repeatable environment. Get the baseline done correctly and be able to scale out. The data is still very valuable. Establish a repeatable baseline to scale out.
  • Automated processes to address security up front. We admire DevOps and rapid delivery but must apply security best practices. Driven by different requirements – deliver applications on time and under budget. Unless pressure is applied to DevOps we’ll have less secure application. Hackers do automated monitoring against anyone on the web.
  • The two biggest benefits of DevOps are bringing people together, which is at the center of DevOps, and automating labor-intensive activities that reduce creativity and productivity. Both are essential for increasing software quality, getting it to market faster, and driving up business value.
  • Eliminate human error. The more you automate a well-defined process you will see the greatest value. 
  • If I look at the typical enterprise the value is moving faster, empowering developers, achieving better code quality, having a more resilient infrastructure, and improving the security posture. Software created in a more granular way. There is more confidence in releases that don’t break everything.
  • Every organization understands the need to make a digital transformation. The expectation is you will provide a better CX enabled by software. Containers and DevOps are the tools of mass innovation. Modern approaches of how to build software that can be updated and scaled.
  • Speed to market and quality. Employee retention in the ops side of the house because there is such misery doing releases, deployments, and firefighting. People were quitting because they were miserable. More content employees. Mainframe developers are retiring. This is a real problem.
  • The greatest value is the improvement in the dev, test, deploy and monitor processes which leads to organizations being more nimble in their approach and innovating faster.
  • DevOps enhances overall software quality and enables teams to take innovation, agility, and flexibility one step further, with shorter, iterative processes that serve the business more effectively. With a DevOps culture, deployment, and development to production cycles can go from months to hours, without additional headcount and while decreasing risk through automation. However, despite a focus on speed through “sprint projects,” leveraging a DevOps mentality does not impact an organization’s ability to execute on larger, long-term projects. A DevOps culture does more than just improve technology use: it enables tech pros to reinvent their use of technology, transitioning from a cost center to growth driver. DevOps measures success not by meeting service level agreements, but by delighting users with constant improvement—trusting that end users will reward brands with higher return, new business, or both, and including business metrics alongside system metrics to prove it.
  • Good DevOps allows staff to focus on delivering value to the business. Low value and repetitive tasks are automated or removed from your daily work life. The greatest value realized is the time you can spend delivering good software and not being consumed by the thousand cuts of poor deliveries.
  • We didn’t realize we were encountering a lot of problems in the development and testing phases until after we adopted DevOps and saw how quickly and smoothly these updated processes were converging things. For one, we realized how much of our testing process was still being done manually. Automating wherever possible was the key to faster delivery. Besides that, embracing the use of relevant third-party applications complemented our practices and helped us ease a lot of our regularly exhausting processes.
  • We have found adopting DevOps methods and tools we are continuously improving our entire application delivery process. We are constantly finding areas where we can automate. As we move to higher levels of abstraction across development, infrastructure management, and monitoring we are improving reliability and velocity. Perhaps most important, our teams are far more integrated which delivers benefits across the board. In the past, moving faster typically meant sacrificing quality and reliability. We’re finding that we can move faster while making gains in quality and reliability, which is a huge win.

Here’s who shared their insights with us:

Original Link

Top DevOps Experts You Should Know

To me, continuous integration/continuous delivery (CI/CD) also includes continuous learning and experimentation…I’m always interested in finding out about new books, podcasts or new teachers. This isn’t just my work philosophy, but it also carries onto my personal growth projects. It’s led to fun reads from authors like Tim Ferriss’ blogs, Farnam Street, Freakonomics, etc… Similarly, I’ve been collating a list of DevOps experts which I’ve been turning to increase my knowledge in this space.

I was turned on to DevOps because a few years ago, I watched several hackers at Defcon talk about how they hacked into a Tesla. They were amazed at how the systems were architected. The car was basically a server on wheels. Yet, they had found an obscure way to access the controls. Then, unlike most vendor/hacker horror stories, Tesla actually patched the security hole within weeks and then hired those hackers to further secure their systems.

Original Link

2018 in Review: State of DevOps Adoption

Last year, IT Svit published a report on the state of DevOps adoption in 2017, based on the findings of Puppet and Atlassian surveys. Now we compare it to the latest DORA report on the state of DevOps.

While DevOps practices are becoming the mainframe of the IT industry, different companies get different results in adopting them:

Original Link

DevOps Enterprise Summit Las Vegas 2018 — The Best Yet?

Its already over again — the annual get-together of the brightest DevOps minds (well, the brightest who could make it to Vegas). And in this instance, I want to make sure that what happens in Vegas does not stay in Vegas by sharing my highlights with all of you. It was a great event with a slightly higher focus on operations than last time.

The four trends that I picked up on:

Original Link

DevSecOps Best Practices – Building an E-Commerce Application on Alibaba Cloud

In this article, we will explore the concept of DevSecOps and discuss how we can apply its principles by building an e-commerce application on Alibaba Cloud.

Gartner predicts that,

Original Link

Adding a GitHub Webhook in Your Jenkins Pipeline

Have you ever tried adding GitHub webhook in Jenkins? In this blog, I will be demonstrating the easiest way to add a webhook in your pipeline.

First, what is a webhook? The concept of a webhook is simple. A webhook is an HTTP callback, an HTTP POST that occurs when something happens through a simple event-notification via HTTP POST.

Original Link

What CI/CD Tool Should I Use?

In our ongoing series, the Kubernetes FAQ, where we’ve been answering some commonly asked questions in the community, this week we discuss what you need to consider when choosing a CICD tool.

There are a ton of CICD tools out there to choose from – both open source solutions as well as commercial ones. In here, we highlight some of the most important considerations to make when setting up a continuous delivery pipeline.

Original Link

Structure of a Jenkins Pipeline

In this blog, I will be discussing the basic structure of a Jenkins Pipeline, what a pipeline consists of, and the components used in the pipeline.

You can see the basic overview of a pipeline here, on GitHub.

Original Link

DevOps 101: What Is a DevOps Platform?

Introduction to a DevOps Platform

In a DevOps organization, Continuous Delivery (CD) is used to create a constant flow of changes to production. The entire automated software production line is commonly referred to as the Continuous Delivery pipeline. The CD pipeline breaks the software delivery process into several stages, each of which verifies the quality of new features before moving them to the next stage until they finally are available to users. The pipeline provides feedback to the team and visibility into the flow of changes to everyone involved. To successfully scale DevOps in an enterprise, a set of components are leveraged to help teams achieve CD. This is called a DevOps platform.

While there may be slight variations from organization to organization, or within the type of software project, a typical DevOps platform facilitates CD through the following stages.

Original Link

Choosing the Right Continuous Integration Tool

A typical software development process is based on an agile framework with a need to roll out quality products at a fast pace. Software delivery tools are also evolving to keep pace with challenges like frequent changing requirements, evolving design, and continuous integration with test-driven development. Continuous integration (CI) and continuous delivery (CD) are not only the latest buzzwords but also a highly effective and practical way of developing and delivering quality products. Today, we are flooded with many CI tools and choosing the right tool is becoming difficult. Many organizations take the easy route by picking a popular tool, but this strategy may be risky since the chosen tool may not meet their needs in the long term.

This article will help you choose the right CI tool as per your business needs. Let us first look into the popular CI tools on the market. The below table gives a list of CI tools (not ranked in any order) that are popular today.

Original Link

Solving Java EE Nightmares Without Docker Containers or Microservices

Developers and application owners have many new tools and technologies such as microservices, Docker containers, CI/CD, and DevOps that help them produce better software, faster. Yet, the sad truth is that most organizations rely on untold numbers of legacy applications, many of which are Java EE, to power mission-critical systems that can’t be migrated to some of the emerging technologies and processes.

Legacy Java EE apps are almost a necessary evil, providing core business functions while forcing IT teams to face myriad operational problems including planning for and addressing scaling challenges, managing inefficient and unpredictable resource consumption, protecting unsecured confidential information, and applying patching and restarting applications without service disruption.

Original Link

The Role of DevOps in Mobile App Development

Over the past five years, mobile devices have become the primary source for accessing the internet for millions of people around the globe. These trends have scrambled many industries to adapt towards the shift in business application users by developing a mobile app for their business.

During the early years of this shift, the IT industry focused on meeting market demand and businesses focused on creating a market presence. They overlooked to focus on app development costs, security, maintainability, and code quality.

Original Link

9 Reasons DevOps Is Better With Docker and Kubernetes

One of the main challenges that companies face with is a long time to market, which usually happens when your development process is slowed down. When deploying applications most of the teams usually face a problem between Dev and Ops because these two departments make the same application but work completely in different ways.

Wouldn’t it be nice if they work together without any misunderstandings to make shorten time to market? I’ve assembled this list of advantages that DevOps plus Docker and Kubernetes can provide you compared to a traditional DevOps approach.

Original Link

Software Engineering Daily — GitOps Key Takeaways

In a recent episode of Software Engineering Daily, Alexis Richardson spoke with Jeffrey Meyerson and recorded a podcast on GitOps. Here is a small excerpt from that interview.

When did convergence start to happen around the ideas that became GitOps?

Original Link

Testing as the Driver Towards a DevOps Culture

At Abstracta, we work with many companies, several of whom already have a DevOps culture and others whom we’ve helped to define and promote it. Over the years, we’ve seen DevOps gaining popularity, and most teams are on their way there. In this post, I’ll share some lessons from our experiences in helping companies with their agile transformations.

From what we’ve seen, we’re convinced that teams with a DevOps culture work better, obtain better results and are, just… happier.

Original Link

What We Learned About CI/CD Analyzing 75,000 Builds

One can read a lot of why continuous integration is a powerful techniqueand how it can speed up your mobile app development process. However, we decided to dig deeper and analyze who are the users of a continuous integration tool tailored for mobile (confused about why CI for mobile is different than standard CI?) and what are their cases, needs and, most importantly, the benefits…in real numbers! We gathered data from Nevercode, a CI/CD tool for Android, iOS, React Native, Ionic and Cordova, and analyzed more than 75K builds from the first quarter of 2018. Here are the results.

What Is Continuous Integration (CI)

In short, continuous integration (CI) is a software development practice of merging developer build copies daily, if not multiple times a day, into a shared code repository. Each integration is verified by an automated build to detect errors and get to the root of the problem as soon as possible without losing track of the development process. Check out the top CI tools for mobile projects.

Original Link

Continuous Discussions (#c9d9) Podcast 92: All Day DevOps [Video]

This morning on our Continuous Discussions (#c9d9) podcast, we had a great discussion with some of the folks at All Day DevOps. Electric Cloud is proud supporters of this online event — it’s a great way for the global software delivery community to learn, for free!

Today’s episode dove into the 2018 All Day DevOps program as well as what makes the event so special. One of the great things about All Day DevOps is it provides folks around the world the opportunity to learn without having to worry about travel or any other budget limitations. Many people or companies simply do not have the money to spend on pricey events, plus travel and accommodations, which means they miss out on a lot of opportunities to not only learn but connect with the industry. Attendees of All Day DevOps also get to use the dedicated Slack channel to ask speakers questions and engage with one another – last year there were over 30,000 conversations that took place during the event! Plus, this year there are talk tracks for just about everyone – from DevSecOps, site reliability engineering and cultural transformations – you won’t want to miss out on these great talks.

Original Link

Kubernetes in the DevOps Space: Everything You Need to Know

It can be rightly said that Kubernetes and DevOps are the power couple of the cloud! They run hand-in-hand for enterprises looking to develop complex applications. You may be thinking, both DevOps and Kubernetes have a different context — how this is possible?

In our previous blog, we described every bit about Kubernetes, but how are Kubernetes and DevOps related to each other? What output can software developers and enterprises get if all these terms are mapped together?

Original Link

DevOps Tool Tyranny

In the software development world, we hear the adage "use the right tool for the job" all the time. Its use goes back decades, and we’ve all been told, "you don’t hammer a nail with…" For me, deciding on the tool is often the most important step in the process (as significant as how you use it) because the implications are long-term and can be expensive to undo if you make the wrong choice.

When it comes to programming languages, different languages are better suited to specific use cases than others. In other instances, the decision is less clear-cut. For example, today, if I were to develop a multi-threaded application I would select Go or perhaps even Node.js in a Kubernetes cluster. I would not choose Java for such a project. No doubt some reading this may disagree with my example, and that illustrates my point. It can be difficult to determine which language is the best for a particular project; there are lots of factors that must be weighed and considered.

Original Link

Continuous, Incremental, Progressive Delivery: Pick Three

Software developers have spent the last decade talking about Continuous Delivery and the benefits of delivering working code as often as possible. But it turns out that’s only one part of the whole picture of software delivery. Modern teams actually have three distinct outcomes they are trying to achieve — a holy trinity of continuous, incremental, and progressive delivery. Each of these delivery practices can help your team move faster with less risk.

Continuous Delivery

Continuous Delivery is a set of practices that ensure your code is always in a deployable state. You accomplish this by increasing the frequency at which code is committed, built, tested, and deployed-steps that in the past only occurred at the end of a project when it was ‘code complete’.

Original Link

[DZone Research] DevOps Adoption Rates

This article is part of the Key Research Findings from the 2018 DZone Guide to DevOps: Culture and Process.


For this year’s DZone Guide to DevOps, we surveyed 549 software professionals to find out their thoughts on various aspects of DevOps. In this article, we focus on that data around DevOps adoption. 

Original Link

Architecture for Continuous Delivery

This is part 3 in a series on continuous delivery. In parts one and two, we introduced you to the concept of continuous delivery and how you can prepare your organization before adopting CD practices.

In this article, we’re going to discuss architecture for continuous delivery. How do we architect our systems in a way that enables us to continuously deliver value to our customers?

Original Link

Women in DevOps: Tanu McCabe

Tanu McCabe’s expertise as a solutions architecture director at Capital One has enabled her to lend invaluable insights about her exciting adventure within the company’s digital journey. Since 2015, Capital One, one of the country’s largest banks, has championed a large-scale tech transformation. During an interview, Tanu reflected on her decision to join Capital One, her hopes for the future direction of the company, and how burnout brought her to a dream job in DevOps.McCabe’s job as a solution architect allows her to provide leadership and guidance that leverages the latest technological developments. As part of her job, Tanu positions the company on the best solution designs, projects, and company-wide initiatives.

How did you decide to come to Capital One?

Original Link

4 Compelling Benefits of CI/CD Businesses Cannot Afford to Ignore

Waterfall, Agile, and now DevOps – are the most sought-after approach to building great mobile apps. The old methods of software development and delivery have now become passé.

Gone are the days when companies deployed software in annual, quarterly, or even monthly releases. Moving over to DevOps practices, software is deployed weekly, daily, or even multiple times a day without disturbing the user journey.

Original Link

Jenkins in a Nutshell

In many projects, the product development workflow has three main concerns: building, testing, and deployment. Each change to the code means something could accidentally go wrong, so in order to prevent this from happening developers adopt many strategies to diminish incidents and bugs. Jenkins, and other continuous integration (CI) tools are used together with a source version software (such as GIT) to test and quickly evaluate the updated code.

In this article, we will talk about Jenkins, applicable scenarios, and alternatives to automated testing, deployment, and delivering solutions.

Original Link

Installing CI/CD Tools With Ansible: Everything You Need to Know

When setting up a CI/CD pipeline, you need to choose the right tools. Things you should take into consideration include your specific needs, abilities and ease of use. In my last post, I recommended different tools for building a CI/CD pipeline. Today, I will explain how to install and configure them with Ansible. In the end, I will provide resources that explain how to configure them to work together.

The tools we will show are

Original Link

9 Top DevOps Conferences — A Developer’s Picks

With the DevOps movement only continuing to grow, plenty of conferences have sprung up around the topic. These are a great way to get acquainted with the DevOps methodology and the capabilities it can bring to your organization.

Conferences also let you do the following:

Original Link

Why Is DevOps Becoming Mainstream in Software-Powered Organizations?

Early DevOps practitioners have shown DevOps to be more than just a cultural aspect or a set of tools – they have confirmed it to be a crucial success factor and a competency well worth developing in today’s environment of rapid evolution, technological advancement, and huge customer or employee expectations. The demand for DevOps in organizations is high and need of the hour, but it is not something that can be adopted on to the average team just like that. When this happens, the current organizational undercurrents will weaken the effectiveness of such a program. Rather, the development, operations, and overarching management processes must be redesigned anew and from the scratch. DevOps can be profoundly disruptive to a business, it has an enduring and strong impact on organizational success. After all, IT is the core of almost any business and the effectiveness and agility gained there will have a notable impact on the readiness and coordination of the organization as a whole.

The term DevOps has entered into our general language and has gathered much attention and focus these days.

Original Link

  • 1
  • 2
  • 5