pipeline-examples | A collection examples , tips and tricks and snippets | Plugin library

Found the solution:

• ARTIFACTORY_DOCKER_REGISTRY should be IP/Artifactory-Repo-Key/Image:Tag

• HOST should be docker daemon (Docker for windows is localhost:2375)

The process is exactly the same, you just have to change the interface to use the new IPipelineBehavior interface.

The problem was occuring because when the the fat/uber jar was being created, files in META-INF/serivces where being overwritten by duplicate files. Specifically com.fasterxml.jackson.databind.Module where a number of Jackson modules needed to be defined but where missing. These include org.apache.beam.sdk.io.aws.options.AwsModule and com.fasterxml.jackson.datatype.joda.JodaModule. The code in the DirectRunner instantiates the ObjectMapper like so :

FluentValidation does not stop handling your command even if validation fails - it just registers rules.

Mediatr Validation Pipeline checks for existing validation errors and stops sending command - Handler wont fire if errors exist.

But you implemented your own logic - HandleInvalidCommand. You should choose one option - mediatr pipiline or implementing own logic with ModelState.IsValid

I had some similar issue and I switched to basics. If you are using jfrog(which you should) you can simply use the API(https://www.jfrog.com/confluence/display/RTF/Artifactory+REST+API) and hit it with curl, eg:

curl -u ${username}>:${password}@ -X PUT \"${mavenRepo}/${relativeMavenPath}/${serviceName}/${serviceTag}/${serviceName}-${serviceTag}.jar\" -T ${your-jar-name}.jar

Run this command in the directory where your jar exists.

I was able to fix it myself by using emailext plugin on Jenkins instead of mail. The code looks as follows now:

You should got to Manage Jenkins -> In-process Script Approval, find signature of getBuilfDependencies() method and click Approve to approve it. See In-process Script Approval for more information.
Also depending on version of Jenkins pipeline that you use each{} method may not work properly (JENKINS-26481, JENKINS-27421). If your version of Jenkins has those issues try to use old-style for loop or wrap iteration in @NonCPS method.

Jenkins issue 36826 is a feature request for this to happen.

The posts you mention use MediatR 2.x.
MediatR 3.0 has been released not long ago, and has built-in support for pipelines. I would suggest you read the associated documentation.

In short, MediatR now exposes a IPipelineBehavior, and the instances you register in your container will be discovered automatically by MediatR when constructing the handler.

Here's what it could look like in ASP.NET Core: