You mean besides reading from a file in the workspace? Not right now, but it should.
One thing I've had on my TODO list forever is to add support for direct entry of the YAML at the project level (big text box), but also possibly at the BuildStep and Publisher levels. Now that JIRA is set up, I should move my known issues / TODO items into there, which will enable folks to poach and submit PR's ;-) thanks again for getting me set up, and definitely LMK if you have any feedback or hit any issues. -M On Tue, Sep 9, 2014 at 11:13 AM, 'Bruno P. Kinoshita' via Jenkins Developers <jenkinsci-dev@googlegroups.com> wrote: > testng-plugin and build-flow-plugin also use the -plugin suffix in the > artifact id . > > All set Matthew, plugin created at [1], component yaml-project created in > JIRA. You should already have commit access, but let me know if that > doesn't work. > > Also, I have already tried the YAML plug-in and I liked it. Are there > other ways to get the YAML file, like from some web site, ftp, etc? > > Thanks! > Bruno > > [1] https://github.com/jenkinsci/yaml-project-plugin > > ------------------------------ > *From:* 'Matthew Moore' via Jenkins Developers < > jenkinsci-dev@googlegroups.com> > *To:* "jenkinsci-dev@googlegroups.com" <jenkinsci-dev@googlegroups.com> > *Sent:* Tuesday, September 9, 2014 3:00 PM > > *Subject:* Re: new plugin hosting request > > Found one: > <dependency> > <groupId>org.jenkins-ci.plugins</groupId> > <artifactId>build-pipeline-plugin</artifactId> > <version>1.4.3</version> > <optional>true</optional> > </dependency> > > However, I'm just happy it means I'm not crazy, I have already pushed a > change removing '-plugin' from artifactId. > > > thanks again, > -M > > > > > On Tue, Sep 9, 2014 at 10:57 AM, Matthew Moore <mattm...@google.com> > wrote: > > Huh, my mistake on Artifact ID. I've been using "-plugin" for the various > Google-specific plugins, but I sampled a few plugins I would have > referenced and you are 100% correct :) > > I'll change the artifact id shortly. My username is generally 'mattmoor', > pretty sure I am registered, since I've released a few plugins now. > > thanks for the quick turnaround. > -M > > > On Tue, Sep 9, 2014 at 10:49 AM, 'Bruno P. Kinoshita' via Jenkins > Developers <jenkinsci-dev@googlegroups.com> wrote: > > Oh got it, then you simply convert the YAML file back to JSON. > > If there's no objection, I'll fork this repository under jenkinsci using > the IRC bot in the next hour. The Wiki looks good, no similar plug-ins, or > any other that could have this plug-in as a feature, code looks good as > well, license compatible. > > I think the only thing wrong is the artifactId. Can you rename it > to <artifactId>yaml-project</artifactId>, please? The plug-in part only > gets added to the github repository name. We can create a component in JIRA > and assign you as maintainer, do you have a JIRA user already? > > Thanks! > Bruno > > > > ------------------------------ > *From:* 'Matthew Moore' via Jenkins Developers < > jenkinsci-dev@googlegroups.com> > *To:* "jenkinsci-dev@googlegroups.com" <jenkinsci-dev@googlegroups.com> > *Sent:* Tuesday, September 9, 2014 1:41 PM > *Subject:* Re: new plugin hosting request > > To be clear: I am not defining any YAML syntax. > > The syntax for the YAML this parses is entirely defined by Jenkins' > Structured Form Submissions. > > This is entirely by design, since it means that basically any plugin that > Jenkins can create through the UI, this plugin *should* be able to create > from YAML. > > Better still, the YAML asks users to specify precisely what the UI does :) > > > > *"Are you going to host the plug-in under jenkinsci org at GitHub?"* > > Yes, that is essentially what this thread is about. > > > Happy to chat more, especially if any of the above isn't clear. > -M > > > > On Tue, Sep 9, 2014 at 8:55 AM, 'Bruno P. Kinoshita' via Jenkins > Developers <jenkinsci-dev@googlegroups.com> wrote: > > > Hey Matthew, > > I'm working with a team using Ansible YAML playbooks, so probably using > similar syntax for creating Jenkins projects would be a good idea. > > Are you going to host the plug-in under jenkinsci org at GitHub? > > Thanks! > Bruno > > ------------------------------ > *From:* 'Matthew Moore' via Jenkins Developers < > jenkinsci-dev@googlegroups.com> > *To:* "jenkinsci-dev@googlegroups.com" <jenkinsci-dev@googlegroups.com> > *Sent:* Tuesday, September 9, 2014 12:41 PM > *Subject:* new plugin hosting request > > I have posted a new plugin here: > https://github.com/mattmoor/yaml-project-plugin > > and added its associated wiki page here: > https://wiki.jenkins-ci.org/display/JENKINS/YAML+Project+Plugin > > FWIW, this is the basis of the talk I plan to give at JUC 2014 this Fall. > > > thanks, > -M > > > -- > Matthew Moore > DI/Docker (aka Convoy) > Developer Infrastructure @ Google > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > > > > > -- > Matthew Moore > DI/Docker (aka Convoy) > Developer Infrastructure @ Google > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > > > > > -- > Matthew Moore > DI/Docker (aka Convoy) > Developer Infrastructure @ Google > > > > > -- > Matthew Moore > DI/Docker (aka Convoy) > Developer Infrastructure @ Google > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Matthew Moore DI/Docker (aka Convoy) Developer Infrastructure @ Google -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
