jira-plugin repository access

[Radek Antoniuk]

Hi,

There is a pile of PRs waiting in https://github.com/jenkinsci/jira-plugin/pulls and nobody seems to maintain it anymore.

Please grant committer access (gh user: warden)

Thanks!

Regards,

Radek

[Richard Bywater]

To confirm,  have you attempted to contact the current maintainer?

Richard

--
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/91119faf-0c09-4f84-8594-788abcdf24aa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Radosław Antoniuk]

Hi Richard,

Thanks, I sorted it out with Olivier.

Is there any chance to get a "Fix Version" field in the Jenkins JIRA?

Regards,
Radek Antoniuk

[Daniel Beck]

We removed these a while back. 'current' was the only valid value for years, and the test of having all versions of all plugins didn't go well, autocompletion completely broke.

Right now, the best option to indicate which release a fix will be in is probably in a comment.

> --
> 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/CAPe2pWjBPtDdNaTS9GKvuqbqDSvTVT--DyT6EDsBmWeD4Z4H6w%40mail.gmail.com.

[Radosław Antoniuk]

Yeah, that makes sense.

There's a plugin for standalone install of JIRA for that and an old ticket: https://jira.atlassian.com/browse/JRA-3501

Thanks for the info.

Regards,

Radek

[Radek Antoniuk]

One quick follow up. Currently when there is a new JIRA ticket created in Jenkins JIRA, I am not getting any notifications, even if the correct component is selected.

Is there a way we can send out notifications to the plugin maintainers when JIRA issues are created?

One way to achieve that using JIRA would be to assign a component lead, but that would require some alias mechanism that would fetch maintainers from github and put them in component-<name>@jira.jenkinsci.org (where jira.jenkinsci.org is the server that Jenkins JIRA is sending email through). 

Or maybe there's something already in place? ;-)

Thanks,

Radek

[Daniel Beck]

On 09.11.2015, at 14:49, Radek Antoniuk <radek.a...@gmail.com> wrote:

> Or maybe there's something already in place? ;-)

Let us know which Jenkins-CI.org accounts should be lead for which components.

There's also the jenkinsci-issues mailing list, which you can have your email client filter to only see issues you care about.

Alternatively, you could subscribe to a saved search in Jira. If you limit it to e.g. "Issues created in the last two days" there won't be a long list of old issues you already know.

[Radosław Antoniuk]

Hey Daniel,

Thanks, yes, I am using the subscribed filter. Unfortunately you can set only one Lead for component and that's not what we want.

I will stay with the filter then: " created > startOfDay(-1d)" that will actually email daily new issues.

Here is it for refererence: https://issues.jenkins-ci.org/issues/?filter=15145

Regards,
Radek Antoniuk

--
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/UGU4hTHWqhI/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/B084BE3B-EBA4-48E6-A838-AABB12106BC2%40beckweb.net.

[Daniel Beck]

On 09.11.2015, at 15:56, Radosław Antoniuk <radek.a...@gmail.com> wrote:

> Thanks, yes, I am using the subscribed filter. Unfortunately you can set only one Lead for component and that's not what we want.

Right, that's a limitation. I don't think this is a major issue so far, with most plugins having one maintainer.

Maybe you could register a 'meta-account' with a e.g. googlegroups email address and have all co-maintainers subscribe to that list?

> Here is it for refererence: https://issues.jenkins-ci.org/issues/?filter=15145

You should share it if you want others to have access.

[Radosław Antoniuk]

> > Thanks, yes, I am using the subscribed filter. Unfortunately you can set only one Lead for component and that's not what we want.
>
> Right, that's a limitation. I don't think this is a major issue so far, with most plugins having one maintainer.
>
> Maybe you could register a 'meta-account' with a e.g. googlegroups email address and have all co-maintainers subscribe to that list?

Sure, that would be an option, but I thought about an automatic
general solution.

>
> > Here is it for refererence: https://issues.jenkins-ci.org/issues/?filter=15145
>
> You should share it if you want others to have access.

Good point, shared :)