Pro Automation with Jenkins, GitHub Actions and n8n is a hands-on course in building CI/CD for Spring Boot, Flask and Express apps on Docker with Jenkinsfiles and GitHub Actions, then using n8n for LINE and Slack alerts, routine DevOps tasks and AI summaries of pull requests. It suits developers, system administrators and people starting out in DevOps.
Building, testing and deploying by hand every time is slow and error-prone. CI/CD makes sure every push is tested and released through clear, repeatable steps. Jenkins suits organisations that want to control their own server and pipelines, while GitHub Actions works directly with the repository. Adding n8n as the glue lets a team send alerts, connect other systems and automate the repetitive work around the pipeline with little code.
This course works hands-on with sample apps in three languages, Java Spring Boot, Python Flask and Node.js Express, all running on Docker. Learners set up a Git workflow, build pipelines as code with Jenkinsfiles on Jenkins LTS, then do the same work with GitHub Actions to compare the two. They then use n8n 2 to send results through the LINE Messaging API, Slack and email, automate DevOps tasks and use AI to summarise pull requests, finishing with a workshop that combines every tool into one flow. (3 days, 6 hours per day, 18 hours in total, Intermediate level.)
Course Details
This course is the 2026 edition of Pro Automation with Jenkins and GitHub Actions plus n8n. It runs for 3 days, 6 hours per day (18 hours in total, 09:00-16:00), as lectures with labs. Intermediate level. This edition uses the current Jenkins LTS, which needs Java 21 or later, updates GitHub Actions to current security practice, adds pushing images to GHCR and environments with approvals, moves to n8n 2 and
switches LINE alerts to the Messaging API, replacing the discontinued LINE Notify. The course focuses on using Jenkins alongside GitHub Actions and n8n; learners who want to go deep on Jenkins alone can choose Continuous Integration and Delivery with Jenkins. The main tools are open source or free, while LINE OA and AI services use the learner's own accounts. Learners take home a lab guide with Jenkinsfiles, workflow YAML files and n8n workflows.
Section 1: CI/CD and Workflow Automation
Section 2: Lab: Setting Up Your Tools
Section 3: Lab: Docker for CI/CD
Section 4: Lab: Git and GitHub for CI/CD
Section 5: Lab: Jenkins LTS and a First Jenkinsfile
Section 6: Lab: Jenkins Pipelines for Three Apps
Section 7: Lab: Connecting Jenkins to GitHub
Section 8: GitHub Actions Fundamentals
Section 9: Lab: Building and Pushing Images with GitHub Actions
Section 10: Lab: Deploying Safely with GitHub Actions
Section 11: Lab: Getting Started with n8n 2
Section 12: Lab: Build and Deploy Notifications
Section 13: Lab: Automating DevOps Tasks with n8n
Section 14: Lab: AI Summaries and Reviews of Pull Requests
Section 15: Workshop: An End-to-End Automated Flow
No public rounds are open right now. Join the waiting list and we will contact you first when the next round opens, or ask us on LINE. Or call 02-570-8449 or 088-807-9770
Continuous integration means merging the team's code often and letting the system build and run tests automatically on every push to catch problems early. Continuous delivery goes further, keeping tested code always ready to deploy while a person still approves the release. Continuous deployment releases to production automatically once every step passes. In GitHub Actions, environments with required reviewers let you choose between delivery and deployment.
Create a YAML file in .github/workflows, set on to push and pull_request, and add a job that runs on ubuntu-latest. The main steps are checking out the code, installing the language with an action such as setup-java, setup-python or setup-node, enabling the dependency cache and running the tests. Keep GITHUB_TOKEN permissions to a minimum and make the workflow a required status check in branch protection so failing code cannot be merged.
Jenkins is an open source automation server that an organisation installs and runs itself. It works with any Git provider, has a large plugin ecosystem and uses Jenkinsfiles for pipelines, suiting organisations that need full control or internal networks. GitHub Actions is built into GitHub repositories, uses YAML workflows and runs on GitHub-hosted or self-hosted runners, so it starts quickly with no server to maintain. Many teams use both together.
It suits developers who want to automate build, test and deploy work, Spring Boot, Flask or Node.js developers, system administrators, people starting out in DevOps and tech leads choosing tools for their team. You should understand web applications, use the command line and Git at a basic level and have done some programming. No prior Jenkins, GitHub Actions or n8n experience is needed.
You will be able to build Docker images for your apps, write Jenkinsfile pipelines on Jenkins LTS, create GitHub Actions workflows that build, test, push images and deploy safely, use n8n to send results through LINE, Slack and email, automate repetitive DevOps tasks and use AI to summarise pull requests with human review. Participants who complete the training receive a Certificate of Completion with its own number, which can be verified online.
Yes. The course can be run in-house, with examples adapted to the languages, Git server or alerting tools your team already uses, such as replacing the sample apps with your team's language or connecting n8n to internal systems. Contact the institute for a quotation.
Articles are published in Thai.
Every major browser now supports HTML and CSS features that used to need JavaScript or third-party libraries: forms that validate themselves, dialogs and popovers, styling based on what an element contains with :has(), components that adapt to the space they…
