Classic ASP Setup
Hello,
We use TeamCity with our MVC projects, but have several Classic ASP sites that we want to deploy to our test server using TeamCity and Octopus.
However, when setting up a TeamCity project it requests a .SLN solution file, which ASP doesn't really have.
Can I simply create an Empty Solution in VS2017 and then add all of my files, then use that SLN file in TeamCity? Will it deploy via Octopus using this setup?
Or is there a better/different tool that we can use to deploy a Git branch to our test server?
Thanks,
Chris
Please sign in to leave a comment.
Hi Chris,
I'm not fully familiar with the way ASP sites are published, but I might be able to give you some pointers:
-If they don't require compilation or anything of sorts, then you should be able to simply deploy it. Set the VCS Root and the files will be automatically picked up, then proceed with deployment however you normally do it.
-If your deployment build configuration requires artifact dependencies to pick up the files to send, you can always create a dummy one that simply takes the files from VCS and publishes it as an artifact.
-Octopus has a plugin that provides integration with their services. I'm unfortunately unaware of how it works exactly, you might want to check their docs on how to deploy your projects with their plugin. We have some guidance here but I can't tell how well it adapts to your scenario. https://blog.jetbrains.com/teamcity/2015/11/automating-deployments-with-teamcity-and-octopus-deploy/
-If it needs to be pre-compiled, you should be able to compile either via an equivalent step, or a script that performs the compilation.
If I missed something, please feel free to expand on what exactly you are doing
Denis,
The pages/site should simply be deployed like static HTML files. No compilation needed. I just need to commit the changes to Git, then have TeamCity pull the branch and deploy directly to the server via Octopus.
Not sure what an artifact is. The guy who setup our TeamCity server and Octopus integration is no longer with the company, so I am trying to learn as I go.
I still need to look into the empty .SLN file for Visual Studio, as it may resolve my issues.
Thanks for the info, though.
Hi Chris,
an artifact is simply any file https://confluence.jetbrains.com/display/TCD10/Build+Artifact. While the article mentions "produced by the build", technically you can also post artifacts that simply existed in the repository even if they weren't made by your build.
I would suggest taking a look at the octopus plugin if you are using octopus for deployment, it will probably simplify the process.
This said, if you have the files in version control, you will have direct access to the files simply by adding the VCS Root to the build configuration, so you should only need to worry about how to deploy them, which is obviously specific on your infrastructure.
Hope this helps, if you have any further question, please feel free to follow up.