How do I extend retention period of existing symbol indices (without symbol packages)?

[dagood]

At release time, expiration date needs to be extended from 180 days to 10950 days (30 years). In earlier infra, this was done by publishing the same symbol packages again with the longer expiration date.

How is this done when some bits aren't in the symbol packages?

I imagine you could by downloading all the bits and pushing them back up, but how is that done in a release context? Is there tooling?

[jcagme]

FYI @JohnTortugo

[tmat]

I believe we should set the expiration data to the required value right away for all builds, so that we do not need to ever extend it.

[markwilkie]

Moving to P7

[JohnTortugo]

Anyone see an issue with just extending the expiration data from the start? Who can confirm that the expiration period should be?

[dagood]

Anyone see an issue with just extending the expiration data from the start?

@mikem8361 might have thoughts here. I don't know who would specifically care about overusing symbol indexing/storage space. Maybe until we get a bill, nobody cares. 😄

[mikem8361]

If we are talking about extending the expiration date to 30 years for every daily build that might add up and actually cost some storage space. I'm not basing that on any data I have, just a feeling :).

If we can extend only for the potential release builds, then that shouldn't be a problem at all. The old prodcon final publish job had a build variable that could be set to 10950 days. Not sure how things work for releases anymore.

We only have republishing as far as tooling to extend the expiration date.

[jcagme]

@JohnTortugo is this done? If not should this be done be P7?

[JohnTortugo]

It's not done. Currently the expiration date is 10 years. Not a blocker for P6 and IMO not a blocker for P7 as well.

I think now that we are going to have a set or rings where we promote builds through, we might solve this problem by increment the expiration date once the build reach a certain ring. That way we wouldn't increment the expiration date for every build.

[riarenas]

@JohnTortugo should we move this to the Ringed releases epic? dotnet/arcade#2891

[JohnTortugo]

Yeah, I think this should be part of the Ringed release epic. Can you please move it? I don't know why but the 'Epic dropdown' isn't showing up for me.

[riarenas]

Yep I think it's broken right now 😢

[dagood]

Works in ZenHub app.

[riarenas]

Works in ZenHub app.

Didn't even know that was a thing. Thanks Davis

[dagood]

I ended up there accidentally at some point. Funny that it's ended up useful. 😄

[michellemcdaniel]

@riarenas says that build's symbol retention is now 10 years. Is that long enough? Ricardo, please let me know if that's incorrect

[dagood]

I haven't heard anything about the requirement dropping from 30 years to 10 years. Some teams have been ok with 10, but AFAIK the runtime was always 30 years.

[michellemcdaniel]

Out of scope for dotnet/arcade#6418.

[andriipatsula]

Closing this as the issue is almost 4 years old and we don’t have plans to work on this in the near future. In case you believe the issue needs resolution - please reopen it and provide a reason.