Automated builds possible?

[Richard Shaw]

I just had a thought and wondered if it were possible.

I have an upstream that posts alpha and beta releases to a specific URL.

What I'd like copr (or something) to do is:
1. Monitor those URLs so it knows when a new alpha is pushed
2. Pull the spec file from fedora rawhide (master)
3. Run rpmdev-bumpspec -n <version> -c "Update to <version>."
<spec>
4. Create a build in my COPR project using the new source.

Is this possible?

Thanks,
Richard

[Pavel Raiskup]

On Thursday, January 9, 2020 4:17:51 PM CET Richard Shaw wrote:
>  I just had a thought and wondered if it were possible.
>  
>  I have an upstream that posts alpha and beta releases to a specific URL.
>  
>  What I'd like copr (or something) to do is:
>  1. Monitor those URLs so it knows when a new alpha is pushed 
This part would be complicated on Copr side.  We shouldn't be responsible
for polling (perhaps DoS'ing) external urls.  If anything, we'd need to
let others to do this job for us carefully (e.g. anitya).

But copr is able to react on webhook call, which can be done by external
project (e.g. can be called by github - on tag event - automatically; from
upstream repo, if you tell upstream to do so):

Go to your project -> Settings -> Integrations -> Custom webhook

>  2. Pull the spec file from fedora rawhide (master)
>  3. Run rpmdev-bumpspec -n <version> -c "Update to <version>."
> <spec> 
You probably want custom script, so go to

  -> your project -> Packages -> (create one if you don't have it yet) ->
  -> [Edit] package -> Custom method

There you can specify shell script which will be executed to obtain
SRC.RPM sources (from whatever destination you want):
https://docs.pagure.org/copr.copr/custom_source_method.html#custom-source...

So all this you should be able to do manually.

>  4. Create a build in my COPR project using the new source. 
This is done automatically then.

Pavel

[harbottle]

I have a scheduled Ruby script that I use for monitoring upstream packages for updates and
updating my spec files:

https://gitlab.com/harbottle/automation/blob/master/main.rb

It uses a yaml file defining the upstream packages to be checked and how to check them:

https://gitlab.com/harbottle/automation/blob/master/main.yml


‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, January 10, 2020 10:49 AM, Pavel Raiskup <praiskup(a)redhat.com&gt; wrote:

>  On Thursday, January 9, 2020 4:17:51 PM CET Richard Shaw wrote:
>
>  > I just had a thought and wondered if it were possible.
>  > I have an upstream that posts alpha and beta releases to a specific URL.
>  > What I'd like copr (or something) to do is:
>  >
>  > 1.  Monitor those URLs so it knows when a new alpha is pushed
>
>  This part would be complicated on Copr side. We shouldn't be responsible
>  for polling (perhaps DoS'ing) external urls. If anything, we'd need to
>  let others to do this job for us carefully (e.g. anitya).
>
>  But copr is able to react on webhook call, which can be done by external
>  project (e.g. can be called by github - on tag event - automatically; from
>  upstream repo, if you tell upstream to do so):
>
>  Go to your project -> Settings -> Integrations -> Custom webhook
>
>  > 2.  Pull the spec file from fedora rawhide (master)
>  > 3.  Run rpmdev-bumpspec -n <version> -c "Update to <version>."
> <spec>
>
>  You probably want custom script, so go to
>
>  -> your project -> Packages -> (create one if you don't have it yet) ->
>  -> [Edit] package -> Custom method
>
>  There you can specify shell script which will be executed to obtain
>  SRC.RPM sources (from whatever destination you want):
>  https://docs.pagure.org/copr.copr/custom_source_method.html#custom-source...
>
>  So all this you should be able to do manually.
>
>  > 4.  Create a build in my COPR project using the new source.
>
>  This is done automatically then.
>
>  Pavel
>
>  copr-devel mailing list -- copr-devel(a)lists.fedorahosted.org
>  To unsubscribe send an email to copr-devel-leave(a)lists.fedorahosted.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.fedorahosted.org/archives/list/[e-mail]...

[Miroslav Suchý]

Dne 09. 01. 20 v 16:17 Richard Shaw napsal(a):
>  I just had a thought and wondered if it were possible.
>  
>  I have an upstream that posts alpha and beta releases to a specific URL.
>  
>  What I'd like copr (or something) to do is:
>  1. Monitor those URLs so it knows when a new alpha is pushed
>  2. Pull the spec file from fedora rawhide (master)
>  3. Run rpmdev-bumpspec -n <version> -c "Update to <version>."
> <spec>
>  4. Create a build in my COPR project using the new source.
>  
>  Is this possible? 
You are descibing rebase-helper:
  https://developer.fedoraproject.org/deployment/maintain/rebase-helper.html
integrated with upstream-monitoring:
  https://developer.fedoraproject.org/deployment/maintain/rebase-helper-int...

This works right now. When you register to release-monitoring.org and new release is out,
then you will get BZ report
stating that new release is out and there is linked build with bumped version and with new
sources.


-- 
Miroslav Suchy, RHCA
Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys

[Pavel Raiskup]

On Friday, January 10, 2020 11:54:45 AM CET Miroslav Suchý wrote:
>  Dne 09. 01. 20 v 16:17 Richard Shaw napsal(a):
>  > I just had a thought and wondered if it were possible.
>  > 
>  > I have an upstream that posts alpha and beta releases to a specific URL.
>  > 
>  > What I'd like copr (or something) to do is:
>  > 1. Monitor those URLs so it knows when a new alpha is pushed
>  > 2. Pull the spec file from fedora rawhide (master)
>  > 3. Run rpmdev-bumpspec -n <version> -c "Update to <version>."
> <spec>
>  > 4. Create a build in my COPR project using the new source.
>  > 
>  > Is this possible?
>  
>  You are descibing rebase-helper:
>    https://developer.fedoraproject.org/deployment/maintain/rebase-helper.html
>  integrated with upstream-monitoring:
>    https://developer.fedoraproject.org/deployment/maintain/rebase-helper-int...
Good idea, but is this working correctly for alpha versions?  People usually
intentionally ignore alpha versions in upstream-monitoring config.

Pavel


>  This works right now. When you register to release-monitoring.org and
> new release is out, then you will get BZ report
>  stating that new release is out and there is linked build with bumped version and with
> new sources.
>  
>  
>  -- 
>  Miroslav Suchy, RHCA
>  Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys
>  _______________________________________________
>  copr-devel mailing list -- copr-devel(a)lists.fedorahosted.org
>  To unsubscribe send an email to copr-devel-leave(a)lists.fedorahosted.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.fedorahosted.org/archives/list/[e-mail]...
>

[Richard Shaw]

On Fri, Jan 10, 2020 at 6:20 AM Pavel Raiskup <praiskup(a)redhat.com&gt; wrote:

>  On Friday, January 10, 2020 11:54:45 AM CET Miroslav Suchý wrote:
>  > Dne 09. 01. 20 v 16:17 Richard Shaw napsal(a):
>  > integrated with upstream-monitoring:
>  >
>  https://developer.fedoraproject.org/deployment/maintain/rebase-helper-int...
>
>  Good idea, but is this working correctly for alpha versions?  People
>  usually
>  intentionally ignore alpha versions in upstream-monitoring config.
>  
Yeah, I would have to set it up as a separate project in
release-monitoring.org, which I would have to do anyway because they are in
a ./alpha subdirectory separate from the full releases.

Thanks,
Richard