Hi team,
Just wanted to discuss whether it’s possible to add support for this in our Grove clusters. In theory we only need to tweak our CI runners’ configuration a bit, but I’m not sure. I think being able to connect to a shell of a tools container right from the GitLab UI can simplify our lives a lot.
What do you think?
@gabor What do you think? I know it must not be a priority. If I understand the feature correctly, this might help a lot with debugging pipelines.
I think it could be a great improvement for Grove. However, as you mentioned, it may not be a priority that much. Based on the epic schedule of Serenity, the most appropriate epic for this task would be Grove Maintenance, though it is just temporarily put back to development.
If it is a big issue for Bebop, we can make another exception (right, @tikr?) and hand out a task to Bebop to handle this task – then we can put the epic on hold again.
Yep that’s right 
@gabor @tikr Rather than making exceptions, could we simply use unbilled hours in Bebop to work on this? There is currently a budget excess for sustainability in the cell, and that is the intended use of cell budgets - let’s not centralize decision-making when it’s not necessary? Bebop can opt to work on this on its own.
@antoviaque I think the exception that @gabor was talking about above was to allow a task to be added to the Grove Maintenance epic. We had deprioritized that epic and put it on hold a while back; and we had also made plans to treat it as a fixed-scope epic going forward. (For a long time it was a recurring epic that acted as a catch-all for Grove-related tickets.) So the idea was to try and stop scope creep by closing it for new tickets.
On the budget front, Serenity does have unused hours from its non-billable budget that it could give away, but we could just as well create a task for adding support for interactive web terminals in the BB project 
@tikr I see, ok - and sounds good for the budget