Details
-
Type:
Story
-
Status: To Do
-
Resolution: Unresolved
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Story Points:1
-
Epic Link:
-
Team:Alert Production
-
Urgent?:No
Description
**Make a new shared stack of the last n dailies on the dev nodes at SLAC, once they're up, where n is probably ~7-14 to deal with intraweekly needs and/or missing weekly builds.
Would be separate to the main shared stack for reasons John Swinbank knows about (something about cleaning things out is hard, but rebuilding from scratch easy, so just rebuild a 7-day daily stack every day is >>easier than adding weeklies to the main stack without it ballooning).
Attachments
Activity
> So question on this, are we going to create a whole new shared stack every day?
I think that would be required, unless I'm missing something.
> What happens to the older ones? Do we delete at some point?
Yes, on some kind of circular buffer.
> If someone has an open screen to one of the ones we delete, are we responsible?
No. I think it should be advertised as a stop-gap for when you need a daily because of churn and the weekly won't do, but people should switch back to weeklies as soon as they can. If we use a 2 week buffer then this should never be an issue.
> How long before we should clear out older built stacks?
For the reasons above I think ~2 weeks is about right
Nate Lust and Yusra AlSayyad and maybe Kian-Tat Lim - do you think this will ever get done, or should I stop dreaming and close this ticket? Right now I have about 9 custom branches I've had to make from tags and setup because the far-reaching DM-31722 merged just after the latest weekly. Should I give up here and just start maintaining my own stack for times like this (as I know many others do) or do you think this might be a reasonable solution that we could give some priority/effort to?
This is not going to happen on NCSA resources for sure, We can close this ticket or change the contents and revisit on slack resources.
I think the ticket is just as relevant to the shared stack on whatever the machines at SLAC will be called, so let's keep it open and I'll just edit to make it clear that it's for the new machines.
I can make all these decisions but other may want to weigh in. Kian-Tat Lim