I created a release in VSTS and deploy, but I got the "Path must be a string" error. Does anyone has tried using the latest release of Artifactory ?
The latest JFrog-Artifactory-VSTS-Extension v1.0.4 include a fix for that issue.
It uses 'System.DefaultWorkingDirectory' instead of 'Agent.BuildDirectory'.
I had the same issue, and I found out that the task doesn't work in release pipelines, only in build pipelines, since it's looking for the Agent.BuildDirectory variable.
Related
I am trying to setup JFrog Pipelines. I am new to this so starting small with a pipleline that just has a single npm build step. The source code is taken from github. When I run the pipeline, I get a 404 not found error in the artifactory_configure task. I double checked the Artifactory Integration but the error persists. Any ideas on how to solve it.
Please make sure that you include the Artifactory context as part of the URL when creating the Artifactory integration. For example:
https://xxx.jfrog.io/artifactory
i git clone this repository, and build it in android studio 3.4. it gives me such error:
Method com/github/jengelman/gradle/plugins/shadow/internal/DependencyFileCollection.getBuildDependencies()Lorg/gradle/api/tasks/TaskDependency; is abstract
so what's wrong with it?
Per https://github.com/johnrengelman/shadow/issues/447, just update dependencies.gradle's shadowPluginVersion to the latest (currently 5.1.0) and things should start working again.
I just installed a clean install of the new .NET Core SDK on a CentOs 7 box. I had a different Linux VM I was running to test this and received the same error there.
I am building my application in VS 2017 on a Windows box and copying the project file over to the Linux box to test it. I am coming from netframework environment and trying to learn dotnetcore so I am sure this is probably just a newb issue. Here is what I am doing.
I run a dotnet restore, which works without error.
I run a dotnet build, which I receive a
Build succeeded.
0 Warning(s)
0 Error(s)
Then I run a dotnet run and receive the following error:
Error:
An assembly specified in the application dependencies manifest (apf-ws.deps.json) was not found:
package: 'System.Text.Encoding.CodePages', version: '4.3.0'
path: 'runtimes/unix/lib/netstandard1.3/System.Text.Encoding.CodePages.dll'
Nowhere in my code do I actually reference any type of Encoding explicitly. I have tried including System.Text.Encoding.CodePages in my project to see if that would add a reference and bring in the library to ignore the one it is looking for, but it doesn't help. Anyone have any ideas of what would be causing this?
I tried several things before wiping the directory out in Linux and copying the files over again. In doing so it seemed to fix the problem.
I recently added the new .NET compiler NuGet packages (Microsoft.CodeDom.Providers.DotNetCompilerPlatfor) to an existing older MVC.NET website. Now when trying to publish the website I get the following exception:
Could not find a part of the path …
\obj\DEV\AspnetCompileMerge\Source\bin\roslyn\csc.exe'
I have tried everything mentioned in this question, but nothing worked. It is, after all, a slightly different problem. The problem mentioned in that post is build exceptions, my solution builds fine locally. Uninstalling the NuGet packages works, but that's not really a solution.
The issue is basically the same as this one, but that also has no solution.
Publish output:
4>------ Publish started: Project: Jdn.ArticleCatalogue.Web, Configuration: DEV Any CPU ------
4>Connecting to \\vm-arcawebdev01\WEBSITES\ArticleCatalogue...
4>Transformed Web.config using D:\DOTNET\Local\Logistics.Web\Portal\DEV\Application Projects\Article Catalogue\Jdn.ArticleCatalogue.Web\Web.DEV.config into obj\DEV\TransformWebConfig\transformed\Web.config.
4>Copying all files to temporary location below for package/publish:
4>obj\DEV\AspnetCompileMerge\Source.
4>C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_compiler.exe -v / -p "D:\DOTNET\Local\Logistics.Web\Portal\DEV\Application Projects\Article Catalogue\Jdn.ArticleCatalogue.Web\obj\DEV\AspnetCompileMerge\Source" "D:\DOTNET\Local\Logistics.Web\Portal\DEV\Application Projects\Article Catalogue\Jdn.ArticleCatalogue.Web\obj\DEV\AspnetCompileMerge\TempBuildDir" -keyfile "..\..\..\Solution Items\Jdn.LogisticsPortal.snk"
4>ASPNETCOMPILER(0,0): Error ASPRUNTIME: Could not find a part of the path 'D:\DOTNET\Local\Logistics.Web\Portal\DEV\Application Projects\Article Catalogue\Jdn.ArticleCatalogue.Web\obj\DEV\AspnetCompileMerge\Source\bin\roslyn\csc.exe'.
Any ideas on how to solve this one?
This was a known issue whereby the Roslyn binary wasn't being copied correctly to the publish directory. It should be fixed if you install Microsoft.CodeDom.Providers.DotNetCompilerPlatform 1.0.7.
There seem to be some residual issues which are being tracked here.
Same problem accourred to me while publish MVC .NET application to my local path. I solved the problem delete Microsoft.CodeDom.Providers.DotNetCompilerPlatform by nuget package.
Recently I need to deploy something on Karaf. I use Karaf 3.0.2 and event try 4.0.0M1. Both are not able to install war feature. Once I type feature:install war in console after Karaf start-up.
3.0.2 gives me:
Error executing command: Error resolving artifact org.apache.servicemix.specs:org.apache.servicemix.specs.activation-api-1.1:jar:2.2.0: Could not find artifact org.apache.servicemix.specs:org.apache.servicemix.specs.activation-api-1.1:jar:2.2.0
4.0.0M! gives me:
Erroe executing command: Error
I try to delete Maven and reinstall it. The issue is still there. It's not happened on other machine.
It's a strange issue. Could anyone meet it ever? Could anyone help me out?
As it works on the other machines, it's something on that certain machine.
Without much more details on the setup I'm using assumptions here.
1) No Network connection to the central repo
2) Using a Proxy wich isn't configured or configured wrong on the server
3) Using a nexus with credentials and those aren't configured or configured wrong
I encountered the same issue and it was because there were mirrors defined in my Maven settings.xml (due to usage in another project). After I commented them out I was able to install the karaf war deployer.