hosting request for new plugin

[Alexander Leibzon]

Github: https://github.com/alexanderlz/jenkins-pagerduty-plugin

jenkins repo name: pagerduty

Github Username: alexanderlz

jenkins username: alexanderlz

The plugin allows to trigger incidents on PagerDuty as a postbuild action

[Alexander Leibzon]

Ping?

(Sorry if I'm nagging, I'm not fully aware of the average waiting time, and from browsing the history I found that usually ppl reply within 2 days)

[Daniel Beck]

Cool plugin!

What's a bit inconsistent is that the artifact ID is pager-duty, the repo is jenkins-pagerduty-plugin. Any particular reason for that?

Note that by convention, the JIRA component and GitHub repo would both be named foo-plugin, if 'foo' is your artifact ID.

Daniel

> --
> 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/c6df136c-ac86-4a79-9f17-2f82bfb91a40%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Alexander Leibzon]

Thanks for pointing me on that!

artifactid in pom.xml changed to 'pagerduty'

on github the repository will stay 'jenkins-pagerduty-plugin' to stay verbose for people not from jenkins community.


/Alexander.

[Baptiste Mathus]

Well, as your plugin, when forked, is gonna be under the Jenkins org, it will both clear that it's Jenkins related and inconsistently named compared to others.

-- Baptiste

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/2603764a-cefc-4372-8c4b-88246ff9e7ee%40googlegroups.com.

[Daniel Beck]

Right, I specifically meant the name of the forked repo in the jenkinsci org:

https://github.com/jenkinsci/pagerduty-plugin

There's also a component 'pagerduty-plugin' owned by you in issues.jenkins-ci.org.

Welcome aboard!

[Alexander Leibzon]

Thanks!