You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Is it possible to change diff algorithm in FishEye/Crucible?
Consider the following case.
We have a text file shown below.
Brief Info Type : Rule-Obj-Model Id : TVSOrg-TVSApp-Work UndefinedParamDt Label : DT with undefined parameters Avail : Yes RuleSet : TVSApp:01-01-01 Check-In : NJA-405 CoR. Diff-algorithm in FishEye/Crucible Warnings Informational [Ninja] The following parameters are used without being declared on 'Parameters' tab: label2. Definition 1 : [Set] Param.label1 [equal to] "defined" 2 : [Set] .pyLabel [equal to] "New Value" 3 : [Set] Param.label2 [equal to] "undefined" Call superclass data transform: true Parameters label1 : String : No : IN : "" : defined param History Description Not declared parameter is used
If we insert row in [Definition] section between row #2 and row #3 -- see changed file below.
Brief Info Type : Rule-Obj-Model Id : TVSOrg-TVSApp-Work UndefinedParamDt Label : DT with undefined parameters Avail : Yes RuleSet : TVSApp:01-01-01 Check-In : NJA-405 CoR. Diff-algorithm in FishEye/Crucible Warnings Informational [Ninja] The following parameters are used without being declared on 'Parameters' tab: label2. Definition 1 : [Set] Param.label1 [equal to] "defined" 2 : [Set] .pyLabel [equal to] "New Value" 3 : [Set] .pyNote [equal to] "Absolutely New Value" 4 : [Set] Param.label2 [equal to] "undefined" Call superclass data transform: true Parameters label1 : String : No : IN : "" : defined param History Description Not declared parameter is used
Notice, that row numbers are changed respectively.
Then FishEye treats such change as removal of row #3 and addition of a new row and row being a copy of row #3 -- see screenshot below.
Is it possible to customize diff algorithm to treat such change as addition of a new row between two existing that were slightly modified (row numbers were chaged).
I'm afraid it's not possible at the moment, vote on and watch the https://jira.atlassian.com/browse/CRUC-7491 issue please to get updated when this gets implemeted.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.