Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deploy only changed rdls #17

Open
fabianre opened this issue Jul 25, 2017 · 6 comments
Open

Deploy only changed rdls #17

fabianre opened this issue Jul 25, 2017 · 6 comments

Comments

@fabianre
Copy link

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
Copy link
Collaborator

Hello @fabianre,

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

@fabianre
Copy link
Author

fabianre commented Aug 3, 2017

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

@anton-kirschhock
Copy link
Contributor

@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
Copy link
Collaborator

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
Copy link
Author

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
Copy link
Contributor

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 :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants