Re: Request for hosting: Git Relasenotes Plugin
Hi Tomas, I merged your pull request and build a release, further I added you to the Contributors on github (you should have had write access anyway as part of the jenkins github team). Have a nice evening, Paul. On Wednesday, December 9, 2015 at 5:41:13 PM UTC+1, Paul Wellner Bou wrote: > > Hi Tomas, > > no problem, we will get the code into it tomorrow, if all works. > > Regards > Paul. > > On Wednesday, December 9, 2015 at 10:21:01 AM UTC+1, Tomas Bjerre wrote: >> >> I would suggest both, to continue support Jira filtering. >> >> How do you feel about being 2 maintainers of the Jenkins plugin? I would >> really like to get my code into a release as soon as possible. >> >> -Tomas >> >> Den onsdag 9 december 2015 kl. 10:12:02 UTC+1 skrev Paul Wellner Bou: >>> >>> Hi Tomas, >>> >>> this looks promising, I had in mind to create something similar for the >>> git-changelog-plugin as well, a configurable, templateable changelog. >>> >>> I will look into the pull requests today and give you feedback. Do we >>> need both libraries? My git-changelog-lib and yours? The >>> JIRA-Filter-feature seems to be the difference. >>> >>> Regards >>> Paul. >>> >>> >>> On Tuesday, December 8, 2015 at 7:59:54 PM UTC+1, Tomas Bjerre wrote: >>>> >>>> I created a pull request here: >>>> https://github.com/jenkinsci/git-changelog-plugin/pull/1 >>>> >>>> Lets wait and see what he thinks about merging the plugins. >>>> >>>> Den fredag 20 november 2015 kl. 22:56:26 UTC+1 skrev Tomas Bjerre: >>>>> >>>>> >>>>> Repo: https://github.com/tomasbjerre/git-releasenotes-plugin >>>>> Username: tomasbjerre >>>>> JenkinsCI username: tomasbjerre >>>>> >>>>> I made a pre-release here with some screenshots: >>>>> https://github.com/tomasbjerre/git-releasenotes-plugin/releases >>>>> >>>>> This plugin may look similar to Git Changelog Plugin, and I actually >>>>> would have taken that name if it was not already taken. But its very >>>>> different when you look at it. >>>>> >>>>> The basic idea is to use a Mustache template to render the changelog. >>>>> This makes it very flexible! The changelog can: >>>>> >>>>> * Be stored to a file in workspace >>>>> * Be rendered as summary of the build job >>>>> * Be posted to a MediaWiki page! >>>>> >>>>> Hope you like it! >>>>> >>>>> -Tomas >>>>> >>>> -- 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/d4dbd8c2-7abe-4d02-bf81-3c73da9bba14%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Request for hosting: Git Relasenotes Plugin
Hi Tomas, this looks promising, I had in mind to create something similar for the git-changelog-plugin as well, a configurable, templateable changelog. I will look into the pull requests today and give you feedback. Do we need both libraries? My git-changelog-lib and yours? The JIRA-Filter-feature seems to be the difference. Regards Paul. On Tuesday, December 8, 2015 at 7:59:54 PM UTC+1, Tomas Bjerre wrote: > > I created a pull request here: > https://github.com/jenkinsci/git-changelog-plugin/pull/1 > > Lets wait and see what he thinks about merging the plugins. > > Den fredag 20 november 2015 kl. 22:56:26 UTC+1 skrev Tomas Bjerre: >> >> >> Repo: https://github.com/tomasbjerre/git-releasenotes-plugin >> Username: tomasbjerre >> JenkinsCI username: tomasbjerre >> >> I made a pre-release here with some screenshots: >> https://github.com/tomasbjerre/git-releasenotes-plugin/releases >> >> This plugin may look similar to Git Changelog Plugin, and I actually >> would have taken that name if it was not already taken. But its very >> different when you look at it. >> >> The basic idea is to use a Mustache template to render the changelog. >> This makes it very flexible! The changelog can: >> >> * Be stored to a file in workspace >> * Be rendered as summary of the build job >> * Be posted to a MediaWiki page! >> >> Hope you like it! >> >> -Tomas >> > -- 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/f35aed08-0bdd-427b-8e9f-15c8ca7b7f59%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Request for hosting: Git Relasenotes Plugin
Hi Tomas, no problem, we will get the code into it tomorrow, if all works. Regards Paul. On Wednesday, December 9, 2015 at 10:21:01 AM UTC+1, Tomas Bjerre wrote: > > I would suggest both, to continue support Jira filtering. > > How do you feel about being 2 maintainers of the Jenkins plugin? I would > really like to get my code into a release as soon as possible. > > -Tomas > > Den onsdag 9 december 2015 kl. 10:12:02 UTC+1 skrev Paul Wellner Bou: >> >> Hi Tomas, >> >> this looks promising, I had in mind to create something similar for the >> git-changelog-plugin as well, a configurable, templateable changelog. >> >> I will look into the pull requests today and give you feedback. Do we >> need both libraries? My git-changelog-lib and yours? The >> JIRA-Filter-feature seems to be the difference. >> >> Regards >> Paul. >> >> >> On Tuesday, December 8, 2015 at 7:59:54 PM UTC+1, Tomas Bjerre wrote: >>> >>> I created a pull request here: >>> https://github.com/jenkinsci/git-changelog-plugin/pull/1 >>> >>> Lets wait and see what he thinks about merging the plugins. >>> >>> Den fredag 20 november 2015 kl. 22:56:26 UTC+1 skrev Tomas Bjerre: >>>> >>>> >>>> Repo: https://github.com/tomasbjerre/git-releasenotes-plugin >>>> Username: tomasbjerre >>>> JenkinsCI username: tomasbjerre >>>> >>>> I made a pre-release here with some screenshots: >>>> https://github.com/tomasbjerre/git-releasenotes-plugin/releases >>>> >>>> This plugin may look similar to Git Changelog Plugin, and I actually >>>> would have taken that name if it was not already taken. But its very >>>> different when you look at it. >>>> >>>> The basic idea is to use a Mustache template to render the changelog. >>>> This makes it very flexible! The changelog can: >>>> >>>> * Be stored to a file in workspace >>>> * Be rendered as summary of the build job >>>> * Be posted to a MediaWiki page! >>>> >>>> Hope you like it! >>>> >>>> -Tomas >>>> >>> -- 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/6c65a021-cb7f-4395-9640-b01fd3211646%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Hosting request for new plugin creating a Jira URL out of the Git history/changelog
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. >>>>> >>>>>
Re: Hosting request for new plugin creating a Jira URL out of the Git history/changelog
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 <p...@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.nenas...@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 >>>&g
Re: Post-build Actions on Jobs executed on slaves
Hi,
thanks, seems to work now, with MasterToSlaveCallable, on master and slave
as well. I just have to take care that all objects I need are serializable.
Regards
Paul.
On Thu, Oct 1, 2015 at 12:01 PM Paul Wellner Bou <p...@wellnerbou.de> wrote:
> Thank you for the reply.
>
> I am using a Publisher extending Publisher.
>
> This looks promising. I discovered a stackoverflow thread with a bit of
> code doing a smiliar thing (
> http://stackoverflow.com/questions/9279898/can-hudson-slaves-run-plugins).
>
> Whats the difference between launcher.getChannel().call(task); and
> build.getWorkspace().act(task)? The JavaDoc of the latter looks promising.
>
> What I am wondering now, is which Caller to use. There is a
> FilePath.FileCallable, where the JavaDoc says "Subtypes would likely want
> to extend from either {@link MasterToSlaveCallable}* or {@link
> SlaveToMasterFileCallable}."
>
> I would use MasterToSlaveCallable now, does this work on the master then
> as well? Or do I have to detect somehow if I am running on a master or a
> slave?
>
> Thank you very much,
> Paul.
>
>
>
> On Thu, Oct 1, 2015 at 10:38 AM Ullrich Hafner <ullrich.haf...@gmail.com>
> wrote:
>
>> Are you referring to an action that implements the Action interface? Or
>> to a post build publisher that derives from Recorder or Publisher?
>>
>> The latter one can execute Runnables on a slave, e.g. to read information
>> from the workspace. See FilePath#act for details...
>>
>> Am 01.10.2015 um 08:25 schrieb Paul Wellner Bou <p...@wellnerbou.de>:
>>
>> Good morning,
>>
>> I have a build job checking out a git repository running on a jenkins
>> slave, which works fine. But I am trying to access the workspace in an
>> Post-build Action plugin, which does not seem to be possible: The
>> Post-build Action is run on the master (at least thats what the
>> System.getenv("HOSTNAME") is telling me.
>>
>> Is there any way to run the Post-build Actions on the slave?
>>
>> Thank you and regards
>> Paul.
>>
>>
>> --
>>
>> 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/fe2bda4d-a374-4b04-b720-5702c4586e2b%40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/fe2bda4d-a374-4b04-b720-5702c4586e2b%40googlegroups.com?utm_medium=email_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/NwNN-HnnI8Q/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/9A91F3C4-F8DA-4D10-9693-77AF5ADF7B35%40gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/9A91F3C4-F8DA-4D10-9693-77AF5ADF7B35%40gmail.com?utm_medium=email_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/CAMDwiY_Oz1SgyfwUOW_%2BsdX05Um8sdpKnUKYMOeQa_DUN%2BjhrA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: Post-build Actions on Jobs executed on slaves
Thank you for the reply.
I am using a Publisher extending Publisher.
This looks promising. I discovered a stackoverflow thread with a bit of
code doing a smiliar thing (
http://stackoverflow.com/questions/9279898/can-hudson-slaves-run-plugins).
Whats the difference between launcher.getChannel().call(task); and
build.getWorkspace().act(task)? The JavaDoc of the latter looks promising.
What I am wondering now, is which Caller to use. There is a
FilePath.FileCallable, where the JavaDoc says "Subtypes would likely want
to extend from either {@link MasterToSlaveCallable}* or {@link
SlaveToMasterFileCallable}."
I would use MasterToSlaveCallable now, does this work on the master then as
well? Or do I have to detect somehow if I am running on a master or a slave?
Thank you very much,
Paul.
On Thu, Oct 1, 2015 at 10:38 AM Ullrich Hafner <ullrich.haf...@gmail.com>
wrote:
> Are you referring to an action that implements the Action interface? Or to
> a post build publisher that derives from Recorder or Publisher?
>
> The latter one can execute Runnables on a slave, e.g. to read information
> from the workspace. See FilePath#act for details...
>
> Am 01.10.2015 um 08:25 schrieb Paul Wellner Bou <p...@wellnerbou.de>:
>
> Good morning,
>
> I have a build job checking out a git repository running on a jenkins
> slave, which works fine. But I am trying to access the workspace in an
> Post-build Action plugin, which does not seem to be possible: The
> Post-build Action is run on the master (at least thats what the
> System.getenv("HOSTNAME") is telling me.
>
> Is there any way to run the Post-build Actions on the slave?
>
> Thank you and regards
> Paul.
>
>
> --
>
> 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/fe2bda4d-a374-4b04-b720-5702c4586e2b%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/fe2bda4d-a374-4b04-b720-5702c4586e2b%40googlegroups.com?utm_medium=email_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/NwNN-HnnI8Q/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/9A91F3C4-F8DA-4D10-9693-77AF5ADF7B35%40gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/9A91F3C4-F8DA-4D10-9693-77AF5ADF7B35%40gmail.com?utm_medium=email_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/CAMDwiY_v-yXrY8dE9bVAymZAn1-W%2B%3D1UMktdADcEJKLAstMdQg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: Hosting request for new plugin creating a Jira URL out of the Git history/changelog
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.nenas...@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
Re: Hosting request for new plugin creating a Jira URL out of the Git history/changelog
That may be new, I searched several days for something similar and did not find anything. I know that the JIRA plugin is able to create a changelog, but only if the releases are managed by Jira as well. It is new for me that the Jira plugin was able to scan the actual git history of the workspace. At least, I did not get it to work. I will have a look though again. Thanks and regards Paul. On Sunday, September 27, 2015 at 11:26:32 PM UTC+2, Oleg Nenashev 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 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/00c5054e-034e-4398-8d12-9baa2787bf21%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Hosting request for new plugin creating a Jira URL out of the Git history/changelog
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.nenas...@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-dev+unsubscr...@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_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/CAMDwiY8Yozm5XF6TcnL-18yHVgiamf7_8WH4UmAKcRvFZ6ORfw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Hosting request for new plugin creating a Jira URL out of the Git history/changelog
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 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/dd5d4328-5085-442b-aadc-869fd8654eb0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Automatically import sample job while launching hpi:run
Hello, I am developing a plugin, and for testing purposes I would like to create an example Job on launching mvn hpi:run. Is this possible, and what would be the best way to do this? Thank you and best regards Paul Wellner Bou -- 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/e27e6100-7020-4924-92c4-deb4834965fe%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
