1 of 1 people found this helpful
You are correct that the Deploy tab would not show individual packages results if you deployed a repository. Going to the Repository subtab, only shows the instance of the repository. You would have to click it to see what is inside. However, you can see this in the reports in some capacity. This is by either doing an environment report, which would show the repo and its content (in this case instances). Or you could do a repo instance report, which would again tell you where the repo and its content (package instances) was deployed. What you cannot do and I think you are asking for, is to run a package instance report to see where that instance was deployed regardless if you deployed it as a package or repo instance.
Thanks for the follow up. You are correct - what I'm asking for is to see a report (or UI page filter) that shows me the package instance regardless of whether it was deployed via a standalone package instance or a package instance within a repo instance. I have to disagree though with your statement that doing an environment report would show the content of a repo. Here is an example of what I see when I do an environment report. Note, these are all repo deployments with several package instances inside. I see no reference to repo content.
2014June14_NMV_FMEFC 0.0.0.1 Pass Fri Jun 13 09:51am 2014MAR28_MarketView_FMHelp 0.0.0.1 Pass Sat Mar 29 05:23pm 2014MARCH19_BTTBEARs_BTTBTAR_TPSJBOSSPROP 0.0.0.1 Pass Wed Mar 26 01:36pm
We should move this over to an idea to see if we can create a more comprehensive report.
I think you are using the Environment Contents report. If you use the Environment Manifest report, you would see something like this :
Instance Date Thu Nov 6 04:46pm
Deployment Date Thu Nov 6 04:46pm
Also, the Environment History report would show you more specifics on each deployment to the selected environment. Regardless, neither of these solve your real problem because in both these cases you would have to be doing a report per environment and not for the instance. So you would have to know which environment you expected the deployment to be on. Again, let's create an idea and we will see if we can come up with a better report.
We had to build SQL queries at our firm in order to extract this information because we were also finding it difficult to get this information.
Just wanted to follow up to say thanks for patch 8. A report feature is now available that answers the cardinal rule:
Cardinal Rule: A deployment tool must answer the question: In what environment is an application (package) baseline (instance) deployed to?