.Net Build, Publish issue in Published code artifact
Hi Team,
We are publishing .net project but some issues in doing the process. Currently we are publishing the code from visual studio working with visual studio but unable to configure the publish code from Teamcity. Please help in this out. Going forward below are the logs i have attached.
Basic Requirement: We want to publish the code one directory (Code arhitechture: DAL: .NET CLass library project, Entity : .NET Class Library, MVC Web application has referred the DAL and Entity class liabrary) we are publishing the web application.
The build is removed from the queue to be prepared for the start
[12:00:47]Collecting changes in 1 VCS root
[12:00:47]Starting the build on the agent EITL28
[12:00:47]Clearing temporary directory: C:\TeamCity\buildAgent\temp\buildTmp
[12:00:47]Publishing internal artifacts (1s)
[12:00:47]Using vcs information from agent file: 2d5de5985c1cf33a.xml
[12:00:47]Checkout directory: C:\TeamCity\buildAgent\work\2d5de5985c1cf33a
[12:00:47]Updating sources: auto checkout (on agent) (3s)
[12:00:51]Step 1/1: Step1 (Visual Studio (sln)) (7s)
[12:00:59]Publishing internal artifacts (4s)
[12:01:03][Publishing internal artifacts] Publishing 1 file using [ArtifactsCachePublisher]
[12:01:03][Publishing internal artifacts] Publishing 1 file using [WebPublisher]
[12:00:59]Publishing artifacts (1m:59s)
[12:00:59][Publishing artifacts] Collecting files to publish: [**=>app1.zip]
[12:01:03][Publishing artifacts] Creating archive app1.zip (1m:51s)
[12:02:55][Publishing artifacts] Publishing 1 file using [ArtifactsCachePublisher]: ** => app1.zip
[12:02:55][Publishing artifacts] Publishing 1 file using [WebPublisher]: ** => app1.zip
[12:02:58]Build finished
Please sign in to leave a comment.
Hi, and sorry for the delay. There are several possibilities here:
-You might be able to have the "Publish" target of the visual studio project to build. If it's properly configured, it should work, but I'm afraid we would need more details if it doesn't. Expand the build log until you can see the publish part of the log and see whether the runner reports any errors there.
-You might want to use an extra step to upload it somewhere, be it via ssh, ftp, or some of the other specific deployers, even third parties such as octopus.