This study compares the performance of three Continuous Integration and Continuous Delivery (CI/CD) tools—Jenkins, GitHub Actions, and GitLab CI/CD—within a DevSecOps pipeline for mobile application development in the context of small organizations. Most prior research has focused on general or web-based software, so the mobile pipeline remains under-studied. The authors designed a five-stage DevSecOps pipeline and built two prototype applications with the Flutter framework: a small Task Management application and a medium-sized Home Repair and Maintenance Services application. Each tool ran the complete pipeline 20 times for each application size, which gives six experimental conditions and a total sample of 120 pipeline runs (n = 3 tools × 2 application sizes × 20 runs per condition = 120). Pipeline duration and system resource usage (CPU and memory) were measured automatically. Jenkins delivered the fastest pipeline (median 127 s for the small app and 156 s for the medium app), GitLab CI/CD ranked second and was the most consistent tool, and GitHub Actions had the longest and most variable execution time. CPU usage did not differ significantly across tools, but Jenkins consumed the most memory and GitHub Actions the least. The findings reveal a clear trade-off between speed and resource use, and provide practical guidance: Jenkins for speed-driven teams, GitHub Actions for teams with limited staff and infrastructure, and GitLab CI/CD for teams that need predictable delivery.

This study developed a web-based learning system to support new-member onboarding in a multi-level marketing organization. The previous workflow used videos and business documents from separate services, allowed members to select content in an order that might not match the organization’s intended sequence, and required managers to follow up on progress manually. The implemented scope covers 13 feature areas, including role-based access control, ordered learning paths, sequential completion rules, progress tracking, business-file access with download logging, team reports, leaderboards, and manager-member feedback. These functions connect content preparation, registration, learning activities, team monitoring, and guidance within one workflow. Development followed ISO/IEC 29110 and included requirements analysis, prototyping, software design, iterative implementation, testing, and traceability verification. All 23 unit-test groups passed; 256 of 260 system-test cases passed (98.46%); and all 31 cases in the second user-acceptance round passed. The mean satisfaction scores were 4.51 out of 5 for managers and 4.71 out of 5 for members. The results indicate that the system supports a more structured onboarding process by organizing learning content into ordered learning paths with completion rules, recording learning and file-access activities, and presenting progress information through personal dashboards and team reports.