5 Aug 2026, 10:01 UTC34 viewsread 7 August 2026
Video
Run your Gatling Enterprise simulations from your Jenkins CI https://redd.it/1lecgpw @jenkinsci
Signed reddit2telegram
Channel
JenkinsCI
@jenkinsci
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
1,655subscribers
-27 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001156922298 |
|---|---|
| Type | Channel |
| Username | @jenkinsci |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/jenkinsci |
Topic
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 17 September 2026 and assigned it the closest of 31 fixed categories, at 99% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 23:00 | 1,655 | -2 |
| 11 Sept 2026, 20:20 | 1,657 | -7 |
| 7 Sept 2026, 04:17 | 1,664 | -4 |
| 2 Sept 2026, 07:43 | 1,668 | -6 |
| 30 Aug 2026, 02:54 | 1,674 | -1 |
| 19 Aug 2026, 23:34 | 1,675 | -6 |
| 16 Aug 2026, 14:53 | 1,681 | -3 |
| 13 Aug 2026, 08:14 | 1,684 | +2 |
| 6 Aug 2026, 16:11 | 1,682 | no change |
| 6 Aug 2026, 16:08 | 1,682 | first reading |
Engagement
20 posts held, back to 11 May 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 0s
- Average length
- 0s
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Recent posts
1 Aug 2026, 08:01 UTC67 viewsread 7 August 2026
Jenkins Reverse Proxy (IIS) reporting as broken after update but Jenkins works fine https://stackoverflow.com/questions/79293872/jenkins-reverse-proxy-iis-reporting-as-broken-after-update-but-jenkins-works-f https://redd.it/1hhspj0 @jenkinsci
Signed reddit2telegram
12 Jul 2026, 18:01 UTC150 viewsread 7 August 2026
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 und…
Signed reddit2telegram
7 Jul 2026, 06:01 UTC137 viewsread 7 August 2026
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…
Signed reddit2telegram
2 Jul 2026, 10:01 UTC120 viewsread 7 August 2026
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 Jenk…
Signed reddit2telegram
16 Jun 2026, 08:01 UTC147 viewsread 7 August 2026
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 so…
Signed reddit2telegram
14 Jun 2026, 20:01 UTC115 viewsread 7 August 2026
Photo
Mc and cheese at Jenkin's https://redd.it/1u5uinm @jenkinsci
Signed reddit2telegram
12 Jun 2026, 11:01 UTC127 viewsread 7 August 2026
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 …
Signed reddit2telegram
11 Jun 2026, 09:01 UTC112 viewsread 7 August 2026
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 - i…
Signed reddit2telegram
8 Jun 2026, 07:01 UTC101 viewsread 7 August 2026
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
Signed reddit2telegram
7 Jun 2026, 08:01 UTC99 viewsread 7 August 2026
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 u…
Signed reddit2telegram
4 Jun 2026, 16:01 UTC90 viewsread 7 August 2026
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 ha…
Signed reddit2telegram
Showing the 12 most recent of 20 posts we hold for @jenkinsci. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Mentions
Named by 8 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
/r/IngressPrimeFeedback
@IngressPrimeFeedback · 321 postOctober Strike
@OctoberStrike · 71 postr/badcode
@r_badcode · 391 postr/Furrypasta
@r_furrypasta · 301 postr/GharKeKalesh
@r_gharkekalesh · 761 postI'm going to hell for this
@r_imgoingtohellforthis · 1261 post@r_invites
@r_invites · 1891 postRussianIsSoHard
@RussianIsSoHard · 61 post
@IngressPrimeFeedback · 321 postOctober Strike
@OctoberStrike · 71 postr/badcode
@r_badcode · 391 postr/Furrypasta
@r_furrypasta · 301 postr/GharKeKalesh
@r_gharkekalesh · 761 postI'm going to hell for this
@r_imgoingtohellforthis · 1261 post@r_invites
@r_invites · 1891 postRussianIsSoHard
@RussianIsSoHard · 61 post
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
Technical Hub 📈
@placementtolekerahenge · 21,848
Telegram ranks this channel #59 of 68 here — alongside 67 others — read 22 September 2026
@placementtolekerahenge · 21,848
Telegram ranks this channel #59 of 68 here — alongside 67 others — read 22 September 2026
Abhishek.Veeramalla
@abhishekveeramalla · 50,947
Telegram ranks this channel #62 of 68 here — alongside 67 others — read 25 August 2026
@abhishekveeramalla · 50,947
Telegram ranks this channel #62 of 68 here — alongside 67 others — read 25 August 2026
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
Cite this entry
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 15 September 2026 — this entry's latest reading, not the date you are reading this.
“JenkinsCI” (@jenkinsci), 1,655 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/jenkinsci.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.