Download to read offline
Uploaded byChu Xu
Solano vs Jenkins
The document discusses switching from Jenkins to Solano CI. It provides an overview of Solano CI, describing it as a continuous integration and deployment solution available as both a hosted SaaS product and private virtual appliance. It outlines some of the key requirements and benefits of a hosted CI system like Solano CI, such as easy setup, parallel performance, analysis capabilities, and compatibility with popular programming languages. The document then compares Jenkins setup to Solano CI setup, noting issues like arbitrary jobs and nodes in Jenkins that require maintenance. It also describes the Jenkins to Solano CI conversion process. Finally, it highlights reasons to switch to Solano CI, including optimized performance, high availability, simplified administration and maintenance, advanced security features, and
More Related Content
Solano vs Jenkins
- 1. Switching from Jenkins toSolano CI
- 2. Solano Labs ©2014 Confidential Attendees are on mute Submit questions via chat feature in webinar’s console Recording will be available later this week HOUSE KEEPING 2 T T T Solano Labs © 2016 Confidential
- 3. Solano Labs ©2014 Confidential What is Solano CI and where does it fit in the delivery pipeline? Requirements and benefits of a hosted CI system like Solano Jenkins Setup vs Solano Setup Why Solano CI? Demo Q&A AGENDA 3 T1 T2 T3 T4 T5 5T6 Solano Labs © 2016 Confidential
- 4. Solano Labs ©2014 Confidential Solano Labs founded in March 2011 Solano CI is a continuous integration and deployment solution, and is available both as a hosted SaaS solution and private virtual appliance. Solano CI automatically and intelligently parallelizes automated software tests to deliver results 10 to 80 times faster than existing solutions. WHAT IS SOLANO CI? 4 Visit our website for more information on Continuous Integration and Deployment Start Code Review Commit Code Staging QA Signoff Deploy Solano Labs © 2016 Confidential
- 5. Solano Labs ©2014 Confidential EASY SETUP Fast self-service setup for new projects and branches, compact YAML config file. PARALLEL PERFORMANCE Safe parallel execution and dynamic task distribution finish builds faster, automatically. ANALYSIS SSH into a Worker, Screenshots & Attachments, detailed history, & metrics. COMPATIBILITY Seamlessly supports popular languages (Java, C/C++, Python, Ruby, Javascript, Scala, PHP, Go). CONTINUOUS INTEGRATION Tests every code change, automatically. No excuses. REQUIREMENTS OF A HOSTED CI SYSTEM LIKE SOLANO Solano Labs © 2016 Confidential 4 T1 T2 T3 T4 T5
- 6. Solano Labs ©2014 Confidential • Proper setup of a continuous integration system enables faster, more agile development and continuous delivery. BENEFITS OF A HOSTED CI SYSTEM LIKE SOLANO Devs Push Code Build Workers Install Packages Auto Configured Selenium, DBs, Search Builds Finish Faster with Safe Parallel Execution Debug with Screenshots , Logs, History Auto- Deploys and Notifies you via Email, IM & GitHub Solano Labs © 2014 Confidential 4Solano Labs © 2016 Confidential • Faster ability to spot errors, faster ability to debug and recover, faster ability to deploy. • Valuable IT time is spent building tools, not maintaining test infrastructure.
- 7. Solano Labs ©2014 Confidential JENKINS SETUP • Arbitrary number of Jenkins jobs (seems like a benefit at first) • As job XML files are edited, necessity for manual cleaning and maintenance grows, as does likelihood for mistakes, errors. • Jobs can be grouped improperly (manual error) - mistakenly using same repos – Name prefix – Build triggers – Plugins • Nodes (“slaves”) become corrupt and messy with dependencies, sometimes undocumented ghosts • Expensive bottleneck type administration – One or a handful of people have all control over execution and maintenance – Takes power out of developers’ hands • You break it, you buy it JENKINS Setup Master JOB XML Repo A … Node B, C Repo B … Node A, B Repo C … Node A, C Node A Node B Node C Repo A Repo B Repo C JENKINS JOB Solano Labs © 2016 Confidential
- 8. Solano Labs ©2014 Confidential JENKINS CONVERSION PROCESS JOB XML Repo A … Repo B … Repo C … Download each Jenkins job config.xml file you want to port to your hosted CI Branch A Repo Branch B Repo Branch C Repo YML YML YML T1 T2 Parse out each repository- down to the branch level- with its own solano.yml PRODUCTION REPO YML Solano Labs © 2016 Confidential
- 9. Solano Labs ©2014 Confidential SOLANO CI SETUP SOLANO CI WORKER • One Jenkins Job --> One repository/branch • Each repo branch can have a different configuration. • Repository-specific configuration listing all of the associated tasks • Power is democratized to the developers • Spend your valuable IT time building tools, not maintaining test infrastructure WORKER WORKER Repo A Repo B Repo C YML YML YML Solano Labs © 2016 Confidential
- 10. Solano Labs ©2014 Confidential SOLANO CI RUNTIME SOLANO CI WORKER • Fresh worker image created every time for each job – Keeps process clean and organized – Additional benefit of discovering undocumented dependencies • Automatically spreads tests across parallel workers. • Automatically runs builds concurrently • Flexible build profiles allow you to run different test suites on the same repo WORKER WORKER Repo A Repo B Repo C YML YML YML Solano Labs © 2016 Confidential
- 11. Solano Labs ©2014 Confidential WHY SOLANO? Solano CI Optimized Performance High Availability Simplified Admin & Maintenance Distributed Team Management Advanced Security Container Support Highly Configurable Deployment & Notification Hooks Most Advanced Integration in AWS Auto- Parallelism Engine Solano Labs © 2016 Confidential
- 12. Solano Labs ©2014 Confidential MAINTENANCE • Jenkins CI requires a full team to implement, support, and maintain. Solano CI system is automated with maintenance and updates provided by the Solano CI team. As a result, there is no more valuable CI downtime due to plugin updates or additional time spent administering backups on your end. • Painless, revision-controlled setup: fast self-service setup for new projects and branches, compact YAML configuration file that lives in the code repository Solano Labs © 2016 Confidential
- 13. Solano Labs ©2014 Confidential PERFORMANCE & TIME SAVINGS Fully Automated Parallelism & Work Distribution • Solano CI is the fastest on the market – central to the core from the beginning, 5 years ago. Work is automatically found, batched, and distributed. • Solano's automated test parallelization makes performance speed ups easier to achieve than Jenkins- up to 80X faster. A majority of Solano CI customers have switched from a Jenkins build system to Solano CI because it reduces their build times from hours to minutes. Solano Labs © 2016 Confidential
- 14. Solano Labs ©2014 Confidential SCALABILITY • Powerful Dynamic Scaling - Automatic scaling for hundreds or thousands of tests • Dive deeper into totally automated workflows - even for complex environments. Control how to run your build and tests with Build Profiles and Plans. Solano Labs © 2016 Confidential
- 15. Solano Labs ©2014 Confidential • Offers best-in-class Security • Private Virtual Appliance - Solano CI is available as a private virtual appliance. It is most commonly deployed in a private installation using Amazon's Virtual Private Cloud and secured so that it is accessible only through desired networks. Other deployment models are also available. SECURITY Solano Labs © 2016 Confidential
- 16.
- 17.
Editor's Notes
- #2 Thank you so much for joining us this morning, we’re here to discuss Switching from Jenkins to Solano CI so we'll discuss requirements of a successful continuous integration platform & process, why transitioning out of Jenkins is critical to the success of your agile development goals, and how you can use this technology to become a DevOps champion.
- #5 Change “Commit Code” to “Merge” or “Merge & Test”? Typical workflow – - Check out code -Made a branch -Make your change -Commit code -Run tests -Code Review -Staging…QA Signoff…Deploy
- #6 **Change title to “Qualities of a strong CI system” and then at the end “Solano covers all of these.” What are the features that are necessary to be privded in a CI system for maximum productivity and efficiency? 1) First off, you want something that is easy to set up, to be able to be set up by multiple users for new projects and even branches. And we want to have a YAML style configuration file, which we we will get in to more detail of why that’s important. 2) Parallel performance – this is a must have for achieving the fastest builds to get the fastest results and we believe this should be an automatic, out of the box feature that can intelligently find and distribute work, and should not be maintained by the user. 3) We should also have features that enable us to analyze our builds and that provide us with intelligence and debug capability to fix errors faster. 4) We need one system that supports a variety of languages and tools 5) All of this is pushing us towards continuous integration. If we get results back within seconds or minutes, changes can be made while code is fresh in the user’s mind.
- #7 So now we know what we’re looking for, and here is what you’ll get if we employ a system with these features and capabilities: You’ll enable a true continuous integration flow that is completely automated, so developers can focus on developing.
- #8 Now that we know what we’re looking for and the overall benefit a powerful hosted CI solution can offer, let’s take a step back and understand the small
- #9 Add a line that developers can add a repo for each branch if they want – be confident that their changes are correct. Simple, version controlled syntax. Tar Baby? What do I get for doing this work?
- #10 Red highlight are benefits of the runtime model of Solano, not of the setup
- #12 **Logo instead of ”Solano CI” These are the features we feel every developer should have in their continuous integration system and which we feel set us apart.
- #14 Split in to 2 slides
- #15 Split in to 2 slides