Re: Automation of Fedora SCM requests

[Michel Alexandre Salim]

On Sat, 2023-01-21 at 20:52 +0100, Fabio Valentini wrote:
> On Thu, Jan 19, 2023 at 11:18 AM Michal Konecny 
> wrote:
> > 
> > I would say that the current way is OK, the bot asks fedora-scm-
> > requests
> > admins to validate the requests, because it is marked as exception.
> > After being validated it gets created.
> > 
> > Or if there should be an exception for Rust packages, we can add
> > name
> > validation and if the name of the package is rust something, we can
> > skip
> > the validation process. But this unfortunately let people create
> > any
> > repository with name rust with exception set to true without any
> > validation and I'm not sure if we want this.
> 
> I don't think there should be any special-casing of Rust packages.
> The
> same guidelines for compat packages apply to them as to any other
> package, so I don't see why they should be processed differently
> (i.e.
> without human validation).
> 
One half-way solution might be to allow different operators to approve
certain requests -- e.g. if for rust-*[NUM] requests with exceptions,
@rust-sig members also get pinged and can approve such requests.


Best regards,

-- 
Michel Alexandre Salim
identities:
https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2


signature.asc
Description: This is a digitally signed message part
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Automation of Fedora SCM requests

[Fabio Valentini]

On Thu, Jan 19, 2023 at 11:18 AM Michal Konecny  wrote:
>
> I would say that the current way is OK, the bot asks fedora-scm-requests
> admins to validate the requests, because it is marked as exception.
> After being validated it gets created.
>
> Or if there should be an exception for Rust packages, we can add name
> validation and if the name of the package is rust something, we can skip
> the validation process. But this unfortunately let people create any
> repository with name rust with exception set to true without any
> validation and I'm not sure if we want this.

I don't think there should be any special-casing of Rust packages. The
same guidelines for compat packages apply to them as to any other
package, so I don't see why they should be processed differently (i.e.
without human validation).

Fabio
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Automation of Fedora SCM requests

[Michal Konecny]

I would say that the current way is OK, the bot asks fedora-scm-requests 
admins to validate the requests, because it is marked as exception. 
After being validated it gets created.


Or if there should be an exception for Rust packages, we can add name 
validation and if the name of the package is rust something, we can skip 
the validation process. But this unfortunately let people create any 
repository with name rust with exception set to true without any 
validation and I'm not sure if we want this.


The solution from kevin that the fedpkg request will actually say that 
it's a compat request and provides name of the previous package, it 
could be validated by bot itself and automated. Right now the bot 
doesn't really know if this is a compat package or not, the request 
doesn't have that info.


Michal

On 18. 01. 23 23:13, Kevin Fenzi wrote:

On Wed, Jan 18, 2023 at 12:36:35PM -0600, Michel Alexandre Salim wrote:

Hi Michal,

On Wed, 2023-01-11 at 17:13 +0100, Michal Konecny wrote:

  Hi everyone,
  
  all the remaining issues were solved and the bot is now processing

tickets as it should. I will watch the SCM request repository for
next few days to see if everything is working as it should.
  Thanks for your patience.
  

Where can I direct feature requests? Per
https://pagure.io/releng/fedora-scm-requests/issue/50507 seems like
requesting repos with exceptions (e.g. for Rust compat packages) is
currently not automated.

I'm not sure how we can automate this.

I mean I guess we could just check that the requestor is a packager and
let them create any package name they wish? Or is there some programic
way we can tell it's a compat package and that its correctly named?

Perhaps we could extend fedpkg to ask for and provide more info to the
processing ticket? like name of orig package (check that it exists, etc)
and that the new compat package has a name thats based on it?

Thoughts?

kevin

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Automation of Fedora SCM requests

[Michal Konecny]

Hi Michel,

you can file feature requests in 
https://pagure.io/fedora-infra/toddlers/issues


On behalf of CPE Team,
Michal

On 18. 01. 23 19:36, Michel Alexandre Salim wrote:

Hi Michal,

On Wed, 2023-01-11 at 17:13 +0100, Michal Konecny wrote:

  Hi everyone,
  
  all the remaining issues were solved and the bot is now processing

tickets as it should. I will watch the SCM request repository for
next few days to see if everything is working as it should.
  Thanks for your patience.
  

Where can I direct feature requests? Per
https://pagure.io/releng/fedora-scm-requests/issue/50507 seems like
requesting repos with exceptions (e.g. for Rust compat packages) is
currently not automated.

Thanks,


___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Automation of Fedora SCM requests

[Kevin Fenzi]

On Wed, Jan 18, 2023 at 12:36:35PM -0600, Michel Alexandre Salim wrote:
> Hi Michal,
> 
> On Wed, 2023-01-11 at 17:13 +0100, Michal Konecny wrote:
> >  Hi everyone,
> >  
> >  all the remaining issues were solved and the bot is now processing
> > tickets as it should. I will watch the SCM request repository for
> > next few days to see if everything is working as it should.
> >  Thanks for your patience.
> >  
> Where can I direct feature requests? Per
> https://pagure.io/releng/fedora-scm-requests/issue/50507 seems like
> requesting repos with exceptions (e.g. for Rust compat packages) is
> currently not automated.

I'm not sure how we can automate this. 

I mean I guess we could just check that the requestor is a packager and
let them create any package name they wish? Or is there some programic
way we can tell it's a compat package and that its correctly named?

Perhaps we could extend fedpkg to ask for and provide more info to the
processing ticket? like name of orig package (check that it exists, etc)
and that the new compat package has a name thats based on it?

Thoughts?

kevin


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Automation of Fedora SCM requests

[Michel Alexandre Salim]

Hi Michal,

On Wed, 2023-01-11 at 17:13 +0100, Michal Konecny wrote:
>  Hi everyone,
>  
>  all the remaining issues were solved and the bot is now processing
> tickets as it should. I will watch the SCM request repository for
> next few days to see if everything is working as it should.
>  Thanks for your patience.
>  
Where can I direct feature requests? Per
https://pagure.io/releng/fedora-scm-requests/issue/50507 seems like
requesting repos with exceptions (e.g. for Rust compat packages) is
currently not automated.

Thanks,

-- 
Michel Alexandre Salim
identities:
https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2


signature.asc
Description: This is a digitally signed message part
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Automation of Fedora SCM requests

[Michel Alexandre Salim]

Hi Michal and CPE,
On Wed, Jan 11, 2023 at 05:13:47PM +0100, Michal Konecny wrote:
> Hi everyone,
> 
> all the remaining issues were solved and the bot is now processing tickets
> as it should. I will watch the SCM request repository for next few days to
> see if everything is working as it should.
> Thanks for your patience.
> 
> On behalf of CPE Team,
> Michal
> 

Thank you so much! As someone who does a lot of EPEL 9 branch requests,
the branch request I did earlier today (the first after the automation
landed) was a pleasant surprise.

Best regards,

-- 
Michel Alexandre Salim
identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Automation of Fedora SCM requests

[Michal Konecny]

Hi,

churchyard already responded on this ticket and this is caused by 
webhook that is preventing creating new branches. And he even mentioned 
how we should process it in the SCM Request Processor.


I didn't know there is even something like webhook that could prevent 
pushing new branches and the original script used by release engineering 
didn't cover this case. This needs to be implemented in SCM Request 
Processor.


Michal

On 12. 01. 23 15:27, Jonathan Wright via devel wrote:
Just got the following error: 
https://pagure.io/releng/fedora-scm-requests/issue/50417


I'm pretty sure I've always requested branches as someone with 
"commit" access and never had them rejected.


On Thu, Jan 12, 2023 at 3:30 AM Dominik 'Rathann' Mierzejewski 
 wrote:


On Wednesday, 11 January 2023 at 17:13, Michal Konecny wrote:
> Hi everyone,
>
> all the remaining issues were solved and the bot is now processing
> tickets as it should. I will watch the SCM request repository
for next
> few days to see if everything is working as it should.
> Thanks for your patience.

Thank you Michal and the CPE Team. Automating this part is a very
welcome improvement.

Regards,
Dominik
-- 
Fedora https://getfedora.org  | RPM Fusion http://rpmfusion.org

There should be a science of discontent. People need hard times and
oppression to develop psychic muscles.
        -- from "Collected Sayings of Muad'Dib" by the Princess Irulan
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue



--
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 

___
devel mailing list --devel@lists.fedoraproject.org
To unsubscribe send an email todevel-le...@lists.fedoraproject.org
Fedora Code of 
Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines
List 
Archives:https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report 
it:https://pagure.io/fedora-infrastructure/new_issue
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Automation of Fedora SCM requests

[Gwyn Ciesla via devel]

-- 
Gwyn Ciesla
she/her/hers
 
in your fear, seek only peace 
in your fear, seek only love
-d. bowie


Sent with Proton Mail secure email.

--- Original Message ---
On Thursday, January 12th, 2023 at 8:40 AM, Stephen Smoogen 
 wrote:


> 

> 

> On Thu, 12 Jan 2023 at 09:27, Jonathan Wright via devel 
>  wrote:
> 

> > Just got the following error: 
> > https://pagure.io/releng/fedora-scm-requests/issue/50417
> > 

> > I'm pretty sure I've always requested branches as someone with "commit" 
> > access and never had them rejected.
> 

> 

> So what I think is being exposed is more of the 'errors/problems' that 
> whoever was doing this in releng ran into at times. Hopefully this will allow 
> for work on getting the lower level issues fixed or replaced.


This is correct. At the same time it fixes issues like "ownership got messed up 
because Gwyn's ISP lost the plot".  A definite improvement.


> > On Thu, Jan 12, 2023 at 3:30 AM Dominik 'Rathann' Mierzejewski 
> >  wrote:
> > 

> > > On Wednesday, 11 January 2023 at 17:13, Michal Konecny wrote:
> > > > Hi everyone,
> > > >
> > > > all the remaining issues were solved and the bot is now processing
> > > > tickets as it should. I will watch the SCM request repository for next
> > > > few days to see if everything is working as it should.
> > > > Thanks for your patience.
> > > 

> > > Thank you Michal and the CPE Team. Automating this part is a very
> > > welcome improvement.
> > > 

> > > Regards,
> > > Dominik
> > > --
> > > Fedora https://getfedora.org | RPM Fusion http://rpmfusion.org
> > > There should be a science of discontent. People need hard times and
> > > oppression to develop psychic muscles.
> > > -- from "Collected Sayings of Muad'Dib" by the Princess Irulan
> > > ___
> > > devel mailing list -- devel@lists.fedoraproject.org
> > > To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> > > Fedora Code of Conduct: 
> > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > > List Archives: 
> > > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> > > Do not reply to spam, report it: 
> > > https://pagure.io/fedora-infrastructure/new_issue
> > 

> > 

> > 

> > --
> > Jonathan Wright
> > AlmaLinux FoundationMattermost: chat
> > ___
> > devel mailing list -- devel@lists.fedoraproject.org
> > To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> > Fedora Code of Conduct: 
> > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives: 
> > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> > Do not reply to spam, report it: 
> > https://pagure.io/fedora-infrastructure/new_issue
> 

> 

> 

> --
> 

> Stephen Smoogen, Red Hat Automotive
> Let us be kind to one another, for most of us are fighting a hard battle. -- 
> Ian MacClaren

signature.asc
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Automation of Fedora SCM requests

[Stephen Smoogen]

On Thu, 12 Jan 2023 at 09:27, Jonathan Wright via devel <
devel@lists.fedoraproject.org> wrote:

> Just got the following error:
> https://pagure.io/releng/fedora-scm-requests/issue/50417
>
> I'm pretty sure I've always requested branches as someone with "commit"
> access and never had them rejected.
>
>
So what I think is being exposed is more of the 'errors/problems' that
whoever was doing this in releng ran into at times. Hopefully this will
allow for work on getting the lower level issues fixed or replaced.


> On Thu, Jan 12, 2023 at 3:30 AM Dominik 'Rathann' Mierzejewski <
> domi...@greysector.net> wrote:
>
>> On Wednesday, 11 January 2023 at 17:13, Michal Konecny wrote:
>> > Hi everyone,
>> >
>> > all the remaining issues were solved and the bot is now processing
>> > tickets as it should. I will watch the SCM request repository for next
>> > few days to see if everything is working as it should.
>> > Thanks for your patience.
>>
>> Thank you Michal and the CPE Team. Automating this part is a very
>> welcome improvement.
>>
>> Regards,
>> Dominik
>> --
>> Fedora   https://getfedora.org  |  RPM Fusion  http://rpmfusion.org
>> There should be a science of discontent. People need hard times and
>> oppression to develop psychic muscles.
>> -- from "Collected Sayings of Muad'Dib" by the Princess Irulan
>> ___
>> devel mailing list -- devel@lists.fedoraproject.org
>> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>> Fedora Code of Conduct:
>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives:
>> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>> Do not reply to spam, report it:
>> https://pagure.io/fedora-infrastructure/new_issue
>>
>
>
> --
> Jonathan Wright
> AlmaLinux Foundation
> Mattermost: chat 
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>


-- 
Stephen Smoogen, Red Hat Automotive
Let us be kind to one another, for most of us are fighting a hard battle.
-- Ian MacClaren
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Automation of Fedora SCM requests

[Jonathan Wright via devel]

Just got the following error:
https://pagure.io/releng/fedora-scm-requests/issue/50417

I'm pretty sure I've always requested branches as someone with "commit"
access and never had them rejected.

On Thu, Jan 12, 2023 at 3:30 AM Dominik 'Rathann' Mierzejewski <
domi...@greysector.net> wrote:

> On Wednesday, 11 January 2023 at 17:13, Michal Konecny wrote:
> > Hi everyone,
> >
> > all the remaining issues were solved and the bot is now processing
> > tickets as it should. I will watch the SCM request repository for next
> > few days to see if everything is working as it should.
> > Thanks for your patience.
>
> Thank you Michal and the CPE Team. Automating this part is a very
> welcome improvement.
>
> Regards,
> Dominik
> --
> Fedora   https://getfedora.org  |  RPM Fusion  http://rpmfusion.org
> There should be a science of discontent. People need hard times and
> oppression to develop psychic muscles.
> -- from "Collected Sayings of Muad'Dib" by the Princess Irulan
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>


-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Automation of Fedora SCM requests

[Dominik 'Rathann' Mierzejewski]

On Wednesday, 11 January 2023 at 17:13, Michal Konecny wrote:
> Hi everyone,
> 
> all the remaining issues were solved and the bot is now processing
> tickets as it should. I will watch the SCM request repository for next
> few days to see if everything is working as it should.
> Thanks for your patience.

Thank you Michal and the CPE Team. Automating this part is a very
welcome improvement.

Regards,
Dominik
-- 
Fedora   https://getfedora.org  |  RPM Fusion  http://rpmfusion.org
There should be a science of discontent. People need hard times and
oppression to develop psychic muscles.
-- from "Collected Sayings of Muad'Dib" by the Princess Irulan
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Automation of Fedora SCM requests

[Otto Liljalaakso]

Richard Shaw kirjoitti 10.1.2023 klo 15.08:

On Tue, Jan 10, 2023 at 5:26 AM Michal Konecny  wrote:


Hi everyone,

this automation is now in place and new SCM requests will be processed
automatically. If you find any issue with the automation, please report it
to toddlers issue tracker [0].

On behalf of CPE Team,
Michal

[0] - https://pagure.io/fedora-infra/toddlers/issues



While I'm hopeful I can find this email if needed but it would be better if
this was documented here (and wherever else appropriate):

https://docs.fedoraproject.org/en-US/package-maintainers/New_Package_Process_for_New_Contributors/#add_package_to_source_code_management_scm_system_and_set_owner


Pull request:
https://pagure.io/fedora-docs/package-maintainer-docs/pull-request/107

I am grateful if authors of the new automation can review this.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Automation of Fedora SCM requests

[Michal Konecny]

Hi everyone,

all the remaining issues were solved and the bot is now processing 
tickets as it should. I will watch the SCM request repository for next 
few days to see if everything is working as it should.

Thanks for your patience.

On behalf of CPE Team,
Michal

On 10. 01. 23 18:29, Michal Konecny wrote:
Most of the issues are resolved now. There is one remaining ticket [0] 
that is returning 500 on branch creation. I will continue 
investigation on this ticket tomorrow.


I'm sorry for the rough start.

On behalf of CPE Team,
Michal

[0] - https://pagure.io/releng/fedora-scm-requests/issue/50370

On 10. 01. 23 13:52, Michal Konecny wrote:

Hi everyone,

after deployment we had some issues with API tokens for 
src.fedorapoject.org and pagure.io. Those issues are now solved.
Only one issue remains and that is missing list of epel9 packages on 
https://infrastructure.fedoraproject.org/repo/json

We are currently working on that.

All the epel9 branch requests will fail right now, we will reprocess 
them once this is fixed.


On behalf of CPE Team,
Michal

On 10. 01. 23 12:26, Michal Konecny wrote:

Hi everyone,

this automation is now in place and new SCM requests will be 
processed automatically. If you find any issue with the automation, 
please report it to toddlers issue tracker [0].


On behalf of CPE Team,
Michal

[0] - https://pagure.io/fedora-infra/toddlers/issues

On 08. 12. 22 11:10, Michal Konecny wrote:

Hello everyone,

for some time CPE (Community Platform Engineering) team is working 
on automating Fedora SCM requests [0]. The automation is currently 
live on staging. You can see the output (closed tickets) in Fedora 
SCM requests staging repo [1].
The automation is done using a plugin in toddlers [2]. We have a 
documentation [3] for the new toddler, if you want to know more 
about it. There is also a ticket [4] tracking this work.


We plan to deploy this in production on *10th January 2023*, after 
that all the Fedora SCM request will be processed automatically and 
it will ping correct people if the manual intervention is needed. 
This will not change anything in user workflow, it will just make 
the job of Fedora Release Engineering Team easier and let them 
focus on other things.


On behalf of CPE Team,
Michal

[0] - https://pagure.io/releng/fedora-scm-requests
[1] - https://stg.pagure.io/releng/fedora-scm-requests
[2] - https://pagure.io/fedora-infra/toddlers
[3] - https://pagure.io/fedora-infra/toddlers/blob/main/f/docs
[4] - https://pagure.io/releng/issue/9274






___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Automation of Fedora SCM requests

[Michal Konecny]

Most of the issues are resolved now. There is one remaining ticket [0] 
that is returning 500 on branch creation. I will continue investigation 
on this ticket tomorrow.


I'm sorry for the rough start.

On behalf of CPE Team,
Michal

[0] - https://pagure.io/releng/fedora-scm-requests/issue/50370

On 10. 01. 23 13:52, Michal Konecny wrote:

Hi everyone,

after deployment we had some issues with API tokens for 
src.fedorapoject.org and pagure.io. Those issues are now solved.
Only one issue remains and that is missing list of epel9 packages on 
https://infrastructure.fedoraproject.org/repo/json

We are currently working on that.

All the epel9 branch requests will fail right now, we will reprocess 
them once this is fixed.


On behalf of CPE Team,
Michal

On 10. 01. 23 12:26, Michal Konecny wrote:

Hi everyone,

this automation is now in place and new SCM requests will be 
processed automatically. If you find any issue with the automation, 
please report it to toddlers issue tracker [0].


On behalf of CPE Team,
Michal

[0] - https://pagure.io/fedora-infra/toddlers/issues

On 08. 12. 22 11:10, Michal Konecny wrote:

Hello everyone,

for some time CPE (Community Platform Engineering) team is working 
on automating Fedora SCM requests [0]. The automation is currently 
live on staging. You can see the output (closed tickets) in Fedora 
SCM requests staging repo [1].
The automation is done using a plugin in toddlers [2]. We have a 
documentation [3] for the new toddler, if you want to know more 
about it. There is also a ticket [4] tracking this work.


We plan to deploy this in production on *10th January 2023*, after 
that all the Fedora SCM request will be processed automatically and 
it will ping correct people if the manual intervention is needed. 
This will not change anything in user workflow, it will just make 
the job of Fedora Release Engineering Team easier and let them focus 
on other things.


On behalf of CPE Team,
Michal

[0] - https://pagure.io/releng/fedora-scm-requests
[1] - https://stg.pagure.io/releng/fedora-scm-requests
[2] - https://pagure.io/fedora-infra/toddlers
[3] - https://pagure.io/fedora-infra/toddlers/blob/main/f/docs
[4] - https://pagure.io/releng/issue/9274




___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Automation of Fedora SCM requests

[Michal Konecny]

Most of the issues are resolved now. There is one remaining ticket [0] 
that is returning 500 on branch creation. I will continue investigation 
on this ticket tomorrow.


I'm sorry for the rough start.

On behalf of CPE Team,
Michal

[0] - https://pagure.io/releng/fedora-scm-requests/issue/50370

On 10. 01. 23 13:52, Michal Konecny wrote:

Hi everyone,

after deployment we had some issues with API tokens for 
src.fedorapoject.org and pagure.io. Those issues are now solved.
Only one issue remains and that is missing list of epel9 packages on 
https://infrastructure.fedoraproject.org/repo/json

We are currently working on that.

All the epel9 branch requests will fail right now, we will reprocess 
them once this is fixed.


On behalf of CPE Team,
Michal

On 10. 01. 23 12:26, Michal Konecny wrote:

Hi everyone,

this automation is now in place and new SCM requests will be 
processed automatically. If you find any issue with the automation, 
please report it to toddlers issue tracker [0].


On behalf of CPE Team,
Michal

[0] - https://pagure.io/fedora-infra/toddlers/issues

On 08. 12. 22 11:10, Michal Konecny wrote:

Hello everyone,

for some time CPE (Community Platform Engineering) team is working 
on automating Fedora SCM requests [0]. The automation is currently 
live on staging. You can see the output (closed tickets) in Fedora 
SCM requests staging repo [1].
The automation is done using a plugin in toddlers [2]. We have a 
documentation [3] for the new toddler, if you want to know more 
about it. There is also a ticket [4] tracking this work.


We plan to deploy this in production on *10th January 2023*, after 
that all the Fedora SCM request will be processed automatically and 
it will ping correct people if the manual intervention is needed. 
This will not change anything in user workflow, it will just make 
the job of Fedora Release Engineering Team easier and let them focus 
on other things.


On behalf of CPE Team,
Michal

[0] - https://pagure.io/releng/fedora-scm-requests
[1] - https://stg.pagure.io/releng/fedora-scm-requests
[2] - https://pagure.io/fedora-infra/toddlers
[3] - https://pagure.io/fedora-infra/toddlers/blob/main/f/docs
[4] - https://pagure.io/releng/issue/9274




___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Automation of Fedora SCM requests

[Michal Konecny]

The documentation would need to be updated in multiple places, but I 
didn't know about this one. Thanks for sharing.


Michal

On 10. 01. 23 14:08, Richard Shaw wrote:
On Tue, Jan 10, 2023 at 5:26 AM Michal Konecny  
wrote:


Hi everyone,

this automation is now in place and new SCM requests will be
processed automatically. If you find any issue with the
automation, please report it to toddlers issue tracker [0].

On behalf of CPE Team,
Michal

[0] - https://pagure.io/fedora-infra/toddlers/issues


While I'm hopeful I can find this email if needed but it would be 
better if this was documented here (and wherever else appropriate):


https://docs.fedoraproject.org/en-US/package-maintainers/New_Package_Process_for_New_Contributors/#add_package_to_source_code_management_scm_system_and_set_owner

Thanks,
Richard

___
devel mailing list --devel@lists.fedoraproject.org
To unsubscribe send an email todevel-le...@lists.fedoraproject.org
Fedora Code of 
Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines
List 
Archives:https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report 
it:https://pagure.io/fedora-infrastructure/new_issue
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Automation of Fedora SCM requests

[Richard Shaw]

On Tue, Jan 10, 2023 at 5:26 AM Michal Konecny  wrote:

> Hi everyone,
>
> this automation is now in place and new SCM requests will be processed
> automatically. If you find any issue with the automation, please report it
> to toddlers issue tracker [0].
>
> On behalf of CPE Team,
> Michal
>
> [0] - https://pagure.io/fedora-infra/toddlers/issues
>

While I'm hopeful I can find this email if needed but it would be better if
this was documented here (and wherever else appropriate):

https://docs.fedoraproject.org/en-US/package-maintainers/New_Package_Process_for_New_Contributors/#add_package_to_source_code_management_scm_system_and_set_owner

Thanks,
Richard
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Automation of Fedora SCM requests

[Michal Konecny]

Hi everyone,

after deployment we had some issues with API tokens for 
src.fedorapoject.org and pagure.io. Those issues are now solved.
Only one issue remains and that is missing list of epel9 packages on 
https://infrastructure.fedoraproject.org/repo/json

We are currently working on that.

All the epel9 branch requests will fail right now, we will reprocess 
them once this is fixed.


On behalf of CPE Team,
Michal

On 10. 01. 23 12:26, Michal Konecny wrote:

Hi everyone,

this automation is now in place and new SCM requests will be processed 
automatically. If you find any issue with the automation, please 
report it to toddlers issue tracker [0].


On behalf of CPE Team,
Michal

[0] - https://pagure.io/fedora-infra/toddlers/issues

On 08. 12. 22 11:10, Michal Konecny wrote:

Hello everyone,

for some time CPE (Community Platform Engineering) team is working on 
automating Fedora SCM requests [0]. The automation is currently live 
on staging. You can see the output (closed tickets) in Fedora SCM 
requests staging repo [1].
The automation is done using a plugin in toddlers [2]. We have a 
documentation [3] for the new toddler, if you want to know more about 
it. There is also a ticket [4] tracking this work.


We plan to deploy this in production on *10th January 2023*, after 
that all the Fedora SCM request will be processed automatically and 
it will ping correct people if the manual intervention is needed. 
This will not change anything in user workflow, it will just make the 
job of Fedora Release Engineering Team easier and let them focus on 
other things.


On behalf of CPE Team,
Michal

[0] - https://pagure.io/releng/fedora-scm-requests
[1] - https://stg.pagure.io/releng/fedora-scm-requests
[2] - https://pagure.io/fedora-infra/toddlers
[3] - https://pagure.io/fedora-infra/toddlers/blob/main/f/docs
[4] - https://pagure.io/releng/issue/9274


___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Automation of Fedora SCM requests

[Michal Konecny]

Hi everyone,

this automation is now in place and new SCM requests will be processed 
automatically. If you find any issue with the automation, please report 
it to toddlers issue tracker [0].


On behalf of CPE Team,
Michal

[0] - https://pagure.io/fedora-infra/toddlers/issues

On 08. 12. 22 11:10, Michal Konecny wrote:

Hello everyone,

for some time CPE (Community Platform Engineering) team is working on 
automating Fedora SCM requests [0]. The automation is currently live 
on staging. You can see the output (closed tickets) in Fedora SCM 
requests staging repo [1].
The automation is done using a plugin in toddlers [2]. We have a 
documentation [3] for the new toddler, if you want to know more about 
it. There is also a ticket [4] tracking this work.


We plan to deploy this in production on *10th January 2023*, after 
that all the Fedora SCM request will be processed automatically and it 
will ping correct people if the manual intervention is needed. This 
will not change anything in user workflow, it will just make the job 
of Fedora Release Engineering Team easier and let them focus on other 
things.


On behalf of CPE Team,
Michal

[0] - https://pagure.io/releng/fedora-scm-requests
[1] - https://stg.pagure.io/releng/fedora-scm-requests
[2] - https://pagure.io/fedora-infra/toddlers
[3] - https://pagure.io/fedora-infra/toddlers/blob/main/f/docs
[4] - https://pagure.io/releng/issue/9274
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Automation of Fedora SCM requests

[Michal Konecny]

Hi everyone,

after deployment we had some issues with API tokens for 
src.fedorapoject.org and pagure.io. Those issues are now solved.
Only one issue remains and that is missing list of epel9 packages on 
https://infrastructure.fedoraproject.org/repo/json

We are currently working on that.

All the epel9 branch requests will fail right now, we will reprocess 
them once this is fixed.


On behalf of CPE Team,
Michal

On 10. 01. 23 12:26, Michal Konecny wrote:

Hi everyone,

this automation is now in place and new SCM requests will be processed 
automatically. If you find any issue with the automation, please 
report it to toddlers issue tracker [0].


On behalf of CPE Team,
Michal

[0] - https://pagure.io/fedora-infra/toddlers/issues

On 08. 12. 22 11:10, Michal Konecny wrote:

Hello everyone,

for some time CPE (Community Platform Engineering) team is working on 
automating Fedora SCM requests [0]. The automation is currently live 
on staging. You can see the output (closed tickets) in Fedora SCM 
requests staging repo [1].
The automation is done using a plugin in toddlers [2]. We have a 
documentation [3] for the new toddler, if you want to know more about 
it. There is also a ticket [4] tracking this work.


We plan to deploy this in production on *10th January 2023*, after 
that all the Fedora SCM request will be processed automatically and 
it will ping correct people if the manual intervention is needed. 
This will not change anything in user workflow, it will just make the 
job of Fedora Release Engineering Team easier and let them focus on 
other things.


On behalf of CPE Team,
Michal

[0] - https://pagure.io/releng/fedora-scm-requests
[1] - https://stg.pagure.io/releng/fedora-scm-requests
[2] - https://pagure.io/fedora-infra/toddlers
[3] - https://pagure.io/fedora-infra/toddlers/blob/main/f/docs
[4] - https://pagure.io/releng/issue/9274


___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Automation of Fedora SCM requests

[Jonathan Wright via devel]

This is incredible, thank you all so much for the work!

On Tue, Jan 10, 2023, 5:26 AM Michal Konecny  wrote:

> Hi everyone,
>
> this automation is now in place and new SCM requests will be processed
> automatically. If you find any issue with the automation, please report it
> to toddlers issue tracker [0].
>
> On behalf of CPE Team,
> Michal
>
> [0] - https://pagure.io/fedora-infra/toddlers/issues
>
> On 08. 12. 22 11:10, Michal Konecny wrote:
>
> Hello everyone,
>
> for some time CPE (Community Platform Engineering) team is working on
> automating Fedora SCM requests [0]. The automation is currently live on
> staging. You can see the output (closed tickets) in Fedora SCM requests
> staging repo [1].
> The automation is done using a plugin in toddlers [2]. We have a
> documentation [3] for the new toddler, if you want to know more about it.
> There is also a ticket [4] tracking this work.
>
> We plan to deploy this in production on *10th January 2023*, after that
> all the Fedora SCM request will be processed automatically and it will ping
> correct people if the manual intervention is needed. This will not change
> anything in user workflow, it will just make the job of Fedora Release
> Engineering Team easier and let them focus on other things.
>
> On behalf of CPE Team,
> Michal
>
> [0] - https://pagure.io/releng/fedora-scm-requests
> [1] - https://stg.pagure.io/releng/fedora-scm-requests
> [2] - https://pagure.io/fedora-infra/toddlers
> [3] - https://pagure.io/fedora-infra/toddlers/blob/main/f/docs
> [4] - https://pagure.io/releng/issue/9274
>
>
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Automation of Fedora SCM requests

[Michal Konecny]

Hi everyone,

this automation is now in place and new SCM requests will be processed 
automatically. If you find any issue with the automation, please report 
it to toddlers issue tracker [0].


On behalf of CPE Team,
Michal

[0] - https://pagure.io/fedora-infra/toddlers/issues

On 08. 12. 22 11:10, Michal Konecny wrote:

Hello everyone,

for some time CPE (Community Platform Engineering) team is working on 
automating Fedora SCM requests [0]. The automation is currently live 
on staging. You can see the output (closed tickets) in Fedora SCM 
requests staging repo [1].
The automation is done using a plugin in toddlers [2]. We have a 
documentation [3] for the new toddler, if you want to know more about 
it. There is also a ticket [4] tracking this work.


We plan to deploy this in production on *10th January 2023*, after 
that all the Fedora SCM request will be processed automatically and it 
will ping correct people if the manual intervention is needed. This 
will not change anything in user workflow, it will just make the job 
of Fedora Release Engineering Team easier and let them focus on other 
things.


On behalf of CPE Team,
Michal

[0] - https://pagure.io/releng/fedora-scm-requests
[1] - https://stg.pagure.io/releng/fedora-scm-requests
[2] - https://pagure.io/fedora-infra/toddlers
[3] - https://pagure.io/fedora-infra/toddlers/blob/main/f/docs
[4] - https://pagure.io/releng/issue/9274
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Automation of Fedora SCM requests

[Zbigniew Jędrzejewski-Szmek]

On Thu, Dec 08, 2022 at 02:07:01PM +0100, Simon de Vlieger wrote:
> On Thu, Dec 8, 2022, at 11:10 AM, Michal Konecny wrote:
> > Hello everyone,
> >
> > for some time CPE (Community Platform Engineering) team is working on 
> > automating Fedora SCM requests [0]. The automation is currently live on 
> > staging. You can see the output (closed tickets) in Fedora SCM requests 
> > staging repo [1].
> > The automation is done using a plugin in toddlers [2]. We have a 
> > documentation [3] for the new toddler, if you want to know more about 
> > it. There is also a ticket [4] tracking this work.
> >
> > We plan to deploy this in production on *10th January 2023*, after that 
> > all the Fedora SCM request will be processed automatically and it will 
> > ping correct people if the manual intervention is needed. This will not 
> > change anything in user workflow, it will just make the job of Fedora 
> > Release Engineering Team easier and let them focus on other things.
> 
> Awesome and very welcome news.

+1.

Zbyszek
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Automation of Fedora SCM requests

[Simon de Vlieger]

On Thu, Dec 8, 2022, at 11:10 AM, Michal Konecny wrote:
> Hello everyone,
>
> for some time CPE (Community Platform Engineering) team is working on 
> automating Fedora SCM requests [0]. The automation is currently live on 
> staging. You can see the output (closed tickets) in Fedora SCM requests 
> staging repo [1].
> The automation is done using a plugin in toddlers [2]. We have a 
> documentation [3] for the new toddler, if you want to know more about 
> it. There is also a ticket [4] tracking this work.
>
> We plan to deploy this in production on *10th January 2023*, after that 
> all the Fedora SCM request will be processed automatically and it will 
> ping correct people if the manual intervention is needed. This will not 
> change anything in user workflow, it will just make the job of Fedora 
> Release Engineering Team easier and let them focus on other things.

Awesome and very welcome news.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue