Re: [DISCUSS] CI improvements

Given the length of time precheckin seems to run, would it make sense to break it up? -Sean. On Thu, Nov 2, 2017 at 11:49 AM, Dan Smith wrote: > Looks good. Should we go ahead and change this to run precheckin instead of > build? > > -Dan > > On Thu, Nov 2, 2017 at 9:53 AM,

Re: [DISCUSS] CI improvements

precheckin is literally './gradlew build :geode-assembly:acceptanceTest integrationTest distributedTest flakyTest' :) -S. On Thu, Nov 2, 2017 at 1:10 PM, Dan Smith <dsm...@pivotal.io> wrote: > On Thu, Nov 2, 2017 at 11:58 AM, Sean Goller <sgol...@pivotal.io> wrote: > &g

Concourse pipeline

Hi everyone, If you haven't already heard, we have a new concourse pipeline infrastructure up and running at https://concourse.apachegeode-ci.info/ . When these jobs fail, email will be sent to the dev list, so be aware! :) -Sean.

Re: Concourse pipeline

ail alias for these messages if they are > going to be even more frequent than Travis? > > On Fri, Dec 1, 2017 at 3:24 PM, Sean Goller <sgol...@pivotal.io> wrote: > > > Hi everyone, > > If you haven't already heard, we have a new concourse pipeline > > infrastructure up

Concourse infrastructure

Currently the concourse infrastructure is suffering from massive internal networking issues, we are working to resolve this as soon as possible. I'll update the community as we progress on the repair.

Re: Concourse infrastructure

Update: The infrastructure is still messed up. I've been working on bringing up a replacement infrastructure, but it's taking longer than anticipated. Hopefully I'll be able to finish up in the morning. -S. On Mon, May 14, 2018 at 9:59 AM, Sean Goller <sgol...@pivotal.io> wrote: >

Re: Concourse infrastructure

Update: We are back! Once a build makes it all the way through develop I'll enable the metrics pipeline. On Mon, May 14, 2018 at 9:12 PM, Sean Goller <sgol...@pivotal.io> wrote: > Update: The infrastructure is still messed up. I've been working on > bringing up a replacement in

Re: Next release: 1.4.0

The release pipeline is up: https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.4.0 -Sean. On Fri, Jan 5, 2018 at 10:00 AM, Anthony Baker wrote: > +1 > > It should be pretty easy to clone the current pipeline for the 1.4.0 > release branch. > > I’ll plan to

Re: Logging in to concourse.apachegeode-ci.info

Yeah, the geode pipelines are completely public. You don't need to log into concourse to see anything, only to pause, kill or start jobs. Any changes made to the pipeline is done through the git repo, and those changes will be automatically pushed to concourse when merged. -S. On Wed, Feb 21,

Pipeline instability

A major refactor is going in shortly so expect turbulence for the next hour or so. -Sean.

Re: Moving from gradle to maven

This is a non starter without a maven equivalent of the gradle dockerized plugin. Switching to maven without that will mean longer testing times, which I feel is unacceptable. So far I've found this reference on stack overflow (

Major CI changes PR

Hi, I've submitted a PR to make the pipeline much more fork friendly for ease in testing. As soon as this PR gets merged, I expect some degree of instability and redeployment of pipelines, so please be aware of that if you see issues. -Sean.

Re: [DISCUSS] Apache Geode 1.7.0 release branch created

Reverting GEODE-5591 results in code that can produce an infinite loop, so I don't feel that's a viable option. I feel as though the code treats bind exceptions as transient occurrences, but my direct experience with them leads me to the opposite conclusion. I don't believe a long wait time is

Re: 2 minute gateway startup time due to GEODE-5591

If it's to get the release out, I'm fine with reverting. I don't like it, but I'm not willing to die on that hill. :) -S. On Tue, Sep 4, 2018 at 4:38 PM Dan Smith wrote: > Spitting this into a separate thread. > > I see the issue. The two minute timeout is the constructor for > AcceptorImpl,

Re: 2 minute gateway startup time due to GEODE-5591

It affects us on any linux platform that doesn't use glibc. It's not worth holding up the release for. It's been this way for 20 years, right? ;) Revert it. On Tue, Sep 4, 2018 at 5:09 PM Udo Kohlmeyer wrote: > Imo (and I'm coming in cold)... We are NOT officially supporting Alpine > linux

Concourse instability

We're experiencing a minor amount of instability relating to filled up disks on workers, along with massive job execution. We're recreating workers so for the next hour or so things may not be working optimally. Thank you for your patience. -Sean.

Re: Concourse instability

I think we're firing on all cylinders again. I'll be monitoring it for the rest of the day for issues. On Thu, Jul 5, 2018 at 11:39 AM Sean Goller wrote: > We're experiencing a minor amount of instability relating to filled up > disks on workers, along with massive job execution.

concourse excitement

We're having some unintended instability in the geode concourse at the moment, the concourse atc vm is being recreated so some DNS may need to be updated once everything settles down. For the moment however, geode concourse is going to be inaccessible for a bit. My apologies, it did not seem like

Re: [PROPOSAL] use default value for validate-serializable-objects in dunit

I agree with this. We should have a default state that reflects an “out of the box” configuration, and if tests expects a different configuration, it should manage that within the context of the test. -Sean On Tue, Mar 13, 2018 at 10:04 AM Kirk Lund wrote: > I want to propose

Re: Geode 1.6.0 release branch has been created

The corresponding pipeline has been created: https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.6.0 On Thu, Apr 12, 2018 at 3:03 PM, Michael Stolz wrote: > Can someone please create a concourse pipeline for this release? > > > -- > Mike Stolz >

Re: [DISCUSS]: Tests requiring external services

I'm actually fine with putting it in AcceptanceTest for now. Ideally I'd like to see something like JDBC connection strings that could be passed in as properties via the command-line, and if they're not present the relevant tests don't get run. That way the entity running the tests can decide the

Re: [DISCUSS] New List for Commit and CI Emails

Concourse sends mail whenever a job fails. On Wed, Mar 21, 2018 at 9:49 AM, Swapnil Bawaskar wrote: > I know travis is already configured to send emails only when the build > breaks and then when it is fixed. Is concourse configured the same? > > On Wed, Mar 21, 2018 at

Re: Next release: 1.5.0

1.5.0 pipeline is up and running, please take a look at it and let the list know if there are problems. https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.5.0 On Mon, Mar 5, 2018 at 11:07 AM, Anthony Baker wrote: > LGTM > > > On Mar 2, 2018, at 4:05 PM,

Re: Concourse upgrade

penjdk-amd64 > Please set the JAVA_HOME variable in your environment to match the > location of your Java installation. > > > On 10/10/18 11:03 AM, Sean Goller wrote: > > We're going to be upgrading the concourse infrastructure to the latest > > version today,

Pipeline names changing shortly

In order to standardize CI deployment and to improve quality of life around running pipelines for forks, we've merged a number of changes to the ci/ directory which will create new pipelines for the develop branch. If you have direct links to specific pipelines (specifically develop ones) those

Re: Pipeline names changing shortly

New pipelines for develop (apache-develop-main) and PR (apache-develop-pr) are up. We'll bring up the rest of the pipelines (metrics, examples, etc.) tomorrow. On Mon, Oct 15, 2018 at 3:03 PM Sean Goller wrote: > In order to standardize CI deployment and to improve quality of life >

concourse problems

The web front end for the geode concourse is currently experiencing some issues. we are actively troubleshooting this. -Sean.

Re: concourse problems

This should be stable again. -S. On Wed, Oct 24, 2018 at 9:36 AM Sean Goller wrote: > The web front end for the geode concourse is currently experiencing some > issues. we are actively troubleshooting this. > > -Sean. >

Concourse upgrade

We're going to be upgrading the concourse infrastructure to the latest version today, since 1.7 has been released. Best case it will be fairly seamless and everything will be unicorns and puppies and happiness. Worst case it'll be messed up for a few days. -Sean.

concourse environment recreation

Unfortunately due to some fat fingering on my part, the concourse deployment was destroyed. We are in the process of recreating it. The impact of this is that build logs/history is gone, but artifacts are still present. Any jobs that were running at the time are gone. Pipelines will need to be

Re: Failing to get resources from Maven in CI

I agree. We should deploy a caching server to resolve this. On Thu, Dec 6, 2018 at 4:16 PM Jacob Barrett wrote: > Given that this seems to be an ongoing problem with bintray I think it is > time we put a local caching repository in our CI network. The native > project ran into this same issue

JIRA write access?

Hi, In order to start dealing with some JIRA tickets could I get assign and resolve access? My apache username is smgoller. Thanks! -Sean.

Concourse upgrade

We will be upgrading the concourse infrastructure to version 5.5.1 in the next few hours. Please be aware there will be turbulence. -Sean.

Re: Flaky test caused by missing JDK dependency

The Liberica JDK does not include the Attach API. I'm investigating why. Given the inherent insecurity of this API, I recommend we transition away from using it. From: Kirk Lund Sent: Monday, July 6, 2020 10:36 AM To: dev@geode.apache.org Subject: Flaky test

Re: [VOTE] Apache Geode 1.12.3.RC3

+1 Looks good from what I can see. On Fri, Jun 25, 2021 at 1:15 PM Owen Nichols wrote: > Hello Geode Dev Community, > > I'd like to propose a 1.12 patch release. > > This is a release candidate for Apache Geode version 1.12.3.RC3. > Note: This is the first vote email due to a build issue with

Re: Need Access to apachegeode/geode-native-build on docker hub

Travis can pull authenticated docker images so GCR is usable. I'm not thrilled about a docker image that gets pushed to by a release process having a 'latest' tag that is not the same as the latest release artifact. We have a few options here: 1) Update travis to access GCR in an authenticated

Re: Apache Geode CI upgrade

GitHub. > So, is there anything we might need to do to have access to the pipelines > after this update? > Or do you need to grant us access? If so, my GH username is > gaussianrecurrence. > > Thanks! > Mario > ____ > From: Sean Goller >

Re: Apache Geode CI upgrade

The Apache Geode Concourse deployment upgrade is now complete. You should clear the DNS cache on your browser, or restart it completely in order to pick up the DNS changes. -Sean. On Wed, Nov 10, 2021 at 9:01 AM Robert Houghton wrote: > We are upgrading the Apache Geode Concourse deployment.

Temporary Instability

Due to some memory pressure we need to increase the size of some nodes in the ci infrastructure. Due to this there may be some instability with concourse, but we don't believe there will be any. This is just a heads up in case something happens. -Sean.

Re: Temporary Instability

The upgrade is complete, so everything should be working normally. On Thu, Dec 2, 2021 at 2:05 PM Sean Goller wrote: > Due to some memory pressure we need to increase the size of some nodes in > the ci infrastructure. Due to this there may be some instability with > concourse, but

Recent CI outage - resolved

This morning we had an unexpected problem with Concourse. The database volume filled up and locked everything up. The database volume has been increased in size and everything should be functioning properly again. It's highly likely that a few jobs failed because of this and we're looking into it.