Jesse Glick

Be the pull request you want to see in the world. @JenkinsCI @CloudBees

[Jesse Glick @tyvole]

@github this should be a built-in feature

[Kim Lewandowski @kimsterv]

We open sourced Octo STS. Check it out and send us feedback! https://t.co/LsW8ypbZSk

[Jesse Glick @tyvole]

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

[Jesse Glick @tyvole]

@csanchez CrashLoopBackOff

[Jesse Glick @tyvole]

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'

[Jesse Glick @tyvole]

@amazingmap My father explaining why the US is so high here: https://t.co/5nnJaZJuSU

[Jesse Glick @tyvole]

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

[Jesse Glick @tyvole]

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

[Jesse Glick @tyvole]

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

[Jesse Glick @tyvole]

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.

[CloudBees @CloudBees]

Big news from CloudBees! 🎉 We're introducing a new High Availability and Horizontal Scalability (HA/HS) feature for continuous operations and easy scalability. Goodbye, downtime. Hello, productivity! Read more: https://t.co/YWgUAbaDxg #ContinuousIntegration #HAHS #NoDowntime

[Jesse Glick @tyvole]

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

[Jesse Glick @tyvole]

@oleg_nenashev Hehe no code but much inspiration!

[Jesse Glick @tyvole]

@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.

[Jesse Glick @tyvole]

@OpenJDK farewell https://t.co/oQaZPyNmGh

[Jesse Glick @tyvole]

@kenbrittain @tasssko https://t.co/1kITDbSVHF

[Jesse Glick @tyvole]

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

[Jesse Glick @tyvole]

@jawnsy @lorenc_dan @antitree Maybe showing my age here, but I think the state of the art has regressed since https://t.co/ClxbuaVNjr

[Jesse Glick @tyvole]

@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”.

[Jesse Glick @tyvole]

@kohsukekawa But it will fall out of the hammock.

[Jesse Glick @tyvole]

@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.

[Jesse Glick @tyvole]

@oleg_nenashev @cowai @jenkinsci https://t.co/3TXa9P4UdE