-
Notifications
You must be signed in to change notification settings - Fork 4
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
Project & Enviroment Reffrencing #6
Comments
Are you referring to #2 ? |
Yes, it is similar to #2. When the the option to 'Drop project before deploy' is unchecked the environment should only be added and referenced if it doesn't already exist. If the environment already exists then it should validate the config XML/JSON against the variables within the environment, either dropping ones which no longer exist, creating new variables which are not present in the environment or amended variable values if they differ. Currently, it still looks to add the referencing between an environment and the project which is causing it to error as it already exists. I hope i've successfully explained the issue. |
OK, thanks. I'll check and address that together with #5 |
Hi, |
Being an open source project it depends on my free time and energy. So sorry, no commitments or ETA. If this is important for you, please get in touch with me in private via http://blog.majcica.com/contact/ |
I understand, thank you. |
@whits91 I think I found the reason for your issue and wrote some code that should solve it. Unfortunately, I have no way to test it at the moment. Let me know |
@mmajcica I'm struggling to apply your change to TFS cloud. I don't foresee being able to actively test it without it being published within the marketplace - Sorry |
Hi @whits91 In this way a new version of the task will be uploaded manually into VSTS. Later once I do publish the new version of extension, it will overwrite this one. Would you be so kind to try it? Thanks |
@whits91 any updates? |
Hi Mario; Hope you are doing well. Then we checked the option of "Drop project before deploy", and deploy the project, then it works. I test deployment with unchecked the option of "Drop project before deploy", and I deleted the reference in the SSIS DB with below sql.
Thanks every much. |
Hi,
I've tested this, and there's an issue with the environment being created:
Exception calling "Add" with "2" argument(s): "An entry with the same key already exists." An entry with the same key already exists.
This is because the referencing between environment and project already exists.
The text was updated successfully, but these errors were encountered: