Re: New Year blogpost for Jenkins

[Mark Waite]

Thanks to all for the suggestions.

Please review the proposed blog post 
at https://github.com/jenkins-infra/jenkins.io/pull/4821 

I would like to publish before the end of the day in Europe on Friday, 
January 14, 2022.

Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/468f9eee-8db1-434b-aed9-ec0356263420n%40googlegroups.com.

Re: INFRA project issues migration from Jira to Github

['Daniel Beck' via Jenkins Developers]

On Thu, Jan 13, 2022 at 11:41 AM Ullrich Hafner 
wrote:

> Well, I think it is very important to notify reporters that their issues
> have been moved to a new system.
>

Once, sure, but 500+ times? 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtKQ1NqZCBqSjmExRef1Yd7hogYvUWKQsTJchL37vO%2BRmw%40mail.gmail.com.

Re: New Year blogpost for Jenkins

[Basil Crow]

Between 2.274 (2021-01-05) and 2.328 (2022-01-03), we removed 9
outdated dependencies, unforked and upgraded 2 outdated dependencies,
and upgraded 20 other dependencies:

- Removed Akuma
- Removed ASM 5
- Removed ASM 6
- Removed Bytecode Compatibility Transformer
- Removed Commons Digester
- Removed `jna-posix`
- Removed JTidy
- Removed `libpam4j`
- Removed Woodstox
- Unforked Commons FileUpload and upgraded from 1.3.1-jenkins-2 to 1.4
- Unforked Ant and upgraded from 1.10.9 to 1.10.12
- Upgraded Antlr from 2.7.6 to 2.7.7
- Upgraded ASM from 9.0 to 9.2
- Upgraded Commons BeanUtils from 1.9.3 to 1.9.4
- Upgraded Commons Codec from 1.14 to 1.15
- Upgraded Commons Compress from 1.19 to 1.21
- Upgraded Commons Discovery from 0.4 to 0.5
- Upgraded Commons IO from 2.8.0 to 2.11.0
- Upgraded Groovy from 2.4.12 to 2.4.21
- Upgraded Guava from 11.0.1 to 31.0.1
- Upgraded Guice from 4.0 to 5.0.1
- Upgraded Jaxen from 1.1-beta-11 to 1.2.0
- Upgraded jCIFS from 1.3.17-kohsuke-1 to 1.3.18-kohsuke-1
- Upgraded JLine from 2.12 to 2.14.6
- Upgraded JNA from 5.6.0 to 5.10.0
- Upgraded JNR from 3.1.4 to 3.1.14
- Upgraded `json-lib` from 2.4-jenkins-2 to 2.4-jenkins-3
- Upgraded SLF4J from 1.7.30 to 1.7.32
- Upgraded Spring from 5.2.9 to 5.3.14
- Upgraded Spring Security from 5.4.1 to 5.6.1
- Upgraded XStream from 1.4.15 to 1.4.18

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjqK8s2wvrf2Q5ZywB_5vC-%2BmBmRYzzdWd6oEDeDcpNjgQ%40mail.gmail.com.

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

[Tim Jacomb]

I've switched this to use a GitHub app with the Checks API as well.

Instead of a plain link to Artifactory it now gives you a page with a link
per artefact, example:
https://github.com/jenkinsci/jenkins-infra-test-plugin/pull/16/checks?check_run_id=4801158779
https://github.com/jenkinsci/plugin-installation-manager-tool/runs/4795504430

If anyone wants to tweak the messaging or add something like
https://github.com/jenkins-infra/incrementals-publisher/issues/22
The UI code is at:
https://github.com/jenkins-infra/incrementals-publisher/blob/master/lib/github.js#L49-L52


On Wed, 5 Jan 2022 at 18:11, 'Gavin Mogan' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> 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: installations } = await createAppAuth({
>   appId: config.github.appId,
>   privateKey: config.github.privateKey,
> }).hook(githubRequest.defaults({
>   baseUrl: config.github.server,
> }), 'GET /app/installations');
>
> return new Octokit({
>   baseUrl: config.github.server,
>   request: {
> hook: createAppAuth({
>   appId: config.github.appId,
>   privateKey: config.github.privateKey,
>   installationId: installations[0].id,
> }).hook,
>   },
> });
>   }
>
>
> On Wed, Jan 5, 2022 at 9:56 AM Tim Jacomb  wrote:
> >
> > 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 Wed, 5 Jan 2022 at 17:43, 'Jesse Glick' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com> wrote:
> >>
> >> 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.
> >>
> >>
> https://github.com/jenkinsci/prism-api-plugin/pull/2/commits/2b9b1326b405c9cb427d2ca43a4083a89a9e62bf
> >>
> >>
> https://repo.jenkins-ci.org/artifactory/incrementals/io/jenkins/plugins/prism-api/1.25.0-2-rc48.2b9b1326b405/
> >>
> >> and
> https://ci.jenkins.io/job/Plugins/job/prism-api-plugin/job/PR-2/34/console
> claims successful deployment, but no check or commit status is created.
> Presumably missing permission in the publisher? Is there some warning in
> microservice logs?
> >>
> >>
> https://github.com/jenkins-infra/incrementals-publisher/blob/78139813d7e4957aedea0b9840747cef8070b686/IncrementalsPlugin.js#L245
> >>
> >> Also see:
> https://github.com/jenkins-infra/incrementals-publisher/issues/4
> >>
> >> --
> >> You received this message because you are subscribed to the Google
> Groups "Jenkins Developers" group.
> >> To unsubscribe from this group and stop receiving emails from it, send
> an email to jenkinsci-dev+unsubscr...@googlegroups.com.
> >> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2YqByAC9mDw4ChpnTEoxb%2B_dcSAJdRnV90cNkBEke20Q%40mail.gmail.com
> .
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "Jenkins Developers" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to jenkinsci-dev+unsubscr...@googlegroups.com.
> > To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Biew8%2Be4_5%2B2Cd86-3UobTdhTkubHpst2mqgwebZ6oYCig%40mail.gmail.com
> .
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_Duuu-6zw_POR1o%2BKOGv_8A_ugUx-GeafFO_5CWNF%3DT5NMg%40mail.gmail.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BidhCzDd3HnS_yRqp6%3D%2Ba%3DtrqHEwUfRLS21P%2BLKwbc6iJQ%40mail.gmail.com.

ci.jenkins.io slow builds: Artifactory download issue

[Damien Duportal]

Hello dear contributors,

The builds on ci.jenkins.io are really slow since ~ 2hours.
An issue is opened at https://github.com/jenkins-infra/helpdesk/issues/2733

We identified the source of slowness: it seems that the downloads from 
repo.jenkins-ci.org are really really slow. 
JFrog had been contacted and we are waiting for feedback from them to fix 
the issue.

We'll answer back there as soon as we have more informations.

Don't hesitate to watch the GitHub issue 
(https://github.com/jenkins-infra/helpdesk/issues/2733) to track the 
changes.

Please note that your local builds could also be impacted (if you do not 
have the artefacts on your local build cache).

For the infra team,
Damien Duportal

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/4b0d6a9e-5ec0-456a-8803-55d3ea6d8b2cn%40googlegroups.com.

Re: INFRA project issues migration from Jira to Github

[Ullrich Hafner]

> 
> My regret is the fact I've learned about the "notifyUsers=false" Jira REST 
> API parameter too late.
> 

Well, I think it is very important to notify reporters that their issues have 
been moved to a new system. 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/BF7840EA-1A0D-4D6C-8FCD-253C08947C92%40gmail.com.

Re: INFRA project issues migration from Jira to Github

['Herve Le Meur' via Jenkins Developers]

On Thu, Jan 13, 2022 at 9:50 AM Ullrich Hafner 
wrote:

>
> Am 13.01.2022 um 08:46 schrieb Tim Jacomb :
>
> The information was included in the import
>
> All of them have the reporter, and the ones assigned have it in the
> expanded details section, e.g
> https://github.com/jenkins-infra/helpdesk/issues/2690
>
> GitHub doesn’t let you report as another user,
>
>
> I see, this is a real drawback of the import. I am using a „reporter"
> filter quite often in Jira.
>

I can propose you as a workaround this kind of search:
https://github.com/jenkins-infra/helpdesk/issues?q=is%3Aissue+%22originally+reported+by+hlemeur%22

> and assignee would require a Jira -> GitHub mapping, which might work for
> the INFRA project as it’s unlikely to be many people assigned to, but also
> not very valuable info IMO.
>
>
> I think it is a very valuable information who actually fixed a bug. But
> since the information is at least visible in the description text at least
> a workaround is available...
>

As you noticed, there is additional information in the issues body in a
 block, closed by default to avoid clutter.

Tim already said what I was about to respond about the author and assignee
possibilities or lack of.

My regret is the fact I've learned about the "notifyUsers=false" Jira REST
API parameter too late.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAL-LwjyHVrJSWPfT3m11HHkvL%3DdQ6mHUxVs%2B6UZ_smQTgKMURw%40mail.gmail.com.

Re: INFRA project issues migration from Jira to Github

[Ullrich Hafner]

> Am 13.01.2022 um 08:46 schrieb Tim Jacomb :
> 
> The information was included in the import
> 
> All of them have the reporter, and the ones assigned have it in the expanded 
> details section, e.g 
> https://github.com/jenkins-infra/helpdesk/issues/2690 
> 
> 
> GitHub doesn’t let you report as another user,

I see, this is a real drawback of the import. I am using a „reporter" filter 
quite often in Jira. 

> and assignee would require a Jira -> GitHub mapping, which might work for the 
> INFRA project as it’s unlikely to be many people assigned to, but also not 
> very valuable info IMO.

I think it is a very valuable information who actually fixed a bug. But since 
the information is at least visible in the description text at least a 
workaround is available... 

> 
> There’s hundreds of old issues to review and likely close which should end up 
> with a much more manageable backlog
> 
> On Wed, 12 Jan 2022 at 23:42, Ullrich Hafner  > wrote:
> It seems that the reporters (and assignees) of the issues have not been 
> mapped. Is this planned? 
> 
> 
>> Am 12.01.2022 um 14:50 schrieb 'Herve Le Meur' via Jenkins Developers 
>> mailto:jenkinsci-dev@googlegroups.com>>:
>> 
>> Hello!
>> 
>> As some of you might have already noticed, all issues related to the 
>> Infrastructure project have been migrated from Jira 
>> (https://issues.jenkins.io/projects/INFRA/issues 
>> ) to Github 
>> (https://github.com/jenkins-infra/helpdesk/issues?q=label%3Aimported-jira-issue
>>  
>> )
>> 
>> It's almost done, several docs linking to the jira project still have to be 
>> updated to point to this Github repository.
>> 
>> You can find more details and the related infra meeting notes here: 
>> https://github.com/jenkins-infra/helpdesk/issues/9 
>> 
>> 
>> Regards,
>> 
>> Hervé
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-dev+unsubscr...@googlegroups.com 
>> .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/e564ed63-3fd7-4888-a8b5-6630974ed91cn%40googlegroups.com
>>  
>> .
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-dev+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/DB75232C-4F54-4BC7-AD27-94F2D5292C87%40gmail.com
>  
> .
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-dev+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BidW%2BDzstqjgj7-MvkuPFYLSwFTeWF1%3DKxfOjkrMpa8jqQ%40mail.gmail.com
>  
> .

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/B814ACB6-60B9-4048-84B6-1641ED586075%40gmail.com.

2.319.3 release lead

[Tim Jacomb]

Hello

Is anyone interested in being the release lead for 2.319.3?

Planned dates can be seen on the event calendar:
https://www.jenkins.io/events/#event-calendar
Release candidate by 26th January
Release on 9th February

The documentation is at:
https://github.com/jenkins-infra/release
/blob/master/.github/ISSUE_TEMPLATE/1-lts-release-checklist.md

I'll be available to answer any questions and provide guidance (along with
hopefully other past release leads)

We chat in #jenkins-release on libera IRC,
https://www.jenkins.io/chat/#jenkins-release

Anyone interested?

Thanks
Tim

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bid%3DEqvixnwHmS93XPk1_jAkHMSj3_DAMaHSQOwctUC5HA%40mail.gmail.com.