Re: [JEP-229] Plugin CD workflow version scheme

The CD guide describes a scenario named "Manually controlled prefix*", *that outlines how to setup an example formatted as "major.minor", but you can break it down with ease to something like "major.minor.patch+build-hash" by

Re: [JEP-229] Plugin CD workflow version scheme

Heyo, I admit, the first time I stumbled apart major components releasing via CD last year, I was confused by it too, however, the more I read myself into CD, the clearer it became. The "build.hash" scheme is the default CD setup, if plugin authors choose to use a different setup, they can

Re: Jenkins on SQLite

That sounds impressive! Your prototype implementation looks much promising, thanks for dropping the link here! ~ Alex On Sunday, 3 April 2022 at 18:23:37 UTC+2 m...@basilcrow.com wrote: > I have never used H2, but I have a strong preference for SQLite. It > has been deployed more widely than

Update pinned repositories on the jenkinsci organization

Heyo all, GitHub currently rolls out changes to the organization overview. Previously, three pinned repositories built a line. This behavior has changed. Two pinned repositories do now build a line, while four pinned repositories build a box. Currently, there are three pinned repositories,

Re: Update pinned repositories on the jenkinsci organization

n, 4 Apr 2022 at 23:53, 'Gavin Mogan' via Jenkins Developers < > jenkin...@googlegroups.com> wrote: > >> If I remember correctly, any member of the org can pin and unpin repos so >> we kinds gave up trying to manage it. >> >> On Mon., Apr. 4, 2022, 3:48 p.m. Alexan

Re: Automated plugin release

Various Spotbugs checks are failing. Take a look at https://ci.jenkins.io/job/Plugins/job/bmc-cfa-plugin/job/main/53/spotbugs/ for the list of failures. Locally, you can run `mvn spotbugs:check` to highlight the failures with your IDE to address them. On Tuesday, 5 April 2022 at 13:31:00

Re: Submission process of a new plugin

Heyo, there is this guide that outlines how to open a hosting request alongside the general information for publishing plugins . Though I'm unsure if there's a guideline how

Re: Release lead for 2.332.3

Heyo, I'd like to take it this time. ~ Alex On Tuesday, 12 April 2022 at 15:21:33 UTC+2 timja...@gmail.com wrote: > Hello > > Is anyone interested in being the release lead for 2.332.3? > > Planned dates can be seen on the event calendar: > https://www.jenkins.io/events/#event-calendar >

Re: Need Jenkins Jira access to create a Support ticket

This wiki article shows two possible solutions: > We're asking *what you're using Jenkins for* as an anti-spam measure only. We're not using that information for any purpose other than confirm you're a legitimate user. Try not to look like a (human) spammer when filling in that field. and >

Backporting for LTS 2.332.3 started

Backporting has started and the RC is scheduled for 2022-04-20. Candidates: https://issues.jenkins-ci.org/issues/?filter=12146 Fixed: https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.332.3-fixed Rejected: https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.332.3-rejected

Re: Java 17 support added to build toolchain

Thanks for your work, basil (again!) I've updated a bunch of plugins without issues. Based on my prior experience when building with Java 17, the spotbugs-maven-plugin throws a few warnings regarding JEP 411 (Java, not Jenkins). These warnings should be safe to be ignored, because a PR is

Re: Request to transfer my maintainer role for https://github.com/jenkinsci/fortify-on-demand-uploader-plugin

Heyo, you can do that yourself by filing a pull request against the repository permission updater which updates your plugin's permission file

Re: Request to transfer my maintainer role for https://github.com/jenkinsci/fortify-on-demand-uploader-plugin

That likely happens while processing your repository permission updater PR. The pull request template has a dedicated checklist

Re: Backporting for LTS 2.332.3 started

Looks more like a minor issue, I've labeled it as LTS candidate nevertheless. There's JENKINS-68276 too I'm looking forward to backport, FTR. On Thursday, 14 April 2022 at 19:02:00 UTC+2 m...@basilcrow.com wrote: > Perhaps we should consider

Re: Two week break in LTS schedule at end of 2023

Within the corrections, I'm +1 still :) On Monday, 16 October 2023 at 17:33:48 UTC+2 Mark Waite wrote: > Sad that I made so many date related mistakes in a mail message focused on > dates. Corrections below: > > On Monday, October 16, 2023 at 8:12:50 AM UTC-6 Mark Waite wrote: > > I've been

Re: October 2, 2023 Governance Board Agenda

Unfortunately, I can't make it today :( On Monday, 2 October 2023 at 19:19:03 UTC+2 Mark Waite wrote: > Agenda > > Comment > <https://hackmd.io/6mgEkr1rS7Ca4j4a5YxZfA?view#News>News > >- Jenkins elections 2023 nominations in progress - Alexander Brand

Re: Request to adopt github-scm-trait-notification-context-plugin (abandoned)

Approved. On Saturday, 23 September 2023 at 00:14:46 UTC+2 Ross Bender wrote: > >- Link to a plugin I want to adopt: >https://github.com/jenkinsci/github-scm-trait-notification-context-plugin >- The status of the plugin: abandoned >- Link(s) to pull requests I want to deliver: >

Re: Release lead for LTS 2.414.3

+1 On Monday, 25 September 2023 at 21:09:49 UTC+2 kris...@outlook.com wrote: > Hi everyone, > > I would like to volunteer to be the Release Lead for LTS 2.414.3. > > Planned dates can be seen on the event calendar: > https://www.jenkins.io/events/#event-calendar > > >- Release candidate by

Re: Add a co-maintainer for the Startup Trigger Plugin

Approved. On Friday, 22 September 2023 at 15:06:58 UTC+2 goun...@gmail.com wrote: > Hi, > > This is a request to add me (@gounthar on GitHub, @poddingue on > Jenkins) as a co-maintainer to the Startup Trigger Plugin. > > Link to a plugin you want to co-maintain: >

Re: Proposal: Kris Stern to join the release team

With the approval of the release officer, I've added you to the release team in the jenkinsci organization. To join the release team in the infra org, please file a helpdesk issue, I can't add you there. Welcome aboard :) On Monday, 9 October 2023 at 12:06:28 UTC+2 timja...@gmail.com wrote:

Re: Request to adopt groovy-events-listener-plugin (Up for adoption)

Added. On Tuesday, 17 October 2023 at 22:47:15 UTC+2 ray...@gmail.com wrote: > >- Link to a plugin you want to adopt: >https://github.com/jenkinsci/groovy-events-listener-plugin >- The status of the plugin: up for adoption >- Link(s) to pull requests you want to deliver: >

Re: Mark Waite as release lead for 2.426.1?

eduled to release Nov 15, 2023. >>> >>> I've been testing 2.426 in my development environment and am interested >>> in several of its changes. Some of those changes include: >>> >>>- Removal of Prototype.js JavaScript library >>> - Addi

Jenkins 2.332.3 LTS RC testing started

Hello everyone, Latest LTS RC was made public and it is ready to be tested. Final release is scheduled for 2022-05-04. Please, report your findings in this thread. Download the release from:

Re: Next LTS baseline

Heyo, 2.345 sounds promising, considering it contains current regressions and quite a few from older releases too. What happened to the suggestion to delay the next LTS baseline selection by two to four weeks to have more time to iron out regressions? ~Alex On Saturday, 23 April 2022 at

Re: Backporting for LTS 2.346.1 started

the additional time and start a secondary backporting process from past weekly releases to integrate the new LTS candidates. ~Alex On Saturday, 14 May 2022 at 11:25:09 UTC+2 Alexander Brandes wrote: > Backporting has started and the RC is scheduled for 2022-05-18. > > Candidates: https://issues.j

Re: 2.346.1 release lead

Heyo all, I'd like to take care of it, if possible. ~Alex On Friday, 13 May 2022 at 00:06:02 UTC+2 timja...@gmail.com wrote: > Sure, I've moved the release date 2 weeks out. > > New dates: > RC: 18th May > Release day: 15th June > > On Tue, 10 May 2022 at 17:51, Mark Waite wrote: > >> >> >>

Backporting for LTS 2.346.1 started

Backporting has started and the RC is scheduled for 2022-05-18. Candidates: https://issues.jenkins.io/issues/?filter=12146 Fixed: https://issues.jenkins.io/issues/?jql=labels%20%3D%202.346.1-fixed Rejected: https://issues.jenkins.io/issues/?jql=labels%20%3D%202.346.1-rejected -- You received

Jenkins 2.346.1 LTS RC testing started

Hello everyone, Latest LTS RC was made public and it is ready to be tested. Final release is scheduled for 2022-06-15. Please, report your findings in this thread. Download the release from:

Periodic rebuilding of core PRs on ci.jenkins.io through branch indexing

Hey everyone, if I understood the branch strategy correctly, core PRs are periodically rebuilt against the revision of their target branch, if it moves (e.g. after a PR merge). If you take a look at #6745 , you can see that the 1st

Re: Backporting for LTS 2.346.2 started

Hey Basil, thanks for adding up additional information about the couple of issues. I've backported the former issue. I'm not too opposed to backport the latter one too either, but I'd at least hold it off until it has been merged. ~ Alex On Tuesday, 28 June 2022 at 22:53:58 UTC+2

Backporting for LTS 2.346.2 started

Hey everyone, Backporting for 2.346.2 has started and the RC is scheduled for 2022-06-29. Candidates: https://issues.jenkins.io/issues/?filter=12146 Fixed: https://issues.jenkins.io/issues/?jql=labels%20%3D%202.346.2-fixed Rejected:

Re: Release lead 2.346.2

Hey everyone, if nobody else is interested, I'll take care of it again. Cheers Alex On Saturday, 25 June 2022 at 09:27:51 UTC+2 timja...@gmail.com wrote: > Hello > > Is anyone interested in being the release lead for 2.346.2? > > Planned dates can be seen on the event calendar: >

Re: Security approval required on UI-related PRs in Jenkins core

+1, labels indeed help to make it more clear what still needs to be done. We could add something like "needs-security-fix" next to the "needs-fix" label. On Thursday, 30 June 2022 at 12:37:18 UTC+2 timja...@gmail.com wrote: > I'd suggest another label for security review complete but needs

Jenkins 2.346.2 LTS RC testing started

Hello everyone, Latest LTS RC was made public and it is ready to be tested. Final release is scheduled for 2022-07-13. Please, report your findings in this thread. Download the release from:

Re: Security approval required on UI-related PRs in Jenkins core

Hey Wadeck, > until they have received at least one approval from someone in CERT. Could we add a "security" team with read permissions on jenkinsci/jenkins, core maintainers can request a review upon if a PR touches UI components? I'm aware that Basil (?) created a label, but GitHub honors

Re: Jenkins 2.346.1 LTS RC testing started

c32359.d78ef251ec52.war Per request of the security team and with the approval of the release officer, the final release date has been delayed by one week and is now scheduled for the 2022-06-22. ~ Alex On Wednesday, 18 May 2022 at 08:59:20 UTC+2 Alexander Brandes wrote: > Hello everyone, >

Re: Backporting for LTS 2.346.1 started

plan to merge the PR? > > The second wave of backports seems to contain important fixes, so > postponing those seems to be not really an option. > > Best regards, > > Wadeck > On Tuesday, May 31, 2022 at 8:37:24 PM UTC+2 m...@basilcrow.com wrote:

Re: Workflow approval for first time contributors

Tim > > > On Sat, 18 Jun 2022 at 08:32, Alexander Brandes > wrote: > >> Hey everyone, >> >> I would like to propose to enable workflow approval >> <https://docs.github.com/en/organizations/managing-organization-settings/disabling-or-limiting-github-actions-fo

Workflow approval for first time contributors

Hey everyone, I would like to propose to enable workflow approval for first time contributors, at

Re: Proposal: Jenkins Core PR reviewers team

Hey everyone, late reply but I would be interested in joining as well. Since I joined the release team a few months ago to take care of the last point release and the upcoming 2.346 LTS release, I moderate a bunch of core PRs by applying labels, fixing up changelog entries, PR titles or

Re: Let renovate handle dependency updates in jenkinsci/jenkins

> Is there a compelling reason to prefer Renovate for Jenkins core Java dependencies? dependabot and renovate can manage Java dependencies equally fine, the drawback for frontend deps apply here too, you get one PR each, if that is a reasonable and frequent concern (it is not from what I've

Let renovate handle dependency updates in jenkinsci/jenkins

Hey everyone, dependabot does a good job at handling single artifacts, but it does a bad to no job handling modules of monorepos, see babel -cli, -core, -env, etc. for example. This typically leads me to moving several submodule dependency update PRs into a single PR, before reviewing,

Re: Let renovate handle dependency updates in jenkinsci/jenkins

Small ammandment: The semantic commit messages on the PoC can be turned off, but are picked up, because recent (my) commits use them. On Monday, 18 July 2022 at 22:15:32 UTC+2 Alexander Brandes wrote: > Hey everyone, > > dependabot does a good job at handling single artifacts, but it d

Re: Let renovate handle dependency updates in jenkinsci/jenkins

:33 UTC+2 ga...@gavinmogan.com wrote: > I'm a big fan of renovate, so I think its a good idea, but I also > don't touch core, so have no idea what the impact would be. > > On Mon, Jul 18, 2022 at 1:19 PM Alexander Brandes > wrote: > > > > Small ammandment: The semantic c

Re: comment-ops-bot available in jenkinsci and jenkins-infra

Hey, > What if I don't want randos on the internet messing up labeling of open PRs in repos I maintain? if this is going to be installed on all repositories, https://github.com/jenkinsci/jenkins/pull/6918 should be implemented and outlined in the README how to opt out. This definitely is a

Re: maven-jellydoc-plugin and maven-stapler-plugin

+1 On Friday, 29 July 2022 at 11:00:55 UTC+2 adrien.lec...@gmail.com wrote: > it makes sense to me. +1. > > Le ven. 29 juil. 2022 à 07:48, Ullrich Hafner a > écrit : > >> +1 >> >> > Am 29.07.2022 um 00:49 schrieb Basil Crow : >> > >> > I would like to request a transfer of >> >

Re: Next LTS baseline

+1 for 2.361 It's worth to mention that 2.361 contains several regression fixes too, which you don't want to miss out. On Friday, 29 July 2022 at 18:28:32 UTC+2 m...@basilcrow.com wrote: > On Fri, Jul 29, 2022 at 3:52 AM Mark Waite wrote: > > The folders plugin will need to have a pull

Backporting for LTS 2.346.3 started

Hey everyone, Backporting for 2.346.3 has started and the RC is scheduled for 2022-07-27. Candidates: https://issues.jenkins.io/issues/?filter=12146 Fixed: https://issues.jenkins.io/issues/?jql=labels%20%3D%202.346.3-fixed Rejected:

Jenkins 2.346.3 LTS RC testing started

Hello everyone, Latest LTS RC was made public and it is ready to be tested. Final release is scheduled for 2022-08-10. Please, report your findings in this thread. Download the release from:

Re: Frontend unit tests in core

+1 for removing it. > The status quo does not seem sustainable to me. Agreed. If we want to investigated into frontend tests in the future, we should use something more maintainable, rather a bunch of standalone repositories bundling ancient or detached plugins. Could likely archive all these

Re: Release lead for 2.346.3

Hey, I'll take care of it. Best regards Alex On Friday, 15 July 2022 at 21:32:15 UTC+2 timja...@gmail.com wrote: > Hello > > Is anyone interested in being the release lead for 2.346.3? > > Planned dates can be seen on the event calendar: > https://www.jenkins.io/events/#event-calendar >

Re: New Gradle Plugin for JTE Plugin

Hey, for 1., forking to the jenkinsci organization is typically the last step if you submit a hosting request for a plugin. I would add up 2. into your hosting request

Re: [ci.jenkins.io] Replace Blue Ocean in default display URL

+1 for changing the default URL. If I'm navigating through the checks' integration on GitHub, I almost always copy the URL to remove the "/display/redirect" part to not end up on the blue ocean view. ~ Alex On Tuesday, 3 May 2022 at 11:50:31 UTC+2 damien@gmail.com wrote: > Hello dear

Re: Backporting for LTS 2.346.3 started

Sounds reasonable. If the solution causes no unforeseen regressions, I'll backport it. Thanks for adding it to the list. On Saturday, 30 July 2022 at 00:06:02 UTC+2 m...@basilcrow.com wrote: > Once verified, I think we should consider backporting > https://github.com/jenkinsci/remoting/pull/559

Re: BMC DevOps for CFA Jenkins plugin

Hey, it exists in the update center: https://updates.jenkins-ci.org/current/update-center.json There's been an issue with the update center this morning, but that's resolved by now. If you check for updates manually, Jenkins should

Re: Maintainer access to UiPath plugin

Make sure you set the desired name full name on accounts.jenkins.io and issues.jenkins.io . On Thursday, 25 August 2022 at 10:59:49 UTC+2 ganesh...@gmail.com wrote: > Thanks, Gavin! I can see the name now

Re: ASM in core

+1 for detaching On Thursday, 18 August 2022 at 08:36:25 UTC+2 timja...@gmail.com wrote: > If core no longer uses it the. Yes absolutely +1 > > On Thu, 18 Aug 2022 at 05:40, Basil Crow wrote: > >> Recent weeklies no longer consume ASM. So shall we detach it to a >> library plugin? >> >> -- >>

Re: BMC DevOps for CFA Jenkins plugin

[image: image.png] > It displays a version from two months ago > > > > > On Tue, Aug 23, 2022 at 2:26 PM Alexander Brandes > wrote: > >> Hey, >> >> it exists in the update center: >> https://updates.jenkins-ci.org/current/update-center.json >> &

Re: Proposal: Alexander Brandes (@NotMyFault) to join the Core team

;>> >>> On Saturday, October 15, 2022 at 7:58:15 PM UTC+2 >>> adrien.lec...@gmail.com wrote: >>> >>>> of course +1. >>>> >>>> >>>> Le sam. 15 oct. 2022 à 18:31, Alexander Brandes a >>>> écrit : >>>> >&

Re: Next LTS baseline selection

+1 for 2.375 On Monday, 24 October 2022 at 23:12:43 UTC+2 m...@basilcrow.com wrote: > I feel strongly that the following fixes be included in the next LTS > release: > > jenkinsci/jenkins#7208 - Fix for weather icon issue that many users > have complained about (included in the forthcoming

Re: Request for access to YouTube account

+1 On Wednesday, 26 October 2022 at 15:09:53 UTC+2 damien@gmail.com wrote: > +1 for me! > > Bruno's work on the SIG is clearly an indicator of the trust we can put. > I'm also convinced that he'll have plenty of idea to > documente/describe/improve the SIG publication process > > Le

Re: Next LTS baseline selection

As an alternative to 2.375, I'd like to bring up 2.372 as a possible candidate. 2.375 ships a (possible) issue tracked in JENKINS-69966 . 2.372 is a much less recent weekly release, with a better rating

Jenkins 2.361.3 RC testing has started

Hello everyone, Latest LTS RC was made public, and it is ready to be tested. Final release is scheduled for 2022-01-02. Please, report your findings in this thread. Download the release from:

Re: pipeline-graph-view-plugin on infra.ci.jenkins.io

+1 On Friday, 16 September 2022 at 19:40:01 UTC+2 Mark Waite wrote: > +1 from me. It's working very well on my instance. All the rendering > issues that I had seen before are resolved. > > On Friday, September 16, 2022 at 11:33:42 AM UTC-6 timja...@gmail.com > wrote: > >> +1 >> >> On Fri, 16

Re: Backporting for LTS 2.361.2 has started

Hey, thanks for your work so far! Is there a particular reason, why JENKINS-69534 was rejected? Did Basil's concern come true, and I missed the relevant Jira issue? ~ Alex On Saturday, 17 September 2022 at 09:49:52 UTC+2 kris...@outlook.com

Re: Backporting for LTS 2.361.2 has started

Hey, thanks for your work so far! Is there a particular reason, why JENKINS-69534 was rejected? The PR, that resolves the issue, has not been delivered in a weekly release yet, hence the change isn't available for backporting in the first

Re: Kevin Martens as a copy editor for jenkins.io

+1 On Thursday, 15 September 2022 at 19:28:41 UTC+2 m...@basilcrow.com wrote: > +1 > -- 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

Re: 2.361.3 release lead

I'll take care of it. BR, Alex On Thursday, 13 October 2022 at 00:03:38 UTC+2 timja...@gmail.com wrote: > Hello > > Is anyone interested in being the release lead for 2.361.3? > > Planned dates can be seen on the event calendar: > https://www.jenkins.io/events/#event-calendar > Release

Backporting for LTS 2.361.3 started

Hey everyone, Backporting for 2.361.3 has started, and the RC is scheduled for 2022-10-19. Candidates: https://issues.jenkins.io/issues/?filter=12146 Fixed: https://issues.jenkins.io/issues/?jql=labels%20%3D%202.361.3-fixed Rejected:

Re: Jenkins Wiki CSS issues

Nice work everyone, the banner is really suitable! On Thursday, 6 October 2022 at 13:09:11 UTC+2 jamie...@gmail.com wrote: > Great stuff, thanks for picking this up! > > On Thu, 6 Oct 2022, 11:52 'Herve Le Meur' via Jenkins Developers, < > jenkin...@googlegroups.com> wrote: > >> The version with

Re: Adoption Maintenance plug-in upload-pgyer-plugin

+1 Please include this thread in your Repository Permission Updater PR description. Thanks! On Tuesday, 11 October 2022 at 16:38:40 UTC+2 c5620...@qq.com wrote: > pgyer official wants to maintain the uploading-PGyer-plugin, which needs > to be updated due to the update of pgyer's official

Re: Adoption of android-emulator-plugin

+1 On Monday, 3 October 2022 at 21:39:39 UTC+2 kmar...@cloudbees.com wrote: > +1 from me too > > On Mon, Oct 3, 2022 at 1:58 PM Mark Waite wrote: > >> +1 from me >> >> On Monday, October 3, 2022 at 11:46:21 AM UTC-6 goun...@gmail.com wrote: >> >>> Hi, >>> >>> I would like to co-maintain or

Re: Hosting

Hey, I'd be up to assist with handling the RPU too. Best regards, Alex On Sunday, 9 October 2022 at 17:53:13 UTC+2 slide wrote: > I can help with that. I know the process is different from when I was > doing it before, but I can come up to speed. > > On Sat, Oct 8, 2022, 21:11 'Gavin Mogan'

Re: Hosting

2 at 9:07 AM Alexander Brandes > wrote: > >> Hey, >> >> I'd be up to assist with handling the RPU too. >> >> Best regards, >> Alex >> >> On Sunday, 9 October 2022 at 17:53:13 UTC+2 slide wrote: >> >>> I can help with that. I know

Re: Adoption Maintenance plugin basic-branch-build-strategies

The prior maintainers approved the RPU PR, we'll proceed with this adoption request. On Friday, 14 October 2022 at 10:56:38 UTC+2 jack4...@gmail.com wrote: > Hi, > > I tried to submmit PR to fix an issue, but failed to get the maintainer to > review and merge. > The has been lasted in 11

Re: Proposal: Alexander Brandes (@NotMyFault) to join the Core team

>>> +1 for me too >>>>> good luck Alexander >>>>> >>>>> On Thu, Oct 13, 2022 at 9:44 AM 'Daniel Beck' via Jenkins Developers < >>>>> jenkin...@googlegroups.com> wrote: >>>>> >>>>> >>>>>

Re: Backporting for LTS 2.346.3 started

I added the up to date RC URL to the RC announcement thread <https://groups.google.com/g/jenkinsci-dev/c/9UBVyQO69o8>, which contains the additional remoting backport. On Saturday, 30 July 2022 at 11:08:08 UTC+2 Alexander Brandes wrote: > Sounds reasonable. If the solution causes no u

Re: Jenkins 2.346.3 LTS RC testing started

ci.org/incrementals/org/jenkins-ci/main/jenkins-war/2.346.3-rc32381.b_cf1b_587a_0fc/jenkins-war-2.346.3-rc32381.b_cf1b_587a_0fc.war . Kind regards Alex On Wednesday, 27 July 2022 at 09:45:46 UTC+2 Alexander Brandes wrote: > Hello everyone, > > Latest LTS RC was made public and it is ready to b

Re: Forked repositories in GitHub

+1 on Tim's proposal. On Wednesday, 17 August 2022 at 07:48:25 UTC+2 ga...@gavinmogan.com wrote: > So it's just all the old repos at once they have issues with? They are > still okay with one off requests to fix a repo? > > I wonder if they have a private API we could use that would prevent us

Re: Cannot deploy release neither snapshot (ldap connectivity failing)

Hey, quoting Damien from #jenkins-infra, posted 2 hours ago: > For info, it looks like there is an issue around LDAP/authentication impacting JIRA, VPN, account and auth. on controllers. I'm looking. Looks like services went back to normal ~1.5 hours ago. Best, Alex On Wednesday, 28 December

Re: 2.375.3 release lead

I will take care of it. Best, Alex On Thursday, 12 January 2023 at 23:42:36 UTC+1 timja...@gmail.com wrote: > Hello > > Is anyone interested in being the release lead for 2.375.3? > > Planned dates can be seen on the event calendar: > https://www.jenkins.io/events/#event-calendar > Release

Proposal to ensure new plugin hosting requests use Maven instead of Gradle

at new plugin hosting requests use Maven, to have better toolchain support. I would be ready to lift this restriction again if the JPI plugin developers provide the same scope of tools like we have for Maven. Best, Alexander Brandes, for the hosting team -- You received this message becau

Re: Proposal to ensure new plugin hosting requests use Maven instead of Gradle

I submitted a dedicated issue <https://github.com/jenkinsci/gradle-jpi-plugin/issues/213> on the plugin's repository outlining the TODOs and linking to this discussion. On Thursday, 8 December 2022 at 21:53:36 UTC+1 db...@cloudbees.com wrote: > On Wed, Dec 7, 2022 at 11:20 AM Alexande

Re: Renaming a plugin

Hey, take a look at the RPU documentation how to do that. Best, Alex On Sunday, 18 December 2022 at 11:09:59 UTC+1 mar...@gmail.com wrote: > Hello, > > Is there a way to rename a plugin after it's already

Re: Renaming a plugin

...@cloudbees.com wrote: > On Sun, Dec 18, 2022 at 7:47 AM Alexander Brandes > wrote: > >> take a look at the RPU documentation >> <https://github.com/jenkins-infra/repository-permissions-updater/#renaming-a-plugin> >> how >> to do that. >> > > I think th

Jenkins 2.375.1 RC testing has started

Hello everyone, Latest LTS RC was made public, and it is ready to be tested. Final release is scheduled for 2022-11-30. Please, report your findings in this thread. Download the release from:

Re: Removing security vulnerability warning from CloudFormation plugin

> Please follow our guidelines when reporting vulnerabilities, please see https://www.jenkins.io/security/ for details! The CVE's details have been published more than 3 years ago, no new information has been disclosed here. Someone from the security team will need to review your PR to the

Re: Problematic releases

> Can plugins use Renovate as it is done for core? For sure, if you request the addition to your repository, someone will approve it. On Monday, 28 November 2022 at 01:48:46 UTC+1 nowak.b...@gmail.com wrote: > Can plugins use Renovate as it is done for core? Maybe it will work better? > > How

Re: Permission Request for the community Google Document "Jenkins Social Media Covers / Artwork"

+1 from me :) On Wednesday, 23 November 2022 at 12:08:51 UTC+1 damien@gmail.com wrote: > Hello there, > > Both Bruno Verachten (goun...@gmail.com) and I (damien@gmail.com) > would like to get write access to the Community Google Document named > "Jenkins > Social Media Covers /

Re: Next LTS baseline

That would make a viable candidate. The response on the recent weekly releases has been overall very positive. +1 for 2.387. Best, Alex On Tuesday, 24 January 2023 at 10:03:57 UTC+1 timja...@gmail.com wrote: > Hi all, > > It's time to select the next LTS baseline. > The best candidate right

Jenkins 2.375.3 RC testing has started

Hello everyone, Latest LTS RC was made public, and it is ready to be tested. Final release is scheduled for 2023-02-08. Please report your findings in this thread. Download the release from:

Re: Renovatebot for cctray-xml-plugin

Hey, You can request the installation on the repository you want to use renovate at, and an org admin will approve the request. If you don't see renovate doing something after 24 to 48 hours, you can file a helpdesk

Re: Removing inactive Core maintainers to reduce risk

Thanks for your ongoing efforts to make our repositories secure! > Was this decision made in concert with other core maintainers I was not aware of such a change, but I heavily endorse the cleanup :) Alex On Friday, 27 January 2023 at 16:59:41 UTC+1 m...@basilcrow.com wrote: > On Fri, Jan 27,

Backporting for LTS 2.375.3 started

Hey everyone, Backporting for 2.375.3 has started, and the RC is scheduled for 2023-01-25. Candidates: https://issues.jenkins.io/issues/?filter=12146 Fixed: https://issues.jenkins.io/issues/?jql=labels%20%3D%202.375.3-fixed Rejected:

Backporting for LTS 2.375.1 started

Hey everyone, Backporting for 2.375.1 has started, and the RC is scheduled for 2022-11-16. Candidates: https://issues.jenkins.io/issues/?filter=12146 Fixed: https://issues.jenkins.io/issues/?jql=labels%20%3D%202.375.1-fixed Rejected:

Re: 2.375.1 release lead

Hey, I'll take care of it. BR, Alex On Monday, 7 November 2022 at 12:47:25 UTC+1 timja...@gmail.com wrote: > Hello > > Is anyone interested in being the release lead for 2.375.1? > > Planned dates can be seen on the event calendar: > https://www.jenkins.io/events/#event-calendar > Release

Re: one-shot-executor-plugin

> That experiment was indeed abandoned If it's abandoned, we should archive the repository then. On Thursday, 16 March 2023 at 02:25:50 UTC+1 slide wrote: > Awesome, thanks for pointing that out! Much appreciated! > > On Wed, Mar 15, 2023, 18:24 'Jesse Glick' via Jenkins Developers < >

Jenkins 2.387.1 RC testing has started

Hello everyone, Latest LTS RC was made public, and it is ready to be tested. Final release is scheduled for 2023-03-08. Please report your findings in this thread. Download the release from:

Re: Jenkins 2.387.1 RC testing has started

Thanks, the pull request has been merged, and the commit has been backported to the stable branch. A new RC is available at https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/main/jenkins-war/2.387.1-rc33315.3b_778b_3e1c8d/jenkins-war-2.387.1-rc33315.3b_778b_3e1c8d.war On Wednesday, 22

Re: Can someone delete https://plugins.jenkins.io/packageversion/

I don't think one XSS vulnerability in a plugin with 26 installations is impactful enough to justify a suspension of the plugin. Someone may always adopt the plugin to modernize it and mitigate the vulnerability. On Monday, 20 February 2023 at 19:30:37 UTC+1 ga...@gavinmogan.com wrote: > 26

  1   2   >