I know there are a number of questions regarding project groups, but they all seem to either just end or suggest they’ve been addressed in a particular release or suggest that a particular role of it has been replace by something like lifecycles, and I’m just trying to figure out whether there is an easy way to do things that currently seem a bit problematic, and whether the way I’m doing things is the way things are intended to be used (or whether they have been deprecated in favor of other methods).
Currently I have about 40 projects in Octopus across a smattering of teams (if you’re looking to break them down probably 4 distinct teams). I have since the beginning created Project Groups to segment these in the GUI, and they show just fine both on the main dashboard and in the projects area. That is assuming you stick with the “All” option. If I have someone select fewer items because they aren’t interested in what the other 4 teams is doing, if I were to add a project to a group they would have interest in (because say someone has developed a new Windows service for that project), they have no way to know that it has been added (without happening to reconfigure the dashboard). To be clear the “Project Group” does show up in the multi-select, but there is no mechanism to select that project group. Or maybe putting it more succinctly, it SEEMS that by the design of the interface that there should be a mechanism to select a project group but there isn’t. And it appears it has been that way for a long time so that it hasn’t been an added feature or hasn’t been a issue to get upvoted makes it feel as though there is another way around it. This of course presents a similar issue in users/teams when assigning permissions except the interface is different and you have to remember what you had in each project group. With only 40 projects, I’m just looking for advice/suggestions on how people who have been using this for longer (or who have more projects) securely manage this without forgetting things.
That was in the GUI, which there is no “easy” way for me to address (at least for the view maybe I could rewrite the permissions but then I’m managing it in two places). Now when it comes to deployments, looking at the API, I think I should be able a way to deploy all of a project group. However when I was reading other discussions I thought (although now I can’t find it), that the mention was that this was going to be handled by lifecycles going forward. Which looking at how I’ve applied lifecycles would mean I need to rethink my application of them.
I don’t want to write something and find out there was a different intent (or something perhaps I’m missing). Project Groups seems like a great idea to help manage things that are connected, but from what I’ve been there for quite a while and some of the basic reasons for it being there haven’t been fleshed out. And it seems like it would be at a spot where it should be a pain point for others (it is for me) but hasn’t generally been seen as a problem by the majority, so it feels like I’m missing something like maybe a different way to do the same thing?