On Wed, Mar 23, 2022 at 3:46 PM Bryan Stopp wrote:
> I don't suppose there's any way to control the detailed output from a
> config in my project? For example, drop all the 1.x installs?
No. People have those versions installed and report them as such.
The filters that exist attempt to filter
The Jenkins governance board meeting will start at 9:00 PM UTC today.
Agenda items include:
-
News
-
Jenkins 2.332.2-rc build is ready to test
-
Expense approvals for security team
-
Does meeting time need to adjust again because of daylight
Hello everyone,
Latest LTS RC was made public and it is ready to be tested. Final release
is scheduled for 2021-04-06.
Please, report your findings in this thread.
Download the release from:
I don't suppose there's any way to control the detailed output from a
config in my project? For example, drop all the 1.x installs?
-Stopp
On Wednesday, March 23, 2022 at 9:27:15 AM UTC-5 Bryan Stopp wrote:
> Thanks! When i sent the question it still wasn't showing. Now i see it.
>
> Very much
Thanks! When i sent the question it still wasn't showing. Now i see it.
Very much appreciated!
On Tuesday, March 15, 2022 at 3:46:36 PM UTC-5 timja...@gmail.com wrote:
> Hi
>
> The stats look accurate to me.
> I cherry-picked the PR to fix the Html into the gh-pages branch as looks
> like it's
Hello dear contributors and maintainers,
The service repo.jenkins-ci.org (JFrog Artifactory Service) is currently
really slow, which leads to slow builds or worse: failed builds due to
timeouts.
We are tracking it in https://github.com/jenkins-infra/helpdesk/issues/2849
for more informations
Hi all again,
I created the backport PRs:
- https://github.com/jenkinsci/jenkins/pull/6401
- https://github.com/jenkinsci/packaging/pull/299
Currently waiting for reviews and ATH results to merge it. Status of the
release updated in: https://github.com/jenkins-infra/release/issues/225
I will
Thanks Basil,
I would definitely be interested in publishing the syslog-java-client
library to Maven Central from non Jenkins project to easily consume the
library.
My understanding of the Sonatype OSS publishing process is that one can
only publish on a groupId he is legitimate for which
Backporting has started and the RC is scheduled for 2022-03-23
Candidates: https://issues.jenkins-ci.org/issues/?filter=12146
Fixed:
https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.332.2-fixed
Rejected:
https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.332.2-rejected
--
For everyone, to give data about why I started this discussion:
- we have 66 opens pull-requests, 5 of them are marked as ready-for-merge
- 10 out of 61 pull-requests are labeled proposed-for-close
- of the 10 oldest open pull-requests, 7 are labels proposed-for-close
- the 17 oldest open
Hi all, I will take this :-)
Best,
Ildefonso
On Wed, Mar 23, 2022 at 9:46 AM Tim Jacomb wrote:
> Hello
>
> Is anyone interested in being the release lead for 2.332.2?
>
> Planned dates can be seen on the event calendar:
> https://www.jenkins.io/events/#event-calendar
> Release candidate by
No worries Tim.
Thank you!
On Wed, Mar 23, 2022 at 9:44 AM Tim Jacomb wrote:
> I normally set up the dates some months in advance and they ran out and I
> forgot is all.
>
> Calendar dates are set-up now till June
>
> On Tue, 22 Mar 2022 at 21:43, 'Gavin Mogan' via Jenkins Developers <
>
Hello
Is anyone interested in being the release lead for 2.332.2?
Planned dates can be seen on the event calendar:
https://www.jenkins.io/events/#event-calendar
Release candidate by 23rd March (no worries if not possible can stretch a
few days, my mistake for being late)
Release on 6th April
I normally set up the dates some months in advance and they ran out and I
forgot is all.
Calendar dates are set-up now till June
On Tue, 22 Mar 2022 at 21:43, 'Gavin Mogan' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:
> Nothing about release dates was in governance that I
Alex, I agree that we have the list of labels but even for
`ready-for-merge`, we haven't document there what we tend to say when we
put the label: the pr should be merge within 24hr (with no negative
feedback). It is important that we have a clear guideline, like
> * If you do not get feedback
15 matches
Mail list logo
