Custom Report - which data sources/sets are applicable?
Hi - I am interested in creating a custom report in RTC, but am having some trouble figuring out how to access the data that I want in the report.
I did some searching on the jazz.net forums and the Reports TWiki (https://jazz.net/wiki/bin/view/Main/ReportsMain) but haven't found any place where the Data Warehouse "SNAPSHOTS" and "Tables" are defined in detail. This makes it very difficult to figure out which to use. Without it, I am essentially reduced to trial and error... So if this exists, can someone please point me to it?
I understand that I can list all tables under "Administer Data Warehouse" on the web client. However this just give the data item field names, no detailed description. Since the field names are somewhat ambiguous, this is not entirely helpful.
The report I am trying to create is this - It is a report that is required for a security audit. We need to know the date each change set was delivered to a stream, it's comment, and the contributer. The output should be a table.
Thanks,
--Carl
I did some searching on the jazz.net forums and the Reports TWiki (https://jazz.net/wiki/bin/view/Main/ReportsMain) but haven't found any place where the Data Warehouse "SNAPSHOTS" and "Tables" are defined in detail. This makes it very difficult to figure out which to use. Without it, I am essentially reduced to trial and error... So if this exists, can someone please point me to it?
I understand that I can list all tables under "Administer Data Warehouse" on the web client. However this just give the data item field names, no detailed description. Since the field names are somewhat ambiguous, this is not entirely helpful.
The report I am trying to create is this - It is a report that is required for a security audit. We need to know the date each change set was delivered to a stream, it's comment, and the contributer. The output should be a table.
Thanks,
--Carl
5 answers
Rafik,
Is there any other way to access this type of data?
We are currently conducting a trial of RTC to evaluate it against our requirements prior to adoption within our company. It is absolutely necessary for us to create such a report or something very similar to it. The inability to do this could be a deal-breaker for us.
Is there a "creative" way to tie a log of contributions (change sets) to users?
Thanks,
--Carl
Is there any other way to access this type of data?
We are currently conducting a trial of RTC to evaluate it against our requirements prior to adoption within our company. It is absolutely necessary for us to create such a report or something very similar to it. The inability to do this could be a deal-breaker for us.
Is there a "creative" way to tie a log of contributions (change sets) to users?
Thanks,
--Carl
Probably the easiest way would be through the WebUI.
Go to the source control tab for your project area, select the stream of
interest, and the component in that stream.
Clicking on the "History" button gives you the list of change-sets
delivered to that stream, with the date, comment, and contributor.
If you want to generate a report periodically, have a script do a "GET"
on that URL, and save the output to a file.
Would that handle it your use case?
Cheers,
Geoff
On 8/16/2010 6:37 PM, egghead9 wrote:
Go to the source control tab for your project area, select the stream of
interest, and the component in that stream.
Clicking on the "History" button gives you the list of change-sets
delivered to that stream, with the date, comment, and contributor.
If you want to generate a report periodically, have a script do a "GET"
on that URL, and save the output to a file.
Would that handle it your use case?
Cheers,
Geoff
On 8/16/2010 6:37 PM, egghead9 wrote:
Rafik,
Is there any other way to access this type of data?
We are currently conducting a trial of RTC to evaluate it against our
requirements prior to adoption within our company. It is absolutely
necessary for us to create such a report or something very similar to
it. The inability to do this could be a deal-breaker for us.
Is there a "creative" way to tie a log of contributions
(change sets) to users?
Thanks,
--Carl
Geoff,
Thanks - it looks like the contents of the "history" will meet our reporting needs. In thinking about scripting this, we'd ideally like to have the script run periodically and automatically to gather the "report."
To enable full automation (i.e. not requiring a user, who is logged into the repository, to run the script), it appears that we'll have to figure out a way to provide repository credentials via the script. Is the best approach something like trying to using wget with cached authentication cookies, or is there a better way to accomplish this?
Thanks for you help!
--Carl
Thanks - it looks like the contents of the "history" will meet our reporting needs. In thinking about scripting this, we'd ideally like to have the script run periodically and automatically to gather the "report."
To enable full automation (i.e. not requiring a user, who is logged into the repository, to run the script), it appears that we'll have to figure out a way to provide repository credentials via the script. Is the best approach something like trying to using wget with cached authentication cookies, or is there a better way to accomplish this?
Thanks for you help!
--Carl
I'm going to have to forward this question to someone who knows (:-) ...
can someone else out there help Carl with the authentication question?
On 8/18/2010 2:37 PM, egghead9 wrote:
can someone else out there help Carl with the authentication question?
On 8/18/2010 2:37 PM, egghead9 wrote:
Geoff,
Thanks - it looks like the contents of the "history" will
meet our reporting needs. In thinking about scripting this, we'd
ideally like to have the script run periodically and automatically to
gather the "report."
To enable full automation (i.e. not requiring a user, who is logged
into the repository, to run the script), it appears that we'll have
to figure out a way to provide repository credentials via the script.
Is the best approach something like trying to using wget with cached
authentication cookies, or is there a better way to accomplish this?
Thanks for you help!
--Carl