Articles

Today’s world regards time as of paramount importance. This said, the disruptive tech-enabled innovations are foremost meant to save both business owners’ and users’ time. The industry of software development is based upon the same postulates – the sooner the better, provided that timely product deliverables are coupled with efficiency and convenience.

The Continuous Integration (CI) and Continuous Delivery (CD) practices are among popular software engineering industry trends that help cut costs, time, and risks associated with delivering changes. Yet another trend to optimize the industry lies in applying DevOps methods, oriented to increase the efficiency of development and operation processes, and to speed up product delivery.

Source de l’article sur DZONE

Creating a continuous deployment pipeline will bring us a step closer to an automated build, test, deploy strategy. In order to create such a pipeline, we need to have access to several tools. Instead of installing these on on-premise servers, we can make use of the AWS cloud offer. Let’s see how this can be accomplished!

1. Introduction

We want to create an automated pipeline in order to ensure that no manual and error prone steps are required for building, testing and deploying the application. When a failure occurs during one of these steps, we will be automatically notified and can take necessary actions in order to resolve the issue.

Source de l’article sur DZONE

As more organizations move to establish DevOps techniques into their Software Development Life Cycle, the need of security becomes even more evident when so much application development is going on. But…

Security and DevOps Aren’t Natural Companions

The idea of security in DevOps or DevSecOps doesn’t go very well with the classic DevOps process that insists on continuous integration, delivery, and deployment. When at production you’re constantly releasing smaller bits of your code and application using the DevOps pipeline, introducing security to DevOps can slow down the process significantly. You can’t just pass that through a security team that takes several weeks bringing the new release out to production. 

Source de l’article sur DZONE

For the last decade or so, great advancement has been made in regards to Continuous Integration (CI) and Continuous Delivery (CD). The rise of DevOps testing has led to rapid demand for CI/CD tools. Existing solutions are consistently perking up with time and a myriad of new products or new versions are making their entrance into the QA world. When you have such prolific choices at hand, selecting the right tool can definitely get a little intimidating.

Amongst all the available CI/CD tools for testing, two tools that you should certainly consider are Jenkins and GitLab CI/CD. Jenkins has 16,000+ stars on GitHub whereas GitLab CI/CD has 2012. That’s 8 times more than GitLab CI/CD. However, these numbers aren’t the only thing one needs to look into while selecting a CI/CD tool. This is why in spite of the immense difference in stars, Jenkins vs GitLab CI/CD is having a neck to neck race over multiple review platforms as well.

Source de l’article sur DZONE

As businesses become AI-ready, efficient data management has acquired an unprecedented role in ensuring their success. Bottlenecks in the data pipeline can cause massive revenue loss while having a negative impact on reputation and brand value. Consequently, there’s a growing need for agility and resilience in data preparation, analysis, and implementation.

On the one hand, data-analytics teams extract value from incoming data, preparing and organizing it for the production cycle. On the other, they facilitate feedback loops that enable continuous integration and deployment (CI/CD) of new ideas.

Source de l’article sur DZONE

A few months back, I was going through some posts related to Test Automation in Quora. Suddenly a question posted by an anonymous user caught my attention – “What is Maven in Selenium?”

This was not the first time I came across this question or similar questions during my journey as an SDET. This is quite common since there is a lot of confusion regarding the differences between the build automation tools (“Maven” is one of them), and the test automation libraries, mostly among the testers who have just started learning/working on test automation and came across build tools for the first time.

Source de l’article sur DZONE

There’s no shortage of developers and enterprises of all sizes who are interested in the increased speed, collaboration, and iteration that DevOps promises. And with our research showing that more than half of organizations have an officially designated DevOps team, the prevalence of DevOps is only going to grow. In this Guide, you’ll learn about cultural shifts within DevOps, how to achieve resilient software delivery with CI/CD, the rise of DevXOps, and more.
Source de l’article sur DZONE

Containers and orchestration tools have often been cited as ways to facilitate continuous delivery and continuous integration. Download this Refcard to learn about the challenges and solutions to utilizing containers in your DevOps pipeline.
Source de l’article sur DZONE

When it comes to application testing, many project managers and test leads do not routinely conduct performance and load testing early in the development lifecycle. Instead, they undertake performance, and load testing after the application is complete, at the point where functional testing is applied. In fact, in many organizations, the performance test is frequently the last step — almost an afterthought — conducted right before the application goes into production.

This approach creates a classic problem: late-stage testing. Whenever testers identify issues, developers must modify the long-finalized code to fix them. These code changes can impact other parts of the application, resulting in breaks. Addressing problems after-the-fact is time-consuming and expensive. Furthermore, any delay in releasing a new feature or a new app can directly impact revenue, competitive position, brand, and adoption.

Source de l’article sur DZone (Agile)


CI Builds Status

We all know the practice of continuous integration.

One of the common pitfalls of CI is that the build status is not monitored and not treated as one of the top priorities for the team.

Source de l’article sur DZONE