I would really love to see this feature on copr. A button, that would
simply say: "Hey, I'm using this repository". And a counter behind it.
* The maintainer would know that his/her repo has user(s) and how many
* Better selection for Fedora Playground
* Users would need to perform a certain action (not everybody would)
* Users will forget to undo the button once they stop using the repository
* Not all users have FAS accounts and can sign in to the app
What to you think? I might have time to implement this, but I don't want
to invest it to an unwanted feature.
We came up with an idea how to use Docker in copr at Env&Stacks WG meeting:
Let's say you are a maintainer of few packages or you just want to try
to change/fix something in some packages. You decide to use copr for
building these changed packages.
At the moment, when your build is done, you have to install them on your
system or to some virtual machine which requires some additional typing,
time and can cause potential problems if you've broken something in the
My idea would be to enhance copr so that it is able to build layered
Docker image which would contain newly built packages. User could then
download/pull the image and run it as container - that could mean either
run bash there, some specific command or even some automatic test.
I am not sure about the build process yet - we need to discuss it - copr
can either require Dockerfile from user or the Dockerfile could be
probably constructed dynamically. Basic Dockerfile would need to add
repo files and install/update built packages in the image. If we want to
get it further we could think of adding some configuration, run specific
command on container start or let user select base image he would like
to use, but these are implementation details.
Another question that needs to be answered is in what way the built
image would be provided to the user - it can be either *.tar.gz which he
could download and call docker load -i or we can have docker registry
for these images and push them there. User would then be able to run
docker pull to get the image.
What do you think? Do you think this makes sense for copr?
Thanks & regards,
Lead Infrastructure Engineer
Brno, Czech Republic
I just deployed new release of Copr. Main highlights:
* new state "Skipped", which means: package with the same version have been already successfully built in past,
therefore it is skipped (previously Copr behave exactly the same, just marked it as success).
* added Fedora 21 chroot
* epel-7 now works again (and point to CentOS)
* changes in API (see previous email from Adam)
* in 'Monitor' and 'Builds' tabs, you can now see last version of packages
* fedmsg notifications now contains name of chroot
* copr-be run on Fedora 20 now
* copr-be is using nova ansible modules to interact with Fedora Cloud
Miroslav Suchy, RHCE, RHCDS
Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys
we have just deployed a new version of Copr which brings some new features:
- the process of skipping packages which has already been built previously is now 1000 times faster
- we introduced a new build state Starting - an intermediate state between Pending and Running. This also fixed an issue with cancelling
- in case you have added some packages into a chroot, the information (and a list of packages) would show up on the Overview page
- on the Overview page is also a new field which could help you with enabling the repository
- we added a list of running tasks to the status page
Seems like the optional Chroot setup:
"Additional packages to be always present in minimal buildroot"
Stopped working because in the build , neither the scl-utils-build nor
compat-rpm-config packages are installed (both should be in installroot
command specified as I have set it to my for f21 chroots).
tomorrow, we are going to deploy new version of Copr which brings some new features and also one small API change.
As you probably know, if you try to rebuild a package which has been successfully built before (of the same version) Copr skips this package and marks the build as successful. In the new version we introduced a new state "Skipped" which will be used for this situation.
So, if you use API, please remember that Successful build can also come as Skipped.
We also extended the /api/coprs/build_detail/<build_id>/ which provides much more useful information including names and versions of packages which have been built. Please find an example below.
The same information is also provided on the build page in web-GUI.
If you want to see the changes now, check out the dev instance: http://copr-fe-dev.cloud.fedoraproject.org/
Have a nice day
Example result of /api/coprs/build_detail/<build_id>/