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

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. > Am 23.05.2022 um 20:54 schrieb Basil Crow : > > On Thu, Apr 28, 2022 at 1:22 AM 'Daniel Beck' via Jenkins De

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

On Thu, Apr 28, 2022 at 1:22 AM 'Daniel Beck' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > Not part of the core deliverable, but core team repos. Projects still likely cross issue trackers. Yes. In jenkins-infra/helpdesk#2819

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 makes it impossib

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

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 particularly for > onboar

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

I would actually expand that to all developer tools we have in the project They are isolated from distributions, and hence it does not make much sense to keep them in the integrated Jira On Sunday, October 17, 2021 at 12:05:17 PM UTC+2 timja...@gmail.com wrote: > +1 > > On Sun, 17 Oct 2021 at 09

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, and particularly > f