Re: New Year blogpost for Jenkins

2022-01-05 Thread Alyssa Tong
For Jenkins is the Way stories, in 2021 we've published: - 138 Jenkins users stories - 3 Jenkins User Story eBooks On Wed, Jan 5, 2022 at 5:03 AM Mark Waite wrote: > On Wednesday, January 5, 2022 at 5:55:19 AM UTC-7 Daniel Beck wrote: > >> On Fri, Dec 24, 2021 at 3:42 PM Mark Waite

Re: Incremental releases show not up as GitHub action result anymore

2022-01-05 Thread 'Gavin Mogan' via Jenkins Developers
oh good, it uses ocktokit https://github.com/jenkins-infra/incrementals-publisher/blob/master/lib/github.js The code to use an app for ocktokit is pretty straight forward. import { createAppAuth } from '@octokit/auth-app'; async function getRestClientUncached() { const { data:

Re: Incremental releases show not up as GitHub action result anymore

2022-01-05 Thread Tim Jacomb
Ah right this was me, I downgraded the old Jenkins-admin users permissions from owner as I wanted to find if we still used it anywhere, it didn’t really make sense to have 2 bot users with owner permissions Should either switch it to a GitHub app or change the user IMO to the other bot one On

Re: Incremental releases show not up as GitHub action result anymore

2022-01-05 Thread 'Jesse Glick' via Jenkins Developers
On Wed, Jan 5, 2022 at 11:45 AM Tim Jacomb wrote: > See > https://github.com/jenkinsci/incrementals-tools/releases/tag/parent-1.3 > No, that is unrelated. I have also noticed this. The artifact does actually get deployed, e.g.

Re: Incremental releases show not up as GitHub action result anymore

2022-01-05 Thread Tim Jacomb
You likely need to update https://github.com/jenkinsci/prism-api-plugin/blob/main/.mvn/extensions.xml#L5 See https://github.com/jenkinsci/incrementals-tools/releases/tag/parent-1.3 Unsure why dependabot isn't proposing it for you On Wed, 5 Jan 2022 at 16:39, Ullrich Hafner wrote: > Since a

Incremental releases show not up as GitHub action result anymore

2022-01-05 Thread Ullrich Hafner
Since a couple of days, incremental releases do not show up as GitHub action result anymore. Is this a know problem in our infrastructure? E.g. Pull Request: https://github.com/jenkinsci/prism-api-plugin/pull/2 Available incrementals from this PR:

Re: [jenkins-infra] Succession of timeouts during Docker actions on ci.jenkins.io

2022-01-05 Thread 'Jesse Glick' via Jenkins Developers
On Wed, Jan 5, 2022 at 7:41 AM Chris Kilding wrote: > Log is here: > More useful is the test stderr

Re: New Year blogpost for Jenkins

2022-01-05 Thread Mark Waite
On Wednesday, January 5, 2022 at 5:55:19 AM UTC-7 Daniel Beck wrote: > On Fri, Dec 24, 2021 at 3:42 PM Mark Waite wrote: > >> >>- Security fixes and improvements >> - 19 security advisories published >> >> I'm certainly biased here, but our work on agent-to-controller security >

Re: New Year blogpost for Jenkins

2022-01-05 Thread 'Daniel Beck' via Jenkins Developers
On Fri, Dec 24, 2021 at 3:42 PM Mark Waite wrote: > >- Security fixes and improvements > - 19 security advisories published > > I'm certainly biased here, but our work on agent-to-controller security (both the fixes delivered in early November, as well as JEP-235) is notable in this

Re: [jenkins-infra] Succession of timeouts during Docker actions on ci.jenkins.io

2022-01-05 Thread Chris Kilding
I tried migrating from the docker-maven-plugin to testcontainers. The resulting code is indeed a little cleaner, and it's nice to not have to run an out-of-band step before running the test suite. Unfortunately the build still fails on ci.jenkins.io, so the underlying Docker issue is probably