search

tobania / VSTS.Extension.SqlReportingServices

VSTS Extension for uploading SSRS Reports
MIT License
14 stars 20 forks source link

Deploy only changed rdls #17

Open fabianre opened 7 years ago

fabianre commented 7 years ago

Hi, this is not an issue with your extension but more a question about how to handle the process. Each time my release task runs it will deploy all RDL files in my project., is there a way to only delpoy new/changed RDLs ?

ygeelen-tb commented 7 years ago

Hello @fabianre,

At the bottom of the task in the Advanced section there's an option "Override existing files", could you try that?

fabianre commented 7 years ago

I don't see any change with this option. Still all RDLs are uploaded. Any other idea ?

anton-kirschhock commented 7 years ago

@fabianre What @ygeelen-tb is trying to explain is that there is an option for when you need to override a report. For the time being, there is no option to only upload changed/new files. Maybe one day, who knows :)

ygeelen-tb commented 7 years ago

Indeed sorry for the confusion. Are you experiencing performance issues?

To know which RDL's are changed we'd need to compare with the modified dates on the server, which requires querying the RS web service (SOAP). This could possibly be even slower than just uploading all files..

fabianre commented 6 years ago

At the moment I only use the extension for some DEV tests, so I don't see any performance issues right now. But in future we might have projects which include a lot of reports/ressources, for those it would be better to only upload changed files.

anton-kirschhock commented 6 years ago

well this issue has two more issues: Yes we could filter out all not changed files, which has been updated. Issue is, when you store them in a Version control environment, the modified date is not the correct modified date. In its turn, how would you store which file has been updated when using the VSO-SDK? These are items which cannot be implemented, asfar I am aware of. In the end, you would only need to deploy your reports when you are commiting to development branch, your acceptance branch and your production branch. The latter one only would update once in a while.

Conclusion of what I am trying to say: Yes, I see an usecase, but I cannot see a business value of it. Aswel the implementation would be a hell.

Sorry :(