I need some help to determine why my VSTS build agent doesn't create an artifact in the drop folder
I have a solution that contains a website project (not a web application) and a logic project that i'm trying to build the website via VSTS. The build complete's correctly when i reference the solution as part of the "Process" step but nothing is added to the drop folder for the release process.
I have modified my build arguments to look for a publish profile that has been saved to the app_data/PublishProfiles (called vstsbuild) on the website project. The website doesn't have a project file but it does have a website.publishproj file at the root of the website.
Any idea why it won't publish an artifact would be helpful
VSTS Publish Logs
Related
I'm working with WSO2 Identity Server and I'm curious if there is a way to run the product in developer mode without building each component of identity server. I found a way to start the "My Account" component in dev mode by following this tutorial ( https://is.docs.wso2.com/en/5.11.0/develop/setting-up-my-account-in-a-dev-environment/ )
but I want to be able to modify different components such as recovery-portal and authentication-portal by forking and cloning the required github repositories and starting the entire app in developer mode in order to see the code changes in real-time.
AFAIK the developer mode will work only for the MyAccount and Console. You can refer to the doc for more details on that.
The recovery portal, the authentication portal etc. cannot be tried with the developer mode. However, there are two ways that you can try this.
Build the war files manually and add them to the WebApps directory. If the server is running, war file changes will automatically get deployed. If the server is not running, you have to delete the existing directory and restart the server.
You can do the changes to the JSPs that are deployed inside the pack. Once the changes are done, you can save the changes and the changes will automatically get deployed.
I've played with Microsoft Bot Composer and have checked the extensibility points but it looks like it is not possible to deploy the bot to other clouds.
Please confirm my assumption.
My goal is to achieve deploying without additional development if possible.
Deploying a Composer bot is somewhat more complicated than deploying an ordinary Bot Framework bot because the Composer bot is not stored anywhere in a deployable state. Composer must bundle your specific Composer project files together with the centralized Composer runtime in order to create a deployable package.
However, Composer does come with a way to convert your Composer project into an ordinary bot project that can be deployed just like any web app. This is called exporting (or ejecting) the runtime. You can find out how to do that here.
To export your bot runtime:
Navigate to the Project Settings page of your Composer and find the Custom runtime section.
From the Custom runtime section, toggle Use custom runtime then select Get a new copy of the runtime code.
In the pop-up window select C# and select Okay. A copy of your bot's runtime will be added to the bot's project folder and can
be accessed in the following directory: C:\Users\UserName\Documents\Composer\bot\runtime.
The following errors pop in the log when publishing web project to folder.
....
Publishing folder /...
Publishing folder bin...
Publishing folder bin/es...
Publishing folder bin/roslyn...
Unable to add 'bin/roslyn/System.IO.FileSystem.dll' to the Web site. Unable to add file 'bin\roslyn\System.IO.FileSystem.dll'. The process cannot access the file because it is being used by another process.
Unable to add 'bin/roslyn/System.IO.FileSystem.Primitives.dll' to the Web site. Unable to add file 'bin\roslyn\System.IO.FileSystem.Primitives.dll'. The process cannot access the file because it is being used by another process.
Unable to add 'bin/roslyn/System.Reflection.Metadata.dll' to the Web site. Unable to add file 'bin\roslyn\System.Reflection.Metadata.dll'. The process cannot access the file because it is being used by another process.
Unable to add 'bin/roslyn/System.Security.Cryptography.Algorithms.dll' to the Web site. Unable to add file 'bin\roslyn\System.Security.Cryptography.Algorithms.dll'. The process cannot access the file because it is being used by another process.
Unable to add 'bin/roslyn/System.Security.Cryptography.Primitives.dll' to the Web site. Unable to add file 'bin\roslyn\System.Security.Cryptography.Primitives.dll'. The process cannot access the file because it is being used by another process.
Unable to add 'bin/roslyn/System.ValueTuple.dll' to the Web site. Unable to add file 'bin\roslyn\System.ValueTuple.dll'. The process cannot access the file because it is being used by another process.
Unable to add 'bin/roslyn/VBCSCompiler.exe' to the Web site. Unable to add file 'bin\roslyn\VBCSCompiler.exe'. The process cannot access the file because it is being used by another process.
Publishing folder bin/zh...
...
Publishing folder Views/WFDefs...
Publish failed. Target file://machine/d$/PATH.
If i publish using web publish it works, but the real target doesn't support web publishing.
Note: VBCSCompiler is not running.
I had the same problem with my application with Visual Studio community 2017. In my case the solution was simple, I only deleted all the files inside the directory bin (C:\Projects\DotNet\ApplicationName\bin) and after I recompiled the application.
I hope it can help you.
Had this same issue in Visual Studio 2017 Community Edition. As your question came up in Google but no answer, I thought I'd add to it.
I found Process Explorer from Sysinternals helped me a bunch.
Open sysinternals and go to Find -> Find Handle or DLL... or (Ctrl + F) and search the file that's being held open. In my case "System.IO.FileSystem.dll"
The search results showed two instances of MSBuild and one VBCSCompiler was hanging onto the files. Worst case, I just killed the process tree, built the project and all was well again.
Related answer: https://serverfault.com/questions/1966/how-do-you-find-what-process-is-holding-a-file-open-in-windows
If you try to publish asp.net web app in Azure and getting above error then try to UPDATE the Microsoft.CodeDom.Providers.DotNetCompilerPlatform package to V1.0.7 or later. Initially, in your application, there will be Microsoft.CodeDom.Providers.DotNetCompilerPlatform version 1.0.5 then uninstall and then install the latest version V 1.0.7 or later of it. Clean your solution and build. Now you will be able to publish your web app in Azure using Visual Studio 2017.
In Resource folder I have a folder that contains many JS files. so while building the Application can I someway edit the build so that the only files which I need at that time should build rest of the files will be ignored. Is this possible in Titanium
The only way I found out that was applying resource filter on the project. But that is the manual task.
By applying the resource filter only the selected resources will get build and rest will be ignored..
I've set up a number of build machines, but I always manually edited the XSL files in the web dashboard so that the build report includes a link to the created output package (typically a ZIP file).
Is there a better way (for example a plug-in) to include a link? How do you get at the finished product that CCNet exists for?
Example:
Copy the build package in a folder accessible for web browsing.
Example in ccnetlive
http://ccnetlive.thoughtworks.com/CCNet-builds/1.4.4/
The link is displayed in this page with the tag <externalLinks> :
http://ccnetlive.thoughtworks.com/ccnet/server/CCNet%20Live/project/CCNet%201.5/ViewProjectReport.aspx
Take a look at the recently-added Package Publisher.
Update: Note that with CruiseControl.Net 1.5, the packages are available through the cctray application. There is also a Package List package that can be added from the admin screen. I suspect this will show the package links as well.