On 23 September 2014 18:37, Curtis Rueden <[email protected]> wrote: > Hi James, > > > I can no longer see "Deploy artifacts to Maven repository" > > as a post-build action. > > Just add a build step that does "mvn deploy" or similar. >
See this for me is a post-build action. I guess Jenkins doesn't see it that way. Raises the question of how to use the release plugin since that performs deployment itself. > > > Dare I ask what I'm missing having chosen the full-fat option..? > > If you're asking what you cannot do with freeform jobs: I don't know of > anything. I think the Maven-style job is just a convenience to get very > basic CI set up as quickly as possible, for people without much technical > know-how. > I rather suspect despite it's technical weaknesses, it's the de-facto unless an organisation hits on it's limitations. I've not spotted a tutorial on building maven projects with Jenkins that does not use the Maven style job. We have virtually all our jobs as Maven style ones - we've not hit any limitations yet.
