Re: Persistent cache for Buildbot Pelican builds

> On Feb 13, 2024, at 6:08 PM, Dave Fisher wrote: > > > >> On Feb 13, 2024, at 2:49 PM, sebb wrote: >> >> On Tue, 13 Feb 2024 at 20:21, Dave Fisher wrote: >>> >>> One way that could work is to put a cache into a branch of the repository … >>> >>> It could double as a data cache. >> >>

new jenkins websites node

Hi folks, We added a new websites build node which is running Ubuntu 22.04. Please let us know if you run into any problems building on websites3. -Chris ASF Infra

new nodes

Hi folks, Y! has provided us with some updated build nodes. Nodes asf951-asf960 replace the following nodes: asf900-910 (asf900, asf901, asf902, asf904, asf905, asf906, asf909, asf910) asf944-950 (asf944, asf945, asf946, asf947, asf948, asf949, asf950) The new nodes map to hadoop51-55 and

[DOWNTIME] Correction: Nexus outage begins Monday 13 March 0200 UTC

> On Mar 9, 2023, at 5:14 PM, Chris Lambertus wrote: > > > All, > > The ASF Nexus server repository.apache.org <http://repository.apache.org/> > will be taken down for a prolonged outage beginning Sunday 12 March at 0200 > UTC and completing approximately 14 h

[DOWNTIME] - repository.apache.org (Nexus) - 12 March 0200 UTC to 13 March 1600 UTC

All, The ASF Nexus server repository.apache.org will be taken down for a prolonged outage beginning Sunday 12 March at 0200 UTC and completing approximately 14 hours later, at 1600 UTC Monday 13 March, while it is migrated to new hardware. The current system is

Re: Detecting errors in Buildbot

> On Jan 4, 2023, at 4:03 AM, sebb wrote: > > The www-site builds failed recently, however this was not obvious > because the failures don't appear to have been reported anywhere > outside the dashboard. > > As I recall, the previous version of BuildBot would send an email for > broken (and

Re: ci2 / buildbot notifications

> On Aug 30, 2022, at 8:19 AM, Mark Thomas wrote: > > Hi, > > The Tomcat project migrated to ci2 a while ago. Since the migration, the > Tomcat dev list no longer receives notifications of either failed or fixed > builds. > > I have checked the buildbot configuration and I can't see

Re: Hardware issues on ci-builds

is unstable (seems to have a memory controller error.) We will most likely be replacing it over the weekend. > On Jun 23, 2022, at 3:34 PM, Chris Lambertus wrote: > > The replacement hardware has been deployed, and we are in the process of > synchronizing the 2.1TB of build dat

Re: Hardware issues on ci-builds

The replacement hardware has been deployed, and we are in the process of synchronizing the 2.1TB of build data to the new system. ETR is 24-48 hours. -fluxo > On Jun 23, 2022, at 11:57 AM, Chris Wells wrote: > > We are in the process of rebuilding ci-builds.a.o and migrating data to a new >

Re: ephemeral builds via AWS ECS and/or EKS? GPU Nodes?

with specific services in need > for a project? > > Thanks and Regards, > Janardhan > > On Sat, Jan 1, 2022 at 12:19 AM Allen Wittenauer > wrote: >> >> >> >>> On Dec 30, 2021, at 10:58 AM, Chris Lambertus wrote: >>> >>>

Re: dockerhub limitations - maximum user count reached

; (semi-automatically using the same scripts as are used on CI) and push them > from there (I actually plan to sign those images very soon too with private > keys). > > > J > > > On Fri, Jan 21, 2022 at 5:57 PM Chris Lambertus wrote: > >> Hi folks, >> &g

dockerhub limitations - maximum user count reached

Hi folks, We have reached our 200 seat maximum for dockerhub users in the Apache organization, and Docker Hub is unable to provide any activity records for those users, so we do not know who to cull. Do we have any internal contacts amongst the list at DockerHub who might be able to assist?

ephemeral builds via AWS ECS and/or EKS? GPU Nodes?

Hi folks, We have some funding to explore providing ephemeral builds via ECS or EKS in the Amazon ecosystem, but Infra does not have expertise in this area. We would like to integrate such a service with Jenkins. Does anyone have experience with using these services for CI, and would you be

Re: Pushing Docker Images

> On Nov 17, 2021, at 10:22 AM, Allen Wittenauer > wrote: > > > >> On Nov 17, 2021, at 4:17 AM, Martin Grigorov wrote: >> >>> - In my trials this morning, building both amd64 and arm64 took >>> ~1h. That’s at least better than my M1 Max MBP which never completed after >>> several

Re: Nexus' Apache-rules fail on missing md5/sha1

Since SHA1/MD5 are deprecated and no longer supported by the policy[1], it seems like they should be removed from Nexus as a requirement, replaced instead by a requirement for SHA256|512 I'm not sure exactly how to go about doing this, but please open an Infra jira ticket and we can look into

docker login

It has come to Infra's attention that projects are using 'docker login' in Jenkins jobs. This has the effect of exposing your cleartext credentials in ~jenkins/.docker/config.json, and blocking any other projects from using docker on whatever node your jobs runs on. Please stop doing this.

Re: Dependabot-like solution for Apache projects

pts this without problem so I guess >>>> we have a similar level of source management. >>>> >>>> >>>> >>>> On Wed, 1 Sept 2021 at 05:33, Gary Gregory >>> wrote: >>>> >>>>> I am missing somethin

Re: Dependabot-like solution for Apache projects

Third party write access to code repositories is expressly forbidden by Foundation policy: https://infra.apache.org/repository-access.html Infra has worked with GitHub to prevent dependabot from being able to write to our repos, but it

Re: Dependabot-like solution for Apache projects

We still do not allow dependabot to write to repos. There is a way to receive the dependabot alerts via email, but no write access to the repo. > On Aug 30, 2021, at 9:50 AM, Jarek Potiuk wrote: > > I believe that changed when Github bought dependabot and it become > "embedded" in GitHub

Re: Migration from travis-ci.org to travis-ci.com

You haven't specified any specific repo so I can only guess that you need to add a .travis.yml file, as described in the travis documentation. > On Aug 15, 2021, at 5:21 PM, sebb wrote: > > PING? > > On Sat, 7 Aug 2021 at 17:28, sebb wrote: >> >> Whimsy is still using travis-ci.org, but

ci-builds crash/reboot notice

Hi folks, FYI - ci-builds Jenkins UI crashed and was restarted 27 May 2325 UTC. It is in the process of coming back up. -Chris ASF Infra

Re: ci-builds.apache.org offline - network issue

for at least another 24 hours. We’ll provide another update as soon as possible within that timeframe. -Chris ASF Infra > On Feb 18, 2021, at 11:09 AM, Chris Lambertus wrote: > > On Wednesday 18 Feb approximately 1800 hours UTC, Infra was notified that the > ci-builds Jenkins service was

Re: ci-builds.apache.org offline - network issue

On Wednesday 18 Feb approximately 1800 hours UTC, Infra was notified that the ci-builds Jenkins service was offline. We contacted our service provider, and they restarted the system. After this restart, Infra started receiving notifications of missing job configurations. Upon beginning the

ci-builds.apache.org offline - network issue

Hi, ci-builds.apache.org is currently offline due to some kind of network issue. I’ve opened a support ticket with our hosting provider.

Re: GA again unreasonably slow (again)

> On Feb 8, 2021, at 1:51 PM, Jarek Potiuk wrote: > > This uses https://github.com/actions/runner/pull/783 to not have > un-trusted users run code (security is based on the actors of the commit - > commiter’s PRs and direct pushes are allowed to run builds on self-hosted > runners) on our

Re: Using GitHub Actions for Apache Hudi repo

> On Jan 23, 2021, at 10:15 PM, Jarek Potiuk wrote: > Let me explain then what I see as the current state of Github Actions. > > And note to Infra: > > If you think it might be helpful, I am happy to Capture it all as a Wiki page > - with your comments and such - so that other projects have

Re: ASF Jenkins usability [Was: Re: GA again unreasonably slow (again)]

> On Jan 8, 2021, at 1:45 PM, Zach Hoffman wrote:\ > Since running on all forks is not an option with Jenkins, that's where my > preference comes from. Jenkins is still useful for jobs that don't need to > run on forks, (e.g., periodically checking for Go version updates and > opening a PR

Re: ASF Jenkins usability [Was: Re: GA again unreasonably slow (again)]

> On Jan 8, 2021, at 1:33 PM, Jarek Potiuk wrote: > > We moved to GA when we had exactly the same troubles with > Apache-organisation run Travis. more than a year ago we got in very much > the same situation and GA seemed like an easy win for us. The ASF does not run Travis. We pay a large

ASF Jenkins usability [Was: Re: GA again unreasonably slow (again)]

> On Jan 8, 2021, at 12:11 PM, Kamil Breguła wrote: > I would be happy if we could get a tip on what we can do next to improve > our CI as well as keep our community happy. Is there any solution that > complies with the Apache policy and is more stable? In Airflow, we've > already tried

Re: Summary of builds meeting Wed 4th Nov 2020

> On Nov 25, 2020, at 1:06 PM, Robert Munteanu wrote: > > Hi, > > On Wed, 2020-11-25 at 20:30 +0100, Gavin McDonald wrote: >> Chris Lambertus <https://cwiki.apache.org/confluence/display/~cml> >> asked >> for interest in setting up a K8s cluster of nod

Re: Builds related Meeting

Thanks for the offer, we'd love to take you up on that. We'd be looking at a K8s proof of concept deployment in AWS. Cloudbees has also offered some expertise in getting us set up on the Jenkins side. Some questions: - can I get a show of hands as to which project(s) in general would be

Re: Hung website job

Try directing your git checkouts to github. There are some circumstances when gitbox becomes overloaded, let's see if the problem goes away with github. > On Nov 2, 2020, at 1:21 PM, Zoran Regvart wrote: > > Seems that this has happened again with this job: > >

Re: Docker rate limits likely spell DOOM for any Apache project CI workflow relying on Docker Hub

problems entirely. > > Even without such "default" access, we could add a simple Action that could > automatically assign the right access to such uploaded Images - I already > wrote a few of those - happy to write another one. > > J. > > > > On Thu

Re: Docker rate limits likely spell DOOM for any Apache project CI workflow relying on Docker Hub

> On Oct 28, 2020, at 11:47 PM, Allen Wittenauer > wrote: > > > >> On Oct 28, 2020, at 9:01 PM, Joan Touzet wrote: >> >> Even for those of us lucky enough to have sponsorship for dedicated CI >> workers, it's still a problem. Infra has scripts to wipe all >> not-currently-in-use Docker

Re: Docker rate limits likely spell DOOM for any Apache project CI workflow relying on Docker Hub

Hi Joan, I’m adding CC: vp-infra for visibility. The reason Infra aggressively prunes docker cache on the build nodes is that projects generally do not clean up after their builds, and run the nodes out of space with infinite docker images. Our donated general purpose build hardware resources

Re: [ci-builds] GitHub credentials

> On Aug 14, 2020, at 4:01 PM, Richard Eckart de Castilho > wrote: > > Hi, > >> On 30. Jul 2020, at 05:42, Chris Lambertus wrote: >> >> There is no policy per-se, we have done this in the past, specifically for >> repo:status tokens; &g

Re: [ci-builds] GitHub credentials

> On Jul 30, 2020, at 1:50 PM, Zoran Regvart wrote: > > Hi Chris, > > On Thu, Jul 30, 2020 at 5:42 AM Chris Lambertus wrote: >> Please create an infra jira ticket. Unfortunately, it’s an extremely manual >> process on our end, and requires Infra to cre

Re: [ci-builds] GitHub credentials

There is no policy per-se, we have done this in the past, specifically for repo:status tokens; INFRA-19879 INFRA-20042 Please create an infra jira ticket. Unfortunately, it’s an extremely manual process on our end, and requires Infra to create and maintain an account and password+token for

several H nodes down

Infra is aware that a number of the jenkins H nodes are down. We are working with our upstream provider on getting these back online.

Re: DNS issue on build nodes

> On May 15, 2020, at 7:59 PM, Chris Lambertus wrote: > > All, > > Infra is investigating problems with DNS on the build nodes. > The DNS issue (which also affected docker) should be fixed now. -Chris

DNS issue on build nodes

All, Infra is investigating problems with DNS on the build nodes.

Re: docker permissions on websites node

e host (and having to manually > ssh into Jenkins machines to clear these files as root). > > On 2020/04/10 19:22:57, Chris Lambertus wrote: >> All,> >> >> Infra has implemented some permissions changes to the docker installation > on the websites node, and all cont

Re: Website publishing Jenkins job using Docker issue

Please see my post to this list from last week regarding this issue and the fix: https://lists.apache.org/thread.html/r00c669dd82bbde47958e81ecb330116de131d774e2d4df26a06fe92f%40

docker permissions on websites node

All, Infra has implemented some permissions changes to the docker installation on the websites node, and all containers now map to the jenkins UID on the host. If you have specified a UID on the command line previously to avoid permissions issues, your build may now be broken. Please remove

jenkins restart - 2300UTC 31 Mar

Hi all, We will be restarting Jenkins tonight at 2300UTC (31 March.) This restart should allow our nodes to pick up increased heap allocations in the hopes to address some ongoing chronic issues with certain types of operations (similar to issues as reported in INFRA-20025.) -Chris

Re: broken builds taking up resources

> On Jan 28, 2020, at 8:22 PM, Allen Wittenauer > wrote: [snip] > [1] - The best on-prem solution I came up with (before I moved my $DAYJOB > stuff to cloud) was to run each executor in a VM on the box. That VM would > also have a regularly scheduled job that would cause it to wipe

Re: broken builds taking up resources

> On Jan 27, 2020, at 10:52 PM, Allen Wittenauer > wrote: > > > >> On Jan 27, 2020, at 6:37 PM, Andriy Redko wrote: >> >> Thanks a lot for looking into it. From the CXF perspective, I have seen that >> many CXF builds have been aborted >> because of the connection with master is lost

Re: broken builds taking up resources

-Dmaven.repo.local=/home/jenkins/jenkins-slave/workspace/CXF-Master-JDK11/.repository -U -B clean install -Dmaven.test.skip.exec=true -Pnochecks asf999 59270 0.0 0.0 16576 2088 pts/0S+ 05:39 0:00 grep --color=auto CXF > On Jan 26, 2020, at 7:06 PM, Chris Lambertus wrote: >

Re: broken builds taking up resources

Here is some data from H24, which also contains many broken CXF jobs (not Karaf) from Jan 22. The builds on H41 use karaf artifacts, but they were CXF builds, not karaf builds as previously noted. Copying dev@CXF since this build seems to be related to ongoing node problems. Additionally,

Re: broken builds taking up resources

> On Jan 22, 2020, at 4:55 PM, Chris Lambertus wrote: > > Folks, > > Over the last week or so we have received many reports of broken builds due > to nodes out of resources. As noted in INFRA-19751, builds appear to fail yet > continue to run, using up all available

broken builds taking up resources

Folks, Over the last week or so we have received many reports of broken builds due to nodes out of resources. As noted in INFRA-19751, builds appear to fail yet continue to run, using up all available resources on a build node. I will be implementing a system to kill jenkins processes based on

Re: Node H29 (not H23) insufficient memory - not really, more likely out of threads?

H29 has been restarted. > On Jan 17, 2020, at 12:53 PM, Marshall Schor wrote: > > oops, the runs are on H29, not H23, the H23 just left over from the subject > thread. > > -Marshall > > On 1/17/2020 3:40 PM, Chris Lambertus wrote: >> As far as I can tell, H

Re: Node H23 insufficient memory

As far as I can tell, H23 is working normally, builds are running normally since the reboot to clear up issues a couple days ago. > On Jan 17, 2020, at 12:34 PM, Marshall Schor wrote: > > Today, my github pull request Jenkins jobs are continually failing with > messages > similar to this -

jenkins restart approx 1730UTC

All, Jenkins will be restarted at approximately 1730UTC today to troubleshoot problems with github status checks and phantom builds of deleted jobs. -Chris

Re: maven-site job stuck on jenkins

> Hervé > > Le dimanche 29 septembre 2019, 23:29:55 CEST Chris Lambertus a écrit : >> Hi Maven folks, >> >> The following build >> https://builds.apache.org/job/maven-box/job/maven-site/job/MNG-6432/ >> <https://builds.apache.org/job/maven-box/job/maven-site

maven-site job stuck on jenkins

Hi Maven folks, The following build https://builds.apache.org/job/maven-box/job/maven-site/job/MNG-6432/ has been hung for some time due to the fact that it is using the incorrect label for the website builder node. The

Re: temporarily disabled GHPRB on trafficcontrol-PR job

>> On Sep 29, 2019, at 10:37 AM, Chris Lambertus wrote: >> >> >> Hi Traffic Control folks. >> >> We are troubleshooting an issue with Jenkins and we noticed something >> strange with your PR builder— jenkins is iterating over thousands of PRs

Re: temporarily disabled GHPRB on trafficcontrol-PR job

Oops, removing misaddressed private@infra for builds@a.o <mailto:builds@a.o>. This is a public message. > On Sep 29, 2019, at 10:37 AM, Chris Lambertus wrote: > > > Hi Traffic Control folks. > > We are troubleshooting an issue with Jenkins and we noticed something

Re: OutOfMemory on Jenkins Slave H37

I rebooted the machine, but it didn’t come back up. Waiting on the colo to take a look at it. > On Sep 24, 2019, at 7:36 AM, Enrico Olivelli wrote: > > Hello, > I see this OutOfMemoryError on H37, can you please take a look ? > >

DNS failures on build systems

All, The tickets regarding DNS failures on Jenkins nodes are due to a problem which turns out to be that a combination of a new docker install and a broken regex in the tool that assigns a resolv.conf based on colo, which in turn caused an incorrect nameserver to be written to resolv.conf.

Re: Fw: website build broken

Have you tried recently? There were some missing dependencies that I think were added last week. On Jul 15, 2019, 13:17, at 13:17, Matt Rutkowski wrote: >For greater context, the comprehensive Jenkins build page for our >website >is here:

Re: website build broken

I’ve added the npm package to the puppet config, it should get automatically installed in ~30 minutes or so. > On Jul 9, 2019, at 11:52 AM, Matt Rutkowski wrote: > > Apache build team, > > It appears that recently that our Jenkins jobs for building and publishing > our project website for

Jdk9 issues

All, We have received a number of tickets related to jdk9 and the libjli problem. I’m not sure exactly what the issue is, and we don’t have a solution yet, but I notice that JDK9 was EOL over a year ago. I suppose it goes without saying that the Java ecosystem is undergoing some changes wrt to

Re: jdk 13 missing on jenkins

> On Jun 15, 2019, at 1:00 PM, Tilman Hausherr wrote: > > Since a few hours ago, I get this with PDFBox builds using jdk13 (this is > done at most once a day to see whether any builds fail while new jdk13 ea > releases are coming), other build jobs work fine: I just pushed a fix, it

Re: ACTION REQUIRED: disk space on jenkins master nearly full

t; Is it possible that maybe Jenkins failed to cleanup these, for some > reason? In any case, please go ahead and remove those directories. > > Matteo > -- > Matteo Merli > > > On Mon, Jun 10, 2019 at 2:29 PM Chris Lambertus wrote: >> >> Matteo, >> >> pu

Re: ACTION REQUIRED: disk space on jenkins master nearly full

the size of your retained builds, please let me know. I have added some additional project dev lists to the CC as I would like to hear back from everyone on this list as to the state of their stored builds. Thanks, Chris > On Jun 10, 2019, at 10:57 AM, Chris Lambertus wrote: > &

Re: ACTION REQUIRED: disk space on jenkins master nearly full

either. I have not yet found any suggested solutions to this. -Chris > On Jun 10, 2019, at 11:14 AM, Chris Lambertus wrote: > > Outstanding, thanks. I believe the job cleanup runs when the next build runs. > You could manually trigger a build to test, or we can check next time

Re: ACTION REQUIRED: disk space on jenkins master nearly full

e switched to multiple smaller PR validation jobs a while > ago). I have removed the Jenkins job. Hopefully that should take care > of cleaning all the files. > > > Thanks, > Matteo > > -- > Matteo Merli > > > On Mon, Jun 10, 2019 at 10:57 A

ACTION REQUIRED: disk space on jenkins master nearly full

Hello, The jenkins master is nearly full. The workspaces listed below need significant size reduction within 24 hours or Infra will need to perform some manual pruning of old builds to keep the jenkins system running. The Mesos “Packaging” job also needs to be corrected to include the project

update to git autocrlf setting on windows build nodes

Hello, Per https://issues.apache.org/jira/browse/INFRA-18383 we have updated the git autocrlf setting to ‘input' on the Windows build nodes. While we do not expect any issues to arise from this, if you have sudden changes in build behavior on

Re: repository.apache.org - Re: Blocking Polaris Alpha Traffic to Apache

nt from my iPhone > > On May 13, 2019, at 11:28 AM, Chris Lambertus <mailto:c...@apache.org>> wrote: > >> Thanks. I have removed the ban. Note that it is an automated system, so if >> the traffic recurs, it will be banned again. >> >> -Chris >>

jenkins restart

Hi folks, I will be performing a restart of Jenkins at midnight UTC (about 45 minutes from now) in order to update the gitbox scanner plugin (INFRA-17899.) -Chris

Re: workspace cleanups needed on jenkins master

> On Dec 27, 2018, at 10:31 AM, Joan Touzet wrote: > > Hi there, > - Original Message - >> From: "Chris Lambertus" > >> As a rule of thumb, we’d like to see >> projects retain no more than 1 week or 7 builds worth of historical >> da

Re: workspace cleanups needed on jenkins master

> On Dec 27, 2018, at 4:36 AM, Karl Heinz Marbaise wrote: > > Hi Gavin, > > On 27/12/18 13:00, Gavin McDonald wrote: >> On Thu, Dec 27, 2018 at 10:27 AM Karl Heinz Marbaise > > wrote: >> >>Furthermore I'm a little bit astonished that jobs consume space on >>

workspace cleanups needed on jenkins master

All, The Jenkins master needs to be cleaned up. Could the following projects please reduce your usage significantly by 5 January. After 5 Jan Infra will be purging more aggressively and updating job configurations as needed. As a rule of thumb, we’d like to see projects retain no more than 1

Re: jenkins restart - Sun Oct 7th 2300 hours

Announcements are always UTC > On Oct 7, 2018, at 2:15 PM, Karl Heinz Marbaise wrote: > > Hi Chris, > > On 07/10/18 01:14, Chris Lambertus wrote: >> All, >> Jenkins will be restarted on Sun Oct 7th 2300 hours to address some >> inconsistent build history

jenkins restart - Sun Oct 7th 2300 hours

All, Jenkins will be restarted on Sun Oct 7th 2300 hours to address some inconsistent build history issues. -Chris ASF Infra signature.asc Description: Message signed with OpenPGP

Re: disk space or git issues on H30 & H32

> On Oct 4, 2018, at 10:06 AM, Dave Brondsema wrote: > > I saw on other threads that general disk usage issues should be resolved by a > cleanup job - very nice! > > However I've just had jobs fail doing a git fetch on H30 and H32. I tried > deleting the workspace too, in case the local .git

Re: No space on H21 (Was: Fwd: Build failed in Jenkins: guacamole-client-coverity #73)

ntu-eu2> > (git clone fails :((( ) > > On Tue, 2 Oct 2018 at 02:29, Chris Lambertus wrote: > >> Well, I had thought it was something specific to the build, since it only >> happens for a couple projects, but upon further investigation, there >> appears to be an ope

Re: No space on H25 (Was: Fwd: Build failed in Jenkins: guacamole-client-docker #6)

THis should be more broadly solved by https://github.com/apache/infrastructure-puppet/pull/1181 > On Oct 3, 2018, at 7:10 AM, Mike Jumper wrote: > > FYI - we're currently seeing disk space issues on H25. > > - Mike > > -- Forwarded message - > From: Apache Jenkins Server >

Re: No space on H21 (Was: Fwd: Build failed in Jenkins: guacamole-client-coverity #73)

or "Days to keep artifacts" is left blank. Should that be set to 1 day > too? > > Any other hint at things we can try to ensure builds are cleaned up > promptly? > > Thanks, > Matteo > > On Sun, Sep 30, 2018 at 3:57 PM Chris Lambertus wrote: > >> T

Re: No space on H21 (Was: Fwd: Build failed in Jenkins: guacamole-client-coverity #73)

The main culprit on H31 appears to be pulsar ws-cleanup jobs consuming almost 40% of the disk. (The problem on H21 was something docker-related.) This is the second project I have found (Brooklyn was the first) which is leaving ws-cleanup directories all over the workspace and filling up the

Re: jenkins down

> On Aug 30, 2018, at 9:46 AM, Chris Lambertus wrote: > > > >> On Aug 29, 2018, at 2:35 PM, Chris Lambertus > <mailto:c...@apache.org>> wrote: >> >> >> >>> On Aug 29, 2018, at 7:36 AM, Chris Lambertus >> <mailto:c...@a

Re: jenkins down

> On Aug 29, 2018, at 2:35 PM, Chris Lambertus wrote: > > > >> On Aug 29, 2018, at 7:36 AM, Chris Lambertus > <mailto:c...@apache.org>> wrote: >> >> >> >>> On Aug 28, 2018, at 8:39 PM, Chris Lambertus >> <mailto:c...@apac

Re: jenkins down

> On Aug 29, 2018, at 7:36 AM, Chris Lambertus wrote: > > > >> On Aug 28, 2018, at 8:39 PM, Chris Lambertus > <mailto:c...@apache.org>> wrote: >> >> If you have not been following status.a.o or the infrabot twitter, our >> Jenkins master has

Re: jenkins down

> On Aug 28, 2018, at 8:39 PM, Chris Lambertus wrote: > > If you have not been following status.a.o or the infrabot twitter, our > Jenkins master has suffered a critical disk controller failure. We are > working with our datacenter colocation provider to identify and repair

jenkins down

Hello all, If you have not been following status.a.o or the infrabot twitter, our Jenkins master has suffered a critical disk controller failure. We are working with our datacenter colocation provider to identify and repair the problem, but we do not currently have an estimated time of

Re: Jenkins (builds.a.o) extended downtime - 2000 UTC Saturday July 21st 8-24 hours

:01 PM, Chris Lambertus wrote: > > This maintenance window is beginning now. > > -Chris > > >> On Jul 16, 2018, at 7:33 PM, Chris Lambertus > <mailto:c...@apache.org>> wrote: >> >> All, >> >> At 2000 UTC Saturday July 21st, the bu

Re: Jenkins (builds.a.o) extended downtime - 2000 UTC Saturday July 21st 8-24 hours

This maintenance window is beginning now. -Chris > On Jul 16, 2018, at 7:33 PM, Chris Lambertus wrote: > > All, > > At 2000 UTC Saturday July 21st, the builds.apache.org > <http://builds.apache.org/> jenkins service will be shut down and migrated to

Jenkins (builds.a.o) extended downtime - 2000 UTC Saturday July 21st 8-24 hours

All, At 2000 UTC Saturday July 21st, the builds.apache.org jenkins service will be shut down and migrated to a new machine. We hope this will resolve myriad performance issues and frequent need for restarts of the master. We anticipate the downtime will take 8

jenkins restarts today

All, We will be restarting jenkins today between 1530 UTC and 1730 UTC to address the recent UI hanging issues. signature.asc Description: Message signed with OpenPGP

migration of buildbot

Hi folks, We are beginning the migration of buildbot to a new host per my mail yesterday. The master will be down for some time while we effect this change. Build histories should be preserved. -Chris

Re: buildbot downtime

We will be re-attempting this upgrade on 8 July beginning approximately 1400 UTC. The version will be updated to 0.8.14. > On May 16, 2018, at 10:14 AM, Chris Lambertus wrote: > > All, > > On Thursday May 17th at 1800 UTC, the buildbot master will be taken down for > app

Re: Build hangs

> On Jul 1, 2018, at 12:32 PM, Jan Matèrne wrote: > > Our nightly build hangs for seven hours [1]. > > Could someone kill that so the next could start? Cancelled via the UI. Did you try that? That’s ordinarily self-service. -Chris > > > > [WARNINGS] Computing warning deltas based

Re: buildbot downtime

[removing operations@ CC] > On May 20, 2018, at 4:32 PM, sebb <seb...@gmail.com> wrote: > > On 20 May 2018 at 17:55, Chris Lambertus <c...@apache.org > <mailto:c...@apache.org>> wrote: >> >> >>> On May 20, 2018, at 5:09 AM, sebb <seb

Re: buildbot downtime

> On May 20, 2018, at 5:09 AM, sebb <seb...@gmail.com> wrote: > > On 19 May 2018 at 18:28, Chris Lambertus <c...@apache.org> wrote: >> Likely to be next week sometime, I discovered problems with the >> buildbot+mysql packages on 16.04 so I have to re-engin

Re: buildbot downtime

provide a > patch for the script. > > On 17 May 2018 at 04:17, Chris Lambertus <c...@apache.org> wrote: >> This downtime has been cancelled. >> >> >> >> On May 16, 2018, at 10:14 AM, Chris Lambertus <c...@apache.org> wrote: >>

Re: buildbot downtime

This downtime has been cancelled. > On May 16, 2018, at 10:14 AM, Chris Lambertus <c...@apache.org> wrote: > > All, > > On Thursday May 17th at 1800 UTC, the buildbot master will be taken down for > approximately 8 hours to migrate to a new server. During this

buildbot downtime

All, On Thursday May 17th at 1800 UTC, the buildbot master will be taken down for approximately 8 hours to migrate to a new server. During this time buildbot builds will be unavailable, as will access to ci.apache.org . This is a minor version upgrade for buildbot

jenkins being restarted

Jenkins crashed around 0200 UTC 16 May. We are restarting it with some additional performance adjustments added to the config. -Chris ASF Infra signature.asc Description: Message signed with OpenPGP

  1   2   >