Code changed in jenkins
User: Jesse Glick
Path:
COMPATIBILITY.md
http://jenkins-ci.org/commit/workflow-plugin/b448a6311ee0b424c92eafbf8b265a40e8bca349
Log:
JENKINS-30121 Noting; closes #189.

Is this intended to be distinct from existing Builder/Publisher implementations in this plugin? In what way?

It should deploy the built artefacts to a repository on an artifactory server. If this can be achieved as easy as with the artifactory plugin with Builder/Publisher then I'd be happy to learn how.

Well the plugin already has a bunch of build steps and/or post-build actions which work in freestyle projects. The question is whether you simply expect some/all of those to work essentially the same way from a Workflow script (via the core step), which just requires implementing SimpleBuildStep and doing some corresponding fixups; or whether you are requesting a brand-new Workflow step with new behavior that has no direct analogue in freestyle projects.

I do not know enough about this plugin’s features to recommend one or the other at the moment. Generally speaking it is easier to maintain a SimpleBuildStep since there is only one code path. In some cases functionality that is necessary in a freestyle project just does not make sense in a Workflow.

The point is, that if I activate "Maven3-Artifactory Integration" in a freestyle project it automatically deploys all artefacts from "Invoke Maven 3" build steps as maven would if mvn deploy would have been called. So if I could also activate this plugin in the same manner in a workflow project I would excpect it also to deploy all artefacts from mvn-workflow-steps. I think for this to work the maven integration (https://issues.jenkins-ci.org/browse/JENKINS-26057) should also be solved, right?

Perhaps, though I have never been clear on the relation of the Maven build step defined in this plugin to the Maven build step defined in Jenkins core (a common source of user confusion).

In the near term, just sh 'mvn deploy' if that is what you want to do. You can use the Config File Provider plugin (2.9.2+) with Workflow to keep a secure per-job settings.xml.

Sure, with mvn deploy I can deploy my artefacts to my artifactory server (or any other maven server like i.e. nexus) but then I can't benefit as easily from the additional features from artifactory like licence check, capture build info or such. Sure I can call these things over the REST API from artifactory but that would be a "workaround". I think artifactory-plugin does exactly that but I do not have to worry about the REST API.