Request for hosting: Git Relasenotes Plugin

[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

[Tomas Bjerre]

Anything happening here? =)

[Christopher Orr]

Hi there,

On 20/11/15 22:56, Tomas Bjerre wrote:
> 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.

Given that these two plugins are indeed similar, though clearly with
very different publishing mechanisms, would it make sense to merge the two?

If not, I think the plugin name definitely needs to be more descriptive.
Having two near-identically named plugins isn't going to be helpful for
users.

Git Changelog Template Generator, or Git Changelog Publisher, or
something along those lines?

(The artifact ID would need to be changed as well in any case; see
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Prerequisites)

Regards,
Chris

[Tomas Bjerre]

No I dont want to merge them.

I changed the name:

https://github.com/tomasbjerre/git-publisher-plugin

And the artifactid: git-changelog-publisher

-Tomas

[Tomas Bjerre]

Any chance of getting this one forked soon? =)

[Daniel Beck]

Would a name like 'Git Release Notes Publisher' make sense? It looks like you actually made the name more similar to the existing plugin.

> --
> 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-de...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/4b6eb58e-21e9-4fc1-a47d-46a30c4a828a%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Tomas Bjerre]

Sure, if I change the name to "Git Release Notes Publisher" will you fork it then? I changed the name because of Christopher:s suggestion.

[Tomas Bjerre]

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:

[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.

[Tomas Bjerre]

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

[Paul Wellner Bou]

Hi Tomas,

no problem, we will get the code into it tomorrow, if all works.

Regards

Paul.

[Paul Wellner Bou]

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.