# Jenkins Published articles for Jenkins. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Migrating to a Mobile Monorepo for React Native DevFeed: [Migrating to a Mobile Monorepo for React Native]() Original publisher: [Read original article]() Author: Khan Academy Published: 2017-05-29T22:00:00Z Content type: tutorial Language: en Sources: [Khan Academy]() Topics: [monorepo](), [React Native](), [Mobile](), [Submodules](), [Android](), [iOS](), [pull-requests](), [Jenkins]() Tags: [also](), [android](), [engineering](), [ios](), [jenkins](), [mobile](), [monorepo](), [news](), [react-native](), [submodules]() ### AI overview Khan Academy describes moving its React Native-related iOS and Android repositories from separate repositories and submodules into a single mobile monorepo. The change was intended to reduce synchronization problems, coordinate bridge changes across platforms, make pull requests and reviews more coherent, and simplify verification between codebases. The article also outlines repository-merging steps and anticipated trade-offs. ### Source excerpt By Jared Forsyth Over the past few months, we've been adding some React Native to our existing iOS ... Read more ## Port's Integration Catalog: 200+ Tools for Your Context Lake DevFeed: [Port's Integration Catalog: 200+ Tools for Your Context Lake]() Original publisher: [Read original article]() Author: Alina Barenboim Published: 2026-08-10T16:27:08Z Content type: article Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [CI/CD](), [Kubernetes](), [GitHub](), [Provisioning](), [incident management](), [Application Performance Management (APM)](), [Security](), [Code review](), [Deployment](), [DevOps](), [GitHub Actions](), [GitLab]() Tags: [apm](), [ci-cd](), [deployment](), [devops](), [git](), [github](), [github-actions](), [gitlab](), [incident-management](), [jenkins](), [kubernetes](), [review](), [security](), [vulnerabilities]() ### AI overview Port's Integration Catalog describes more than 200 integrations that unify engineering-tool data in a queryable Context Lake. It covers Git, Kubernetes, CI/CD, incident management, APM, security scanning, service mesh, policy violations, deployments, build results, and code activity, with support for custom integrations through Ocean, connectors, APIs, events, and MCPs. ### Source excerpt Explore Port's 200+ integrations across CI/CD, Kubernetes, incident management, security, and more, all feeding one Context Lake. ## Set Up Developer Self-service in Your Internal Developer Portal | Port DevFeed: [Set Up Developer Self-service in Your Internal Developer Portal | Port]() Original publisher: [Read original article]() Author: Yonatan Boguslavski Published: 2026-07-30T10:17:19Z Content type: tutorial Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [internal developer portal](), [Platform Engineering](), [Provisioning](), [Terraform](), [AWS Lambda](), [Jenkins](), [REST API](), [GitHub](), [Amazon S3](), [Microservice]() Tags: [api](), [aws](), [aws-lambda](), [catalog](), [cognitive-load](), [configuration](), [developer](), [developer-portal](), [github](), [infrastructure](), [internal-developer-portal](), [jenkins](), [platform-engineering](), [provisioning](), [rest-api](), [s3](), [terraform](), [tooling]() ### AI overview This article explains how to implement developer self-service actions in Port's internal developer portal. It covers provisioning, updating, and deleting software catalog entities and cloud resources, while describing webhook-based execution through tools such as AWS Lambda and REST APIs. ### Source excerpt Port supports many variations of implementing developer self service actions, including allowing for self-service RBAC, TTL and manual approvals. ## Best Jenkins Alternatives in 2026 DevFeed: [Best Jenkins Alternatives in 2026]() Original publisher: [Read original article]() Author: Pete Miloravac Published: 2026-07-24T09:56:00Z Content type: article Language: en Sources: [Semaphore Engineering]() Topics: [CI/CD](), [Jenkins](), [Groovy](), [GitHub Actions](), [GitLab](), [Vulnerabilities](), [DevOps](), [Open Source]() Tags: [ci-cd](), [circleci](), [compare](), [devsecops](), [github-actions](), [gitlab](), [groovy](), [jenkins](), [open-source](), [security](), [security-vulnerabilities](), [self-hosted]() ### AI overview A 2026 guide compares Jenkins alternatives and explains why teams migrate away from Jenkins, citing maintenance overhead, plugin conflicts, Groovy pipeline complexity, and security-patch concerns. It highlights Semaphore, GitHub Actions, GitLab CI/CD, and CircleCI for different use cases. ### Source excerpt Jenkins earned its place as the default CI server of the 2010s: it was free, endlessly extensible, and available before any serious managed CI/CD competitor existed. More than a decade later, that same flexibility has become the thing teams complain about most -- plugin sprawl, Groovy pipeline scripts nobody wants to maintain, and infrastructure that [...] The post Best Jenkins Alternatives in 2026 appeared first on Semaphore. ## Nix flake check + JUnit = Junix DevFeed: [Nix flake check + JUnit = Junix]() Original publisher: [Read original article]() Author: Yajo Published: 2026-07-23T12:35:46Z Content type: release Language: en Sources: [Announcements - NixOS Discourse]() Topics: [Nix](), [ci](), [GitHub](), [GitHub Actions](), [GitLab](), [Jenkins]() Tags: [announcements](), [build](), [ci](), [github](), [github-actions](), [gitlab-ci](), [jenkins]() ### AI overview Junix converts Nix JSON output into standard JUnit XML reports, allowing Nix builds and checks to integrate with JUnit-compatible CI systems such as GitLab CI, Jenkins, and GitHub Actions. It can evaluate system checks, repeat failed evaluations for full tracebacks, build local checks, include logs, and print a human-readable summary. ### Source excerpt Hi all! I'd like to share Junix, a small tool that converts Nix @nix JSON output into standard JUnit XML so you can integrate Nix builds with any JUnit-compatible CI (GitLab CI, Jenkins, GitHub Actions, etc.). Try it: cd your/flake nix run gitlab:moduon/junix check -o result.xml This will: Eval all systems checks in one shot If any eval fails, repeat that check's eval to get full traceback Build local system checks Write the JUnit XML report in result.xml with check build logs and eval failure logs, if any Print a colorful human-readable summary 9 posts - 6 participants Read full topic ## Platform Product Management: AI-enabled vs. AI-native capability stacks DevFeed: [Platform Product Management: AI-enabled vs. AI-native capability stacks]() Original publisher: [Read original article]() Author: Poojitha Marreddy Published: 2026-07-23T05:40:01Z Content type: article Language: en Sources: [Platform Engineering Blog]() Topics: [Product Management](), [code productivity](), [developer-productivity](), [Artificial Intelligence](), [Infrastructure as code](), [Terraform](), [DevSecOps](), [GitHub](), [Jenkins](), [Kubernetes]() Tags: [agents](), [ai](), [code](), [cognitive-load](), [configuration](), [developer](), [developer-productivity](), [devsecops](), [github](), [iac](), [jenkins](), [kubernetes](), [management](), [platform](), [product](), [productivity](), [terraform]() ### AI overview This article presents platform product management as a way to reduce developer cognitive load and improve delivery velocity. It contrasts AI-enabled capability stacks, which use AI to assist developers, with AI-native stacks, which run AI workloads; both depend on an internal developer platform but require different investments, governance, and success metrics. The article introduces the double diamond framework for discovering, defining, developing, and delivering platform capabilities. ### Source excerpt Platform PM framework: Shift from tool standardization to product thinking. Learn to build AI-enabled vs AI-native stacks to boost developer productivity ## Osmocom.org Servers - server outage of host3.osmocom.org DevFeed: [Osmocom.org Servers - server outage of host3.osmocom.org]() Original publisher: [Read original article]() Author: laforge Published: 2026-07-06T18:58:49Z Content type: news Language: en Sources: [Open Source Mobile Communications: News]() Topics: [servers](), [Debian](), [maintenance](), [upgrade](), [Jenkins]() Tags: [bug](), [debian](), [hosting](), [issue](), [jenkins](), [maintenance](), [outage](), [server](), [servers](), [tracker](), [update](), [upgrade]() ### AI overview Osmocom.org reports an outage affecting host3.osmocom.org during routine maintenance for a Debian upgrade. The host, which primarily serves Jenkins, downloads, and people subdomains, has fully recovered. ### Source excerpt We're currently experiencing some troubles during routine maintenance (Debian upgrade) of host3.osmocom.org, which is primarily hosting jenkins.osmocom.org, downloads.osmocom.org and people.osmocom.org. We ask for your patience while we try to resolve the situation. Update: host3 has fully recovered. ## hh.ru's Test Framework Experiments for Handling Flaky Tests DevFeed: [hh.ru's Test Framework Experiments for Handling Flaky Tests]() Original publisher: [Read original article]() Author: yzhanov (hh.ru) Published: 2026-05-07T07:10:11Z Content type: article Language: ru Sources: [HeadHunter RU]() Topics: [Jenkins](), [Job](), [ui]() Tags: [flaky](), [hh](), [hh-ru](), [jenkins](), [job](), [qa](), [qa-automation](), [qa-automation-engineer](), [qa-engineer](), [qa-management](), [qa-mobile](), [qa-testing](), [retry](), [tag-4adf7d504f34](), [tag-95a52fc82d81](), [tag-b7f0358ac141](), [tag-e34f6dec12c4](), [tag-e932065bc8da](), [ui]() ### AI overview An hh.ru engineer describes experiments in the test framework to reduce the impact of flaky tests on release automation. One experiment allowed repeated retries until the queue emptied; it added about three minutes to build time and was not adopted in production. ### Source excerpt Привет, Хабр! Меня зовут Юра Жанов, я занимаюсь автоматизацией тестирования в hh.ru. Про flaky-тесты написано много, борьбу с ними не прекращаем и мы. Но сегодня немного о другом -- хочу поделиться нашим опытом минимизации неприятностей, которые наносят такие тесты. Для этого мы провели ряд экспериментов со стороны тестового фреймворка. Читать далее ## Jenkins Series DevFeed: [Jenkins Series]() Original publisher: [Read original article]() Author: baeldung Published: 2026-04-03T12:36:55Z Content type: tutorial Language: en Sources: [Baeldung - Ops]() Topics: [Jenkins](), [Automation](), [CI/CD](), [Groovy](), [Scripting](), [Server](), [Open Source]() Tags: [administration](), [automation](), [ci-cd](), [docker](), [jenkins](), [jenkins-series](), [open-source](), [scripting](), [series](), [server]() ### AI overview A tutorial series covering Jenkins pipelines, job management, administration, Groovy scripting, parameterized and parallel builds, and server maintenance across the CI/CD lifecycle. ### Source excerpt This tutorial provides an overview of Jenkins pipelines, job management, and administration. Related Stories Git Series Troubleshoot Docker Daemon Connection Issues in Jenkins Troubleshooting Jenkins 403 No Valid Crumb in Request Error ## Headless Screenshot Testing in Thumbtack's Android Apps DevFeed: [Headless Screenshot Testing in Thumbtack's Android Apps]() Original publisher: [Read original article]() Author: Brian Terczynski Published: 2026-03-31T22:47:00Z Content type: tutorial Language: en Sources: [Thumbtack Engineering - Medium]() Topics: [screenshot-testing](), [Testing](), [Android](), [Emulator](), [Firebase](), [Jenkins]() Tags: [android](), [android-app-development](), [emulator](), [firebase](), [jenkins](), [mobile](), [robolectric](), [roborazzi](), [screenshot-testing](), [sdk](), [testing]() ### AI overview Thumbtack explains how it chose Roborazzi to run high-fidelity screenshot tests for its Android apps without an emulator. The article describes how emulator-based testing was slow and difficult to use for Jenkins verification, especially with more than 1,500 tests. ### Source excerpt How we chose Roborazzi for fast, easy, and high-fidelity screenshot tests of our Android apps, without needing to run them on an emulator. As mentioned in our earlier blog post, screenshot tests are a fundamental part of our testing pyramid at Thumbtack. They validate that our UI code renders correctly. They catch UI regressions as our code evolves. They make it easy to share incremental progress with designers. In code reviews, they provide a great way for reviewers to "see" what the UI code is doing. Finally, they are very easy to write! But they were not always easy to run. Because they tested Android UI code, they had to run in a "real" Android environment so that the drawing operations would work. This meant running them on an Android device or emulator. To ensure consistent renderings, developers would have to run their tests on the same device used by our CI job. In the past, this meant having to run a script that would connect to our cloud device testing provider to generate the reference image, which would then be downloaded for inclusion in the local Git branch. Such a process would take minutes to run (not including build time). This got easier when we switched to Firebase Test Lab (FTL), because their emulators were the same as the emulators provided in the Android SDK used on developers' machines. Developers could then simply run their tests on a local emulator which sped up execution time significantly. But it still meant the emulator profile needed to match that of the device on FTL; in particular, the screen size and pixel density. Another problem was, because these were run on an emulator, they could not run with our CR verification job on Jenkins because their execution time was too slow (especially since we have over 1,500 of these tests!). This therefore meant that we had to run our screenshot tests separately, and they could not be used to gate code pushes because they were just too slow to run. So what would often happen was developers would me ## How we standardized MariaDB in our Integration Server DevFeed: [How we standardized MariaDB in our Integration Server]() Original publisher: [Read original article]() Author: Eloy Gonzalez Published: 2026-03-26T18:59:43Z Content type: article Language: en Sources: [Wealthfront]() Topics: [MariaDB](), [Testing](), [migration](), [Databases](), [Jenkins](), [CI/CD](), [Back end]() Tags: [architecture](), [backend](), [careers](), [ci-cd](), [data](), [engineering-culture](), [hibernate](), [infrastructure](), [integrity](), [jenkins](), [locking](), [migration](), [modularization](), [production](), [sql](), [testing](), [tests](), [wealthfront-engineering]() ### AI overview Wealthfront describes migrating its Integration Server from HSQLDB to MariaDB to improve parity with production. The article covers the migration strategy, architectural hurdles, and benefits for data integrity, concurrency, locking, and production-like testing. ### Source excerpt Engineering at Wealthfront is centered on the idea that code should be written to facilitate testing, not the other way around. Without a staging environment to fall back on, we maximize confidence through a sophisticated, multi-layered testing strategy. While unit tests provide our most rigorous line of defense, our Integration Server is the workhorse that... Read more ## Odin: Dream11's Open-Source Deployment Platform Built After Jenkins Deployment Challenges DevFeed: [Odin: Dream11's Open-Source Deployment Platform Built After Jenkins Deployment Challenges]() Original publisher: [Read original article]() Author: Dream Blog Published: 2025-12-11T07:55:37Z Content type: article Language: en Sources: [Dream11 Engineering]() Topics: [Deployment](), [Jenkins](), [DevOps](), [Open Source](), [Testing](), [Microservice]() Tags: [deployment](), [developer](), [devops](), [dream-horizon](), [jenkins](), [microservices](), [open-source](), [tech](), [testing]() ### AI overview This article introduces Odin, Dream Horizon's open-source deployment platform from Dream11. It describes how Dream11 evolved from numerous Jenkins jobs to a deployment system intended to support building, testing, and deploying services through on-demand environments. The article identifies job complexity, limited support for virtual machines and Kubernetes, and the lack of a unified deployment-lifecycle vision as challenges in the earlier setup. ### Source excerpt By Suraj Gour and Ankit Pare Dream Horizon, our open-source effort to make Dream11's battle-tested tech available to every developer, brings you Odin -- a high-performance deployment platform that lets developers build, break, test, and ship smarter and more efficiently. Explore Odin here. Deployments at Dream11 have come a long way. From Jenkins jobs to on-demand environments, we have reimagined how services are built, tested and deployed. With Odin -- our new deployment system -- developers define what they need and deploy with confidence in seconds. This evolution started with key lessons from our earlier setup. Navigating Jenkins Mayhem: When Jobs Ran Wild It was a regular day at Dream11. A new joiner was browsing onboarding documents, trying to understand how to test their code alongside other dependent microservices, and then eventually deploy it live in production. They simply asked their teammate how to proceed. Here's how their conversation went: The newly joined developer (looking perplexed) asked: "My code is master-merged. How can I test the complete user authentication flow? And what are the steps I need to follow to get my feature live in production? I can't seem to find any documentation around this."The teammate (with a sympathetic sigh) replied: "Come with me. Let's talk to the DevOps team. They'll guide you and take you through the process."Upon reaching the DevOps team, our developer presented their request.The DevOps team (calmly, with the weariness of having answered this question several times) responded: "You want to push this code to production? Alright. We have a set of Jenkins jobs for this."The newly joined developer asked again: "And what about testing in a dev environment and performing a load test?"The DevOps team replied: "For load tests, we have... guess what... separate jobs!" Jenkins jobs introduced more complexity than clarity. More jobs meant greater uncertainty and longer turnaround times. Given our use case, we were running into recurr ## Gradle Now Maintains the Official Docker Image DevFeed: [Gradle Now Maintains the Official Docker Image]() Original publisher: [Read original article]() Author: Laura Kassovic Published: 2025-09-15T04:00:00Z Content type: release Language: en Sources: [The Gradle Blog]() Topics: [Gradle](), [Docker Image](), [Docker](), [Docker Hub](), [CI/CD](), [GitHub Actions](), [GitLab](), [Jenkins]() Tags: [ci-cd](), [docker](), [docker-hub](), [docker-image](), [github](), [github-actions](), [gitlab](), [gradle](), [jenkins](), [open-source](), [releases](), [support]() ### AI overview Gradle is now the official maintainer of the Gradle Docker image on Docker Hub. The article explains that the image will be kept current with Gradle releases, including security updates, while its usage, CI workflows, and community support continue to evolve. ### Source excerpt We're excited to announce we're now the official maintainer of the Gradle image on Docker Hub. For years, developers have relied on the Gradle Docker image to run builds in containers and CI/CD pipelines. Originally created and maintained by community contributor Keegan Witt, this image became a trusted resource for thousands of teams. Today, we're bringing it under the Gradle organization to ensure it remains reliable, up to date, and aligned with Gradle's release cadence. Why this Matters Docker is a critical part of modern software delivery. Many teams build and test their projects in containerized environments, and CI/CD platforms like GitHub Actions, GitLab CI, and Jenkins depend on official images to provide consistency and trust. By becoming the official maintainer of the Gradle Docker image, we can: Provide timely updates for each Gradle release, including security fixes Ensure alignment with the official Gradle -bin distributions Collaborate with the community to evolve the image for new use cases Provide support through the standard support channels (Slack and Community Forum) This also reduces the burden on individual contributors who've generously kept the image running until now. A big Thank You We want to recognize Keegan Witt, who has maintained the Gradle Docker image for years. His diligent work ensured developers could trust the image long before it became officially supported. We're grateful for his contributions and stewardship! What to Expect Going Forward The official Gradle Docker image will continue to be published under hub.docker.com/_/gradle. Images will be kept aligned with Gradle releases to the greatest extent possible. We'll review and evolve best practices for image usage, including improvements for CI workflows and ephemeral build environments. Using the Image Try the latest official image today: docker pull gradle:latest Or specify a versioned tag: docker pull gradle:9.0.0-jdk17 Get Involved The Gradle Docker image remains open sour ## Expanding Chainguard VMs: Zero-CVE Application & Base Virtual Machine Images for Cloud and On-Prem DevFeed: [Expanding Chainguard VMs: Zero-CVE Application & Base Virtual Machine Images for Cloud and On-Prem]() Original publisher: [Read original article]() Published: 2025-09-03T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard vms](), [Cloud](), [on-prem](), [chainguard os](), [Java](), [Jenkins](), [nginx](), [Python]() Tags: [chainguard-vms](), [cloud](), [cloud-virtual-machines](), [cve](), [java](), [jenkins](), [nginx](), [on-prem](), [os](), [provenance](), [python](), [rebuilds](), [sbom](), [secure-by-default](), [security-vm-images](), [virtual-machine-images](), [zero-cves]() ### AI overview Chainguard VMs is expanding with zero-CVE application images for Jenkins, Nginx, and Squid Proxy, plus base images for Chainguard OS, Java, and Python. The virtual machine images support cloud and on-premises deployments and are continuously rebuilt from source with automated updates, CVE remediation, and SBOM-driven provenance attestations. ### Source excerpt Chainguard VMs is expanding with new Application and Base VM Images -- giving teams a secure, zero-CVE foundation to build and innovate faster. ## Watch the on-demand webinar: Shift left without the strain DevFeed: [Watch the on-demand webinar: Shift left without the strain]() Original publisher: [Read original article]() Author: Rob Samuels Published: 2025-07-14T13:00:00Z Content type: article Language: en Sources: [PortSwigger Blog]() Topics: [Application Security](), [CI/CD](), [Testing](), [Docker](), [GitHub Actions](), [GitLab](), [Jenkins](), [YAML](), [configuration]() Tags: [ci-cd](), [ci-cd-workflows](), [configuration](), [containers](), [docker](), [false-positives](), [github-actions](), [gitlab](), [jenkins](), [security](), [shift-left](), [software-delivery](), [yaml]() ### AI overview This article promotes an on-demand webinar about shifting application security left without slowing software delivery. It discusses the challenges of integrating DAST into CI/CD workflows, including slow scans, false positives, and workflow friction, and presents Burp Suite DAST as a fast, configurable, Docker-based solution that integrates with common pipeline tools. ### Source excerpt Shifting security left promises faster, safer software delivery - but for many teams, that promise is undercut by painful scan performance, false positives, and pipeline friction. In our recent webina ## Your Infrastructure Has a Non-Human Trust Problem DevFeed: [Your Infrastructure Has a Non-Human Trust Problem]() Original publisher: [Read original article]() Author: jack.pitts@goteleport.com (Jack Pitts) Published: 2025-06-04T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [Security](), [cloud security](), [Zero Trust](), [CI/CD](), [GitHub Actions](), [Kubernetes](), [Amazon Web Services](), [GitLab](), [Jenkins]() Tags: [agent](), [agents](), [auditability](), [aws](), [ci-cd](), [cloud-security](), [credentials](), [github-actions](), [gitlab](), [jenkins](), [kubernetes](), [secrets](), [security](), [token](), [tokens](), [zero-trust]() ### AI overview This article explains how non-human identities, including bots, CI/CD runners, and AI-driven automation, can create cloud security and resiliency risks when they use static credentials and excessive permissions. It presents Teleport Machine & Workload Identity as a way to use short-lived, scoped cryptographic credentials and reviews CI/CD deployment to Kubernetes as an example. ### Source excerpt Non-human identities are a major cloud security risk. Learn how to eliminate static credentials, enforce zero trust, and secure machine-to-machine access. ## Node.js Test CI Security Incident DevFeed: [Node.js Test CI Security Incident]() Original publisher: [Read original article]() Published: 2025-04-23T16:30:00Z Content type: article Language: en Sources: [Node.js Blog]() Topics: [incident](), [Node.js](), [ci](), [Jenkins](), [Security](), [Git](), [GitHub]() Tags: [ci](), [git](), [github](), [incident](), [jenkins](), [node-js](), [security](), [vulnerabilities](), [vulnerability]() ### AI overview Node.js reported a successful compromise of several test CI hosts after an attacker used a pull request and an outdated Git commit timestamp to cause Jenkins pipelines to execute altered fork code. The incident exposed a Time-of-Check-Time-of-Use vulnerability involving mutable Git references. The team restricted CI runs, rebuilt 24 compromised hosts, enforced commit SHA validation, audited 140 Jenkins jobs, and patched vulnerable GitHub workflows. ### Source excerpt Node.js® is a free, open-source, cross-platform JavaScript runtime environment that lets developers create servers, web apps, command line tools and scripts. ## How Indeed Replaced Its CI Platform with Gitlab CI DevFeed: [How Indeed Replaced Its CI Platform with Gitlab CI]() Original publisher: [Read original article]() Author: Carl Myers Published: 2024-08-06T15:03:51Z Content type: article Language: en Sources: [Indeed]() Topics: [GitLab](), [CI/CD](), [Jenkins](), [Kubernetes](), [Amazon EC2](), [Amazon Web Services]() Tags: [aws](), [ci](), [ec2](), [gitlab](), [gitlab-ci](), [jenkins](), [kubernetes](), [unsorted]() ### AI overview Indeed's engineering platform evolved from Hudson to Jenkins and later encountered architectural and scaling limitations as the company grew and adopted AWS EC2 and Kubernetes. The article discusses replacing that CI platform with GitLab CI. ### Source excerpt Here at Indeed, our mission is to help people get jobs. Indeed is the #1 job site in the world with over 580M+ Job Seeker Profiles. For Indeed's Engineering Platform teams, we have a slightly different motto: "We help people to help people get jobs". As part of a data-driven engineering culture that has spent [...] ## Using a Portable Monitor for Home-Lab Debugging and Streaming DevFeed: [Using a Portable Monitor for Home-Lab Debugging and Streaming]() Original publisher: [Read original article]() Author: Alex Ellis Published: 2024-06-12T13:47:26Z Content type: opinion Language: en Sources: [Alex Ellis' Blog]() Topics: [Homelab](), [monitor](), [Raspberry Pi](), [Jenkins](), [Tooling](), [ci]() Tags: [ci](), [debugging](), [headless](), [home-lab](), [jenkins](), [portable](), [raspberry-pi](), [video]() ### AI overview The article explains why the author prefers a portable monitor for debugging headless home-lab computers, setting up Raspberry Pis, monitoring Jenkins CI pipelines, and managing streaming or product-demo software. ### Source excerpt I cover why as a one monitor kind of guy, I found a portable monitor essential - both for streaming and for debugging the home lab. ## Bazaarvoice Notification System for Transactional Email Delivery DevFeed: [Bazaarvoice Notification System for Transactional Email Delivery]() Original publisher: [Read original article]() Author: Someswar Bhowmick Published: 2024-04-24T10:24:56Z Content type: article Language: en Sources: [Bazaarvoice]() Topics: [notifications](), [Amazon Web Services](), [Amazon EC2](), [Amazon S3](), [AWS CloudFormation](), [Jenkins]() Tags: [aws](), [cloud](), [cloudformation](), [ec2](), [email](), [engineering](), [jenkins](), [notifications](), [s3](), [scalability](), [serverless](), [software-architecture]() ### AI overview Bazaarvoice describes its notification system for sending transactional email on behalf of clients. The article outlines data ingestion and a decision engine for scheduled delivery, then discusses operational challenges in its earlier AWS-based architecture, including EC2 scaling, updates, logging, and prolonged file-processing batch jobs. ### Source excerpt Bazaarvoice notification system stands as a testament to cutting-edge technology, designed to seamlessly dispatch transactional email messages (post-interaction email or PIE) on behalf of our clients. The heartbeat of our system lies in the constant influx of new content, driven by active content solicitations. Equipped with an array of tools, including email message styling, default [...] ## CI Shootout: Getting started with Jenkins, Concourse, Tekton and Argo Workflows DevFeed: [CI Shootout: Getting started with Jenkins, Concourse, Tekton and Argo Workflows]() Original publisher: [Read original article]() Author: Tom Godkin Published: 2023-10-04T11:05:39Z Content type: comparison Language: en Sources: [Blog - Container Solutions]() Topics: [ci](), [Self-hosted](), [Jenkins](), [Kubernetes]() Tags: [argo](), [ci](), [continuous-integration](), [helm](), [jenkins](), [kubernetes](), [self-hosted](), [workflows]() ### AI overview This comparison evaluates Jenkins, Concourse, Tekton, and Argo Workflows as self-hosted CI systems. It examines installation and configuration, along with introductory pipeline tasks, using deployments to an existing Kubernetes cluster. ### Source excerpt At EngineerBetter we've evaluated four self-hosted CI systems in order to compare them against each other: Jenkins, Concourse, Tekton and Argo Workflows. For each CI system we've created some pipelines that: ## 8 tips for securing your CI/CD pipeline with Snyk DevFeed: [8 tips for securing your CI/CD pipeline with Snyk]() Original publisher: [Read original article]() Author: Eric Smalling Published: 2023-07-20T05:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [CI/CD](), [snyk](), [snyk-open-source](), [Application Security](), [GitHub Actions](), [Jenkins]() Tags: [application-security](), [blog](), [cheat-sheet](), [ci-cd](), [ci-cd-pipeline](), [devops](), [devrel](), [devsecops](), [enablement](), [github-actions](), [jenkins](), [security](), [snyk](), [snyk-open-source](), [snyk-platform](), [software-composition-analysis]() ### AI overview This cheat sheet presents eight tips for securing CI/CD pipelines with Snyk. It covers dependency and open-source component scanning, vulnerability detection, remediation guidance, and implementation examples for Jenkins and GitHub Actions. ### Source excerpt In this post, we'll cover using Snyk in your CI/CD pipelines to catch security issues quickly and empower your developers to fix them before they ever get to production. ## Retry flaky tests with dotnet test and PowerShell DevFeed: [Retry flaky tests with dotnet test and PowerShell]() Original publisher: [Read original article]() Author: {"twitter"=\>"hlaueriksson"} Published: 2023-03-26T19:00:00Z Content type: tutorial Language: en Sources: [Henrik Lau Eriksson]() Topics: [PowerShell](), [.NET](), [Command-line interface](), [Smoke Tests](), [Playwright](), [Selenium]() Tags: [c-sharp](), [cli](), [configuration](), [dotnet](), [flaky](), [jenkins](), [mstest](), [nunit](), [playwright](), [powershell](), [retry](), [selenium](), [test](), [testing](), [unit-tests](), [xunit]() ### AI overview This tutorial presents a PowerShell script that uses dotnet test and TRX result files to track failed tests, retry them, report the final result, and allow a configured percentage of failures. It demonstrates the script with NUnit, MSTest, and xUnit. ### Source excerpt Introducing test.ps1, a script for running flaky tests - Keeps track of failing tests and retries them - Notifies the test framework of the current retry iteration - Makes it possible to accept a certain percentage of failing tests - Outputs the test result in a coherent way ## Using Teleport to Create and Maintain Shared Demo Environments DevFeed: [Using Teleport to Create and Maintain Shared Demo Environments]() Original publisher: [Read original article]() Author: info@goteleport.com (Steven Martin) Published: 2022-02-09T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [Demo](), [DevOps](), [Cloud](), [Provisioning](), [Amazon EC2](), [Kubernetes clusters](), [Security](), [audit](), [Authentication](), [Authorization](), [Jenkins](), [AWS IAM]() Tags: [audit](), [authentication](), [authorization](), [aws](), [blog](), [cloud](), [demo](), [devops](), [ec2](), [iam](), [jenkins](), [kubernetes](), [kubernetes-clusters](), [maintenance](), [provisioning](), [solutions]() ### AI overview The Teleport Solutions Engineering team describes building a shared demo environment on Teleport Enterprise. The approach provides each engineer access to demo resources while controlling provisioning costs, supporting distributed Teleport clusters, and using just-in-time requests and auditing for administrative changes. ### Source excerpt This blog shows how the Teleport Solutions Engineering team uses Teleport to create and maintain shared demo environments. [Next page]()