I agree. I'd love to see Jenkins migrate from Jira to GH. As a user, if I
want to submit an issue to Jenkins, it's a bit cumbersome to create an
additional account for Atlassian just so that I can create a ticket.
However, it's highly likely that I already have a GH account and have even
browsed
personally, as someone who replies to emails/tickets on my phone a lot, I'd
love to see everything migrated from self hosted jira to github, and have
one less item that the infra team needs to manage. Plus easier for people
to report bugs since they don't need to make an ldap account first
On
This is great! Thank you for all that you do.
> On Jun 10, 2020, at 12:15 PM, Oleg Nenashev wrote:
>
> Hi all,
>
> Just to provide some updates, we have had a few roadmap reviews at the
> Jenkins Governance meetings, and we have also collected roadmap feedback from
> all special interest
I think this sounds great, thanks for all of your efforts in this area!
On Wed, Jun 10, 2020 at 12:15 PM Oleg Nenashev
wrote:
> Hi all,
>
> Just to provide some updates, we have had a few roadmap reviews at the
> Jenkins Governance meetings, and we have also collected roadmap feedback
> from
Hi all,
Just to provide some updates, we have had a few roadmap reviews at the
Jenkins Governance meetings, and we have also collected roadmap feedback
from all special interest groups and sub-projects. We have been less
successful with plugin maintainer communications, but I hope to address
That can be fixed via IRC bot, just ping in #jenkins-infra or reply here or
what’s the ticket?
Administer comes by default and only historical teams / people manually
added to the repo won’t have it
On Wed, 10 Jun 2020 at 15:26, Jesse Glick wrote:
> On Wed, Jun 10, 2020 at 8:54 AM Tim Jacomb
Thanks to everyone for the review, the JEP Draft is now published as
JEP-15: https://github.com/jenkinsci/jep/tree/master/jep/15
I will go ahead and propose a change for jenkins.io/donate and Core
components so that we could enable funding there. Also, I will add a topic
to the next governance
On Wed, Jun 10, 2020 at 8:54 AM Tim Jacomb wrote:
> The plugin author should have the administer role though?
Sometimes, sometimes not. In general you need to request administer
role via `INFRA` ticket. (I am still waiting on at least one, though
with Artifactory uploads blocked anyway I guess
>
> Am 10.06.2020 um 11:47 schrieb Radosław Antoniuk >:
>
> Not sure I got the question right, but IMO it's each plugin's maintainer
> responsibility to transfer the issues from Jira to GH (with a pre-prepared
> solution I mentioned long ago).
>
>
> I think we are still one step before: should we
> Am 10.06.2020 um 11:47 schrieb Radosław Antoniuk :
>
> Not sure I got the question right, but IMO it's each plugin's maintainer
> responsibility to transfer the issues from Jira to GH (with a pre-prepared
> solution I mentioned long ago).
I think we are still one step before: should we as
On Wed, Jun 10, 2020 at 3:46 PM Slide wrote:
> We could remove the component from Kira for the plugin. It wouldn't stop
> someone from opening one and assigning it to the wrong component, but
> people assign to the wrong component all the time anyway.
>
Yes, removing the category is the other
We could remove the component from Kira for the plugin. It wouldn't stop
someone from opening one and assigning it to the wrong component, but
people assign to the wrong component all the time anyway.
On Wed, Jun 10, 2020, 02:47 Radosław Antoniuk
wrote:
> Not sure I got the question right, but
Hi,
I'd like to change name of this repository (
https://github.com/jenkinsci/testflo-test-results-publisher-plugin) to
"testflo-for-jira-test-management-automation".
I've already made Jira ticket for that (
https://issues.jenkins-ci.org/browse/INFRA-2626), but I'm not sure if that
was the
The plugin author should have the administer role though?
The maintainer role lets you do very little, what repos do people have
access to but they only have maintainer on?
Thanks
Tim
On Wed, 10 Jun 2020 at 09:49, Ullrich Hafner
wrote:
> It took some discussions with the Codacy team but now I
Not sure I got the question right, but IMO it's each plugin's maintainer
responsibility to transfer the issues from Jira to GH (with a pre-prepared
solution I mentioned long ago).
The question is how to prevent opening new issues in Jira afterwards, but
this actually could be automated via a
It took some discussions with the Codacy team but now I understand why it is
not working:
In order to let plugins authors decide to use Codacy, the author needs to have
the Administer role for a repository but they currently only have the role
Maintainer.
So maybe it makes sense to wait for
Yea I want to get the discussion restarted so a conclusion can happen.
And no, was just thinking of transferring tickets between plugins that do
GitHub issues. And the triaging issues within, but yea that's another issue
with the mixed env
On Wed., Jun. 10, 2020, 1:14 a.m. Ullrich Hafner,
> Am 10.06.2020 um 01:24 schrieb 'Gavin Mogan' via Jenkins Developers
> :
>
> So re surfacing this old topic now that we've merged and deployed the updated
> plugin site with GitHub releases and jira issues
>
Seems that I overlooked the PR for the new plugins site. Nice work, thanks for
18 matches
Mail list logo
