embeddable-build-status-plugin orphaned?

115 views
Skip to first unread message

Thomas Döring

unread,
Nov 28, 2018, 6:17:40 PM11/28/18
to Jenkins Developers
Hi everyone,

I noticed that the plugin was long time not updated despite some really interesting feature requests.
Is there a "current" maintainer of this plugin?

Greetings,
Thomas

Thomas D.

unread,
Nov 29, 2018, 3:25:17 AM11/29/18
to jenkin...@googlegroups.com
I’m asking this, because I’d like to contribute (see PR #31).

Oleg Nenashev

unread,
Nov 29, 2018, 3:33:47 PM11/29/18
to Jenkins Developers
Hi,

The plugin is not officially marked for adoption, but there was no activity there for a while.
I will ask the maintainers

BR, Oleg

Thomas Döring

unread,
Nov 29, 2018, 5:56:23 PM11/29/18
to Jenkins Developers
Hi Oleg,

Thank you. That would be great.

Greetings,
Thomas

Jesse Glick

unread,
Nov 30, 2018, 10:01:58 AM11/30/18
to jenkin...@googlegroups.com
On Thu, Nov 29, 2018 at 3:33 PM Oleg Nenashev <o.v.ne...@gmail.com> wrote:
> I will ask the maintainers

I do not know if there _are_ any maintainers. Not me.

Thomas Döring

unread,
Dec 3, 2018, 2:13:04 AM12/3/18
to Jenkins Developers
Is there any way to "adopt" the plugin if there is no current maintainer (since I can ask no one to approve).

Oleg Nenashev

unread,
Dec 3, 2018, 2:39:26 AM12/3/18
to JenkinsCI Developers, mar...@gedmin.as
Added Marius Gedminas to Cc.
Since Jesse Glick says he is not a maintainer, Marius is the last contributor to release 2 versions of the plugin before Jesse.

Let's set a standard 2-week timeout.

BR, Oleg


--
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/BXZUKKEQWQk/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/40d20b77-0125-4811-a368-bedb8f8b9e58%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Thomas Döring

unread,
Dec 3, 2018, 3:54:03 AM12/3/18
to Jenkins Developers
Thats what we do.

Thank you and greetings,
Thomas

Marius Gedminas

unread,
Dec 3, 2018, 8:30:30 AM12/3/18
to Oleg Nenashev, JenkinsCI Developers
Hi!

I have no interest in maintaining embeddable-build-status-plugin, so if
my opinion matters, anyone else is welcome to step up!

(I have some slight interest in having the plugin continue working, and
in having it produce badges in the common shields.io style, until end of
December, when I plan to shut down my Jenkins instance.)

On Mon, Dec 03, 2018 at 08:39:08AM +0100, Oleg Nenashev wrote:
> Added [1]Marius Gedminas to Cc.
> Since Jesse Glick says he is not a maintainer, Marius is the last contributor
> to release 2 versions of the plugin before Jesse.
>
> Let's set a standard 2-week timeout.
>
> BR, Oleg
>
>
> On Mon, Dec 3, 2018 at 8:13 AM Thomas Döring <[2]thoma...@gmx.net> wrote:
>
> Is there any way to "adopt" the plugin if there is no current maintainer
> (since I can ask no one to approve).
>
> Am Freitag, 30. November 2018 16:01:58 UTC+1 schrieb Jesse Glick:
>
> On Thu, Nov 29, 2018 at 3:33 PM Oleg Nenashev <o.v.ne...@gmail.com>
> wrote:
> > I will ask the maintainers
>
> I do not know if there _are_ any maintainers. Not me.

Marius Gedminas
--
Q: How many IBM CPU's does it take to execute a job?
A: Four; three to hold it down, and one to rip its head off.
signature.asc

Thomas Döring

unread,
Dec 3, 2018, 2:13:26 PM12/3/18
to Jenkins Developers
Hello again,

Well then: I hereby request adoption for the embeddable-build-status-plugin.
And Marius: There will be no new release until January.

Greetings,
Thomas.

Thomas Döring

unread,
Dec 4, 2018, 9:39:45 AM12/4/18
to Jenkins Developers

Oh. I forgot: My GitHub username is "thomas-dee". My Jenkins-ID is "thomas_dee".

Oleg Nenashev

unread,
Dec 5, 2018, 1:53:34 AM12/5/18
to Jenkins Developers
Thanks for the response, Marius!

Hi Thomas,

I have granted you the write permissions to the repo and made you a default assignee in JIRA.
Thanks again for your interest, and welcome aboard!


Best regards,
Oleg

Thomas Döring

unread,
Dec 5, 2018, 7:13:24 AM12/5/18
to Jenkins Developers
Hi Oleg,

first of all: Thank you for your work... and your trust ;-)

It seems that there is still an issue with write permissions for the plugin, since GitHub does not allow me to merge PRs to https://github.com/jenkinsci/embeddable-build-status-plugin.

Please be a little patient with me here since I'm new to the whole Git(Hub) stuff. I've been working with Subversion for years now.

Greetings,
Thomas

Thomas Döring

unread,
Dec 7, 2018, 8:45:57 AM12/7/18
to Jenkins Developers
Hi Olge,

is there anything else I need to do to get write permissions for the embeddable-build-status-plugin?

Greetings,
Thomas

Am Mittwoch, 5. Dezember 2018 07:53:34 UTC+1 schrieb Oleg Nenashev:

Oleg Nenashev

unread,
Dec 7, 2018, 8:48:14 AM12/7/18
to JenkinsCI Developers
Hi Thomas,

Once you accept the invitation to the jenkinsci org, everybody should be set.
Please check your inbox, you should have received it on Dec 4

BR, Oleg


--
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/BXZUKKEQWQk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.

Thomas Döring

unread,
Dec 7, 2018, 10:51:21 AM12/7/18
to Jenkins Developers
Hi Oleg,

Yes, on GitHub I got that invitation and accepted it. And it (GitHub) says that I am member of jenkinsci. However, I still have no write access to the plugin repo... :-(

Greetings,
Thomas

Thomas Döring

unread,
Dec 7, 2018, 10:56:18 AM12/7/18
to Jenkins Developers
Hi Oleg again,

maybe a stupid question: The write access is setup for the GitHub user "thomas-dee" (https://github.com/thomas-dee), right? Or do I have to login with another account?

Greetings,
Thomas

Am Freitag, 7. Dezember 2018 14:48:14 UTC+1 schrieb Oleg Nenashev:

Oleg Nenashev

unread,
Dec 7, 2018, 6:48:06 PM12/7/18
to JenkinsCI Developers
Hi,

It should be fixed now.
It seems we have an issue with the ChatOps bot OR with the developer group.
It had read-only permissions due to whatever reason

BR, Oleg

Thomas Döring

unread,
Dec 10, 2018, 9:58:05 AM12/10/18
to Jenkins Developers
Hi,

thank you. Its working now.

Greetings,
Thomas
Reply all
Reply to author
Forward
0 new messages