TASTE bugtrack - Taste
View Issue Details
0000869Taste[All Projects] TASTE-IV/DVpublic2019-05-15 10:092021-06-22 14:00
shd01 
ellidiss 
normalminoralways
closedfixed 
0000869: Build can be started with unsaved deployment view
If a build is started after changes to the interface view, a prompt is given to ask the user if they want to save. The same is not true of the deployment view, even though it is saved by the same action as the interface view.
1. Create a project with a blank deployment view. 2. Attempt to build - fails as objects not assigned to partitions 3. Add a partition in deployment view, assign to partitions, but do not save 4. Attempt to build - build starts but fails as objects not assigned to partitions
No tags attached.
Issue History
2019-05-15 10:09shd01New Issue
2019-05-15 10:09shd01Statusnew => assigned
2019-05-15 10:09shd01Assigned To => ellidiss
2019-05-21 14:39ellidissNote Added: 0003640
2021-06-10 08:15ellidissNote Added: 0003784
2021-06-10 08:15ellidissStatusassigned => resolved
2021-06-10 08:15ellidissResolutionopen => fixed
2021-06-22 14:00maximeStatusresolved => closed

Notes
(0003640)
ellidiss   
2019-05-21 14:39   
I successfully reproduce the problem and analyze the code responsible for the saving operation. There is a limit in the external tool implementation : an external tool depends on one context only (IV, DV, ...). In our case, the iv is saved and only the iv state is checked. However, the build operation concern at least 2 contexts : the DV and IV. The external tools mechanism shall be updated in order to solve the problem.
(0003784)
ellidiss   
2021-06-10 08:15   
this fix is available in the 2.3.2 version