Re: plugin cd issue

I _think_ you're looking at the wrong check_run. This appears to be the right one: https://github.com/jenkinsci/caffeine-api-plugin/runs/3165930312?check_suite_focus=true and it didn't trigger a release because there wasn't an 'interesting' change. You should be able to trigger a release

Re: Forked repositories in GitHub

Wouldn't creating a repo and pushing the code instead of forking work during the hosting process? On Wed, 28 Jul 2021 at 15:02, Jesse Glick wrote: > On Wed, Jul 28, 2021 at 2:48 AM timja...@gmail.com > wrote: > >> Seem's like GitHub won't break the fork relationship anymore without both >>

Re: Forked repositories in GitHub

have any additional questions about this! On Wed, 28 Jul 2021 at 17:38, Slide wrote: > It would be super ideal to do transferring if we could figure out a good > process for it, we lose GitHub Issues and some other things when we fork as > is. > > On Wed, Jul 28, 2021 at 8:3

Re: Using sshd-core in the git plugin

I replied on the PR. You aren't using the sshd provided copy but instead are using the jenkins cli one On Fri, 6 Aug 2021 at 16:08, Mark Waite wrote: > The git credentials binding project in Google Summer of Code is making > progress on private key support. Private keys are working on Windows

Re: [jenkins-infra] Re: Missing Version Installation Count

The issue has been tracked down: https://github.com/jenkins-infra/plugin-site/pull/764#issuecomment-894471739 This code needs changing: https://github.com/jenkins-infra/infra-statistics/blob/gh-pages/pluginversions/pluginversions.js#L12 On Thu, 5 Aug 2021 at 22:13, Tim Jacomb wrote: > Righ

Re: Using JDK 11 instead of JDK 8 in default docker images

Jetty, Hikari, and opensaml are all projects I’ve come across recently where new development has a minimum Java 11 version… there’s probably many others On Wed, 11 Aug 2021 at 16:03, Matt Sicker wrote: > Plus Java 17 comes out really soon. I can imagine that will inspire more > projects to set

Re: Emeritus concept for Jenkins developers (was: Re: Proposal: Adding Basil Crow to the Jenkins Core maintainers team)

+1 we have this in jenkins-infra On Thu, 23 Sep 2021 at 10:28, Baptiste Mathus wrote: > Hi all, > > Following up on Jesse's comment, and as I was reflecting on this a few > days ago: I think we should introduce an Emeritus concept/status for > Jenkins core team's inactive members. > > That

Release team members

Hello Continuing from https://groups.google.com/g/jenkinsci-dev/c/YhXRKybGgMg/m/IRjH_VykCwAJ I would like to invite the previous release leads to join the release team officially in jenkinsci/jenkins-infra GitHub organisations: - Beatriz Muñoz (@bmunozm) - Ildefonso Montero

2.303.3 release lead

Hello Is anyone interested in being the release lead for 2.303.3? Planned dates can be seen on the event calendar: https://www.jenkins.io/events/#event-calendar Release candidate by 20th October Release on 3rd November The documentation is at: https://github.com/jenkins-infra/release

Re: 2.303.3 release lead

Thanks! (libera IRC, not freenode, copied from an old email -.-) On Wed, 13 Oct 2021 at 13:32, Raihaan Shouhell wrote: > Sure I'll take it > > Cheers, > Raihaan > > On Wed, Oct 13, 2021, 8:22 PM Tim Jacomb wrote: > >> Hello >> >> Is anyone intereste

Re: Request to adopt Job DSL Plugin

Adding Daniel to cc On Mon, 11 Oct 2021 at 16:45, Jamie Tanna wrote: > Hi Gavin, > > Thanks for the reply - it's helpuful to understand the process fully! > > Yes, that's a good point, this wouldn't be a takeover, more that I'm > volunteering to be an additional developer. > > I've raised >

Re: GitHub Org profiles for better contributor onboarding and repo navigation

+1 to adding it, I've added an example one to my test org copying Oleg's content: https://github.com/timja-org > We cannot even pin the key repositories Weird I tried setting it directly by messing with the request, it accepts it but doesn't actually do anything, I can add others just fine.

Re: Send asynchronous XmlHttpRequest through javascript with authentication

You don't pass the credentials, you pass along the users cookies On Wed, 20 Oct 2021 at 13:39, t4k30ff wrote: > Hello, > > I was currently experimenting with jelly and javascript and wrote a > RootAction that would be accessed by the loaded page every second through a > timeout. > The problem i

New LTS baseline selection

Hi all, It's time to select the next LTS baseline. The best candidate right now appears to be 2.317 or the upcoming 2.318 2.317 fixed JENKINS-66753 which was reported as a major issue across a few versions. Thanks Tim -- You received this

Re: Company plugins in Jenkins org

Sounds good, could probably have one for the Jenkins core team too in RPU. On Thu, 21 Oct 2021 at 14:47, Baptiste Mathus wrote: > > > Le jeu. 21 oct. 2021 à 13:58, 'Daniel Beck' via Jenkins Developers < > jenkinsci-dev@googlegroups.com> a écrit : > >> >> >> On Thu, Oct 21, 2021 at 1:47 PM

Re: Plugin Maintainer alumni metadata

I don't see the need for this, if someone wants to come back to active they can just ask, the git history is there in RPU, commit history etc On Sun, 17 Oct 2021 at 09:52, Oleg Nenashev wrote: > GitHub contributor metadata does not list former maintainers specifically, > unless you want to

Re: 2.303.3 release lead

nesday, October 13, 2021 at 2:41:44 PM UTC+2 timja...@gmail.com >> wrote: >> >>> Thanks! >>> >>> (libera IRC, not freenode, copied from an old email -.-) >>> >>> On Wed, 13 Oct 2021 at 13:32, Raihaan Shouhell >>> wrote: >

Re: Proposal: Move Jenkins Test Harness issue tracker to GitHub Issues

+1 On Sun, 17 Oct 2021 at 09:50, Oleg Nenashev wrote: > Hi all, > > I suggest moving the Jenkins Test Harness issue tracker to GitHub Issues. > This is a test framework, and it is not exposed to the user ecosystem. > Using GitHub issues would be ore convenient for use-cases, and particularly >

Re: Release team members

Thanks added both On Thu, 14 Oct 2021 at 20:03, Basil Crow wrote: > On Thu, Oct 14, 2021 at 1:10 AM Oleg Nenashev > wrote: > > > > Better late than never, I would like to join the group indeed. > > Ditto for me. Happy to help out as I have time. > > -- > You received this message because you

Re: unable to perform jenkins release through local machine

Or update the permission file with the correct path… On Fri, 15 Oct 2021 at 11:49, Mark Waite wrote: > I believe that the pom.xml file > > for the plugin declares that the plugin will be

Re: Proposal: Move Jenkins Test Harness issue tracker to GitHub Issues

+1 to Jesse’s list On Mon, 18 Oct 2021 at 14:33, 'Jesse Glick' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > On Sun, Oct 17, 2021 at 4:50 AM Oleg Nenashev > wrote: > >> Currently we have only a few issues in Jira >> > > BTW if switching canonical issue tracker I recommend

Re: Missing Docker tags for the latest Docker LTS image (2.303.1)

It was removed, but a few users asked for it back so they could type 'lts' in the docker search. It was restored in https://github.com/jenkinsci/docker/pull/1207 and will be there with the next LTS version on Wednesday next week On Wed, 29 Sept 2021 at 12:55, Victor Martinez <

Re: Plugin docs migration to GitHub as a Hacktoberfest project

See https://github.com/jenkins-infra/plugins-wiki-docs On Wed, 29 Sep 2021 at 13:12, Jesse Glick wrote: > Does the automated conversion tool even still work now that Confluence is > dead? Or do you need to write docs from scratch / memory? > > -- > You received this message because you are

Re: Migration path to spring security with credentials plugin UI

2) correct credentials api needs updating there’s no way to work with it currently that avoids deprecation warnings as far as I know On Tue, 28 Sep 2021 at 02:34, 'Gavin Mogan' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > I think there's helper functions for this > > I want

Add Mark Waite to Jep editors

Hello We've had a bit of a shortage of jep editors recently with some JEPs getting stuck. I've had a chat with Mark Waite and he's happy to help out here. Any objections or +1s for adding Mark? +1 from me Thanks Tim -- You received this message because you are subscribed to the Google

Re: Core build instability

Thanks for tracking down where the memory issue appears to be coming from in https://github.com/jenkins-infra/pipeline-steps-doc-generator/pull/94#issuecomment-923094344 I think the other issue is the CPU count appears to have been accidentally reverted to 2 cores =/ It was increased here:

Re: Core build instability

Given this has been going on for weeks including people looking at flakey tests and a lot of re-running of builds it was not clear at the time this was because resources had actually changed. We were looking for the root cause and thought you may have had an insight into it, I would definitely

Re: Proposal: Adding Basil Crow to the Jenkins Core maintainers team

+1, (if you want it Basil) On Wed, 22 Sept 2021 at 14:32, Mark Waite wrote: > +1 from me > > On Wed, Sep 22, 2021, 4:49 AM 'Daniel Beck' via Jenkins Developers < > jenkinsci-dev@googlegroups.com> wrote: > >> >> >> > On 22. Sep 2021, at 11:14, Oleg Nenashev >> wrote: >> > >> > It would be great

Release team

Hello I would like to propose a release team in the Jenkins GitHub org. The role and permissions are documented in https://github.com/jenkinsci/jenkins/blob/master/docs/MAINTAINERS.adoc#roles but they don’t actually exist in the jenkinsci GitHub org. In jenkins-infra we have a release team

Re: Core build instability

Pending https://github.com/jenkins-infra/jenkins-infra/pull/1872 being approved I've manually changed the settings and we finally have a passing build for stable. (in https://github.com/jenkinsci/jenkins/pull/5729) On Mon, 20 Sept 2021 at 20:57, Jesse Glick wrote: > On Mon, Sep 20, 2021 at

Re: Release team members

y, September 24, 2021 at 9:52:30 AM UTC+2 Ildefonso Montero wrote: > >> No issues from my side :-) Thanks for driving this Tim! >> >> On Thu, Sep 23, 2021 at 9:29 PM Mark Waite wrote: >> >>> I would like to be a member of that group. >>> >

Re: Release team

Thanks Daniel, I've sorted the jenkinsci side out On Mon, 27 Sept 2021 at 10:13, 'Daniel Beck' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > > > On Mon, Sep 27, 2021 at 10:07 AM Tim Jacomb wrote: > >> Can someone create the GitHub team pleas

Re: Release team

..@gmail.com > wrote: > >> +1 >> >> Am 21.09.2021 um 11:32 schrieb Tim Jacomb : >> >> Hello >> >> I would like to propose a release team in the Jenkins GitHub org. >> The role and permissions are documented in >> https://github.com/jen

Re: Plugin Adoption Request: subversion-plugin

Hello As this is up for adoption we can proceed straight away. Please send a PR to https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-subversion.yml Thanks Tim On Mon, 27 Sept 2021 at 08:35, Diego Diez wrote: > Hi, I would like to adopt the

Re: FilePathTest.copyToWithPermissionSpecialPermissions test

Thanks for tracking that down. For the record the test is already disabled on Windows and Mac because of the POSIX specific features it relies on Thanks Tim On Fri, 24 Sep 2021 at 08:43, Nayana Thorat wrote: > This failure is due to unavailability of libjffi-1.2.so for s390x . > basically

Re: Core build instability

> Sounds like the instability in core builds themselves was unrelated, a coincidence? I think it was another symptom compounded by us not having enough history to see when it started very well. There was a clear reliable failure change in 2.309 which was caused by a minor resource increase

Re: Confirming Jan 12, 2022 for 2.319.2

It’s very intentional, is that enough time or should we push it one more week out? On Fri, 3 Dec 2021 at 14:19, Mark Waite wrote: > I see on the Jenkins events calendar at https://www.jenkins.io/events/ > that the 2.319.2 release date is set for January 12, 2022. That's great > with me. > > I

Re: Java 11 as minimum? (Jetty 9.4.x EOL)

Looks like Andrew has fixed the reporting issue for core versions by rewriting the processor: https://github.com/jenkins-infra/jenkins-usage-stats You can see the report at https://stats.jenkins.io/plugin-installation-trend/jvms.json Last month: "163572480": { "1.7": 686,

Re: Repository access request

Can you create an INFRA ticket on https://issues.jenkins.io/ using the netsparker account please? On Thu, 30 Dec 2021 at 11:49, 'Ozgur Ozturk' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > Hi, > > I want to have admin access for that repository >

Re: Adoption request for "sonar-gerrit" plugin

See https://www.jenkins.io/security/plugins/#followup On Thu, 30 Dec 2021 at 18:02, 'Réda Housni Alaoui' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > Hello Mark, > > I just released a fix for > https://www.jenkins.io/security/advisory/2019-10-23/#SECURITY-1003 in > version

Re: Succession of timeouts during Docker actions on ci.jenkins.io

Hmm this isn’t what we were discussing though, this is using ci.Jenkins.io which uses a different cluster as far as I know Cc infra On Tue, 4 Jan 2022 at 15:19, Mark Waite wrote: > > > On Tuesday, January 4, 2022 at 5:57:04 AM UTC-7 Chris Kilding wrote: > >> Hi, >> >> Timeouts related to the

Re: Jakarta Mail and Jakarta Activation

It’s no problem to get those transferred in, we did a few last year Generally just raise an issue in the repo about transferring to jenkinsci feel free to ping me on them On Tue, 4 Jan 2022 at 17:40, Basil Crow wrote: > On Mon, Jan 3, 2022 at 12:57 PM Basil Crow wrote: > > > > Yeah, there are

Re: Repository access request

Done, check https://github.com/jenkinsci for an invite / your email inbobx On Mon, 3 Jan 2022 at 07:34, 'Ozgur Ozturk' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > Created, thanks. > https://issues.jenkins.io/browse/INFRA-3174 > > On Thursday, December 30, 2021 at 9:21:37 PM

Re: Repository access request

Done On Mon, 3 Jan 2022 at 14:15, 'Ozgur Ozturk' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > I apologize, I deleted a team but I noticed that I was in that team too. > Please can you add me again? > > On Monday, January 3, 2022 at 4:43:39 PM UTC+3 Ozgur Ozturk wrote: > >>

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

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

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

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 i

Re: Request to update default assignee on JIRA for job-dsl-plugin

Done, if you use Jira for watching issues it's often worth configuring your own filter anyway. Some people prefer that there's no default assignee and watch via the filter as often people get confused with default assignee as they think someone will be working on it because it's assigned. On

Add timja to jep editors

Hello May I join the jep editors team please? There's a backlog building up there again. https://github.com/jenkinsci/jep/pulls?q=is%3Apr+is%3Aopen+sort%3Aupdated-desc (also is anyone else interested in helping out?) Thanks Tim -- You received this message because you are subscribed to the

Re: Jenkins 2.319.2 LTS RC testing started

We generally do that, https://github.com/jenkins-infra/release/blob/master/.github/ISSUE_TEMPLATE/1-lts-release-checklist.md#rc-creation Matrix auth 3.0 broke a bunch of tests and the RC was already late so we skipped that and used the fallback method. On Tue, 21 Dec 2021 at 21:46, 'Jesse

Re: Java 11 as minimum? (Jetty 9.4.x EOL)

Back to Java 11 :) (I suggest another thread for Java 17 Basil has been doing some great work there) There's been an 'admin monitor' around for quite a while now encouraging users to upgrade to Java 11 if they are on 8. The JavaVersionRecommendationAdminMonitor

Re: Setting up automated plugin release

There's quite a few checks that are run as part of warnings-ng and junit. Only the main check 'Jenkins' matters for release. Which wasn't finished when you sent this email, https://github.com/jenkinsci/bmc-cfa-plugin/runs/4616176655?check_suite_focus=true passed and it's been released now

Re: Java 11 as minimum? (Jetty 9.4.x EOL)

gt; weeklies and hence June for LTS is a bit too aggressive. >> >> I think we should *at least* target the LTS _after_ June. >> >> And in the meantime keep communicating on this timeline like we had done >> for Java 8. >> Blogs. Tweet encouraging to update to Java 11,

ANN: Hosting switched to GitHub issues

Hello New hosting requests will be processed on GitHub in RPU. There is a template for hosting requests: https://github.com/jenkins-infra/repository-permissions-updater/issues/new?assignees==hosting-request=1-hosting-request.yml It's pretty similar to the previous one. The main change is you

Re: Java 11 as minimum? (Jetty 9.4.x EOL)

I don’t really understand this, Basil has done the minor Pom file changes needed. Users have been running Java 11 in production for years including the Jenkins project. Java 11 work from the Jenkins project side is not much work remaining, generally just filling in dates =/ On Mon, 3 Jan 2022 at

Re: Add timja to jep editors

I have added myself, thanks all On Tue, 21 Dec 2021 at 14:54, Oleg Nenashev wrote: > +1 > > On Tuesday, December 21, 2021 at 3:47:25 PM UTC+1 m...@basilcrow.com > wrote: > >> +1 >> > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. >

Re: Setting up automated plugin release

this should fix your current issue: https://github.com/jenkinsci/bmc-cfa-plugin/pull/11 On Wed, 22 Dec 2021 at 09:50, Marit M wrote: > I managed to fix that by applying a label to the PR. > > > ב-יום שלישי, 21 בדצמבר 2021 בשעה 16:53:51 UTC+2, ‪Marit M‬‏ כתב/ה: > >> Hi, >> >> >> >> I have

Re: Java 11 as minimum? (Jetty 9.4.x EOL)

> I don't yet see a compelling benefit that would motivate us to drop support for OpenJDK 8. Its support lifetime is almost as long as Java 11. New language features... Not stuck on a version released 7 years ago... Libraries dropping support for it... I'm now sure how the Java 8 baseline

Re: Java 11 as minimum? (Jetty 9.4.x EOL)

> So it's almost certain we're just not collecting usage stats correctly. Filed https://issues.jenkins.io/browse/JENKINS-67158 for investigation, would be great if someone can take a look! On Wed, 17 Nov 2021 at 09:03, 'Daniel Beck' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote:

Re: Enabling Continuous Delivery / automated release process for Gradle project

I don't think it will have been done yet because the GitHub actions only support maven. There's not many projects using gradle so I guess you're the first to look at it. The action wouldn't need much work to support it, Probably just a flag defaulted to maven and then a change in this script:

Re: New members of jenkins.io triage team

+1 no need for triage, it doesn't give much permission at all On Wed, 17 Nov 2021 at 16:16, Mark Waite wrote: > We met in Docs Office Hours this week and decided that we should proceed > to add the new members to the triage team even without the new CLA process. > > On Thu, Nov 4, 2021 at 10:41

Re: Request to adopt priority sorter plugin

Done On Sat, 27 Nov 2021 at 13:20, Mark Waite wrote: > Oleg has merged the repository permissions updated pull request and I've > confirmed with `mvn deploy` that I have permission to upload to artifactory. > > I don't have permissions to merge pull requests on the GitHub repository. > I don't

Re: release went wrong?

Just release a new version… Jenkins won’t offer older versions to users anyway, so skipping a version isn’t an issue On Fri, 19 Nov 2021 at 23:22, Sergei Butylin wrote: > That’s what missing [maven-release-plugin] prepare release >

Re: 2.319. 1 Release Lead

Thanks Cathy Would you be able to create the checklist at https://github.com/jenkins-infra/release/issues/new/choose Reach out on the issue or in IRC if you’ve got any questions On Fri, 12 Nov 2021 at 17:03, 'Cathy Chan' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > Hi

Re: Plugin documentation not showing on site

The docs are showing for me currently On Thu, 18 Nov 2021 at 12:16, 'Daniel Beck' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > > > On Thu, Nov 18, 2021 at 1:13 PM Daniel Beck wrote: > >> >> >> On Thu, Nov 18, 2021 at 11:48 AM Jean-Marc Meessen < >>

Re: Request to adopt Job DSL Plugin

It's not it's own repository, it's just how github does wiki's `git clone https://github.com/jenkinsci/job-dsl-plugin.wiki.git`, worked just fine for me. On Wed, 27 Oct 2021 at 16:15, Jamie Tanna wrote: > Is it possible to also get access to the Wiki's repository? > > It looks like it's stored

Re: Company plugins in Jenkins org

> that helps at all. > > /James > > > On Wednesday, October 27, 2021 at 10:58:51 AM UTC+1 bma...@gmail.com > wrote: > >> Thanks Tim for the confirmation. >> >> Yeah, not 100% of the naming either. >> But yep, given at this point it's only one + this

Re: New LTS baseline selection

Java 11 >> >> Anything older than 2.317 and later than 2.313 would require a backport >> of JENKINS-66753. >> >> Mark Waite >> >> On Wed, Oct 20, 2021 at 12:31 PM Tim Jacomb wrote: >> >>> Hi all, >>> >>> It's time to sel

Re: New LTS baseline selection

Sure sounds fine On Thu, 28 Oct 2021 at 08:55, 'Daniel Beck' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > If you like 2.318 for this, you should wait for 2.319, which will only > contain security fixes. > > -- > You received this message because you are subscribed to the

Jenkins acceptance tests are passing!

To quote Ulli: "This is the first time (since inception) that the ATH test suite is . Wow, we need to celebrate   https://github.com/jenkinsci/acceptance-test-harness/pull/706#issuecomment-953960043 Hopefully we can keep them that way or at least failures should be more easy to motivate

Re: Request to be maintainer of JiraTestResultReporter plugin

It’s continuing in the PR no need for any further action here On Wed, 27 Oct 2021 at 11:09, Ullrich Hafner wrote: > Since this plugin is not up for adoption you should CC to the current > maintainers. > > > Am 27.10.2021 um 10:57 schrieb 'Ildefonso Montero' via Jenkins Developers < >

Re: Company plugins in Jenkins org

Sounds fine, not 100% sure company needs to be at the start but we can also rationalise it later if we get more On Wed, 27 Oct 2021 at 10:42, Baptiste Mathus wrote: > Hi all, > > FYI I've created this epic to track this: > https://issues.jenkins.io/browse/INFRA-3111. > > I plan to manually do

2.319. 1 Release Lead

Hello Is anyone interested in being the release lead for 2.319.1? Planned dates can be seen on the event calendar: https://www.jenkins.io/events/#event-calendar Release candidate by 17th November Release on 1st December The documentation is at: https://github.com/jenkins-infra/release

Re: New members of jenkins.io triage team

+1 On Wed, 3 Nov 2021 at 06:48, 'Gavin Mogan' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > Sounds good to me. > > On Tue, Nov 2, 2021 at 4:04 PM Mark Waite > wrote: > >> During Docs Office Hours yesterday we discussed adding more people to the >> copy editors team on

Re: Proposal: Changing the Contributor License Agreement Process

Sounds good for infra-cla repo On Mon, 8 Nov 2021 at 09:50, Ullrich Hafner wrote: > This is a good idea, thanks for driving this! > > > Am 08.11.2021 um 10:38 schrieb Oleg Nenashev : > > Hi all, > > I would like to proceed with https://github.com/jenkinsci/infra-cla and > to build a new

Re: Jenkins 2.303.3 LTS RC testing started

FYI release is delayed by 1 day to November 4th On Sun, 31 Oct 2021 at 04:05, Mark Waite wrote: > I've been running the release candidate since shortly after it was > released and have found no issues. > > On Wed, Oct 20, 2021 at 7:16 AM raihaan...@gmail.com < > raihaanhims...@gmail.com> wrote:

2.319.2 Release lead

Hello Is anyone interested in being the release lead for 2.319.2? Planned dates can be seen on the event calendar: https://www.jenkins.io/events/#event-calendar Release candidate by 15th December (short notice apologies but can delay a couple of days) Release on 12th January The documentation

Re: 2.319.2 Release lead

Thank you! On Wed, 15 Dec 2021 at 22:23, 'Cathy Chan' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > Hi Tim, > > I can do this again. I can get the checklist started and ping you. > > - Cathy. > > On Tuesday, December 14, 2021 at 3:54:18 AM UTC-5 timja...@gmail.com > wrote: >

Re: Proposal: Adopting Stapler as official Jenkins project

I've moved stapler to Jenkinsci as part of https://issues.jenkins.io/browse/INFRA-2908 Core team has access Jesse has taken care of most of the rest of the proposals already On Wed, 26 May 2021 at 17:03, Oleg Nenashev wrote: > Thanks to Kohsuke for your approval! And thanks to Kohsuke and

Re: Annotation versions

Former sounds better On Wed, 15 Dec 2021 at 04:12, Basil Crow wrote: > The Jenkins core BOM currently defines versions for > spotbugs-annotations, jcip-annotations, and > access-modifier-annotation, and core ships JARs for > spotbugs-annotations and access-modifier-annotation (but not >

Re: Release lead for the next LTS version

Thanks! Would you create a new issue for it using the new LTS release option: https://github.com/jenkins-infra/release/issues/new/choose On Tue, 20 Jul 2021 at 15:24, Basil Crow wrote: > I can volunteer for this one. > > On Tue, Jul 20, 2021 at 12:01 AM Tim Jacomb wrote: >

[ci.jenkins.io update] Agents upgraded from ubuntu 18.04 to 20.04

Hello Just a note in case anyone notices anything, We've updated ci.jenkins.io to ubuntu 20.04. Smoke tests have passed, Please let us know if you see any issues with the agents post upgrade Thanks Tim -- You received this message because you are subscribed to the Google Groups "Jenkins

Release lead for the next LTS version

Hello I'm looking for a release lead for the next LTS version (most likely 2.302). The release candidate is due on 11th August The release day is 25th August. It doesn't require any specific permissions, anyone can do it (others can merge / setup the initial origin branches required). What

Re: Choosing Jenkins September LTS release baseline

Hi all Thanks for starting this Mark. 2.302 has been selected as the next LTS baseline. I will create the origin branches now so that Basil can continue with the rest of it Thanks Tim On Fri, 16 Jul 2021 at 17:27, Ullrich Hafner wrote: > +1 for 2.302 > > Am 16.07.2021 um 14:26 schrieb

Re: Stapler IntelliJ Plugin JetBrains Marketplace listing

cc Kohsuke On Fri, 28 May 2021 at 22:37, Oleg Nenashev wrote: > FTR the plugin was moved to the jenkinsci GitHub organization: > https://github.com/jenkinsci/idea-stapler-plugin > Denys will be an admin there once he accepts the invitation to the GitHub > org > > On Monday, May 10, 2021 at

Re: best ide

Cc kk On Sun, 25 Jul 2021 at 23:05, Denys Digtiar wrote: > Only the owner of the plugin can publish it. The plugins can be owned by > organizations now. The Jenkins org was created > https://plugins.jetbrains.com/organizations/jenkins. Now Kohsuke needs to > transfer the plugin to the org. Once

Re: best ide

tle but I couldn't find a way to > transfer a plugin. Does anyone know how to transfer it? > > On Sun, Jul 25, 2021 at 11:48 PM Tim Jacomb wrote: > >> >> Cc kk >> On Sun, 25 Jul 2021 at 23:05, Denys Digtiar >> wrote: >> >>> Only the

Re: Proposal: Move Jenkins Test Harness issue tracker to GitHub Issues

I archived the component in Jira for the ones I found, not all of them mapped to a component and I didn't dig too hard. Archiving seems to keep the component there but no new issues can be added which maps to what you said Jesse Anyone can migrate the issues, Herve is the one who did this most

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

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

Re: INFRA project issues migration from Jira to Github

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, and assignee would require a Jira -> GitHub mapping,

2.319.3 release lead

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

Re: Dropping support for IE 11

t; >>> > Drop IE support completely from the support table on >>> https://www.jenkins.io/doc/administration/requirements/web-browsers/ >>> >>> I know I had to use my open source saucelabs account when I was >>> helping out with blueocean, its so hard to t

Re: Plugin for adoption: OWASP Dependency Check

Just the pull request to repository permissions updated is needed, skip the help desk one, we’ll do it there. On Mon, 17 Jan 2022 at 19:18, Mark Waite wrote: > > > On Mon, Jan 17, 2022 at 11:07 AM Daniel Warmuth wrote: > >> Hi, >> >> I'd like to become maintainer of this plugin ( >>

Re: Abstract type and groovy syntax

Best to send code examples if you can specifying a @Symbol(“stepName”) on the descriptor of the step will remove the need for the class syntax On Sat, 8 Jan 2022 at 20:53, 'Réda Housni Alaoui' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > Hello, > > I need to convert a

Re: Sunsetting Georgia bold

There's a 'modern' header hidden behind the 'jenkins.ui.refresh' system property You can also enable it by setting 'Functions.UI_REFRESH = true' in the script console: [image: image.png] We could look at switching over to that? I think there might have been a second iteration of this somewhere

Re: Sunsetting Georgia bold

Is there a specific reason why the header never made it into Jenkins as > default? I mean, it doesn't look bad, but according to git blame it's > shipped for ~2+ years now. It was the first of the UX improvements done a couple of years ago and was put behind a feature 'because', envisaging other

Re: [Proposal] Transfer of CloudBees-community/syslog-java-client to jenkinsci Github org

Is there anyone from CloudBees who wants access to this? On Wed, 16 Mar 2022 at 13:49, 'Cyrille Le Clerc' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > > FYI The repository has been transferred: > https://github.com/jenkinsci/syslog-java-client > > Thanks Mikael, > I verified

Re: Using data-tables-api-plugin

If you can share your code / a branch with what you have you might get better help if that's possible On Tue, 15 Mar 2022 at 19:44, Ullrich Hafner wrote: > > > Am 11.03.2022 um 07:31 schrieb Marit M : > > Hi, > > I'm trying to implement tables with dynamic model based content in my > plugin. >

Re: [jenkins-infra] Re: Missing Version Installation Count

t; The issue has been tracked down: >> >> https://github.com/jenkins-infra/plugin-site/pull/764#issuecomment-894471739 >> >> This code needs changing: >> https://github.com/jenkins-infra/infra-statistics/blob/gh-pages/pluginversions/pluginversions.js#L12 >> >>

Re: regarding enabling automated plugin release for extended-choice-parameter plugin

Should work now, I can confirm secrets are there too On Thu, 24 Feb 2022 at 18:44, vimil saju wrote: > Hi Gavin, > The link I put in the email was incorrect but the issue is still present. > https://github.com/jenkinsci/extended-choice-parameter-plugin/settings/secrets/actions > still gives a

Re: Automated plugin release failing on 'check interesting categories' step

We were just discussing this here: https://github.com/jenkinsci/dark-theme-plugin/pull/170#issuecomment-1050263227 By using a manual trigger to bypass the interesting category check and publishing the release notes myself I was able to get the release out On Thu, 24 Feb 2022 at 22:06, José Lamas

<    1   2   3   4   5   6   >