Re: Welcome Jenkins to the GitHub Issues: Sub-issues, issue types and advanced search beta

;> >>> Le jeu. 3 oct. 2024, 19:00, 'Jesse Glick' via Jenkins Developers < >>> jenkinsci-dev@googlegroups.com> a écrit : >>> >>>> Possibly more helpful link: >>>> https://github.blog/changelog/2024-10-01-evolving-github-issues-pub

Re: Welcome Jenkins to the GitHub Issues: Sub-issues, issue types and advanced search beta

oglegroups.com> a écrit : >> >>> Possibly more helpful link: >>> https://github.blog/changelog/2024-10-01-evolving-github-issues-public-preview/ >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups

Re: Welcome Jenkins to the GitHub Issues: Sub-issues, issue types and advanced search beta

e jeu. 3 oct. 2024, 19:00, 'Jesse Glick' via Jenkins Developers < > jenkinsci-dev@googlegroups.com> a écrit : > >> Possibly more helpful link: >> https://github.blog/changelog/2024-10-01-evolving-github-issues-public-preview/ >> >> -- >> You

Re: Welcome Jenkins to the GitHub Issues: Sub-issues, issue types and advanced search beta

blog/changelog/2024-10-01-evolving-github-issues-public-preview/ > > -- > 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 jen

Re: Welcome Jenkins to the GitHub Issues: Sub-issues, issue types and advanced search beta

Possibly more helpful link: https://github.blog/changelog/2024-10-01-evolving-github-issues-public-preview/ -- 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, sen

Fwd: Welcome Jenkins to the GitHub Issues: Sub-issues, issue types and advanced search beta

FYI -- Forwarded message - From: GitHub Date: Thu, 3 Oct 2024 at 09:45 Subject: Welcome Jenkins to the GitHub Issues: Sub-issues, issue types and advanced search beta To: Tim Jacomb [image: GitHub] Welcome Jenkins to the GitHub Issues: Sub-issues, issue types and advanced

Re: GitHub Issues

Thanks Am 13.03.2024 um 09:54 schrieb 'Daniel Beck' via Jenkins Developers: On Wed, Mar 13, 2024 at 9:08 AM 'Michael Kriese' via Jenkins Developers wrote: Found it. - https://maven.apache.org/pom.html#issue-management - https://github.com/jenkinsci/publish-over-ssh-plugin

Re: GitHub Issues

On Wed, Mar 13, 2024 at 9:08 AM 'Michael Kriese' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > Found it. > > - https://maven.apache.org/pom.html#issue-management > - > https://github.com/jenkinsci/publish-over-ssh-plugin/blob/d6d29fda86b3db5e19d9130ca80ad7915eb1197c/pom.xml#L12

Re: GitHub Issues

se GitHub issues instead of Jira? > So to link to GitHub issues from plugin site? > > I don't like Jira. 🙃 > > Regards > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop r

GitHub Issues

Hi, Is there a way to only use GitHub issues instead of Jira? So to link to GitHub issues from plugin site? I don't like Jira. 🙃 Regards -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and

Re: Is there interest for GitHub issues in core components?

On Wed, Jul 6, 2022 at 12:33 AM Damien Duportal wrote: > Reporting issues with due diligence is absolutely not related to GitHub or > JIRA. It is not, but the difficulty and amount of effort required to write clear steps to reproduce, expected results, and actual results far exceeds the difficul

Re: Is there interest for GitHub issues in core components?

>> The barrier to entry on Jira is a lot higher than on GitHub, many people struggle to report issues. >I do not think the barrier to entry on Jira is prohibitively high. As others have noted, reporting issues requires a certain degree of due diligence, including writing steps to reproduce, ex

Re: Is there interest for GitHub issues in core components?

On Fri, Jul 1, 2022 at 3:22 AM 'Daniel Beck' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > we have 130k users in Jira. While many are probably not legitimate users > of Jira […or] haven't been logged in in years > If we expect and even encourage that most plugins switch to Git

Re: Is there interest for GitHub issues in core components?

On Thu, Jun 30, 2022 at 10:01 PM Basil Crow wrote: > For example, moving from our > traditional Jira server to Jira Software Cloud (with HTTP redirects if > necessary) would be almost completely transparent to core and plugin > maintainers from the perspective of existing Jira issues, which are >

Re: Is there interest for GitHub issues in core components?

On Wed, Jun 29, 2022 at 1:17 AM Tim Jacomb wrote: > I've updated the JEP, could you please take another look when you have time? My sense from reviewing the additions is that GitHub issues lacks feature parity with Jira on a number of fronts and that preserving existing functionality

Re: Is there interest for GitHub issues in core components?

b requires >>> you to type 'Caused by' and 'Depends on' yourself. >>> >>> That is an understatement: GitHub does not support relationships to be >>> set on links at all. Even if you type "Caused by" and "Depends on" >>

Re: Is there interest for GitHub issues in core components?

o type 'Caused by' and 'Depends on' yourself. >> >> That is an understatement: GitHub does not support relationships to be >> set on links at all. Even if you type "Caused by" and "Depends on" >> yourself, there is no way to e.g. view

Re: Is there interest for GitHub issues in core components?

to be > set on links at all. Even if you type "Caused by" and "Depends on" > yourself, there is no way to e.g. view all the bugs that were caused > by a particular change for a given component. > > > GitHub projects can be used to group issues that are across c

Re: Is there interest for GitHub issues in core components?

#x27; and 'Depends on' yourself. That is an understatement: GitHub does not support relationships to be set on links at all. Even if you type "Caused by" and "Depends on" yourself, there is no way to e.g. view all the bugs that were caused by a particular change for

Re: Is there interest for GitHub issues in core components?

components to GitHub issues? > > Not from me. There is, on the other hand, an interest from me (for the > reasons described in > https://groups.google.com/g/jenkinsci-dev/c/9sZipk1PHns/m/mqtV7K8uAAAJ) > for us to > > > (a) stop accepting new issues on GitHub for all core compo

Re: Is there interest for GitHub issues in core components?

On Mon, May 23, 2022 at 1:25 PM Tim Jacomb wrote: > Is there any interest in moving core components to GitHub issues? Not from me. There is, on the other hand, an interest from me (for the reasons described in https://groups.google.com/g/jenkinsci-dev/c/9sZipk1PHns/m/mqtV7K8uAAAJ) for us

Re: Is there interest for GitHub issues in core components?

On Mon, Jun 13, 2022 at 9:05 PM 'Jesse Glick' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > On Mon, Jun 13, 2022 at 10:02 AM 'Daniel Beck' via Jenkins Developers < > jenkinsci-dev@googlegroups.com> wrote: > >> On Mon, Jun 13, 2022 at 3:55 PM Tim Jacomb wrote: >> >>> The barrie

Re: Is there interest for GitHub issues in core components?

On Mon, Jun 13, 2022 at 10:02 AM 'Daniel Beck' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > On Mon, Jun 13, 2022 at 3:55 PM Tim Jacomb wrote: > >> The barrier to entry on Jira is a lot higher than on GitHub, many people >> struggle to report issues. >> > > Is people not repor

Re: Is there interest for GitHub issues in core components?

t work unfortunately > https://jira.atlassian.com/browse/JRASERVER-44537) > > Thanks > Tim > > On Mon, 13 Jun 2022 at 10:19, 'jn...@cloudbees.com' via Jenkins > Developers wrote: > >> https://groups.google.com/g/jenkinsci-dev/c/9sZipk1PHns/m/mqtV7K8uA

Re: Is there interest for GitHub issues in core components?

On Mon, Jun 13, 2022 at 3:55 PM Tim Jacomb wrote: > The barrier to entry on Jira is a lot higher than on GitHub, many people > struggle to report issues. > Is people not reporting issues they experience really a problem we have? Unless we step up our responsiveness, having a backlog of issues n

Re: Is there interest for GitHub issues in core components?

groups.google.com/g/jenkinsci-dev/c/9sZipk1PHns/m/mqtV7K8uAAAJ > would report there is the opposite. > > Whilst Jira is a PITA, GitHub issues for me has more drawbacks. > > We seem to be missing some improvements to Jira that would make it much > nicer day to day, > e.g. > ht

Re: Is there interest for GitHub issues in core components?

https://groups.google.com/g/jenkinsci-dev/c/9sZipk1PHns/m/mqtV7K8uAAAJ would report there is the opposite. Whilst Jira is a PITA, GitHub issues for me has more drawbacks. We seem to be missing some improvements to Jira that would make it much nicer day to day, e.g. https

Is there interest for GitHub issues in core components?

Hello Is there any interest in moving core components to GitHub issues? It would involve things like: - Issue migration - LTS backporting flow updates - Documentation updates - Dashboards / reporting - maybe something like https://github.com/marketplace/actions/issue-dashboard I would be happy

Re: Proposal: Move Jenkins Test Harness issue tracker to GitHub Issues

On Mon, May 23, 2022 at 12:18 PM Ullrich Hafner wrote: > > As mentioned several times before I think that using or allowing 2 different issue tracker systems for *any* Jenkins component (core and plugins) is a mess for users and developers. Indeed, though at least the mess is mitigated for plugin

Re: Proposal: Move Jenkins Test Harness issue tracker to GitHub Issues

I could have easily moved > JENKINS-68600 <https://issues.jenkins.io/browse/JENKINS-68600> to the correct > component, but now the functionality to correct the component of a misfiled > issue is not available to me. The suggested workaround is both burdensome and > incomp

Re: Proposal: Move Jenkins Test Harness issue tracker to GitHub Issues

<https://issues.jenkins.io/browse/JENKINS-68600> to the correct component, but now the functionality to correct the component of a misfiled issue is not available to me. The suggested workaround is both burdensome and incomplete. In short, the suggested workaround is not acceptable to me. Th

Re: Proposal: Move Jenkins Test Harness issue tracker to GitHub Issues

On Thu, Apr 28, 2022 at 12:20 AM Oleg Nenashev wrote: > Jenkins Test Harness is not a core component, it is a separate deliverable > with its own release lifecycle > Same for other developer tools AFAICT > Not part of the core deliverable, but core team repos. Projects still likely cross issue t

Re: Proposal: Move Jenkins Test Harness issue tracker to GitHub Issues

Jenkins Test Harness is not a core component, it is a separate deliverable with its own release lifecycle Same for other developer tools AFAICT On Wed, Apr 27, 2022 at 11:43 PM Basil Crow wrote: > Strong -1 from me. Using GitHub issues for core components but not > core itself ma

Re: Proposal: Move Jenkins Test Harness issue tracker to GitHub Issues

Strong -1 from me. Using GitHub issues for core components but not core itself makes it impossible to do project management in a single view (Jira epic or GitHub project) that covers both core and core components. Additionally, there is no way to define causal relationships or dependencies between

Re: Proposal: Move Jenkins Test Harness issue tracker to GitHub Issues

I archived the component in Jira for the ones I found, not all of them mapped to a component and I didn't dig too hard. Archiving seems to keep the component there but no new issues can be added which maps to what you said Jesse Anyone can migrate the issues, Herve is the one who did this most rec

Re: Proposal: Move Jenkins Test Harness issue tracker to GitHub Issues

Hi Jesse, Enabled it for all remaining projects in the list. BR, Oleg On Tuesday, January 11, 2022 at 3:59:28 PM UTC+1 Jesse Glick wrote: > Anyone with infra-level permissions up for this? I just tried to switch > `maven-hpi-plugin` to GH Issues but noticed I lack admin access to the repo > (

Re: Proposal: Move Jenkins Test Harness issue tracker to GitHub Issues

Anyone with infra-level permissions up for this? I just tried to switch `maven-hpi-plugin` to GH Issues but noticed I lack admin access to the repo (and certainly I would lack permissions to mark a Jira component closed for entry of new issues, which I think is an option). -- You received this me

ANN: Hosting switched to GitHub issues

Hello New hosting requests will be processed on GitHub in RPU. There is a template for hosting requests: https://github.com/jenkins-infra/repository-permissions-updater/issues/new?assignees=&labels=hosting-request&template=1-hosting-request.yml It's pretty similar to the previous one. The main c

Re: Proposal: Move Jenkins Test Harness issue tracker to GitHub Issues

+1 for these repos. Le mar. 19 oct. 2021 à 08:35, Oleg Nenashev a écrit : > I am +1 too. I switched Jenkins Test Harness taking the feedback. > Will give it a bit more time for the rest of the repositories > > On Monday, October 18, 2021 at 4:12:11 PM UTC+2 timja...@gmail.com wrote: > >> +1 to J

Re: Proposal: Move Jenkins Test Harness issue tracker to GitHub Issues

I am +1 too. I switched Jenkins Test Harness taking the feedback. Will give it a bit more time for the rest of the repositories On Monday, October 18, 2021 at 4:12:11 PM UTC+2 timja...@gmail.com wrote: > +1 to Jesse’s list > > On Mon, 18 Oct 2021 at 14:33, 'Jesse Glick' via Jenkins Developers < >

Re: Proposal: Move Jenkins Test Harness issue tracker to GitHub Issues

+1 to Jesse’s list On Mon, 18 Oct 2021 at 14:33, 'Jesse Glick' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > On Sun, Oct 17, 2021 at 4:50 AM Oleg Nenashev > wrote: > >> Currently we have only a few issues in Jira >> > > BTW if switching canonical issue tracker I recommend als

Re: Proposal: Move Jenkins Test Harness issue tracker to GitHub Issues

On Sun, Oct 17, 2021 at 4:50 AM Oleg Nenashev wrote: > Currently we have only a few issues in Jira > BTW if switching canonical issue tracker I recommend also closing any remaining open issues in Jira and refiling them in GitHub (with links in either direction for reference). -- You received t

Re: Proposal: Move Jenkins Test Harness issue tracker to GitHub Issues

On Sun, Oct 17, 2021 at 9:58 AM Oleg Nenashev wrote: > I would actually expand that to all developer tools we have in the project Yes! At a minimum - jenkins-test-harness - pom - plugin-pom - bom - maven-hpi-plugin - incrementals-tools - acceptance-test-harness - archet

Re: Proposal: Move Jenkins Test Harness issue tracker to GitHub Issues

> On 17. Oct 2021, at 10:50, Oleg Nenashev wrote: > > I suggest moving the Jenkins Test Harness issue tracker to GitHub Issues. > This is a test framework, and it is not exposed to the user ecosystem. Using > GitHub issues would be ore convenient for use-cases, and p

Re: Proposal: Move Jenkins Test Harness issue tracker to GitHub Issues

t 2021 at 09:50, Oleg Nenashev wrote: > >> Hi all, >> >> I suggest moving the Jenkins Test Harness issue tracker to GitHub Issues. >> This is a test framework, and it is not exposed to the user ecosystem. >> Using GitHub issues would be ore convenient for use-case

Re: Proposal: Move Jenkins Test Harness issue tracker to GitHub Issues

+1 On Sun, 17 Oct 2021 at 09:50, Oleg Nenashev wrote: > Hi all, > > I suggest moving the Jenkins Test Harness issue tracker to GitHub Issues. > This is a test framework, and it is not exposed to the user ecosystem. > Using GitHub issues would be ore convenient for use-cases, a

Proposal: Move Jenkins Test Harness issue tracker to GitHub Issues

Hi all, I suggest moving the Jenkins Test Harness issue tracker to GitHub Issues. This is a test framework, and it is not exposed to the user ecosystem. Using GitHub issues would be ore convenient for use-cases, and particularly for onboarding new contributors. What do you think? Currently we

Re: Switching a plugin's issue reporting from Jira to Github Issues

Thanks Tim On Thu, 9 Sep 2021 at 18:28, Daniel Beck wrote: > > On Thu, Sep 9, 2021 at 5:55 PM Chris Kilding < > chris+jenk...@chriskilding.com> wrote: > >> I've got a plugin where I want to switch issue reporting from Jira to >> Github Issues. How would I go about

Re: Switching a plugin's issue reporting from Jira to Github Issues

On Thu, Sep 9, 2021 at 5:55 PM Chris Kilding wrote: > I've got a plugin where I want to switch issue reporting from Jira to > Github Issues. How would I go about that? > My suggestion: Step 1: Enable GitHub Issues. You should have repo admin permissions, if not, ask for that (or j

Switching a plugin's issue reporting from Jira to Github Issues

I've got a plugin where I want to switch issue reporting from Jira to Github Issues. How would I go about that? Regards, Chris -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop r

Re: Sign-up for 'beta projects' in GitHub issues

ervention to highlight the fact that some of the Jenkins contributors have > difficulties with accessing beta features on GitHub. I hope that it will help > to gain access and to evaluate the features. With GitHub Issues becoming more > and more popular in Jenkins, I think it is important

Re: Sign-up for 'beta projects' in GitHub issues

+1 from me and thanks to Tim for starting this thread! I did a little Twitter intervention to highlight the fact that some of the Jenkins contributors have difficulties with accessing beta features on GitHub. I hope that it will help to gain access and to evaluate the features. With GitHub

Re: Sign-up for 'beta projects' in GitHub issues

Thanks! Yes, I would like to try it on https://github.com/jenkins-infra/jenkins.io . On Wed, Jun 23, 2021 at 2:26 PM 'Olblak' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > I added jenkins-infra to the waiting list > > On Wed, Jun 23, 2021, at 10:03 PM, Tim Jacomb wrote: > > M

Re: Sign-up for 'beta projects' in GitHub issues

I added jenkins-infra to the waiting list On Wed, Jun 23, 2021, at 10:03 PM, Tim Jacomb wrote: > Mark mentioned on Twitter he’s like to try it on Jenkins.io too > https://twitter.com/markewaite/status/1407780053769850882?s=21 > > On Wed, 23 Jun 2021 at 20:04, Tim Jacomb wrote: >> Hello, >> >>

Re: Sign-up for 'beta projects' in GitHub issues

Mark mentioned on Twitter he’s like to try it on Jenkins.io too https://twitter.com/markewaite/status/1407780053769850882?s=21 On Wed, 23 Jun 2021 at 20:04, Tim Jacomb wrote: > Hello, > > Should we sign-up for the new beta projects in jenkinsci? > > https://github.com/features/issues > > Would b

Sign-up for 'beta projects' in GitHub issues

Hello, Should we sign-up for the new beta projects in jenkinsci? https://github.com/features/issues Would be useful to be able to set-up more featureful boards across plugins, probably other use-cases too. Thanks Tim -- You received this message because you are subscribed to the Google Groups

Re: Proposal: Open Governance - Tracking key action items/requests in GitHub Issues

On Tue, May 18, 2021 at 2:08 PM Tim Jacomb wrote: > Creating a Jira project is a much higher barrier to entry, > Projects are created by admins, once. > subscribing to project / issues is not something someone that is a little > interested is going to do. > > In GitHub it’s 2 clicks > One cli

Re: Proposal: Open Governance - Tracking key action items/requests in GitHub Issues

Thanks to everyone for the feedback! I added the topic to the today's Jenkins Governance Meeting update so that we could formally agree whether we start a trial. FTR https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#heading=h.1gtco63t6ztr @Sudarshan Please u

Re: Proposal: Open Governance - Tracking key action items/requests in GitHub Issues

Creating a Jira project is a much higher barrier to entry, subscribing to project / issues is not something someone that is a little interested is going to do. In GitHub it’s 2 clicks +1 for the governance repo at least as a trial On Tue, 18 May 2021 at 09:02, Daniel Beck wrote: > > On Mon, Ma

Re: Proposal: Open Governance - Tracking key action items/requests in GitHub Issues

On Mon, May 17, 2021 at 11:59 PM Oleg Nenashev wrote: > What if we create a new public github repo like jenkinsci/governance and > put key issues/projects there, e.g. (Adoption of EasyCLA, CDF Project > representatives Elections, Contributor summit, etc.). It should not be a > replacement for the

Re: Proposal: Open Governance - Tracking key action items/requests in GitHub Issues

I will leave the decision w.r.t LTS processes to Tim Jacomb and the Jenkins release team. IMHO this is the matter of the Jenkins core maintenance, not of the community governance. If we want to move discussions to GitHub (not sure about that), we could enable GitHub discussions or even GitHub

Re: Proposal: Open Governance - Tracking key action items/requests in GitHub Issues

I think that's a great idea. +1 Typically I suppose we'll create an issue for the LTS baseline selection, etc. We'll also then get for free linking between PRs and issues (like the release lead checklist, the backporting PR etc.) I'm slightly concerned it may reduce our discussions here but there

Re: Proposal: Open Governance - Tracking key action items/requests in GitHub Issues

I have got +1s from Ulli and Ewelina in the original discussion in the board mailing list. Thanks to everyone for feedback! I will go ahead and setup the repository. Later we could also try out using it for governance meeting notes with HackMD BR, Oleg On Tuesday, May 18, 2021 at 12:28:50 AM U

Re: Proposal: Open Governance - Tracking key action items/requests in GitHub Issues

On Mon, May 17, 2021 at 3:59 PM Oleg Nenashev wrote: > Hi all, > > I would like to follow-up on a Jenkins governance help offer from Rick in this > thread . > > Currently we do the most of the planning and discussions via mailing lists > an

Re: Proposal: Open Governance - Tracking key action items/requests in GitHub Issues

I think it's a good idea. I'm a huge fan of asynchronous communications like that which make it easier for part time contributors to keep up to date. (Of course, I'm biased since that's what we do at Apache) On Mon, 17 May 2021 at 17:00, Oleg Nenashev wrote: > > Hi all, > > I would like to follow

Proposal: Open Governance - Tracking key action items/requests in GitHub Issues

Hi all, I would like to follow-up on a Jenkins governance help offer from Rick in this thread . Currently we do the most of the planning and discussions via mailing lists and governance meetings. For common community members, it might be

Re: GitHub issues option in HOSTING

> On 21. Feb 2021, at 16:50, Radek Antoniuk wrote: > > > Let me know if I missed something but for me this process looks exactly the > same when we replace Jira with GH Security Advisories system described > above. > The only thing I see missing here is probably the possibility for non-write

Re: GitHub issues option in HOSTING

>> Regarding Security issues - maybe GH new Security Advisories hub could be used for that? >> https://help.github.com/en/github/managing-security-vulnerabilities/about-github-security-advisories >> https://github.blog/2020-05-26-giving-credit-for-security-advisories/ > Our usual workflow is docum

Re: GitHub issues option in HOSTING

> On 15. Feb 2021, at 20:32, Radek Antoniuk wrote: > > Regarding Security issues - maybe GH new Security Advisories hub could be > used for that? > https://help.github.com/en/github/managing-security-vulnerabilities/about-github-security-advisories > https://github.blog/2020-05-26-giving-cred

Re: GitHub issues option in HOSTING

legroups.com> wrote: >> >>> Hi, >>> >>> I think this mail discussion is a proof that we won't easily find a >>> consensus any time soon. >>> I just want to add that we started discussing with Linux foundation >>> infra team to see if

Re: GitHub issues option in HOSTING

proof that we won't easily find a >>> consensus any time soon. >>> I just want to add that we started discussing with Linux foundation >>> infra team to see if they could maintained a managed version of Jira for >>> us, more information in this email >

Re: GitHub issues option in HOSTING

foundation >> infra team to see if they could maintained a managed version of Jira for >> us, more information in this email >> <https://groups.google.com/u/1/g/jenkins-infra/c/f0j2xRHkfKA>. >> >> So please keep discussing about Jira and/or Github Issues here and things

Re: GitHub issues option in HOSTING

t; team to see if they could maintained a managed version of Jira for us, more > information in this email > <https://groups.google.com/u/1/g/jenkins-infra/c/f0j2xRHkfKA>. > > So please keep discussing about Jira and/or Github Issues here and things > specific to how we maintain is

Re: GitHub issues option in HOSTING

lt;https://groups.google.com/u/1/g/jenkins-infra/c/f0j2xRHkfKA>. So please keep discussing about Jira and/or Github Issues here and things specific to how we maintain issues.jenkins-ci.org on the other thread. Cheers On Fri, Jun 19, 2020, at 12:58 PM, Radosław Antoniuk wrote: > On Fri, Jun 19, 2020 a

Re: GitHub issues option in HOSTING

On Fri, Jun 19, 2020 at 12:30 PM Tim Jacomb wrote: > On Fri, 19 Jun 2020 at 10:36, Daniel Beck wrote: > >> Having a screen like >> https://github.com/jenkinsci/configuration-as-code-plugin/issues/new/choose >> could help here, but that's far from universal right now. Is this something >> that co

Re: GitHub issues option in HOSTING

On Fri, 19 Jun 2020 at 10:36, Daniel Beck wrote: > Having a screen like > https://github.com/jenkinsci/configuration-as-code-plugin/issues/new/choose > could help here, but that's far from universal right now. Is this something > that could be defined via .github? Having a screen similar to this

Re: GitHub issues option in HOSTING

> On 19. Jun 2020, at 11:47, Radosław Antoniuk wrote: > >> I would be surprised if we wouldn't regularly get 0-days because people with >> just a GH account don't bother to do it properly, and just report issues on >> GH. If that is enabled in repos without someone regularly reviewing incomi

Re: GitHub issues option in HOSTING

> > I would be surprised if we wouldn't regularly get 0-days because people > with just a GH account don't bother to do it properly, and just report > issues on GH. If that is enabled in repos without someone regularly > reviewing incoming issues, or by a maintainer who's unaware of how we > handle

Re: GitHub issues option in HOSTING

> On 18. Jun 2020, at 22:50, Tim Jacomb wrote: > > The security team already uses a different project in Jira to everyone else, > I don't think we need to change that currently, maintainers will just use > whatever the security team decides I would think? > > Mentioned this earlier: > > One

Re: GitHub issues option in HOSTING

To add to Jesse's numbers here's a summary for the JenkinsCI organisation: Org report: jenkinsci Total repositories: 2290 Number with GitHub issues enabled: 355 (15%) Total issues open: 3338 Total issues closed: 17941 Total issues: 21279 https://gist.github

Re: GitHub issues option in HOSTING

On Thu, 18 Jun 2020 at 21:44, James Nord wrote: > > am I missing something in this thread > > security reports? > > currently they are all triaged by the security team so the team can track > disclosure deadlines etc. > how would that worknif the plugin is usimg GH issues? (yes I know gh > issues

Re: GitHub issues option in HOSTING

> am I missing something in this thread security reports? currently they are all triaged by the security team so the team can track disclosure deadlines etc. how would that worknif the plugin is usimg GH issues? (yes I know gh issues can now handle security reports but does that mean the secu

Re: GitHub issues option in HOSTING

Agreed, I think we need to have this as a topic in that meeting. I think there are two parts of this topic: 1. Do we want to allow both Jira and Github issues to coexist in the Jenkins infrastructure? 1. This is _somewhat_ moot at this point because we already have a large

Re: GitHub issues option in HOSTING

> Am 18.06.2020 um 19:48 schrieb 'Gavin Mogan' via Jenkins Developers > : > > > Puh, that is a lot. That means we already cerated a mess for our users by > > providing two different tools for the same thing :-( > > Which is why I want to know what and how we want to support things officiall

Re: GitHub issues option in HOSTING

> Puh, that is a lot. That means we already cerated a mess for our users by providing two different tools for the same thing :-( Which is why I want to know what and how we want to support things officially so I can add it to the plugin site. > The superiority of Jira in terms of features is obvi

Re: GitHub issues option in HOSTING

Puh, that is a lot. That means we already cerated a mess for our users by providing two different tools for the same thing :-( > Am 18.06.2020 um 19:36 schrieb Jesse Glick : > > stashnotifier-plugin -- You received this message because you are subscribed to the Google Groups "Jenkins Develop

Re: GitHub issues option in HOSTING

On Thu, Jun 18, 2020 at 12:51 PM Ullrich Hafner wrote: >> we are already past that point as the plugins are already mixed up between >> Jira and GH. > > I don’t think that we are past the point yet, just because a couple of > plugins managed it to enable GitHub

Re: GitHub issues option in HOSTING

> > > > > About consistency, I fully agree, but we are already past that point as > the plugins are already mixed up between Jira and GH. > > I don’t think that we are past the point yet, just because a couple of > plugins managed it to enable GitHub issues. From my

Re: GitHub issues option in HOSTING

he > plugins are already mixed up between Jira and GH. I don’t think that we are past the point yet, just because a couple of plugins managed it to enable GitHub issues. From my understanding the hosting process creates a Jira component and GitHub Issues is disabled for the repository

Re: GitHub issues option in HOSTING

we need an evaluation with an updated Jira as some people have said the newer one is better. I find working with GitHub issues far superior than Jira, and think that we should do more to support GitHub issues, defaulting to enabling it on new plugins, and showing them in the plugin site etc A

Re: GitHub issues option in HOSTING

On Fri, Jun 12, 2020 at 6:07 AM Dominik Bartholdi wrote: > I fully agrees with Uli and James… the main reason for me is the > searchability of the issue IDs. Many many times I have the JIRA Issue ID > (e.g. in commits) and then a simple Google search brings up the exact issue > - with GH-Issues,

Re: GitHub issues option in HOSTING

to host it. GitHub is > also fast and modern (but Jira 8.x improved a lot on that side, maybe it > would help to upgrade to a more recent version on our side). > >> Am 11.06.2020 um 17:26 schrieb Jeff Thompson > <mailto:jthomp...@cloudbees.com>>: >> >> On

Re: GitHub issues option in HOSTING

According to https://issues.jenkins-ci.org/browse/INFRA-2010?jql=text%20~%20%22jira%22%20and%20text%20~%20%22ldap%22%20and%20text%20~%20%22cloud%22 there's also an issue that you can't import only 5k users total, and we have more than 100k users. https://confluence.atlassian.com/cloud/saml-single-

Re: GitHub issues option in HOSTING

The issue with the cloud version is that it is not compatible with our LDAP (at least that is what I believe Olivier said last time). On Thu, Jun 11, 2020 at 2:28 PM James Nord wrote: > I agree with Ulli's statements. > > There seems to be comments that our hosted Jira is sluggish or hard to > m

Re: GitHub issues option in HOSTING

I agree with Ulli's statements. There seems to be comments that our hosted Jira is sluggish or hard to maintain. I've asked before but why can,t the cloud version be an option? we should be able to spin up a stateless SAML to LDAP integration for Jira Cloud with much less effort than continuing

Re: GitHub issues option in HOSTING

side). > Am 11.06.2020 um 17:26 schrieb Jeff Thompson : > > On 6/11/20 8:32 AM, Slide wrote: >> The big problem with GitHub issues is when a bug involves multiple >> components, or is filed against the wrong component. If you filed an issue >> in the wrong component

Re: GitHub issues option in HOSTING

On Thu, Jun 11, 2020 at 11:26 AM Jeff Thompson wrote: > Jenkins is a system of interacting components and issues may involve multiple. Every time I have worked with a Jira issue with multiple components, I have wound up regretting the resulting confusion. It gets marked fixed by one person due to

Re: GitHub issues option in HOSTING

On 6/11/20 8:32 AM, Slide wrote: The big problem with GitHub issues is when a bug involves multiple components, or is filed against the wrong component. If you filed an issue in the wrong component, what would you expect the maintainers of that component to do? I don't think it should

Re: GitHub issues option in HOSTING

Wouldn't you either transfer it or ask them to re-file with the correct component? Same as with Jira? I doubt issues filed with the wrong component in Jira are ever seen by the right people either. Thanks Tim On Thu, 11 Jun 2020 at 15:33, Slide wrote: > The big problem with GitHub i

Re: GitHub issues option in HOSTING

The big problem with GitHub issues is when a bug involves multiple components, or is filed against the wrong component. If you filed an issue in the wrong component, what would you expect the maintainers of that component to do? I don't think it should be on them to find the right componen

  1   2   >