Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
getting subset of view deployment
swong74
Hello,
Logged in as a user, a person sees all deployments in View Deployments regardless of which ones he/she really has privs to use. Is it possible to either (a) limit the View Deployment as it does in Start Deployment; or (b) allow for search of deployment-name as a future feature of OpenDeploy? I tried setting days to 2 for completed but only see today's as far as 6am. This is a pretty active deployment base. So, if someone scheds something to run say at midnight and want to check on the status of it, they can't under view deployment. I know you can under Reports but educating a big user base can be daunting eh?
Also, say I deploy now and decide I want to view the deployment at a later time ... because it's a long deployment (relaunch the entire sub-site) ... I would like to come back to it much later only to find 50 other deployments listed and mine is off the chart. ;-)
Just my $0.02
Thanks.
Ciao ?:-)
S. Wong
Find more posts tagged with
Comments
Migrateduser
All good questions.
First, there is no way today to authorize which deployment jobs are visible to whom from the Admin UI. There is an open FR to make the authorizations finer grained (FR #36672), which includes this capability.
As for finding a deployment name in the Admin status, you can sort the list of jobs by clicking the "Name (ID)" label at the top of the column.
The # days box pertains only to the pending deployments. If you click the "pending" checkbox, then all scheduled deployments within the past # days are included in the job listing.
Now a point about the jobs listed. This info is kept in memory by the OpenDeploy Base Server or Receiver. If you restart the Base Server or Receiver, the info is lost. By default, info is kept about the last 50 jobs. You can change this value to a max of 100, I believe. There are details in the OD docs about specifying the completed deployments list. Increasing the value will of course consume more memory.
So, recognizing that the deployments list in the Admin UI is only kept in memory by the Base Server or Receiver, and that there is a finite list size after which older jobs fall off the list, the reporting feature can be utilized for a persistent, historical record of deployment activity.
Todd Scallan
Group Product Manager
Interwoven
t: 408-530-7167
e:
tscallan@interwoven.com
Edited by lissa on 09/08/03 10:59 AM (server time).
swong74
Ok, the next question is when is the FR going to be a real feature? :-) Any release date?
Yeah, I know the View Deployments is from last restart. But we're hoping not to have to restart the service too often ... or so I hope. ;-) But anyhow, it is only useful for immediately looking at deployments and not scheduled ones. Was hoping it could subset-ize (sic) or at least do like the Report page.
Well, I guess we have to redo our UserDoc then. :-)
Thanks for the reply Todd!
Ciao ?:-)
S. Wong
Migrateduser
> Ok, the next question is when is the FR going to be a real feature? :-) Any release date?
Next release is in the planning stages. Nothing yet that can be shared on the forum.
Todd Scallan
Group Product Manager
Interwoven
t: 408-530-7167
e:
tscallan@interwoven.com