suffered. Today, if a machine goes down,
we can spin it back up in an hour or two due to the consistency.
I do sympathize that our service reduction is painful. But I hope you can
understand where the Foundation (and its Infra team) is coming from. We
have vastly more projects to support today, meaning more uniformity is
required.
Sincerely,
Greg Stein,
Infrastructure Administrator, ASF
further questions or concerns, then message me. I'll take
it from here.
Thanks,
Greg Stein
Infrastructure Administrator, ASF
What is your point? ... Gavin said, "or file an INFRA ticket" ... that is
what happened.
On Wed, Feb 22, 2017 at 4:37 AM, sebb wrote:
> FTR:
> At least one build using Java 1.6 stopped working; see INFRA-13556
>
> On 19 February 2017 at 03:04, Gavin McDonald
> wrote:
> > Hi Again,
> >
> > Jenki
Infra does not supply any Mac build slaves. Volunteers/contributors can run
them, and we will happily loop them into the ASF build system.
Cheers,
-g
On Fri, Apr 21, 2017 at 3:20 AM, sospartan wrote:
> Hi all,
> Do we still have any macosx node?
> I've search this list. Last thread about 'mac'
I think it depends upon your job type, as Gavin wrote: "in terms of Maven
jobs for JDK 7"
On Wed, Jun 28, 2017 at 10:01 AM, Lukasz Lenart
wrote:
> Hi,
>
> How to understand that? It won't be possible to run a job using JDK7
> anymore, right? Even if I selected such JDK in my build, Jenkins won't
Yup. That single IP is just fine. We just spun up the master at that
address this summer, and have no plans to move it.
Cheers,
-g
On Oct 4, 2017 18:01, "Meghna Baijal" wrote:
> Thanks Gavin.
> I was not sure if a single static IP is sufficient.
>
>
>
> On Wed, Oct 4, 2017 at 3:53 PM, Gavin McD
Heya Stefan! ... I think the best approach is to open a Jira for this. I
imagine that Gavin will handle it, but the ticket will help track the work,
and add some visibility.
Just can't get away from OpenBSD, can ya? ;-)
On Fri, Jan 12, 2018 at 5:55 AM, Stefan Sperling wrote:
> Hi,
>
> I have pr
Let's go back to the start: stuff older than six months will be deleted.
What could possibly need to be retained?
Assume all jobs will be touched.
On Tue, Apr 24, 2018, 18:32 Allen Wittenauer
wrote:
>
> > On Apr 24, 2018, at 4:27 PM, Chris Lambertus wrote:
> >
> > The initial artifact list is
On Wed, Apr 25, 2018 at 9:49 AM, Allen Wittenauer
wrote:
>...
> I apologize. I took Greg’s reply as Infra’s official “Go Pound
> Sand” response to what I felt was a reasonable request for more information.
>
It was "Please stop asking ChrisL for more work. The todo work is upon
users of
uilds I think we deleted.
>
> Thanks,
> -Alex
>
>
> From: Chris Lambertus
> Reply-To:
> Date: Wednesday, April 25, 2018 at 12:04 AM
> To:
> Subject: Re: purging of old job artifacts
>
>
>
>
> On Apr 24, 2018, at 8:04 PM, Allen Wittenauer mailto:a...@ef
;. Some
disabled, some not working, etc. It seemed you were talking about jobs
rather than artifacts within them.
Cheers,
-g
> Thanks,
> -Alex
>
> On 4/26/18, 11:07 AM, "Greg Stein" wrote:
>
> Note that jobs will remain.
>
> This is only about deleting
On Thu, Apr 26, 2018, 16:42 Greg Stein wrote:
> On Thu, Apr 26, 2018, 15:06 Alex Harui wrote:
>
>> Perhaps I wasn't clear. I am not concerned about Jenkins projects being
>> removed, just the artifacts of those projects. I am trying to make two
>> points:
>&
On Thu, Apr 26, 2018 at 5:08 PM, Alex Harui
wrote:
> On 4/26/18, 2:57 PM, "Greg Stein" wrote:
> On Thu, Apr 26, 2018, 16:42 Greg Stein wrote:
>
> > On Thu, Apr 26, 2018, 15:06 Alex Harui
> wrote:
> >
> >> Perhaps I wasn't c
There has been discussion of updating the required hashes. Maybe that got
implemented on Nexus? CC'ing peeps...
On Mon, Apr 30, 2018, 13:17 Emmanuel Lécharny wrote:
> Hi guys,
>
> yesterday, I tried to cut a release of Apache Directory LDAP API 1.0.1.
> It went well, but never hit Nexus.
>
> Tod
ache, of course. The
restriction merely applies to any compatibility/historical shims that are
retained, to map the old-named packages over to new org.apache naming.
Regards,
Greg Stein
Infrastructure Administrator, ASF
On Tue, May 8, 2018 at 12:15 PM, Brian Fox wrote:
> Was there discussion somewher
rojects remain within the culling
period.
Regards,
Greg Stein
InfraAdmin, ASF
On Mon, Jul 23, 2018 at 2:45 AM Gavin McDonald
wrote:
> HI All,
>
> I'd like to ask a basic question.
>
> Is there any reason at all to keep the 'workspace' dirs of builds on the
>
On Mon, Jul 23, 2018 at 7:42 PM Alex Harui wrote:
> Hi Greg,
>
> Thanks for the background. I assume that adding more disk space is
> cost-prohibitive?
>
Most of our Jenkins nodes are donated to us, so we want to use their
generous contributions as best we can.
What would happen if builds.a.o
On Wed, Jul 25, 2018 at 2:36 AM Robert Munteanu wrote:
> Hi,
>
> On Wed, 2018-07-25 at 09:27 +1000, Gav wrote:
> > Disk space issues , yes, not on most of the Hadoop and related
> > projects
> > nodes - H0-H12 do not have disk space issues. As a Hadoop related
> > project
> > HBase should really
We're refining our monitoring and some cron jobs to try and keep the disk
space pruned. But when space balloons due to poor cleanup, there is only so
much we can do.
The short answer is that the multitude of groups at the Foundation using
these shared resources need to be cognizant of that fact, a
Oh, and I'm not trying to avoid your question about auto-removal. I don't
have that answer, and will leave it for others.
On Sun, Sep 30, 2018 at 11:22 PM Greg Stein wrote:
> We're refining our monitoring and some cron jobs to try and keep the disk
> space pruned. But when
The restart was performed, and (yay!) the build history issues were fixed.
Onwards,
-g
On Sat, Oct 6, 2018 at 6:14 PM Chris Lambertus wrote:
> All,
>
> Jenkins will be restarted on Sun Oct 7th 2300 hours to address some
> inconsistent build history issues.
>
> -Chris
> ASF Infra
>
>
bers for our 100 repositories." Alrighty then.
We shall look to other communities to reduce the amount of shared disk
usage.
Regards,
Greg Stein
InfraAdmin, ASF
On Sun, Jan 6, 2019 at 10:20 PM Alex Harui wrote:
>...
> All commits, even PR's from non-commiters accepted by a committer are
> supposed to be reviewed, AIUI. So if the bot makes a commit to the repo,
> the PMC is responsible for reviewing it. In Royale's case, the bot should
> only be changin
On Mon, Jan 7, 2019 at 8:39 AM stephen.alan.conno...@gmail.com <
stephen.alan.conno...@gmail.com> wrote:
> On 2019/01/07 14:35:08, Greg Stein wrote:
> > On Sun, Jan 6, 2019 at 10:20 PM Alex Harui
> wrote:
> > >...
> >
> > > All commits, even PR's
On Mon, Jan 7, 2019 at 12:23 PM Alex Harui wrote:
>...
> I still don't get why allowing a bot to commit to a Git repo isn't
> auditable. The changes should all be text and sent to commits@ and the
> RMs job is to verify that those commits are ok before putting the artifacts
> up for vote. I'd e
On Wed, Jan 9, 2019 at 2:12 AM Alex Harui wrote:
> Here's my current summary:
>
> I think at least 3 projects are interested in sharing a computer to build
> all or some of their release artifacts.
>
> I don't know who actually wears an Infra hat other than Greg, but his
> response was maybe.
>
On Thu, Jan 10, 2019 at 4:58 AM Dominik Psenner wrote:
> On 2019-01-10 11:49, Stephen Connolly wrote:
> > That would meen, though, that the PMC would need to re-encrypt the file
> > every time the PMC changes or any time a PMC member loses their GPG key
> >
> > Note to self: e.g. see
> >
> http:/
f,
and/or can recommend a similar type of outsourced build service ... we
*absolutely* would welcome pointers.
We're gonna keep Jenkins and buildbot around for the foreseeable future,
and are interested in outsourced solutions.
Cheers,
Greg Stein
Infrastructure Administrator, ASF
ss any
possible options here. Thanks!
Regards,
Greg Stein
Infrastructure Administrator, ASF
On Wed, Jul 3, 2019 at 2:55 AM Jarek Potiuk
wrote:
> I spoke to Kamil - Gitlab CI maintainer (in CC:) and he will speak to CEO
> of GitLab and Product Managers of GitLab CI whether GitLab will be will
On Wed, Jul 3, 2019 at 11:36 AM Allen Wittenauer
wrote:
>...
> > CouchDB keeps receiving a lot of pressure to build on aarch64, ppc64le
> > and s390x, which keeps pushing us back to Jenkins CI (ASF or
> > independent). And if we have to do that, then not much else matters to
> us.
>
> One
: 96k
airflow: 77k
... others: less than 50k
I don't know what would be needed from Infra, to enable the use of Gitlab
CI for our projects. ??
Thanks,
Greg Stein
Infrastructure Administrator, ASF
On Tue, Jul 16, 2019 at 7:27 PM Raymond Paik
wrote:
> Joan,
>
> The 50,000 minutes would
ou can always run your tests locally, to prepare for your upcoming
release. The Foundation's paid resources need to remain shared/available
for all of our projects.
Regards,
Greg Stein
Infrastructure Administrator, ASF
t;
Should be possible. Again, comes back to groups trying this and reporting
back how well it went.
Cheers,
Greg Stein
Infrastructure Administrator, ASF
On Sun, Aug 11, 2019 at 5:39 PM Francis Chuang
wrote:
> Hi Greg,
>
> Should we/are we allowed to use Github Actions for ASF projects on
> Github right now? Do we need permission from infra or ASF itself?
>
Try it. We don't know if/what barriers might exist.
Infra's position is that we want to e
b.com/apache/maven-dependency-plugin/runs/192633340
> [2]:
>
> https://github.com/apache/maven-dependency-plugin/blob/66435b225e7885f44b25207e025469f6d5237107/.github/workflows/maven.yml
>
> On 12.08.19 00:31, Greg Stein wrote:
> > On Sun, Aug 11, 2019 at 5:15 PM Francis Chuang &g
in Github Actions and
> there is currently no clear process as to whether this is allowed or how
> to get this done.
>
> See:
> https://issues.apache.org/jira/browse/INFRA-18874
> https://issues.apache.org/jira/browse/INFRA-18875
>
> Francis
>
> On 27/08/2019 7:52 pm, Greg S
pre-verified code
> that executes something with that secret. Otherwise, there’s literally
> infinite ways to leak it being a Turing machine and all. This applies to
> all CICD tools.
>
> On Tue, Aug 27, 2019 at 20:32, Greg Stein wrote:
>
> > Hi Francis,
> >
> > Is t
x,
-g
On Sun, Aug 11, 2019 at 5:31 PM Greg Stein wrote:
> On Sun, Aug 11, 2019 at 5:15 PM Francis Chuang
> wrote:
> >...
>
>> I think there are quite a few ASF projects using gitbox and Github and
>> this would be a very good complement or replacement for Travis, appvo
On Mon, Feb 3, 2020 at 9:29 PM Alex Harui wrote:
> Hopefully last set of questions for now...
>
> 1) It sounds like there is a risk that as the ASF grows, GH may not be
> able to grow with us. Did I understand that correctly?
>
GitHub will always grow faster than us. Not a worry.
> 2) If we h
Can't use that private Jenkins Master ... go back to the shared master and
the git-websites node, in order to push websites.
Cheers,
-g
On Sat, Apr 25, 2020 at 7:36 AM Mick Semb Wever wrote:
> I'm trying to figure out how to git push, using the jenkins user, a
> website build on ci-cassandra.ap
Hey Vladimir ... those are Jenkins Masters for the build clusters.
On Sat, Aug 1, 2020, 11:42 Vladimir Sitnikov
wrote:
> > ci-builds.apache.org - The replacement Master for builds.apache.org
>
> I'm new to CloudBees. Could you please clarify what "Master" means in this
> context?
>
> Vladimir
>
This is some great news, Jarek.
Given that GitHub build minutes are shared, we need more of this kind of
work from our many communities.
Thanks,
Greg
InfraAdmin, ASF
On Sun, Oct 18, 2020 at 2:32 PM Jarek Potiuk
wrote:
> Hello Allen,
>
> I'd really love to give a try to Yetus - how it can actu
This is a cross-project mailing list, by definition. There are always going
to be posts specific to singular communities.
The goal is to bring these multiple communities together around
build-related issues. Maybe one post, on a Tuesday in May, will help
another community with their problems. That
in August ... not something we want.
By constraining all Actions to the apache/ repositories will ensure that
appropriate review is possible.
Regards,
Greg Stein
InfraAdmin, ASF
On Sun, Dec 27, 2020 at 6:43 AM Jarek Potiuk wrote:
> Ok. IT works after logging. I will make another comments
On Sun, Dec 27, 2020 at 6:54 AM Jarek Potiuk
wrote:
>...
> Was it as a response to some security incident that would justify such
> immediate and disruptive action without an earlier warning? What was the
> reasoning behind this?
>
Yes.
is
> reasonable), it could have been acted on before I think, and without such
> rush.
>
> J.
>
>
> On Sun, Dec 27, 2020 at 1:57 PM Greg Stein wrote:
>
>> On Sun, Dec 27, 2020 at 6:54 AM Jarek Potiuk
>> wrote:
>> >...
>>
>>> Was it as a
On Sun, Dec 27, 2020 at 11:29 AM Jarek Potiuk
wrote:
> For the records - I also looked up the discussion we had about the
> Github Action issues
>
> That was a discussion on 7th of October on priv...@airflow.apache.org
> (for those who have access there - here is the link:
> https://lists.apache.
On Tue, Dec 29, 2020 at 2:30 PM Jarek Potiuk
wrote:
>...
> On Tue, Dec 29, 2020 at 2:12 PM Vladimir Sitnikov <
> sitnikov.vladi...@gmail.com> wrote:
>
>...
> Jarek>This is exactly what Greg is writing about
> >
> > Greg's message was very vague, so I asked for clarification.
>
> I hope my explan
On Tue, Dec 29, 2020 at 8:08 PM Brennan Ashton
wrote:
> On Tue, Dec 29, 2020 at 5:33 PM Greg Stein wrote:
> > One of things that we will likely do is perform a scan of any
> > Action/workflow .yml at commit time, to ensure that any "uses:" is
> defined
> > w
[offtopic, pet peeve]
On Wed, Jan 13, 2021 at 2:47 AM Jarek Potiuk wrote:
> One of PMCs @Airflow (in ASIA timezone) asked if the meeting can be
Apache Airflow is a PMC. That Committee has *members* that are part of that
committee. Those members are NOT "PMCs". We have about 200 PMCs at the
Fou
On Wed, Apr 7, 2021 at 12:25 AM Hyukjin Kwon wrote:
> Hi all,
>
> I am an Apache Spark PMC,
You are a member of the Apache Spark PMC. You are *not* a PMC. Please stop
with that terminology. The Foundation has about 200 PMCs, and you are a
member of one of them. You are NOT a "PMC" .. you're a p
What timing! ci2 is on 2.something, but before asking a bunch of projects
to move onto it, we had already planned to upgrade it this coming weekend!
Gavin can provide.orr details, if needed, or simply send an email with the
upgrade results.
Cheers,
Greg
InfraAdmin, ASF
On Wed, Jun 23, 2021, 13:4
ll not touch it.
We *did* need to touch the CMS areas for organizational needs,
self-imposed. But repos/asf/nutch/ is all yours. Carry on!
Cheers,
Greg Stein
InfraAdmin, ASF
does
not want this tool, once we get it debugged.
Regards,
Greg Stein
Infrastructure Administrator, ASF
On Fri, Dec 9, 2022 at 9:05 AM Slawomir Jaranowski
wrote:
>...
> There is no discussion on dev@maven, private@maven ... for a simple reason
> - nobody from the Maven team knows that you want to introduce such
> features.
>
Olivier said the Maven PMC didn't want this. He can't take their name lik
On Fri, Dec 9, 2022 at 9:54 AM Allen Wittenauer wrote:
> > On Dec 9, 2022, at 7:43 AM, Greg Stein wrote:
> >
> > We make changes to the Jenkins environment all the time, to keep it
> > operational, on the latest software, to provide enough CPU and disk space
>
On Fri, Dec 9, 2022 at 7:41 PM Olivier Lamy wrote:
> On Sat, 10 Dec 2022 at 00:48, Greg Stein wrote:
> >> On Fri, Dec 9, 2022 at 5:41 AM Olivier Lamy wrote:
> >>
> >> Hi
> >> Are we seriously activating this gradle enterprise to every build and
> &g
Hey Jarek ... note that we have an infrastructure-actions repository for
"official ASF" GH Actions. If you agree with that approach, then you can
dev/test there or we can move your tested Action there when you're ready to
share it with others.
Cheers,
Greg
InfraAdmin, ASF
On Thu, Jun 20, 2024 at
58 matches
Mail list logo
