Under RunDeck 1.2, I'm trying to setup job grouping similar to
this:
Deployment->[jobs]
Deployment->pre-deploy->[jobs]
Deployment->pre-deploy->internal->[jobs]
Deployment->deploy->[jobs]
Deployment->deploy->internal->[jobs]
Deployment->post-deploy->[jobs]
Deployment->post-deploy->internal->[jobs]
Operations->[jobs]
What I'm seeing in the GUI looks like this:
Deployment (folder)
-> deploy (sub-folder)
->-> internal (subfolder)
Deployment/pre-deploy (folder)
-> internal (subfolder)
Deployment/post-deploy (folder)
-> internal (subfolder)
Operations (folder)
The Deployment/deploy/internal folder structure is the only one
displaying correctly. At one point, all the groups displayed
correctly, however, when I re-defined one of the jobs, I started
seeing the Deployment/pre-deploy and Deployment/post-deploy
groupings. I've looked at the XML files for the jobs and they all
appear to have the correct group structure for the specific
jobs.
It looks like whatever is parsing the group to display it in the
GUI is acting differently based on something I'm unaware of.
I did notice when initially creating groups that if I created
JobX with a group of the form Dir1/Sub-dir1/JobX, as the first job,
this is how it would show up in the GUI [folder name:
Dir1/Sub-dir1] until I created JobY with a group of Dir1/JobY. At
that point, the GUI would display JobX correctly as subfolder
Subdir1 under folder Dir1.