Browsing commits in the web UI at /scm/repo/namspace/repo_name/code/branch/default/changesets returns replacements.flatMap is not a function, see image:
SCM error
I traced this to scm-ui\ui-components\src\repos\changesets\ChangesetDescription.tsx in line 46.
My deployment is in a docker container but I was able to verify the issue on a physical deployment of the application as well. Am I missing a dependency?
edit: The deployed version of scm-manager is 2.3.0 in both cases.
This issue was resolved by updating my browser to a newer version.
Related
i'm trying to deploy my laravel vapor application from my computer, as I always do. But yesterday a got an error:
Whoops! There were some problems with your request.
"You are using an outdated version of Vapor CLI. Please update to the latest version before deploying."
So I updated laravel/vapor-cli from 1.43 to 1.44 (latest now)
But the deployment still fails at the same point.
Tried: composer dump-autoload, composer remove vapor-cli and require again (updated) but always fails at the same point.
I use docker runtime.
The deployment builds the project ok
deploy ok till here
but fails "pushing container image"
==> Pushing Container Image
The push refers to repository [8zzzz4f6h3dz.dkr.ecr.eu-west-3.amazonaws.com/myapp-vapor]
5485100749ee: Preparing
2042d777ff6d: Preparing
...
bfd1896d-0d92-4b72-a8f8-fde92c3ee108: digest: sha256:823b239d4445957e8f7bff478e86c18b023c4d5f7edf9c7339c2e532e67c4780 size: 5557
Whoops! There were some problems with your request.
- You are using an outdated version of Vapor CLI. Please update to the latest version before deploying.
deployment message error
Any ideas on how to solve this situation?
As Laravel Vapor documentation says here
I updated the "local" vapor-cli package.
Once I also updated the "global" package, the deployment finished successfully.
composer global require laravel/vapor-cli --update-with-dependencies
The last container I build on Azure DevOps was with version 2.1.300 of the SDK. After upgrading to .Net Core 2.2 with SDK 2.2.203 I get the error below.
/usr/share/dotnet/sdk/NuGetFallbackFolder/microsoft.aspnetcore.razor.design/2.2.0/build/netstandard2.0/Microsoft.AspNetCore.Razor.Design.CodeGeneration.targets(131,5):
error : rzc generate exited with code 1.
The container still builds successful on my local machine. I tried the suggestion in this post but with the same result. I even went back to version 2.1, but now with the same problem. Any idea what can cause this problem?
Update 09-05-2019
I've created a self hosted agent. It has te same problem, but when I build the docker image myself on the same machine (self hosted agent) the build is successful. I'm out of ideas.
I figured it out. I had multiple views within a components folder. This caused the problem for me. Hope it helps someone.
I created a new .NET Core Console Application with Visual Studio 2017 (RTM). Then added Docker support and got the docker file + compose files just fine. However there are few issues with them.
Docker compose files have version 2 which makes the build fail to the following error message
Microsoft.DotNet.Docker.CommandLineClientException: client version 1.22 is too old. Minimum supported API version is 1.24, please upgrade your client to a newer version.
This can be fixed by manually changing the compose file versions to 2.1. (not sure if valid fix) Then you'll get another error message
MSB4006 There is a circular dependency in the target dependency graph involving target "DockerCleanServiceReferences".
This I have no idea how to fix. I know the error message is due to some configuration that causes circular reference (e.g. post build event that does build)
So, any resources or tips how to package the .NET Core console application into docker container manually? I'm just getting to know Docker so don't assume I know anything of it yet.
Another question, that is there some place where I could get updated versions of these Visual Studio templates or are these known issues?
It turned out the problem for me was having my DockerFile, SLN file, and CSPROJ file all in the same folder. You know how when you create a solution, it asks you if you want to create a subdirectory? If you do not, and your SLN and CSPROJ files share the same folder, inevitably the Docker files will be added to this same folder, creating the circular reference. If your SLN file lives in the directory above your CSPROJ file, the DockerFile et al will be put into your parent directory with the SLN file, and all will be well. This solved it for me.
Can you please check if your Docker for Windows is targeting Linux? It's likely you were targeting Windows container, which is not supported with .NET Core yet.
On my first spin of VS2017 with docker, using the default template, I ran in to the same issue.
I referred to this article - https://blogs.msdn.microsoft.com/containerstuff/2017/03/13/visual-studio-2017-client-version-1-22-is-too-old/
This is what worked for me - As recommended, made this changes in docker-compose project's docker-compose.ci.build.yml :
The 'version' parameter on the top of the file which was set to 2, was change to 2.1
Repeated the same changes on the other files in the project including:
docker-compose.yml
docker-compose.override.yml
docker-compose.vs.debug.yml
docker-compose.vs.release.yml
Regarding your question on how to package a .NET Core console application into a Docker image manually. The https://github.com/dotnet/dotnet-docker-samples are intended to answer that very question. Check them out. If you run into issues with them or have suggestions please log an issue (https://github.com/dotnet/dotnet-docker-samples/issues).
Thanks for the post. We will be adding Nano Server container tooling "soon". Until then, you can work with Linux containers which will give a similar experience.
I have been trying for sometime to get the TFS plugin working, and have had "semi" success.
The parts of the process that use Team Explorer command line client work well (I have defined the TFSPROXY environment variable, which seems to work.)
As soon as the plugin gets to the piece that uses the SDK, I get a stack trace printed, with the main error:
com.microsoft.tfs.core.exceptions.TECoreException: Unknown host somehost.on.corporate.network.
I have tried using the environment variables: HTTP_PROXY, and TFSPROXY. I have also tried adding the registry keys at HKLM/Software/MS/VisualStudio/10.0/TeamFoundation/SourceControl/Proxy (also added v9.0).
My question is: Is there any way to configure proxy settings for the SDK that the plugin is using, or has someone else had success with another alternative?
For anyone else who may be having this issue, I found that it is only the latest versions of the plugin using the SDK (3.0+), and the previous versions (2.0 and less) are using only the command line tool.
So as a workaround, I have downgraded to 2.0 and everything seems to be working correctly now.
We have Jenkins installed and running on a WebSphere Application Server. We recently upgraded the server to version 8.5.5 and switched the profile to use JDK version 1.7. Doing this Jenkins Crashes the WebSphere Application Server and we cannot tell why. Any hints or suggestions on things to look at? Switching the server back to JDK 1.6 seems to work just fine, can Jenkins not run on JDK 1.7 or is it something else?
I'll assume that by crash the websphere application server you mean either a fatal error at startup or a java process crash. Those can have many causes.
Just to give some ideas, it may be related to the fact that you had somewhat customized your JDK install and forgot to re-apply those customization to your new JDK. Or that switching SDK requires you to switch command line options, or that you indeed hit an incompatible class in the stack, or that your process crash because of bad luck, etc.
So please find more information in the logs, either the corresponding stack traces in your WAS server logs or the javacores crash files.
Please also report your jenkins version.
As for JDK 7 compatibility, latest jenkins itself should be compatible, yet some plugins are not
You may also want to read this: https://stackoverflow.com/questions/17411717/jenkins-on-websphere-reports-java-lang-noclassdeffounderror-jenkins-model-jenki. Maybe you have the same issue.
If you indeed find out an incompatibility, please report an issue in jenkins issue tracker and consider updating the Jenkins Websphere wiki.