Re: JIRA Status - Finding Patch Submissions

Thank you Allen for the info! I made some progress with the integration for Solr and had several test-runs on SOLR-10912 and SOLR-10783. I have a WIP script [1] that can executed on a single issue id so it could be used for Precommit jenkins jobs. It... - runs test4tests, notification if no

Re: JIRA Status - Finding Patch Submissions

On 2017-05-17 19:10 (-0700), David Smiley wrote: > > How else other than a comment could the system communicate results back to > > the user? Or do you mean that whatever runs should post a comment, but > > suppress email notification somehow. > > > > Yes; that. The

Re: JIRA Status - Finding Patch Submissions

Hi, Mike pointed to this thread after I created SOLR-10912 (I missed this conversation). I am for running validations automatically against patches, similarly what Hadoop or Oziee (and probably others) have. I don't have strong opinion what and when to check, but I believe that it could be

Re: JIRA Status - Finding Patch Submissions

On Wed, May 17, 2017 at 7:36 PM Mike Drob wrote: > David, what do you mean by > > > Hopefully without generating comments that trigger email/watcher > notifications and thus no more dev list traffic. > > How else other than a comment could the system communicate results back to

Re: JIRA Status - Finding Patch Submissions

> This could be a submitter changing state to "Patch Available" or could be a naming convention Yes, I was thinking on something along those lines too. I've also seen tools triggering by specific comments in Jira. Any way is fine with me. > If the state is set automatically, how do we know when to

Re: JIRA Status - Finding Patch Submissions

David, what do you mean by > Hopefully without generating comments that trigger email/watcher notifications and thus no more dev list traffic. How else other than a comment could the system communicate results back to the user? Or do you mean that whatever runs should post a comment, but

Re: JIRA Status - Finding Patch Submissions

> Additionally, we could use that to start running precommit checks on Jenkins whenever a new patch is put up. This is a good idea, but we don't want to do this for every patch I'd say. We encourage people to submit patches early, probably with failing tests and nocommits. We probably want an

Re: JIRA Status - Finding Patch Submissions

Thanks for researching the state of our JIRA issues and summarizing the situation for us. > Patch Available JIRA state +1 > We should also consider running unit tests as part of the process. +1 That'd be cool! Hopefully without generating comments that trigger email/watcher notifications and

Re: JIRA Status - Finding Patch Submissions

>>For current patches, I think we could really benefit from a Patch Available JIRA state. It would be a bright big flag for committers, instead of making contributors have to hound us periodically to look. Additionally, we could use that to start running precommit checks on Jenkins whenever a new

Re: JIRA Status - Finding Patch Submissions

Wanted to follow up on this, since I've been steadily working away at old JIRA issues when I have some time for them. I think read through 100s of issues and closed about 20 as either duplicates or already committed, which is a tiny drop in the ocean of what we have open. In an attempt to cut the

Re: JIRA Status - Finding Patch Submissions

On 4/28/2017 9:42 AM, Mike Drob wrote: > Thanks for this hint, Alex. > > I ran the following JQL to get some idea of our current status: > project in (lucene, solr) and "Attachment count" > 0 and status = Open > > There were 1500 results. > > 1500. I couldn't believe it. This is a huge number

Re: JIRA Status - Finding Patch Submissions

So I started going through old JIRAs, and realized I don't have permission to close duplicates. Could I have more JIRA permissions to complete this task? I know some projects have given non-committers additional JIRA roles for those willing to do JIRA maintenance as a contribution. Alternatively,

Re: JIRA Status - Finding Patch Submissions

Thanks for this hint, Alex. I ran the following JQL to get some idea of our current status: project in (lucene, solr) and "Attachment count" > 0 and status = Open There were 1500 results. 1500. I couldn't believe it. This is a huge number of patches that are out there. I did a spot check,

Re: JIRA Status - Finding Patch Submissions

There is an "Attachment count" filter, you can say it to be 1+. Not everything will be a patch, but it is a good first pass. It is under "More" dropdown. We also have some Github Integration fields in there, but they don't seem to be actually doing anything for Solr project. Regards, Alex.

JIRA Status - Finding Patch Submissions

Devs, Does anybody have good JIRA filters or processes for finding issues with patches available and attached, or maybe with open pull requests for them? I was talking to a few folks and we remarked how patches can sometimes sit on issues for a long time, and this seems like a wasted opportunity