As per our requirement:
- We get the build package of our solution from TFS online in a .zip format as supported by Octopus.
- We need to publish websites and windows services by using the Upload Package option on the Library tab of Octopus Web Portal.
- Also, we have checked the Automatic Release Creation option for our respective project so that whenever we upload a package through Library tab, a release will be automatically created.
- On clicking deploy for the newly created release, a new version is created, which goes on publishing the package with folder having different version number each time.(Refer Version_Folders.png)
- We want to avoid this versioning at directory levels. Example – Once I upload a package of Website A then I need to publish the deployment to only one folder which is the IIS virtual directory of the respective site.
- Now, if I have a new version package of the same Website A and we upload the same from Library tab, the package should replace the contents of the same IIS Virtual Directory in step 4 and should not create a new version folder for the same.
Kind suggest in order to achieve this requirement.