- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Jan 30 2020
Jan 29 2020
I started to look into it with help of the QUIBA data.
Possibly useful Jenkins plugins:
We also have the possibility to modify the Herald rule that triggers the jobs. For example, if the revision summary contains a certain keyword, trigger a complete rebuild instead of an incremental build. Two disadventages are: Revision creators have to be aware of this possibility, and this is not enough as there may be also some other changes on the master branch since the last build on the build client that affect critical files.
Possible entry points in Jenkions job configuration:
Pushed new branch T27041-MITK_CUSTOM_REVISION_DESC.
Jan 28 2020
Pushed new branch T25947-Unreadable_dicom_node_names.
Not yet closed as branch is not landed in master yet.
Fixed this regression with the propsed in this task. We now go with study and series description.
A more flexible solution like discussed in T19477 would be nice. But will take some time, because it is more complex if done right.
Pushed new branch T27038-CTestSubprojectsInExtensions.
Pushed new branch T27037-CleanUpUnusedComponents.
Jan 27 2020
Pushed new branch T26851-SelectionButton_refresh_on_node_modification.
Jan 25 2020
Unmerged branches in origin/tags/
Unmerged branches that do not match releases/, tags/, personal/, Txxx-, or bug-xxx-
Extracted from the huge list above.
Manual testing and review.
An example of what is now possible has been sent to you.
It's not about identification under the hood but the name of the data in the histogram, i.e. the label of the legend. But it's probably low priority for now.