Re: Broken links in code velocity dashboard

pache/beam/pull/12349, > https://github.com/apache/beam/pull/12374). Not sure what is causing it, > but it seems like a new issue. > > On Fri, Jul 31, 2020 at 10:13 AM Ahmet Altay wrote: > >> Looks fixed. Thank you for the quick response! >> >> On Fri, Jul 31, 2

Re: Java Jenkins tests not running

Hey, We knew about the issue. All Jenkins builds were not being triggered from the pull requests. There's a ticket for that if you're curious about details: INF RA-20649 Seems that we've just

Failing Python builds & AppEngine application

Hey, A strange thing happened a few hours ago. All python builds (e.g. [1]) started failing because of: google.api_core.exceptions.NotFound: 404 The project apache-beam-testing does not exist or it does not contain an active Cloud Datastore or Cloud Firestore database. Please visit

Re: No space left on device - beam-jenkins 1 and 7

ins it should be just fine. Thanks for checking! > > Kenn > > On Tue, Jul 28, 2020 at 10:23 AM Damian Gadomski < > damian.gadom...@polidea.com> wrote: > >> Sorry, mistake while copying, [1] should be: >> [1] >> https://github.com/apache/beam/blob/8aca8cc

Re: Beam Dependency Check Report (2020-08-03)

That's probably caused by this [1] PR, workspace had been deleted before the email was sent. +Udi Meiri Moving the workspace clean up to the very end of post-build actions should help. [1] https://github.com/apache/beam/pull/12326 On Mon, Aug 3, 2020 at 5:42 PM Brian Hulette wrote: > Does

Re: Broken links in code velocity dashboard

m the (https://github.com/damgadbot/beam) fork in > addition to the main repo. > > Dashboard was working normally last week, so probably something changed > recently. I do not see a code change in the dashboard [2]. I am not sure > what happened, maybe the dashboard was deployed from a fork? &g

Re: No space left on device - beam-jenkins 1 and 7

Sorry, mistake while copying, [1] should be: [1] https://github.com/apache/beam/blob/8aca8ccc7f1a14516ad769b63845ddd4dc163d92/.test-infra/jenkins/CommonJobProperties.groovy#L63 On Tue, Jul 28, 2020 at 7:21 PM Damian Gadomski wrote: > That's interesting. I didn't check that myself but

Re: No space left on device - beam-jenkins 1 and 7

ddress this issue? Everything in that directory should be immutable and > just a cache to avoid pointless re-download. > > Kenn > > On Tue, Jul 28, 2020 at 2:25 AM Damian Gadomski < > damian.gadom...@polidea.com> wrote: > >> Agree with Udi, workspaces seem to be th

Re: Beam Jenkins Migration

current size is so small that adding 1s of extra time in some runs >> looks like a 50-60% degradation and we cannot know if this is due to >> some small small CPU/GC pause or a real regression. I wonder however >> if this will impact negatively the worker utilization. >> >

Re: No space left on device - beam-jenkins 1 and 7

kins+nodes >> > >>>>>>>>>>>> >> > >>>>>>>>>>>> On Wed, Jul 22, 2020 at 8:06 AM Kenneth Knowles < >> > >>>>>>>>>>>> k...@apache.org> wrote: >> > >>>>

Re: Beam Jenkins Migration

>>> On Thu, Jun 18, 2020 at 3:30 PM Luke Cwik wrote: >>> >>>> Was about to ask the same question, so can non-committers trigger the >>>> tests now? >>>> >>>> On Thu, Jun 18, 2020 at 11:54 AM Heejong Lee >>>> wrote: >>>>

Re: Jenkins trigger phrase "run seed job" not working?

; On Thu, Jul 23, 2020 at 1:11 PM Damian Gadomski < > damian.gadom...@polidea.com> wrote: > >> Yes, I thought that whitelisting apache organization will do the trick, >> but apparently, it doesn't. Actually, it makes sense as we want to allow >> only beam committers

Re: Jenkins trigger phrase "run seed job" not working?

mmitters? > > I traced the code for the membership check here: > > https://github.com/jenkinsci/ghprb-plugin/blob/4e86ed47a96a01eeaa51a479ff604252109635f6/src/main/java/org/jenkinsci/plugins/ghprb/GhprbGitHub.java#L27 > Is there a way to see these logs? > > > On Thu, Jul 23, 2020 at

Re: Jenkins trigger phrase "run seed job" not working?

on_408.png] As a target solution, I'm planning to fetch the list of beam committers from LDAP and automatically add them to the whitelist above as a part of the seed job. I'll keep you updated about the progress. Regards, Damian On Wed, Jul 22, 2020 at 11:03 PM Ahmet Altay wrote: > +Da

Re: Beam Jenkins Migration

: >> >>> Was about to ask the same question, so can non-committers trigger the >>> tests now? >>> >>> On Thu, Jun 18, 2020 at 11:54 AM Heejong Lee wrote: >>> >>>> This is awesome. Could non-committers also trigger the test now? >

Re: No space left on device - beam-jenkins 1 and 7

Hey, I've recently created a solution for the growing /tmp directory. Part of it is the job mentioned by Tyson: *beam_Clean_tmp_directory*. It's intentionally not triggered by cron and should be a last resort solution for some strange cases. Along with that job, I've also updated every worker

contributor permission for Beam Jira tickets

Hi, Can I be added to the JIRA contributors so I can assign tickets to myself, please? my Jira username: damgad Thanks, Damian

cwiki edit access

Hi, I would like to have write (edit) access on the cwiki. I'm planning to update the Jenkins URLs as we've migrated recently. The username is: dgadomski Thanks, Damian

Re: Beam Jenkins Migration

tance. > > Please let me know if there's anything that I missed. > > Regards, > Damian > > On Mon, Jun 15, 2020 at 8:05 PM Alexey Romanenko > wrote: > >> Great! Thank you for working on this and letting us know. >> >> On 12 Jun 2020, at 16:58, Damia

Re: Beam Jenkins Migration

u for working on this and letting us know. > > On 12 Jun 2020, at 16:58, Damian Gadomski > wrote: > > Hello, > > During the last few days, I was preparing for the Beam Jenkins migration > from builds.apache.org to ci-beam.apache.org. The new Jenkins Master will > be dedica

Beam Jenkins Migration

Hello, During the last few days, I was preparing for the Beam Jenkins migration from builds.apache.org to ci-beam.apache.org. The new Jenkins Master will be dedicated only for Beam related jobs, all Beam Committers will have build configure access, and Beam PMC will have Admin (GUI) Access. We