1919
repost from /r/jenkinsci using @r_channels
How do you handle build caching with short lived Jenkins agents?
Disclosure: We’re building Cachely.
We’ve been looking at how teams handle build caching when Jenkins agents are created for each job and removed afterwards.
A local cache does not help much when every build starts on a clean agent. A shared remote cache can solve that, but it also means running another service, managing access, and trying to understand whether it is actually saving time.
For teams running Gradle, Bazel, Nx, or Turborepo on Jenkins:
\- Are you using a remote cache today?
\- Is it self-hosted, managed, or backed by shared storage?
\- Who owns it internally?
\- Do you see meaningful cache reuse between branches, CI jobs, and developer machines?
\- What has been hardest to configure or debug?
We’re building Cachely as a managed remote build cache that works through the build tool’s existing configuration. It does not require a Jenkins plugin.
We’re also adding visibility into hits and misses, transfer volume, task performance, and estimated time saved.
We’d be interested to hear how this is handled in real Jenkins setups and where the current options fall short.
https://cachely.dev
https://redd.it/1uul0lb
@jenkinsci
Built something for the teammate who always asks you why their Jenkins build failed
Be honest — you have this person on your team.
Good developer. Writes solid code.
Just never learned Jenkins deeply.
Every time their build fails they open the logs, get completely lost, and message you.
You have answered the same question twenty times. They feel bad asking.
You feel bad stopping what you're doing.
I built JenkinLens because of this loop.
When a build fails it reads the log automatically and tells that teammate in plain English what broke and what
to do before they message you.
Not "build failed exit code 1."
Actually this:
"Your npm install failed because
@testing-library/react@14 needs React 18
but your package.json has React 17.
Run npm install react@18 to fix it."
That goes straight to your team's Slack or email the moment the build fails.
No one needs to open Jenkins at all.
And it is not just failure diagnosis.
If you are running multiple Jenkins instances across teams — staging, production, different squads —
you can see all of them in one place instead of switching between tabs and losing context.
It also quietly flags jobs that have not run in months but are still sitting in your Jenkins burning resources.
Most teams are surprised how many they find.
The whole thing works on mobile too. So when something breaks at 2am you can actually understand what happened from your phone without opening a laptop.
\---
To be upfront about a few things:
This is not for you — the person who knows Jenkins well. You have already figured out your own workflow.
It is for the eight other people on your team who haven't.
It connects read-only to your Jenkins.
Nothing changes on your end.
No new plugins. No migration.
No admin access needed to start.
Your setup stays exactly as it is.
I posted here a few times over the past weeks asking questions.
Some of you pushed back hard.
That feedback directly changed what I built and I genuinely mean that.
Free to try — https://jenkinlens.com
Happy to answer anything honestly.
https://redd.it/1uldcnd
@jenkinsci
Mc and cheese at Jenkin's
https://redd.it/1u5uinm
@jenkinsci
Have you tried Jenkins OTel Plugin and an AI on top to analyze job executions based on spans and log?
We have been using Jenkins for years as our main CI. While we are eventually moving to a different solution we have a big need to understand why jobs fail or slow down when it happens.
We have been using the OpenTelemetry plugin for years as it really gives full visibility into each jenkins job execution - plus - it also forwards all build logs.
The problem though was that this is a lot of data and you do not always have the time to dig through thousands of log lines.
With the latest AI models its amazing on how helpful the responses are when you ask an AI to analyze the traces and linked logs for a job to identify the problem. Here is a prompt I used on a job that took 46 min to execute: "Can you analyze trace with id 8a61853d1d3b449b5df3b3963db314df. Tell me where most of the time is spent and what is going by analyzing the spans and the attached logs"
By just analyzing the data that comes out of the OTel Plugin I ended up getting this (removed some data for confidentiallity reasons)
https://preview.redd.it/8p38z9am5m6h1.png?width=823&format=png&auto=webp&s=528a191f1f1ce74828ef48071598b09c3be076b5
And it then also provides a good summary
https://preview.redd.it/fddvp4bx5m6h1.png?width=963&format=png&auto=webp&s=51a35019230f23c4e1ab8c526d219715119baa78
Just wanted to share this in case you wonder how AI can help you in your day2day work with Jenkins
Andi
https://redd.it/1u2t4zb
@jenkinsci
Plugin ForgeAI Pipeline Intelligence with 8 AI analyzers for code review, security, architecture drift, and release readiness
Hi all,
I've published a new Jenkins plugin: ForgeAI Pipeline Intelligence. It's now under the jenkinsci org on GitHub.
It adds two pipeline steps:
\- forgeAI —> runs a configurable suite of 8 AI analyzers and generates an HTML report
\- forgeAIScan —> runs a single analyzer for targeted use
Analyzers: code review, vulnerability, architecture drift, test gaps, dependency risk, commit intelligence, pipeline optimization, release readiness
LLM support: OpenAI, Anthropic Claude, Ollama (local/air-gapped), Groq, LM Studio, or any OpenAI-compatible endpoint
Configuration: Full global config UI under Manage Jenkins → System with per-analyzer toggles, API key via Jenkins credentials, Test Connection button, and quality gate settings.
The architecture drift analyzer is what I haven't seen in other plugins; it detects layer violations, circular dependencies, and coupling decay across hexagonal, layered, and CQRS architectures.
Install from source: clone, mvn clean package -DskipTests, upload the .hpi.
GitHub: https://github.com/jenkinsci/forgeai-pipeline-intelligence-plugin
Feedback welcome. PRs even more so.
HTML report - shows composite score, verdict, per-analyser breakdowns, and findings with severity badges
ForgeAI Pipeline Intelligence Global config page
ForgeAI Pipeline Intelligence Global config page
Pipeline run Console output
Pipeline stage view
https://redd.it/1tz5sqm
@jenkinsci
Jenkins console output is the worst documentation in software
I had a build fail today. The console log was 9,284 lines.
The actual error?
A missing environment variable. It was mentioned on line 8,901.
The fix took 20 seconds once I found it.
I spent 38 minutes finding it.
I know Jenkins is powerful and I'm not bashing it, but the signal-to-noise ratio in console output is genuinely terrible. Error messages buried in thousands of lines of INFO logs, stack traces that don't point at the actual problem, plugin conflicts that surface as cryptic Java exceptions.
Does anyone have a system for making this better? Even just a smarter way of reading logs would save my team hours every week.
https://redd.it/1twm10f
@jenkinsci
We made a free Git course with a real Ubuntu VM in the browser. Figured Jenkins folks might appreciate it
https://redd.it/1tnhhxd
@jenkinsci
Any tutorials to assist reading the "Pipeline as Code" book from Manning publications?
https://redd.it/1timiqr
@jenkinsci
CVE-2026-1605
Is there a security advisory for Jenkins that addresses this Jetty vulnerability? We recently upgraded our dev server to Jenkins 2.541.3. Someone had gotten the impression that this would address the vulnerability, but after the upgrade we found that it is using Jetty 2.1.5, which is still vulnerable.
Is there a release that upgrades Jetty to 2.1.6 or later? If not, is there an advisory from Jenkins about the issue?
https://redd.it/1tbfhda
@jenkinsci
Split Dockerfiles using Dexfile
https://github.com/ctryard/dexfile
https://redd.it/1ta0nmn
@jenkinsci
Does jenkins fits this architecture? Build tool? I mean jenkins probably became more advanced now, I am talking about the original release
https://redd.it/1sv20b2
@jenkinsci
SessiontlTimeout vs sessionEviction
how does sessiontimeout and sessionEviction work in Jenkins.(not cloudbees Jenkins)
I want to know how Jenkins handles sessions for a user.
will a user be logged out after 30 minutes even if the user is actively using the following
https://redd.it/1sqyuml
@jenkinsci
I made a Bash script to completely reinstall Jenkins on Arch Linux (clean reset)
I recently had to reinstall Jenkins multiple times while testing CI pipelines on my Arch Linux machine.
Doing it manually every time (removing packages, deleting data folders, restarting services, etc.) became annoying.
So I wrote a small Bash script that completely resets Jenkins automatically.
What it does:
• Stops Jenkins
• Removes the Jenkins package
• Deletes Jenkins data directories
• Removes Jenkins system user/group
• Reinstalls Jenkins using pacman
• Starts the service again
• Automatically prints the initial admin password
It also includes:
• Internet connectivity check
• Colored terminal output
• Automatic retry until Jenkins generates the admin password
If anyone wants to try it or suggest improvements:
https://github.com/Pradeesh2007/jenkins-arch-reinstaller
Feedback is welcome 🙂
https://redd.it/1rsso6p
@jenkinsci
git-client//org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:173)
09:24:46 at PluginClassLoader for git-client//org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:164)
09:24:46 at hudson.remoting.UserRequest.perform(UserRequest.java:225)
09:24:46 at hudson.remoting.UserRequest.perform(UserRequest.java:50)
09:24:46 at hudson.remoting.Request$2.run(Request.java:391)
09:24:46 at hudson.remoting.InterceptingExecutorService.lambda$wrap$0(InterceptingExecutorService.java:81)
09:24:46 at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
09:24:46 at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
09:24:46 at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
09:24:46 at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:138)
09:24:46 at java.base/java.lang.Thread.run(Thread.java:840)
09:24:46 Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to servername.company.com
09:24:46 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1916)
09:24:46 at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:384)
09:24:46 at hudson.remoting.Channel.call(Channel.java:1108)
09:24:46 at PluginClassLoader for git-client//org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:155)
09:24:46 at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
09:24:46 at java.base/java.lang.reflect.Method.invoke(Method.java:580)
09:24:46 at PluginClassLoader for git-client//org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:140)
09:24:46 at PluginClassLoader for git-client/jdk.proxy90/jdk.proxy90.$Proxy172.execute(Unknown Source)
09:24:46 at PluginClassLoader for git//hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:996)
09:24:46 at PluginClassLoader for git//hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1239)
09:24:46 at PluginClassLoader for git//hudson.plugins.git.GitSCM._checkout(GitSCM.java:1310)
09:24:46 at PluginClassLoader for git//hudson.plugins.git.GitSCM.checkout(GitSCM.java:1277)
09:24:46 at PluginClassLoader for workflow-scm-step//org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:136)
09:24:46 at PluginClassLoader for workflow-scm-step//org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:101)
09:24:46 at PluginClassLoader for workflow-scm-step//org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:88)
09:24:46 at PluginClassLoader for workflow-step-api//org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:49)
09:24:46 at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572)
09:24:46 at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
09:24:46 at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
09:24:46 at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
09:24:46 at java.base/java.lang.Thread.run(Thread.java:1583)
09:24:46 ERROR: Error fetching remote repo 'origin'
09:24:46 ERROR: Maximum checkout retry attempts reached, aborting
09:24:46 [Pipeline\] }
09:24:46 [Pipeline\] // stage
09:24:46 [Pipeline\] }
09:24:46 [Pipeline\] // node
09:24:46 [Pipeline\] stage
09:24:46 [Pipeline\] { (Declarative: Post Actions)
09:24:46 [Pipeline\] cleanWs
09:24:46 Error when executing always post condition:
09:24:46 Also: org.jenkinsci.plugins.workflow.actions.ErrorAction$ErrorId: ee9ae6c1-adf1-4aac-9317-b81461411924
09:24:46
Buildbutler free for first 50 signups
Build Butler for Jenkins is now ready and free (1 year) for the first 50 signups.
The Jenkins local version is fully self contained and just requires a postgres database accessible to your Jenkins.
Connect all your Jenkins installations and see the beautiful dashboard, triaging capabilities, rich email and slack notifications, and top notch JIRA integration.
Would love to get your feedback as we get ready to launch the saas version to support other CI systems like GitHub, gitlab, buildkite, teamcity, Travis, Azure Devops
\#jenkins #cicd #jira
https://redd.it/1ruuzux
@jenkinsci
Got error from step Deploy port address already use
I know the problem issue seems straight to the point. But I make sure the system machine/host is not listening the port (3000) that i was configured in Jenkinsfile. Somehow i keep getting the same error for build it manually. I mention host machine cause I running the Jenkins-lts under Docker.
First earlier the host machine have listening the port 3000. But i take down, then the probem would be solved right?. In fact i tried to build again it still got same error issue. Do i have to restart the Jenkins docker first?. So Jenkins have to be able notice the port is not yet already listening. At least that the on my mind now.
Thank you.
Any help would be appreciated!.
https://redd.it/1uplhoo
@jenkinsci
What does your team's "build is broken" workflow actually look like?
Not the ideal workflow. The real one.
Ours goes something like:
1. Slack notification fires "Build failed"
2. Someone clicks the Jenkins link
3. Spends 10-20 min scrolling through logs
4. Finds something that looks like an error
5. Google it
6. Tries a fix
7. Pushes and waits another 8 minutes for the build
8. Repeat
The notification tells us something broke.
It tells us nothing about what, why, or who should care.
So we've normalized a process where every failure investigation starts from zero context.
Curious if other teams have actually improved this or if everyone's running the same loop.
What does step 3 look like at your company? Does anything actually reduce the time between "build failed" alert and knowing what to do next?
https://redd.it/1u76g7f
@jenkinsci
How do you handle Jenkins build failure notifications?
When a Jenkins build fails at 2am, how does your team actually find out and how long does it take to understand what went wrong?
1. We get a Slack alert, but still have to dig through logs ourselves.
2. We only see it in email, so someone checks it the next morning.
3. We manually check Jenkins UI during the day.
4. We already have something that explains the failure, like an AI summary or root cause hint.
5. Oncall gets paged and spends 30 minutes reading logs.
Follow-up: Roughly how many hours per week does your team spend just reading build logs?
https://redd.it/1u3rz13
@jenkinsci
Jenkins plugin auto-update broke our build, How do you handle plugin version management?
/r/cicd/comments/1tyh8bx/jenkins_plugin_autoupdate_broke_our_build_how_do/
https://redd.it/1u00e73
@jenkinsci
Problem with Github Diff
Hi guys, I'm using jenkins to run terragrunt in a pod, for the plan sometimes when i do a pr and my branch does not have the latest change of master(solved with rebase) the plan takes that commit that is not rebased instead of mine, probably is because i use HEAD\^in the diff instead origin/HEAD, the first one jsut takes the last commit, probably is that but i dont really get why, do you have any clue?
https://redd.it/1twrtek
@jenkinsci
Recommend a good book to take my company to jenkins in production.
https://redd.it/1tqulhb
@jenkinsci
Where did you learn jenkins CI for the first time in your life?
Udemy is not an option anymore.
Youtube is there but lots of courses and unstructured makes it really difficult.
Now I am a support engineer.
All I can do is to deploy jenkins in a single node. Then I cannot do anything else.
I want to enter sysAdmin level. What do I need to do to be at that level?
Finally, I want to enter DevOps level. At that level what I need to do?
I want you to take example of Jenkins.
https://redd.it/1tn449o
@jenkinsci
Didn’t realize how inefficient our Jenkins workers were until we switched to dynamic pod agents
One pattern we’ve been using on EKS for Jenkins workloads is replacing long running static workers with ephemeral Kubernetes pod agents created on demand for builds.
The overall setup became much easier to manage once builds were isolated into short lived agents instead of sharing dedicated executors permanently across teams. Resource utilization also became far more predictable during peak pipeline activity.
Documented the architecture, pod template setup, scaling behaviour and Jenkins Kubernetes integration details here:
https://tasrieit.com/blog/jenkins-on-eks-dynamic-pod-agents
Interested to know how others here are handling Jenkins agents on Kubernetes in production.
https://redd.it/1tid0yg
@jenkinsci
Timing of Java / OS upgrade?
Hi all! I use the EC2 plugin with EC2 instance workers. I need to upgrade Ubuntu 22.04 LTS Master & Workers with Java 17 to the latest (likely Ubuntu 24.04 LTS and Java 21) given Java 17 is not supported with the latest LTS release.
Just wondering, is it possible to do this in stages -- upgrade either the master or the workers first, without upgrading the other? And if so, which should be done first? Can I just install both versions of java on the workers, upgrade them to Ubuntu 24.04, and then do the master second?
https://redd.it/1tah8ml
@jenkinsci
Built a Jenkins plugin that tracks all 4 DORA metrics natively
/r/devops/comments/1t1vixo/built_a_jenkins_plugin_that_tracks_all_4_dora/
https://redd.it/1t1vnkt
@jenkinsci
2026 state of Jenkins vs GitHub Actions — where does Jenkins still win?
Working on a comparison and wanted to get the community's view on where Jenkins is still
the clear choice in 2026. From what I've seen:
Jenkins clearly wins on:
- Air-gapped/offline environments
- Existing Groovy Shared Library investment
- Non-GitHub SCMs
- Some enterprise tools that only have Jenkins plugins (no GHA equivalent)
The areas where it's harder to defend Jenkins these days:
- Setup/maintenance overhead
- Security posture (configuring RBAC, credential management, hardening takes real effort)
- Total cost of ownership for teams under ~50 engineers
Wrote up a full breakdown here:
https://pipeshiftai.com/blog/jenkins-vs-github-actions-2026
Curious what use cases the people here are still running Jenkins for in 2026 — especially
interested in cases where migration isn't worth i
https://redd.it/1sr2987
@jenkinsci
Webhooks without security issues
Is there a way to expose only the webhook API of jenkins to the public internet? I’d like to have webhooks to reduce my GitHub API polling as rate limiting is starting to become a concern but the problem is that throwing up the web interface to the public internet is likely a security issue. I don’t exactly trust myself to be able to patch my jenkins version fast enough if a zero day is discovered. I would like to be able to access my running builds from outside my LAN so if there’s a way to create a sort of sandboxed web interface on a different port that would be super nice. I’m just getting into jenkins so I’m not super familiar with the infrastructure and everything it has to offer yet.
https://redd.it/1sh91yr
@jenkinsci
org.jenkinsci.plugins.workflow.steps.MissingContextVariableException: Required context class hudson.FilePath is missing
09:24:46 Perhaps you forgot to surround the step with a step that provides this, such as: node
09:24:46 at PluginClassLoader for workflow-basic-steps//org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:90)
09:24:46 at PluginClassLoader for workflow-basic-steps//org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:71)
09:24:46 at PluginClassLoader for workflow-step-api//org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:49)
09:24:46 at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572)
09:24:46 at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
09:24:46 at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
09:24:46 at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
09:24:46 at java.base/java.lang.Thread.run(Thread.java:1583)
09:24:46
09:24:46 [Pipeline\] }
09:24:46 [Pipeline\] // stage
09:24:46 [Pipeline\] End of Pipeline
09:24:46 ERROR: Error fetching remote repo 'origin'
09:24:46 Finished: FAILURE
The beginning part of Jenkinsfile is:
@Library('jenkins-shared-library@master') _
properties([
parameters([
...
\])
\])
pipeline {
agent { label 'WindowsAgents' }
environment {
...
}
stages {
stage('Set Environment') {
steps {
script {
// Cleans workspace
cleanWs()
checkout scm
logging.displayHeader(STAGE_NAME)
// Set environment as PPE by default
...
// Override environment to Production when on master branch
if (env.GIT_BRANCH == 'origin/master' || env.GIT_BRANCH == 'refs/heads/master') {
...
}
}
}
}
stage('Validate Parameters') {
steps {
script {
...
}
}
}
If I run the job as is again then it typically runs as expected. The job configuration includes "Pipeline script from SCM" and "Git" using Git Plugin 5.8.1.
Is this anything to do with cleanWs() or checkout scm (e.g. should I use the extended version of this rather than 'Pipeline from SCM'?)
Regards
Craig
[Update\] so the answer (a bit embarrassing tbh) was due to changing too much in one go. The controller, agents, service account, repo were all new and service account didn’t have sufficient access to the repo!!
https://redd.it/1rtfgaz
@jenkinsci
Error Git
Hi all,
[UPDATE\] Subject should read: Error fetching remote repo 'origin'
Recently we migrated our Jenkins controller to new Linux server (this is managed by our DevOps team) running version 2.516.1.
I do manage our agents which I started migrating to Windows Server 2019 (only moved 1 encountering issue described herein).
Agent is running Microsoft's Build of OpenJDK 17.0.17.10.
It seems as though every day any job runs (scheduled or manually) for the first time it fails with this error:
09:23:45 Selected Git installation does not exist. Using Default
09:23:45 The recommended git tool is: NONE
09:23:45 using credential c08a42c6-8620-4566-ab27-aa85ae50b699
09:23:45 Fetching changes from the remote Git repository
09:23:45 > git rev-parse --resolve-git-dir C:\\JenkinsWS014\\workspace\\MyProjects\\Servers\\Backout\\.git # timeout=10
09:23:45 > git config remote.origin.url https://github.company.com/MyProject/Jenkins_Automation.git # timeout=10
09:23:45 Fetching upstream changes from https://github.company.com/MyProject/Jenkins_Automation.git
09:23:45 > git --version # timeout=10
09:23:45 > git --version # 'git version 2.53.0.windows.1'
09:23:45 using GIT_ASKPASS to set credentials GitHub adminaccount PAT
09:23:45 > git fetch --tags --force --progress -- https://github.company.com/MyProject/Jenkins_Automation.git +refs/heads/*:refs/remotes/origin/* # timeout=10
09:24:46 ERROR: Error fetching remote repo 'origin'
09:24:46 hudson.plugins.git.GitException: Failed to fetch from https://github.company.com/MyProject/Jenkins_Automation.git
09:24:46 at PluginClassLoader for git//hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:998)
09:24:46 at PluginClassLoader for git//hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1239)
09:24:46 at PluginClassLoader for git//hudson.plugins.git.GitSCM._checkout(GitSCM.java:1310)
09:24:46 at PluginClassLoader for git//hudson.plugins.git.GitSCM.checkout(GitSCM.java:1277)
09:24:46 at PluginClassLoader for workflow-scm-step//org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:136)
09:24:46 at PluginClassLoader for workflow-scm-step//org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:101)
09:24:46 at PluginClassLoader for workflow-scm-step//org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:88)
09:24:46 at PluginClassLoader for workflow-step-api//org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:49)
09:24:46 at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572)
09:24:46 at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
09:24:46 at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
09:24:46 at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
09:24:46 at java.base/java.lang.Thread.run(Thread.java:1583)
09:24:46 Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --force --progress -- https://github.company.com/MyProject/Jenkins_Automation.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:
09:24:46 stdout:
09:24:46 stderr: fatal: unable to access 'https://github.company.com/MyProject/Jenkins_Automation.git/': Send failure: Connection was reset
09:24:46
09:24:46 at PluginClassLoader for git-client//org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2848)
09:24:46 at PluginClassLoader for git-client//org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:2189)
09:24:46 at PluginClassLoader for git-client//org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:638)
09:24:46 at PluginClassLoader for
Creating Docker image inside Jenkins Agent.
Hi all,
I'm looking forward to building my application Docker image and push to ECR using Jenkins Agent.
Jenkins is currently deployed on EKS and the Agent have to be on EKS as well.
I've tried using buildah but encountering issues with uid/gid. I've search through the internet and cannot find working example within this context just yet.
How do I go to do this?
https://redd.it/1rptq2b
@jenkinsci
