Jesse Glick

@github this should be a built-in feature

@lorenc_dan Nice, but will Maven Central ever support OIDC publishing and Sigstore? Have heard no news in over a year.

This is the way!

@csanchez CrashLoopBackOff

Would you like to run #kubernetes in your car? #kubecon

Get your @github PR in fork remote up to date with origin base branch (and any commits pushed by others or web UI) before starting a day’s work: gh alias set -s updatepr 'git pull; base=`gh pr view --json baseRefName --jq .baseRefName`; git pull origin $base:$base'

@amazingmap My father explaining why the US is so high here: a.co/d/33cUPhT

Percentage of males that are circumcised in each country

@physorg_com @NaturePhysics thanks for the heads-up @AstroKatie

New research sheds light on a phenomenon known as 'false #vacuum #decay' @NaturePhysics doi.org/gtfh58 phys.org/news/2024-01-p…

Quick way to reset context after filing a PR: gh help set -s codef 'git checkout `gh api /repos/{owner}/{repo} -q .default_branch`'

@oleg_nenashev Babe are you OK? You’ve barely touched your .nfs000000000164d77100000002.

@tyvole Hopefully not the locking NFS part 😅

Excited to be a part of finally making this happen! With CloudBees CI you can now run multiple replicas of a Jenkins controller on the same home directory, distributing load transparently.

@recena In the CloudBees SaaS, not (currently) in CI.

@oleg_nenashev Hehe no code but much inspiration!

@tyvole I hope none of the code from Project Nirvana was used 🙏

@vmassol I have also hit Surefire bugs like treating a failure of a parameterized test as a flake (when it was not), and even skipping _all_ tests due to JUnit 4 vs. 5 classpath mixups. May be needed outside the Maven lifecycle in case you split tests in parallel on a cluster & aggregate.

Is there a tool to check that #JUnit tests have executed in a #Maven build? Sometimes, the surefire/failsafe includes/excludes are wrongly set and thus some tests don't execute and you can miss that easily. Could be a #Checkstyle check, a #SonarQube rule, a #Spoon check, etc. Thx

@OpenJDK farewell #L34" target="_blank" rel="nofollow noopener">github.com/jglick/jrunscr…

New candidate JEP: JEP 451: Prepare to Disallow the Dynamic Loading of Agents: openjdk.org/jeps/451 #openjdk #java

@kenbrittain @tasssko github.com/jglick/jk--

True words, some plugins are not necessary. Our Jenkins Service includes what are essential plugins. While a customer can add any plugin our support team have a script similar to this one.

@oleg_nenashev @tasssko @agentdero @bmathus @kohsuke @Tjaynz Maybe at some point, though for now LTS BOMs receive no updates after the line is cut.

@tasssko Jenkins Essentials vibes @agentdero @bmathus @kohsuke🤗 To some extent, it was implemented for community needs in github.com/jenkinsci/bom by @tyvole and @Tjaynz. Maybe we should finally convert it to a user feature by integrating the verified BOM with LTS update centers

@jawnsy @lorenc_dan @antitree Maybe showing my age here, but I think the state of the art has regressed since #Taint-mode" target="_blank" rel="nofollow noopener">perldoc.perl.org/perlsec#Taint-…

@jawnsy @lorenc_dan @antitree “Secure” is often subjective when it comes to CI/CD & credentials. You are handing out secrets to potentially unknown people & processes. The right thing often comes down to UX & docs over features & fixes. The Jenkins sec team spends a lot of time arguing over “vulnerabilities”.

This doesn't push my agenda of hating on Jankins but it's a good in-depth analysis of a few CI tools and how they handle creds. cidersecurity.io/blog/research/…

@kohsukekawa But it will fall out of the hammock.

The age of work from home is the age of desktop computers! They are so much faster, cheaper, and upgradable.

@oleg_nenashev @cowai @jenkinsci Even if it turns out to be technically feasible, I would not _advise_ using SemVer. IMO plugin versions should not even be shown in the GUI by default. If an admin hesitates to accept all available plugin updates, better to link to the intervening GH release pages.

@oleg_nenashev @cowai @jenkinsci github.com/jenkins-infra/…

I would like to know why versioning rule of @jenkinsci plugins has changed like from v1.1.30 to 214.v2fd4234d0554.