(Fear of Missing Out) Jenkins FOMO...© 2018 All Rights Reserved. 5 Who We Are • Alex Taylor •Sr...

Jenkins FOMO(Fear of Missing Out)

What is Everyone Else Doing?#DevOpsWorld #JenkinsWorld #JenkinsFOMO

Objective & GoalsJenkins FOMO

© 2018 All Rights Reserved. 3

Objective - Why Are We Here?• Our industry is changing faster than ever.

• It is impossible for one person to have all the answers.

• While each of us works in a unique environment, there are common use cases and problems across our organizations.

• As members of the DevOps community, we are committed to continual improvement and are open to learning from and sharing with others.

• A critical part to our success as DevOps professionals is connecting with other people who are working on similar issues.

• We work with all sorts of organizations on all sorts of Jenkins and DevOps topics and want to help facilitate connections and learning in the DevOps community.


Goals - How We Will Know It Worked• By the end of this session participants will be better able to:

• Identify one-two specific area(s) of improvement (related to DevOps) on which to focus when returning from the conference.

• Recognize at least two new tools she/he will be able to address the area of concern.• Describe a use for Jenkins about which she/he had not previously known.• Connect with at least one new colleague outside of your team who is working on or has worked on similar areas of improvement.

This session is not intended to provide technical specifics on how to execute solutions and products, rather is intended to be a survey level of ideas/issues.

In order to avoid “presentation creep” we will be timeboxing each topic.


Who We Are• Alex Taylor

• Sr Development Support Engineer, CloudBees

• [email protected]

• Karen Taggart• Sr Customer Success Manager, CloudBees

• [email protected]• @TheCrazyDogLady

● Tweet about how much fun you are having #JenkinsFOMO● Please use the app to provide feedback

mailto:[email protected]

BE AFRAIDbe very afraidJenkins FOMO


What are you so afraid of?• Think about your current work with Jenkins…

• Happy Path: What’s working well? What have you accomplished in the past year?

• FEARFUL PATH: What is broken? What is falling down? Where are your gaps? Security? Admin? User Adoption? Scalability? Resilience?

• Pick one specific FEAR and write it down (this will not have to be shared)

Securitylet’s get this shift out of the way

#ShiftLeftJenkins FOMO


Security • Compliance & Auditing

• Technical: Audit Trail Plugin, Job Config History Plugin: Track what changes are being made and who made them. Close ports and put Jenkins behind a firewall

• Business: Include security in dev team, avoid big fines! (NIST, SOX, HIPPA); policy based scans of container images (Anchore Engine)

• Separation of Duties

• Technical: RBAC/Matrix plugin: Give out permissions as needed

• Business: Separation of masters, LDAP/RBAC/GROUPS, manage roles/permissions via version control (audit of who changed permissions when)

• Automated Security Scans

• Technical: Be aware of real security threats, what their consequences are, and if your DevOps tools are affected.

• Business: Static Application Security Testing (SAST) - in the IDE, at commit

Timebox: 6 min

Management /Administrative Burden

Jenkins FOMO


Management/Administrative Burden • Trusted Users

• Technical: Create trusted admins: Hold admins accountable for their instance but get them the support they need to fix their own projects

• Business: Training - Not as an afterthought. Make part of developer job and give them time/money for it.

• Plugins

• Technical: RBAC/Teams/Matrix security plugins: Give those trusted admins the permissions on their instances but block them off where they are not needed to isolate impact

• Business: Renegade teams using crazy plugins - do they really need them or is there a “better” way to get done what they need to get done. CloudBees Assurance Program/Plugin Catalogue

• Architecture/Infrastructure

• Technical: Build out multiple instances and isolate them using tooling like containers which reduces their downtime impact

• Business: Isolated agents with pre-determined tools; mapping business structures to architecture

• Analytics

• Technical: Report on how much downtime there was per team and celebrate the winners(not punish losers)

• Business: Look at when resources are being taxed; where is this taxing causing delays and why?

Timebox: 6 min

Increasing Use/Adoptionmore users = more betterJenkins FOMO


Increase User Adoption• Availability of Tools

• Technical: Create a well-documented process to access tools and make it easy

• Business: What are engineers using already/want to use? Providing value (carrots) to users so they choose to use vs. mandated adoption. Show off the tools -- internal Evangelism!

• Ease of Use/Flexibility of Tools

• Technical: Ensure the time to see results (finished builds) is as small as possible

• Business: Consider common, necessary functionality that can be templated - those less interested in Jenkins can submit minimal variables to existing pipelines, give more freedom to advanced users (replicate their successful work); Training/learning opportunities.

• User Empowerment

• Technical: Give your users the support they need to succeed

• Business: Who do you hire? Consider the necessary skills needed - Linux, Build/Release, Testing, Tools; provide options for training/certifications. LOTS of experimentation with team structure (Shared Services vs decentralized)

Timebox: 5 min

ScalabilityBut does it scale?Jenkins FOMO


Scalability • More Masters!

• Technical: Means teams with bad practices only affect themselves and are immediately more obvious

• Business: ^+1 Also means more freedom to advanced users; increase users without increasing down time

• Pipelines

• Technical: More flexible, more of the build process can be done in a single job, and creating a new job is fast/easy

• Business: Easier to visualize, re-used advanced code/shared libraries, gating

• Cloud! Cloud! Cloud!

• Technical: Flexible environment, Allocating more resources is easier, and less worry about maintenance downtime

• Business: Not paying for resources not using, reduces time to acquire “hardware”

Timebox: 6 min

ResilienceJenkins FOMO


Resilience • Version Control/Source Code Management/Backups

• Technical: Make sure you can roll back along with tracking changes

• Business: Much simpler to move jobs/applications around - keep trains running when people/tech/processes change

• Upgrades

• Technical: Automate and develop a process which is thoroughly tested

• Business: The bigger the gap, the harder the upgrade. Dig into why teams aren’t upgrading regularly

• Containers

• Technical: Flexible, movable, and isolated

• Business: Self-healing reduces prior heavy HA methods

• Pipeline & Plugins

• Technical: Durable, Restartable, and better visual tracking

• Business: limiting use of bad plugins = fewer crashes, increased security

Timebox: 5 min


Evaluation - Did It Work?• By the end of this session participants will be better able to:

• Identify one-two specific area(s) of improvement (related to DevOps) on which to focus when returning from the conference.

• Explain two specific tools/techniques she/he will try out to address this improvement.• Describe a use for Jenkins about which she/he had not previously known.• Connect with at least one new colleague outside of your team who is working on or has worked on similar areas of improvement.


Q&A● Please use the app to

provide feedback

● Tweet questions/comments #JenkinsFOMO

Thank you

(Fear of Missing Out) Jenkins FOMO...© 2018 All Rights Reserved. 5 Who We Are • Alex Taylor •Sr...

Documents

Transcript of (Fear of Missing Out) Jenkins FOMO...© 2018 All Rights Reserved. 5 Who We Are • Alex Taylor •Sr...