Extending 2.41.0 Java snapshot TTL

Hi all, The Java Firestore connector had a bug recently that needed to be fixed. Until the fix can be released as part of 2.41.0, we need one of the daily snapshot builds

Re: Extending 2.41.0 Java snapshot TTL

Thank you for the email Daniel. Adding people who could help: @Kenneth Knowles @Danny McCormick @Chamikara Jayalath @John Casey @Byron Ellis On Thu, Jul 21, 2022, 4:14 PM Daniel Thevessen via dev wrote: > Hi all, > > The Java Firestore connector had a bug >

Re: Extending 2.41.0 Java snapshot TTL

I think you could change the TTL on the Jenkins side (That sound right to you Danny?) but I'm not sure we could preserve a specific snapshot without keeping all of them... On Thu, Jul 21, 2022 at 4:16 PM Ahmet Altay wrote: > Thank you for the email Daniel. > > Adding people who could help: @Kenn

Re: Extending 2.41.0 Java snapshot TTL

Admittedly this is potentially self-serving, but I feel there could be mutual benefit. I have a similar situation where I want to use pre-release version of beam-sdks-java-io-google-cloud-platform. Though I’ve been having trouble doing so, a possible alternative solution to using the nightly snaps

Re: Extending 2.41.0 Java snapshot TTL

> I think you could change the TTL on the Jenkins side (That sound right to you Danny?) but I'm not sure we could preserve a specific snapshot without keeping all of them... I'm admittedly not particularly well versed in this area of our infra, but after some digging I don't see a way to do this.

Re: Extending 2.41.0 Java snapshot TTL

I don't know if this helps, but I found one directory that has retained an old build from 2017 even, the one for 0.7.0-SNAPSHOT . Every other snapshots directory is empty.

Re: Extending 2.41.0 Java snapshot TTL

I reached out to the Apache Infra team in their slack channel and have yet to hear back. Given that it's getting pretty late on a Friday here (I'm located in East US), it is unlikely that I will have a workaround by the time the snapshot is removed by the retention policy; to ensure continued funct

Re: Extending 2.41.0 Java snapshot TTL

Thanks for looking into this Danny Daniel, it seems like your best bet would be to host snapshots somewhere on your own infrastructure? I feel like that's probably the safest and most reliable solution in case you need to do this again in the future. Best, B On Fri, Jul 22, 2022 at 1:35 PM Danny

Re: Extending 2.41.0 Java snapshot TTL

Thanks everyone for giving this a try, it's much appreciated. I was still seeing the Jul 14 snapshot on Friday, but it looks like it's gotten cleared out over the weekend. We will switch to 2.41.0-SNAPSHOT where necessary, at least the 2.41.0 release isn't too much further out. We'll set up our ow

Re: Extending 2.41.0 Java snapshot TTL

One low-effort thing you can do if you want to freeze at a particular date rather than use -SNAPSHOT is to just mirror the directory yourself at that time. You don't need fancy infrastructure to treat a directory hierarchy as a maven repo. TBH I would guess most organizations would benefit from hav