I recently came across what appears to be an oversight related to declarative projects: namely, that once they are no longer a declarative project (e.g. the “Declarative spec file” is empty), the special .jobsets jobset hangs around. It is my opinion that once the project transitions from declarative to normal, .jobsets should be removed.
I filed an issue about this against Hydra earlier (linked below), and now I’m looking for feedback from you folks – should .jobsets be deleted when the parent project is no longer declarative?
All you should need to do is fill out the “Declarative spec file” field again and update the project, and it should come back.
Once I file a PR implementing this cleanup (assuming nobody else comes along with a reason why this would be problematic for them), I’ll be able to say for certain.