ASPE is an IIBA Endorsed Education Provider of business analysis training. Select Project Delivery courses offer IIBA continuing development units (CDU) in accordance with IIBA standards.
NASBA continuing professional education credits (CPE) assist Certified Public Accountants in reaching their continuing education requirements.
Select courses offer Leadership (PDU-L), Strategic (PDU-S) and Technical PMI professional development units that vary according to certification. Technical PDUs are available in the following types: ACP, PBA, PfMP, PMP/PgMP, RMP, and SP.
This course can be tailored to your needs for private, onsite delivery at your location.
The 21st-century software engineering practices of continuous integration (CI) and continuous delivery (CD) have rapidly come to define the best practices for software development, quality assurance and delivery. CI/CD practices are fundamental to most successful DevOps practices, and enable huge benefits for delivering more value, more frequently and with lower risk than traditional engineering. At the same time CI/CD practices drastically reduce many of the risks and pains associated with deploying software releases and bugfixes.
Jenkins has long been the community tool leader in the open-source world for practicing continuous integration and delivery. It’s more robust and enterprise-capable big brother, the CloudBees Jenkins platform, expands the capabilities users love about Jenkins to an enterprise-class toolchain and level of support.
This hands-on workshop teaches engineering and development teams to use the CloudBees Jenkins platform to run an enterprise CI/CD practice. Our lab environment and classroom model is deeply interactive, giving students hands-on practice and access to an expert in the classroom so they can return to work ready to immediately use everything CloudBees Jenkins has to offer.
A few immediate benefits of attending this course:
- Update your Agile Knowledge
- Understand how CloudBees simplifies your Jenkins Implementation
- Use CloudBees to Automate Jenkins configurations
- Use CloudBees Templates
- Automate your Software Delivery Pipeline with CloudBees Jenkins
- Implement CI/CD with CloudBees Jenkins
- Integrate CloudBees Jenkins with Git / GitHub
- Take your Agile Teams to the next level with CloudBees Jenkins
- Upcoming Dates and Locations
Guaranteed To Run
- Course Outline
As organizations increase the usage of Jenkins, scaling up to deal new issues will arise when additional masters are added to the environment. Business critical challenges are inevitable, because each master will require separate maintenance, security, and upgrades to remain functional. This course will teach you how to use CloudBees as the Master of Jenkins Masters for your solution, resulting in:
- Full control of all masters from one central control
- Accelerated automation, development, and delivery
- Meaningful, measurable, quantifiable performance enhancements
Foundations of CI/CD in enterprise environments
In order to create an efficient Jenkins environment , the stability of the source control system & the Continuous Integration infrastructure needs to be determined. The root of the CD pipeline starts with the foundation of your environment which is constantly affected by automation, integration, testing and quality assessment, and so on.
- What is Jenkns, CI & CD, and how can Jenkins help my business?
- Introduction to Jenkins and its use for CI best practices
- Feature overview: open-source Jenkins vs. enterprise CloudBees Jenkins
Agile development is creating more effective enterprises, and adoption of its values is at an all-time high. The ability to manage changing priorities, increase project visibility, and accelerate product delivery are but a few of the many benefits that Agile development creates. Overall performance has high expectations in todays digital landscape, and the implementation of Agile principles keep teams prepared for new demands, technologies, and trends.
- The Agile Manifesto
- Success with Scaling Agile
- Agile Management Tools
- Implementation of common tools
Getting started with CloudBees Jenkins
The Platform CloudBees Jenkins is at the nucleus of integration & delivery, thus the mastery of it is essential for agile development teams. Pre deployment, deployment, and post deployment functionality should be planned and considered before code is committed.
- Key components of CloudBees Jenkins
- Jobs in Jenkins
- Projects in Jenkins
- Builds in Jenkins
One of the reasons for Jenkins popularity is because it has literally hundreds of plugins that are customized to expand usage and capabilities within all solutions. These days, the right plugin can assist in fixing problems that you didn’t even know you had.
- Build Plugins
- MS Build
- Test Plug Ins
- Deployment Plugins
Integrating CloudBees Jenkins and version control
Jenkins has excellent support for various source code management systems like CVS, Subversion, Git, and more. Complicated jobs continue to need modification, as a natural condition of CI, therefore integration is often a of each new configuration.
- A Git example
- Jenkins and best SCM practices with Github
- Using Jenkins for Optimizing and Measuring Code Quality Code
- Code Coverage Metrics
- Running and using Builds
Any given project will have the option make it’s build parameterized. This enables jobs to be executed with version numbers, server URLs, node names, and specified organizational markers,
- Adding Parameters
- Passing Parameter Values
- Executing a Parameterized Build
Automation is one of the most important components necessary for a development team to by agile. Deployment automation is tricky to implement, and many people think they are doing it correctly when they are not. Without consideration of database changes, configurations, and integration points, the framework is not truly set up for continuous deployment.
- Why use Azure?
- Deploy from Local Git
- FTP or FTPS
- Kudu) Git/Mercurial/OneDrive/Dropbox
- Web Deploy
- Cloud Based SCM
- Master Server
- Client Nodes
- AWS Code Deploy
- AWS Elastic Beanstalk
Common build fails
Recognizing known issues, dealing with problems efficiently, and preventing future errors is a must when it comes to continuous delivery. Pipelines have introduced much greater traceability of changes to the build process, so that build fails can be dealt with immediately.
- Detecting the source of a build failure
- Troubleshooting Jenkins Builds
- Build failure Analyzer
- Build log scanning
- Git Timeouts
- Pip Timeouts
Folders in Jenkins
- Folders Plus
- Validated Merges
- Using GitHub for validated merges
- Pull-Request Builder for GitHub
- Running a CI/CD Pipeline through CloudBees Jenkins
- Pipeline development tools
- Pipeline Plugin
- Trigger a pipeline
Overview of CloudBees Jenkins Operation Center
CloudBees Operations Center assists developers & engineers with risk assessment, compatibility of functionality, older components vs newer releases, and verification of upgrade paths.
- Authentication schemes
- Consolidated management
- Security, resilience, & enforcement
- CloudBees Analytics
- Managing CJOC Tasks
- Who should attend
- Software Developers
- Project Managers
- Quality Assurance Professionals
- Software Testers
- Product Owners
- Business Intelligence Professionals
- Infrastructure Engineers
- Development Team Members
- Operations Team Members
- Anyone who is a hands-on user of the CloudBees Jenkins platform
- Maven plugin
- Junit plugin
- Sonar Plugin