It would be very useful to have the trend configurable by a predicate.
We have a job that builds many different projects, and having the trend comparing to "previous build" is useless. We'd like to compare to "previous build with the same value of PROJECT parameter / env variable".
The coverage plugin does not select the reference build on its own, it delegates that part to an implementation of the forensics-api plugin. You can use the git-forensics plugin as an example on how to implement a reference build finder that chooses builds on environment variables.
Ulli Hafner
added a comment - The coverage plugin does not select the reference build on its own, it delegates that part to an implementation of the forensics-api plugin. You can use the git-forensics plugin as an example on how to implement a reference build finder that chooses builds on environment variables.
Unassigned
Orgad Shaneh
Votes:
0Vote for this issue
Watchers:
2Start watching this issue
Created:
Updated:
{"errorMessages":["jqlTooComplex"],"errors":{}}
[{"id":-1,"name":"My open issues","jql":"assignee = currentUser() AND resolution = Unresolved order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":true},{"id":-2,"name":"Reported by me","jql":"reporter = currentUser() order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":true},{"id":-4,"name":"All issues","jql":"order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-5,"name":"Open issues","jql":"resolution = Unresolved order by priority DESC,updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-9,"name":"Done issues","jql":"statusCategory = Done order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-3,"name":"Viewed recently","jql":"issuekey in issueHistory() order by lastViewed DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-6,"name":"Created recently","jql":"created >= -1w order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-7,"name":"Resolved recently","jql":"resolutiondate >= -1w order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-8,"name":"Updated recently","jql":"updated >= -1w order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false}]
The coverage plugin does not select the reference build on its own, it delegates that part to an implementation of the forensics-api plugin. You can use the git-forensics plugin as an example on how to implement a reference build finder that chooses builds on environment variables.