Hi, thank you very much. It worked, wiki page created, release built.
Regards Paul. On Sun, Oct 4, 2015 at 11:10 AM Oleg Nenashev <o.v.nenas...@gmail.com> wrote: > Hi Paul, > > The plugin has been forked: > https://github.com/jenkinsci/git-changelog-plugin . You should get an > invitation to jenkinsci organization soon. > > Welcome aboard! > > Best regards, > Oleg Nenashev > > пятница, 2 октября 2015 г., 23:46:44 UTC+3 пользователь Paul Wellner Bou > написал: >> >> Good evening, >> >> After a lot of refactoring it works now, even with git workspaces on >> Jenkins slaves. The README may include more examples, but that will be work >> for the wiki page, once this plugin might get included in jenkins' plugin >> collection. >> >> Is there a chance to get it hosted on jenkins? >> >> Thank you and best regards >> Paul Wellner Bou >> >> On Wed, Sep 30, 2015 at 12:21 AM Paul Wellner Bou <pa...@wellnerbou.de> >> wrote: >> > Thank you for the inspiration: I decoupled the logic from the jira >>> functionality and refactored both, the library and the jenkins plugin, even >>> renamed the repositories and artifacts: >>> https://github.com/paulwellnerbou/git-changelog-jenkins-plugin >>> >>> The documentation now needs a bit more of rework, but I am working on >>> it. As a basic, different sample implementation I added a "basic changelog" >>> generator to the "jirafilter". HTML/PDF/... reports may follow. >>> >>> This leaves a lot of room for extensions, for other ticket systems or >>> whatever formats of reports, as the key feature is the automatic >>> tag/revision search and changelog generation -- the output format is >>> adjustable with "Processors", included via Java's ServiceLoader. It would >>> be possible to create a completely generic publish action, but I have to >>> look deeper into the jelly configuration and so on. >>> >>> Which file leak do you mean? The file printstreams for publishing are >>> beeing closed. >>> >>> Thank you and a nice day, >>> Paul. >>> >> On Tue, Sep 29, 2015 at 10:19 AM Oleg Nenashev <o.v.ne...@gmail.com> >>> wrote: >>> >> IMHO such generic plugin makes sense. The code is really hardcoded to be >>>> git=>jira only, but it's possible to generalize it to >>>> "git-changelog-generator". If not, we could also publish it as a >>>> "git-jira-changelog-generator". The most of the functionality is located in >>>> another library BTW, so I'm not sure how they should be decoupled. >>>> >>>> It would be helpful to get a feedback from others before the fork. >>>> >>>> P.S: please be also aware about the potential unclosed file leak in >>>> your code >>>> >>>> понедельник, 28 сентября 2015 г., 8:58:35 UTC+3 пользователь Paul >>>> Wellner Bou написал: >>>>> >>>>> Good morning, >>>>> >>>>> I had a deeper look at the jenkins-jira-plugin, and no, it is not >>>>> doing what I am trying to do with my git-jira-log plugin. >>>>> >>>>> First of all: Maybe I should rename it and give it a more generic aim: >>>>> The logic in my plugin is not about jira, it is mainly about extracting >>>>> changelogs out of Git: searching automatically for the latest build tags >>>>> and being able to generate changelogs between branches or just git >>>>> revisions. The jira filter is actually just one way to filter and >>>>> represent >>>>> this information (the only implemented so far). >>>>> >>>>> The jenkins-jira-plugin actually is able to create release notes: But >>>>> the information of this release notes is not taken out of the git history, >>>>> it is taken out of Jira, so this only works if a) you use only one >>>>> project, >>>>> you can configure only one project key, b) the issues are correctly set >>>>> with it's fixedVersion. >>>>> >>>>> What I was trying to do with the git-jira-log-plugins was the other >>>>> way round: Creating automatically a list of tickets worked on between the >>>>> current tag/branch/revision and the latest released tag, to get all of the >>>>> issues, even those which may not be maintained correctly in Jira. >>>>> >>>>> As we have a special customized workflow (not that this would be a >>>>> good thing, but thats another topic), we do not want jenkins to >>>>> automatically update the workflow nor the fixedVersion in our tickets (the >>>>> fact that there are commits with a certain ticket number does not mean >>>>> necessarily that it is fixed). >>>>> >>>>> Thanks and kind regards >>>>> Paul. >>>>> >>>> On Sun, Sep 27, 2015 at 11:26 PM Oleg Nenashev <o.v.ne...@gmail.com> >>>>> wrote: >>>>> >>>> Seems the core JIRA plugin provides a related functionality ( >>>>>> https://issues.jenkins-ci.org/browse/JENKINS-6381). Would it be >>>>>> possible to somehow merge your proposal into this plugin? >>>>>> >>>>>> пятница, 25 сентября 2015 г., 15:23:44 UTC+3 пользователь Paul >>>>>> Wellner Bou написал: >>>>>> >>>>>>> Github: >>>>>>> https://github.com/paulwellnerbou/git-jira-log-jenkins-plugin >>>>>>> jenkins repo name: git-jira-log(-plugin) >>>>>>> >>>>>>> Github Username: paulwellnerbou >>>>>>> jenkins username: paulwellnerbou >>>>>>> >>>>>>> What the plugin does and how it is used is documented in it's >>>>>>> README.md >>>>>>> >>>>>>> Thank you, kind regards and a nice weekend, >>>>>>> >>>>>>> Paul. >>>>>>> >>>>>> -- >>>>>> You received this message because you are subscribed to a topic in >>>>>> the Google Groups "Jenkins Developers" group. >>>>>> To unsubscribe from this topic, visit >>>>>> https://groups.google.com/d/topic/jenkinsci-dev/6RxOPndNkRo/unsubscribe >>>>>> . >>>>>> >>>>> To unsubscribe from this group and all its topics, send an email to >>>>>> jenkinsci-de...@googlegroups.com. >>>>> >>>>> >>>>>> To view this discussion on the web visit >>>>>> https://groups.google.com/d/msgid/jenkinsci-dev/2ed4f212-b678-4dd8-8107-66fb76c043c1%40googlegroups.com >>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/2ed4f212-b678-4dd8-8107-66fb76c043c1%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 a topic in the >>>> Google Groups "Jenkins Developers" group. >>>> To unsubscribe from this topic, visit >>>> https://groups.google.com/d/topic/jenkinsci-dev/6RxOPndNkRo/unsubscribe >>>> . >>>> To unsubscribe from this group and all its topics, send an email to >>>> jenkinsci-de...@googlegroups.com. >>>> >>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/jenkinsci-dev/0d2cc0b3-8f50-4236-b28a-36c97ee03bd5%40googlegroups.com >>>> <https://groups.google.com/d/msgid/jenkinsci-dev/0d2cc0b3-8f50-4236-b28a-36c97ee03bd5%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 a topic in the > Google Groups "Jenkins Developers" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-dev/6RxOPndNkRo/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > jenkinsci-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/acbf2bfd-34f5-4c37-89ae-b8d55292ecb8%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/acbf2bfd-34f5-4c37-89ae-b8d55292ecb8%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 Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMDwiY8EX%2BugLRuyMgyN7MbpCf2TokfX0ju%2BqFGizqc4hg8DNA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
