Getting Started with Jenkins Pipeline in 4 Steps

Aug 15, 2016 12:38:48 PM / by Kai Prout posted in DevOps, Jekins Pipeline, Jenkins, Modernized Technology


If you are familiar with open-source Jenkins, you understand that it is an award-winning continuous integration and deployment tool for a reason. It’s growing ecosystem of plugins has taken Jenkins to the next level providing extended features and added functionality.

However, an integral part of replicating your software delivery workflow is the ability to represent your delivery model visually while automating the process; with Enterprise Jenkins, you can completely re-write the script pun intended to accomplish this through the Pipeline Plugin.

Read More

Automated Testing with Selenium Grid and Jenkins in 3 Steps

Aug 10, 2016 11:03:41 AM / by Jack Ozment posted in Agile Testing, continuous testing, Automated Testing, Continuous Integration, selenium grid, Selenium, Jenkins, Modernized Technology


Selenium Grid is a powerful tool for testing web applications across browsers and operating systems, but incorporating it into a Continuous Integration pipeline can be frustrating. Integrating the Grid with a CI/CD server is complex, and a misstep during setup can lead to unreliable test errors, and down that path lies madness. Here at AgileTrailblazers, we use the Selenium Grid plugin for Jenkins to quickly execute our UI tests on every build against multiple operating systems and browsers, so front-end bugs are squashed early.

Read More

How to Make Your Scrum Master Happy Using JIRA Integrations

Aug 3, 2016 11:15:59 AM / by Paul Friedman posted in Agile, JIRA, Scrum, GitHub, Continuous Integration, Atlassian, Jenkins


Have you ever had your scrum master ask you, "what is going on with that story?"  As somebody that has assumed virtually every role possible on an Agile team over the course of my career, I can assure you that I have heard it many times, and I'm sure you have too.  Certainly there are many ways to answer this question, but in my opinion, the best way is to make it possible for your scrum master to find the answer for themselves, using the teams primary tool, JIRA.  In this article, I explain how you can make your scrum master happy by configuring your developer's primary tools, Jira, GitHub, and Jenkins to play nicely together and update JIRA stories with all of the information that your scrum master wants to see.  So let's get started.

Read More

Subscribe to Email Updates

Lists by Topic

see all