Report issues in M4
Hi,
We have a couple of issues related to reporting
(we are currently using M4)
1.
After creating a new report-template for a team (for instance Build Health:
D:\jazz\client\eclipse\jazz\reports\eclipse\plugins\com.ibm.team.examples.reports.common_0.6.0.I20071130-1432\Build Health.rptdesign
and opening it to edit the parameters, the team-area and build-defintion selection-boxes are both empty.
2.
When adding a trend report to a dashboard (for instance "open work items by priority") and opening it to configure it we get a java error:
Parameter loading failed: : null
com.ibm.team.reports.service.internal.ReportService.getParameterGroupValues(ReportService.java:942)
...etc...
3.
When enable-ing "preferences-team-jazzsourcecontrol-changes" "show reports section in stream editor"
we get:
The repository doesn't contain historical information about this stream. Please contact your repository administrator for help on enabling historical data collection.
I suppose I need to turn something "on" on the server ?
thanks
Daan.
We have a couple of issues related to reporting
(we are currently using M4)
1.
After creating a new report-template for a team (for instance Build Health:
D:\jazz\client\eclipse\jazz\reports\eclipse\plugins\com.ibm.team.examples.reports.common_0.6.0.I20071130-1432\Build Health.rptdesign
and opening it to edit the parameters, the team-area and build-defintion selection-boxes are both empty.
2.
When adding a trend report to a dashboard (for instance "open work items by priority") and opening it to configure it we get a java error:
Parameter loading failed: : null
com.ibm.team.reports.service.internal.ReportService.getParameterGroupValues(ReportService.java:942)
...etc...
3.
When enable-ing "preferences-team-jazzsourcecontrol-changes" "show reports section in stream editor"
we get:
The repository doesn't contain historical information about this stream. Please contact your repository administrator for help on enabling historical data collection.
I suppose I need to turn something "on" on the server ?
thanks
Daan.
8 answers
Hello,
Regarding 1 and 3:
Jazz provides a data warehouse, as well as an extensible mechanism for gathering information to store in the data warehouse at periodic times. Out of the box, snapshots are provided which aggregate and store various data about work items, source control, and builds. The reporst retrieve data from this data warehous.
Be default the data warehous is updated once a day. Is it possible that the server was not running 24 hours and therefore there is no historical data in the db?
Regarding 1 and 3:
Jazz provides a data warehouse, as well as an extensible mechanism for gathering information to store in the data warehouse at periodic times. Out of the box, snapshots are provided which aggregate and store various data about work items, source control, and builds. The reporst retrieve data from this data warehous.
Be default the data warehous is updated once a day. Is it possible that the server was not running 24 hours and therefore there is no historical data in the db?
Hi Daan,
See Elisabeth's posts in this thread.
1. It's likely that the data warehouse snapshot has not run yet to
populate these fields. Alternatively, this would also happen if the data
warehouse snapshot *did* run but there were no build results for it to
process.
2. See the link in Elisabeth's reply.
3. It's likely that the snapshot simply hasn't run yet, and hence there
is no data in the warehouse to present.
To run the snapshots manually, go to the Reports Web UI, log in as a
user who has the JazzDWAdmins repository permission, click "Administer
Data Warehouse" in the left nav, and click "Update All Snapshot Data".
Hope this helps.
james
dvdmunni wrote:
See Elisabeth's posts in this thread.
1. It's likely that the data warehouse snapshot has not run yet to
populate these fields. Alternatively, this would also happen if the data
warehouse snapshot *did* run but there were no build results for it to
process.
2. See the link in Elisabeth's reply.
3. It's likely that the snapshot simply hasn't run yet, and hence there
is no data in the warehouse to present.
To run the snapshots manually, go to the Reports Web UI, log in as a
user who has the JazzDWAdmins repository permission, click "Administer
Data Warehouse" in the left nav, and click "Update All Snapshot Data".
Hope this helps.
james
dvdmunni wrote:
Hi,
We have a couple of issues related to reporting
(we are currently using M4)
1.
After creating a new report-template for a team (for instance Build
Health:
D:\jazz\client\eclipse\jazz\reports\eclipse\plugins\com.ibm.team.examples.reports.common_0.6.0.I20071130-1432\Build
Health.rptdesign
and opening it to edit the parameters, the team-area and
build-defintion selection-boxes are both empty.
2.
When adding a trend report to a dashboard (for instance "open
work items by priority") and opening it to configure it we get a
java error:
Parameter loading failed: : null
com.ibm.team.reports.service.internal.ReportService.getParameterGroupValues(ReportService.java:942)
..etc...
3.
When enable-ing "preferences-team-jazzsourcecontrol-changes"
"show reports section in stream editor"
we get:
The repository doesn't contain historical information about this
stream. Please contact your repository administrator for help on
enabling historical data collection.
I suppose I need to turn something "on" on the server ?
thanks
Daan.
James, Elizabeth,
regarding 1,3:
We are on M4 for a week now, so the snapshot should have been run for a couple of times by now. (I also tried the manual update using the admin web-ui).
Is there a way to see what data is available in the datawarehouse ?
(there are also quite some build results; we run a build on our test-setup each 10 minutes).
regarding 2:
From what I understand in the discussion in the other thread, this has to do with some bug in the M3->M4 upgrade ? It is not entirely clear wether this will be automatically fixed when we upgrade from M4 to Beta2...
thanks
Daan.
regarding 1,3:
We are on M4 for a week now, so the snapshot should have been run for a couple of times by now. (I also tried the manual update using the admin web-ui).
Is there a way to see what data is available in the datawarehouse ?
(there are also quite some build results; we run a build on our test-setup each 10 minutes).
regarding 2:
From what I understand in the discussion in the other thread, this has to do with some bug in the M3->M4 upgrade ? It is not entirely clear wether this will be automatically fixed when we upgrade from M4 to Beta2...
thanks
Daan.
Daan, I have a question:
- Is this a new database or a database migrated from a pre-M4 server?
- When you install Beta2, I would recommend running a migration of the repo. This will auto-deploy and auto-update any new or modified reports. If not, you would have to manually redeploy all report templates for all projet areas.
- Is this a new database or a database migrated from a pre-M4 server?
- When you install Beta2, I would recommend running a migration of the repo. This will auto-deploy and auto-update any new or modified reports. If not, you would have to manually redeploy all report templates for all projet areas.
Is this a new database or a database migrated from a pre-M4 server?
This is a database upgraded from M3 (and before that from M2 and M1 since we have been following each successive milestone)
I noticed there is no specific description for upgrading from M4 to Beta2 (there is one for Beta1->Beta2 and for M3->Beta2), so I asume this is straightforward ?
regards
Daan.
Daan, It should be a straightforward migration from M4 to Beta2. But I am
advising you to make a backup before doing any migration. We have never
tested a M4 to Beta2 migration. So, let us know if you run into any issues.
Rafik and James, if there are other ways to fix the reports that are not
deployed, I would advice them to do so.
------ Balaji
"dvdmunni" <daan.van.der.munnik@philips-dot-com.no-spam.invalid> wrote in
message news:fk64hv$295$1@localhost.localdomain...
advising you to make a backup before doing any migration. We have never
tested a M4 to Beta2 migration. So, let us know if you run into any issues.
Rafik and James, if there are other ways to fix the reports that are not
deployed, I would advice them to do so.
------ Balaji
"dvdmunni" <daan.van.der.munnik@philips-dot-com.no-spam.invalid> wrote in
message news:fk64hv$295$1@localhost.localdomain...
Is this a new database or a database migrated from a pre-M4 server?
This is a database upgraded from M3 (and before that from M2 and M1
since we have been following each successive milestone)
I noticed there is no specific description for upgrading from M4 to
Beta2 (there is one for Beta1->Beta2 and for M3->Beta2), so I
asume this is straightforward ?
regards
Daan.
I've added a section to our FAQ describing how to deploy these reports
manually, rather than running a migration.
https://jazz.net/wiki/bin/view/Main/ReportsFAQ
james
Balaji Krish wrote:
manually, rather than running a migration.
https://jazz.net/wiki/bin/view/Main/ReportsFAQ
james
Balaji Krish wrote:
Daan, It should be a straightforward migration from M4 to Beta2. But I am
advising you to make a backup before doing any migration. We have never
tested a M4 to Beta2 migration. So, let us know if you run into any issues.
Rafik and James, if there are other ways to fix the reports that are not
deployed, I would advice them to do so.
------ Balaji
"dvdmunni" <daan.van.der.munnik@philips-dot-com.no-spam.invalid> wrote in
message news:fk64hv$295$1@localhost.localdomain...
Is this a new database or a database migrated from a pre-M4 server?
This is a database upgraded from M3 (and before that from M2 and M1
since we have been following each successive milestone)
I noticed there is no specific description for upgrading from M4 to
Beta2 (there is one for Beta1->Beta2 and for M3->Beta2), so I
asume this is straightforward ?
regards
Daan.