My plan, once I come up with a better name for literate, is to have that project type be able to provide smart builds of Maven projects with near zero configuration (other than adding a marker file to say literate should consider this as a valid branch)
I see s/workflow/pipelines/g as the project type for the 10% of jobs that need to do more complicated things such as orchestrating across multiple source control systems, deploying into production, etc. For the 90% of jobs you just want a simple build... I would have thought that adding a README.md to your project with content like # How to build ``` mvn clean verify ``` Would not be objectionable to anyone, and would advance the future maintainability of your projects (who doesn't want a README file in every project that at least tells you what command to type in order to build the project... well from the lack of feedback on literate it would seem that very few people are interested in that README file... I suspect it is a form of job security through obscurity <https://www.doc.ic.ac.uk/~susan/475/unmain.html> but whatever) So instead it seems that literate needs a sexier name and some way to obscure the "how to build" and "what you need to build" information... # Introduction This is the whiz-bang connector module to connect a whiz to multiple bang instances. # Environment You need the following toolchains to build: * `java-1.8` * `maven-3.3.9` * `docker-1.9` # Build The following command will build the module and run all the tests ``` mvn clean verify ``` # Release To release this module run the following command ``` mvn release:prepare release:perform -B ``` I am a sad panda that this project type did not take off... but whatever -Stephen On 17 November 2015 at 15:40, Mark Bidewell <[email protected]> wrote: > Thanks that was my plan and use workflow to emulate as much of the release > plugin functionality as possible (version verification for example). I > just wanted to be sure that was the best course of action and there wasn't > a better way forward. > > On Tuesday, November 17, 2015 at 10:38:08 AM UTC-5, Arnaud Héritier wrote: >> >> yes this one won't be compatible with workflow or freestyle jobs. >> You'll have to replace it with a call of "release:prepare >> release;perform" with few parameters defined as workflow user inputs or >> freestyle parameters. >> >> On Tue, Nov 17, 2015 at 3:29 PM, Mark Bidewell <[email protected]> wrote: >> >>> The primary usage is for the M2 release plugin integration. We are not >>> making use of many other features. >>> >>> On Tuesday, November 17, 2015 at 10:25:00 AM UTC-5, Arnaud Héritier >>> wrote: >>>> >>>> It mainly depends of the usage you have of it. >>>> There are some specific features (post build deployment, snapshots >>>> dependencies) which aren't available in others jobs types. >>>> The migration to freestyle jobs is probably the easiest one from now as >>>> you may have a large part of maven job types features but you'll need some >>>> manual configuration. >>>> Using the workflow is a solution but for now it doesn't cover all >>>> integrations with plugins (contributions are welcome) and thus it may be >>>> blocker depending of the current usage you have of it >>>> Arnaud >>>> >>>> On Tue, Nov 17, 2015 at 1:43 PM, Mark Bidewell <[email protected]> >>>> wrote: >>>> >>>>> In my current position, I inherited a Jenkins server that makes heavy >>>>> use of the Maven Project Type and M2 Release Plugin. As Jenkins is moving >>>>> forward, I am now understanding why many people do not like that project >>>>> type due to the shims needed to support Java 6 builds. >>>>> >>>>> What is the future of the Maven project type? should I be making plans >>>>> to migrate from it? If so what is the best alternative (right now I am >>>>> thinking workflows)? >>>>> >>>>> Thanks >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Jenkins Users" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/jenkinsci-users/45849d7b-990e-4232-a8dd-c4d37b9b2310%40googlegroups.com >>>>> <https://groups.google.com/d/msgid/jenkinsci-users/45849d7b-990e-4232-a8dd-c4d37b9b2310%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> >>>> >>>> -- >>>> ----- >>>> Arnaud Héritier >>>> http://aheritier.net >>>> Mail/GTalk: aheritier AT gmail DOT com >>>> Twitter/Skype : aheritier >>>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-users/b613e575-7b8a-419b-b5a6-0aeb798e519d%40googlegroups.com >>> <https://groups.google.com/d/msgid/jenkinsci-users/b613e575-7b8a-419b-b5a6-0aeb798e519d%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> ----- >> Arnaud Héritier >> http://aheritier.net >> Mail/GTalk: aheritier AT gmail DOT com >> Twitter/Skype : aheritier >> > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/3a3718a8-f2f3-473c-a2eb-cdff95dcee25%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/3a3718a8-f2f3-473c-a2eb-cdff95dcee25%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMyEcOy3UzTxz8E%2BFdodTQNxwxWi-ToWFdWSzLz%2B6NzfaQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
