Re: [ANNOUNCE] Spring Boot for Apache Geode 1.0.0.RELEASE Available!
Congratulations John, Great work as always. -- Mike Stolz Principal Engineer, GemFire Product Lead Mobile: +1-631-835-4771 On Mon, May 6, 2019 at 10:03 PM John Blum wrote: > It is my pleasure to announce the first GA release of Spring Boot for > Apache Geode (SBDG) 1.0.0.RELEASE. > > See the official release announcement on spring.io for more details: > > > https://spring.io/blog/2019/05/07/spring-boot-for-apache-geode-pivotal-gemfire-1-0-0-release-available > > Feedback appreciated and welcomed. > > Regards, > > -- > -John > >
Spring Boot for Apache Geode 1.1.0.M1 Released!
I am pleased to announce the release of *Spring Boot for Apache Geode* (SBDG) 1.1.0.M1. See the official release announcement here: https://spring.io/blog/2019/05/07/spring-boot-for-apache-geode-pivotal-gemfire-1-1-0-m1-released The 1.1 Milestone 1 (M1) release primarily rebases SBDG on the latest and current (GA) of Spring Framework 5.1, Spring Boot 2.1, Spring Data Lovelace/2.1 and Spring Session Bean/2.1. Additionally, since SDG Lovelace is based on Apache Geode 1.6, SBDG has been rebased on Apache Geode 1.6. This 1.1 version will quickly progress to GA by end of May, beginning of June. I am planning 1 more milestone (i.e. 1.1 M2), which will include dedicated support for *Inline Caching*. After M2, there will be a 1.1 RC1 and then the final GA, again, roughly end of May, beginning of June timeframe. At that point, you can expect a early 1.2 M1 release, which will rebase SBDG on Spring Framework 5.2, Spring Boot 2.2, Spring Data Moore/2.2 and Spring Session Corn/2.2, all currently in development (i.e. no GA versions yet). SD[G] Moore/2.2 is currently based on Apache Geode 1.9. SBDG will then be all caught up with the Spring ecosystem. The 1.2 M1 release will roughly occur mid-June. Regards, -- -John
Extensions team hijack into Apache workers
Hi, Not sure if this is the right place to go, but the GemFire Extensions team would like to be able to hijack into the Apache pipeline workers. When attempting to access the workers, we get the following error: fly -t apache hijack -u= https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-pr/jobs/Build/builds/2086 error: forbidden I've been selecting the GitHub method of authentication and it seems to work. The above error only occurs when attempting to actually hijack into the worker. Here's a list of the teams GitHub userids: gemzdude Scott Jewell DonalEvans Donal Evans jchen21 Jianxia Chen gesterzhouXiaojian Zhou BenjaminPerryRoss Benjamin Ross Let me know if there's any more you need from us to make this happen. Thanks -- Scott Jewell sjew...@pivotal.io
Re: Extensions team hijack into Apache workers
Why are you asking to hijack a worker? Workers do not perform any builds or tests as all of this is offloaded to the heavy lifter VMs. These VMs are transient and can’t be accessed after a job is complete. -jake > On May 7, 2019, at 3:28 PM, Scott Jewell wrote: > > Hi, > > Not sure if this is the right place to go, but the GemFire Extensions team > would like to be able to hijack into the Apache pipeline workers. > > When attempting to access the workers, we get the following error: > > fly -t apache hijack -u= > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-pr/jobs/Build/builds/2086 > > error: forbidden > > I've been selecting the GitHub method of authentication and it seems to > work. > The above error only occurs when attempting to actually hijack into the > worker. > > Here's a list of the teams GitHub userids: > > gemzdude Scott Jewell > DonalEvans Donal Evans > jchen21 Jianxia Chen > gesterzhouXiaojian Zhou > BenjaminPerryRoss Benjamin Ross > > Let me know if there's any more you need from us to make this happen. > > Thanks > -- > Scott Jewell > sjew...@pivotal.io
Re: Extensions team hijack into Apache workers
Hi Jacob, The particular case I was interested in was to be able to inspect member logs while tests were running. We had a case where a long running test was occasionally hanging. We wanted to be able peek at the logs in an attempt to determine if the test was making progress or had hung. It sounds as if that hope may be misguided. Is there some way that you'd recommend to accomplish this? Thanks. On Tue, May 7, 2019 at 3:55 PM Jacob Barrett wrote: > Why are you asking to hijack a worker? Workers do not perform any builds > or tests as all of this is offloaded to the heavy lifter VMs. These VMs are > transient and can’t be accessed after a job is complete. > > -jake > > > > On May 7, 2019, at 3:28 PM, Scott Jewell wrote: > > > > Hi, > > > > Not sure if this is the right place to go, but the GemFire Extensions > team > > would like to be able to hijack into the Apache pipeline workers. > > > > When attempting to access the workers, we get the following error: > > > > fly -t apache hijack -u= > > > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-pr/jobs/Build/builds/2086 > > > > error: forbidden > > > > I've been selecting the GitHub method of authentication and it seems to > > work. > > The above error only occurs when attempting to actually hijack into the > > worker. > > > > Here's a list of the teams GitHub userids: > > > > gemzdude Scott Jewell > > DonalEvans Donal Evans > > jchen21 Jianxia Chen > > gesterzhouXiaojian Zhou > > BenjaminPerryRoss Benjamin Ross > > > > Let me know if there's any more you need from us to make this happen. > > > > Thanks > > -- > > Scott Jewell > > sjew...@pivotal.io > -- Scott Jewell sjew...@pivotal.io
Re: Extensions team hijack into Apache workers
I assume you’ve tied running the hanging test locally. When the tests time out in the CI there should be a stackdump file that is collected and uploaded into GCS. The link to download it is at the end of the job. Have you checked this file? -Jake > On May 7, 2019, at 4:16 PM, Scott Jewell wrote: > > Hi Jacob, > > The particular case I was interested in was to be able to > inspect member logs while tests were running. > > We had a case where a long running test was occasionally hanging. > We wanted to be able peek at the logs in an attempt to determine > if the test was making progress or had hung. > > It sounds as if that hope may be misguided. > > Is there some way that you'd recommend to accomplish this? > > Thanks. > >> On Tue, May 7, 2019 at 3:55 PM Jacob Barrett wrote: >> >> Why are you asking to hijack a worker? Workers do not perform any builds >> or tests as all of this is offloaded to the heavy lifter VMs. These VMs are >> transient and can’t be accessed after a job is complete. >> >> -jake >> >> >>> On May 7, 2019, at 3:28 PM, Scott Jewell wrote: >>> >>> Hi, >>> >>> Not sure if this is the right place to go, but the GemFire Extensions >> team >>> would like to be able to hijack into the Apache pipeline workers. >>> >>> When attempting to access the workers, we get the following error: >>> >>> fly -t apache hijack -u= >>> >> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-pr/jobs/Build/builds/2086 >>> >>> error: forbidden >>> >>> I've been selecting the GitHub method of authentication and it seems to >>> work. >>> The above error only occurs when attempting to actually hijack into the >>> worker. >>> >>> Here's a list of the teams GitHub userids: >>> >>> gemzdude Scott Jewell >>> DonalEvans Donal Evans >>> jchen21 Jianxia Chen >>> gesterzhouXiaojian Zhou >>> BenjaminPerryRoss Benjamin Ross >>> >>> Let me know if there's any more you need from us to make this happen. >>> >>> Thanks >>> -- >>> Scott Jewell >>> sjew...@pivotal.io >> > > > -- > Scott Jewell > sjew...@pivotal.io
