comment-ops-bot available in jenkinsci and jenkins-infra

2022-07-25 Thread Tim Jacomb
Hi all I've created a comment-ops bot that can be used to help manage issues and pull requests on GitHub. The features it has currently are: - /close - Issues only - /label - /remove-label - /reopen - Issues only - /reviewer(s) - /transfer It can be found at:

Re: comment-ops-bot available in jenkinsci and jenkins-infra

2022-07-25 Thread Tim Jacomb
I think something like this should sort out the concerns of permissive defaults: https://github.com/timja/github-comment-ops/pull/56#issuecomment-1193852554 something along the lines of (allowed at org and repo level): config: commands: - name: transfer permission: member

Re: comment-ops-bot available in jenkinsci and jenkins-infra

2022-07-25 Thread Tim Jacomb
> What if I don't want randos on the internet messing up labeling of open PRs in repos I maintain? There's an issue here: https://github.com/timja/github-comment-ops/issues/54 I'm not sure how to scale that though, I thought about adding topic controls but that would mean an extra API call on each

Re: comment-ops-bot available in jenkinsci and jenkins-infra

2022-07-25 Thread Alexander Brandes
Hey, > What if I don't want randos on the internet messing up labeling of open PRs in repos I maintain? if this is going to be installed on all repositories, https://github.com/jenkinsci/jenkins/pull/6918 should be implemented and outlined in the README how to opt out. This definitely is a

Re: comment-ops-bot available in jenkinsci and jenkins-infra

2022-07-25 Thread 'Daniel Beck' via Jenkins Developers
On Mon, Jul 25, 2022 at 12:20 PM Tim Jacomb wrote: > > Can we have review requests enabled by default while label changes are > opt in? > > I'm not sure if that would scale across the number of infrequently touched > repositories that we have. > Infrequently touched repos are the problem for

Re: comment-ops-bot available in jenkinsci and jenkins-infra

2022-07-25 Thread 'Daniel Beck' via Jenkins Developers
On Mon, Jul 25, 2022 at 12:03 PM Alexander Brandes wrote: > opt out. > Can we have review requests enabled by default while label changes are opt in? -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and

Re: comment-ops-bot available in jenkinsci and jenkins-infra

2022-07-25 Thread 'Daniel Beck' via Jenkins Developers
On Mon, Jul 25, 2022 at 10:22 AM Tim Jacomb wrote: > It requires no organization permissions, which means anyone can request a > review and add labels to issues and pull requests. > What if I don't want randos on the internet messing up labeling of open PRs in repos I maintain? -- You

Re: comment-ops-bot available in jenkinsci and jenkins-infra

2022-07-25 Thread Tim Jacomb
> Can we have review requests enabled by default while label changes are opt in? I'm not sure if that would scale across the number of infrequently touched repositories that we have. There's some good discussion happening in: https://github.com/timja/github-comment-ops/pull/56 On Mon, 25 Jul

Re: Governance meeting - July 25, 2022

2022-07-25 Thread Mark Waite
On Monday, July 25, 2022 at 10:43:25 AM UTC-6 Gavin Mogan wrote: > *puts on board hat* I'm able to make this weeks meeting. > > Looking at my new team's schedule. I'd love to see this meeting a week > an hour or two earlier, or an hour later. As it stands now the > meeting is at 11am and

Governance meeting - July 25, 2022

2022-07-25 Thread Mark Waite
Governance meeting starts in about 90 minutes at 6:00 PM UTC. Agenda items include: - News - Action items - Blue ocean status statement proposal -

Re: Governance meeting - July 25, 2022

2022-07-25 Thread 'Gavin Mogan' via Jenkins Developers
*puts on board hat* I'm able to make this weeks meeting. Looking at my new team's schedule. I'd love to see this meeting a week an hour or two earlier, or an hour later. As it stands now the meeting is at 11am and smack in the middle of my morning, which makes it hard to plan around. Gavin On

Action disappears after restart

2022-07-25 Thread Nozim Islamov
Hello everyone, hope you guys having a good day, I have a question, I have an action, this action is added during build step, it adds up new action to the build, and after Jenkins restart, all added actions disappear, what could be a solution to keep added actions even after restart? -- You

Re: Action disappears after restart

2022-07-25 Thread 'Gavin Mogan' via Jenkins Developers
What type of action is it? Something extending a transientaction won't persist. You shoudn't need to, especially since it'll be done after a build finishes, but you could call build.save() How are you confirming the action has disappeared? On Mon, Jul 25, 2022 at 2:33 PM Nozim Islamov wrote: >

Re: Action disappears after restart

2022-07-25 Thread Nozim Islamov
I see, yeah I use transient Run, probably that might be the issue, thanks! On Monday, July 25, 2022 at 2:34:52 PM UTC-7 ga...@gavinmogan.com wrote: > What type of action is it? Something extending a transientaction won't > persist. > You shoudn't need to, especially since it'll be done after a