Added support for pipeline and released in version 2.2

Jesse Glick Mentioned something about this implementation on GitHub

And whoever did this integration seems to have done it incorrectly. There is a dedicated NexusArtifactUploaderStep producing a nexusArtifactUploader step; and NexusArtifactUploader was made to implement SimpleBuildStep, meaning it will appear as an option to the step metastep. You only want to do one or the other, not both.

There are other problems in the integration, especially that nexusPassword is passed as a String, which is insecure (must use Credentials instead), but that does not matter here for purposes of recording what the integration consisted of.

As the most of the piece of logic is common to "step" and "build step" so to use of existing code instead of having another plugin, step for uploading artifacts to nexus has been integrated in this plugin. And also this functionality is different from the existing out of the box step.

This plugin's main goal to upload non-maven artifacts to nexus.

Let me know what are the steps to be taken now. Is that mandate to go as a separate plugin for "step" for pipeline integration.

Will discuss about the credentials later once this closed.

Code changed in jenkins
User: Sverre Moe
Path:
COMPATIBILITY.md
http://jenkins-ci.org/commit/pipeline-plugin/fbb0b831764b9fa1206dbc55419178bab9da887d
Log:
JENKINS-34943 Add nexus to COMPATIBLITY.md

Code changed in jenkins
User: Sverre Moe
Path:
COMPATIBILITY.md
http://jenkins-ci.org/commit/pipeline-plugin/d3107677ecaf93d4dc42c0eacf684b2f44fa4c63
Log:
JENKINS-34943 Add cppcheck to COMPATIBLITY.md

Code changed in jenkins
User: Sverre Moe
Path:
COMPATIBILITY.md
http://jenkins-ci.org/commit/pipeline-plugin/7251c2d835227bd30ba67f010eb0c69d3d3d0ec6
Log:
JENKINS-34943 Update nexus in COMPATIBLITY.md

Supported as of 2.2