Retiring Fedora 19
by Miroslav Suchý
Hi,
Fedora 19 is EOLed. Therefore I plan to disable building for Fedora 19 in Copr by end of this month.
If want to build something for F19, you have last chance.
By end of the month new builds for F19 will not be allowed. However existing yum repos for F19 will be preserved.
--
Miroslav Suchy, RHCE, RHCDS
Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys
8 years, 9 months
Copr update
by Valentin Gologuzov
Hi!, I've just updated copr.
Visible changes:
- We have started to sign RPMs, gpg pubkey is moved to the project
results root dir (one level up from the chroot dirs)
- [#1139242] Added option to disable networking during a build
- [#1183702] Interrupted builds should be re added to queue automatically
- [#1169782] Show package "epoch:version-release" instead of
just "version"
- [#1133650] Show urls to each chroot directory on build details
- [#1177179] Human friendly time presentation
- [#1117446] Added a file `build.info`, into the build directory. This
file would contain any usefull information about build, currently it has
only `build_id`.
--
Best regards,
Gologuzov Valentin.
8 years, 10 months
Re: Deploy copr to a VPS. Original: [Re: hi]
by Valentin Gologuzov
Hi, sorry for the late response.
That playbooks is quite fedora-infra specific, and likely more complex
than your need. I've mentioned them primarily as and example. Also they
are missing one (probably most complex) part: setup and configuration of
Virtual Machine provider (in other words - Cloud), which you should
either run yourself or get access to some existing cloud (for example
Amazon EC, but it costs money).
Last week I have created reproducible local copr installation for
testing purpose: https://github.com/evilkost/local-copr . It's much
simpler than fedora-ansible setup and is not suitable for production
environment. But it contains everything to run copr on the localhost.
You can install it and explore Docker files, config files, etc to
understand how it works, and what should you change according to your
environment.
If you encounter some problem with `local-copr`, please create issue at
github tracker.
On 01/09/2015 10:58 AM, Ray Dobie wrote:
> Thx for ur help! So i just need to run (For production):
> $yum install -y ansible
> then set
> [webservers]
> backend'ip ansible_ssh_port=22 ansible_ssh_user=root
> frontend'ip ansible_ssh_port=22 ansible_ssh_user=root
> $git clone https://git.fedorahosted.org/cgit/copr.git
> $git clone http://infrastructure.fedoraproject.org/infra/ansible/
> $ansible-playbooks copr-backend.yml
> <http://infrastructure.fedoraproject.org/infra/ansible/playbooks/groups/co...>
>
> $ansible-playbooks copr-frontend.yml
> <http://infrastructure.fedoraproject.org/infra/ansible/playbooks/groups/co...>
> Right?
> (BTW, There r vars like {{ private }} in yml so i wonder what should i do?
> like "--extra-vars")
>
>
> On Fri Jan 02 2015 at 下午5:51:10 Valentin Gologuzov <vgologuz(a)redhat.com>
> wrote:
>
>> Hi Ray,
>>
>> Right now Copr is mainly developed and provided as a service.
>> Unfortunately we don't have a goal (and resources) to release
>> stand-alone application/container etc.
>>
>> By design, to deploy copr you need at least two hosts for frontend and
>> backend, than you need an instance of OpenStack (or something similar)
>> to provide virtual machines for builders. It is POSSIBLE to run
>> everything on a single machine, but it's not practical (poor performance).
>>
>> https://git.fedorahosted.org/cgit/copr.git/tree/copr-setup.txt is
>> usually outdated, and doesn't describe everything (.
>>
>> You could look at our Ansible playbooks, which is used to deploy Copr to
>> the Fedora-infrastructure cloud:
>>
>> http://infrastructure.fedoraproject.org/infra/ansible/playbo
>> oks/groups/copr-backend.yml
>> http://infrastructure.fedoraproject.org/infra/ansible/playbo
>> oks/groups/copr-frontend.yml
>>
>>
>>
>> p.s.: added copr-devel@ mail-list to cc:
>>
>> On 01/01/2015 05:52 AM, Ray Dobie wrote:
>>> I had read the doc
>>> <https://git.fedorahosted.org/cgit/copr.git/tree/copr-setup.txt> and
>> find
>>> it was so hard for a fish like me,lol.
>>> Is there a CentOS docker for it?
>>>
>>> On Thu Jan 01 2015 at 下午12:29:36 Ray Dobie <tvvocold(a)gmail.com> wrote:
>>>
>>>> hi Gologuzov,
>>>>
>>>> My name is Ray and i am a member of fedora-chinese-group, now i got
>> action
>>>> to build a rpm repo server for fedora chinese user. and i checked ur
>>>> project Copr <https://git.fedorahosted.org/cgit/copr.git/> is cool,is
>>>> that a opensource project? could i use it? and how to install /set it
>> up in
>>>> a vps(in China) ?
>>>>
>>>> Thx!
>>>> Happy new year!
>>>>
>>>> --
>>>> Ray
>>>>
>>>>
>>>
>>
>> --
>> Best regards,
>> Gologuzov Valentin.
>>
>
--
Best regards,
Gologuzov Valentin.
8 years, 10 months
Packages are now signed
by Valentin Gologuzov
Hi,
Today we enabled gpg package signing. Currently it signs only new
builds. .repo files will be changed soon to provide pubkey URL, gpgcheck
on other hand will remain disabled for a few months.
If you want to check gpg signature right now, you could find public key
at
`https://copr-be.cloud.fedoraproject.org/results/$USERNAME/$COPRNAME/$CHROOT/`.
--
Best regards,
Gologuzov Valentin.
8 years, 10 months
copr-backend bugfix update
by Valentin Gologuzov
Current update is mainly fixes a few bugs.
What's fixed:
- build timeout is fixed, and now it is set to 6 hours (rhbz: 1176364)
- JobGrabber now ignores errors during action processing.(rhbz: 1182106)
- weird /devel/ in repository name (rhbz: 1179713)
--
Best regards,
Gologuzov Valentin.
8 years, 10 months
Copr upgrade
by Valentin Gologuzov
New year with a new Copr release!
Visible changes:
- Now repository metadata generation can be disabled and executed upon
request (BZ 1150954). This feature primary targets owners of big
repositories.
- Repeat build button respects selected chroots (BZ 1149091)
- Show copr-frontend version (BZ 1171798)
- Bug: Wrong OS distribution order on Monitor page (BZ 1146825)
Also new version of python client to the Copr API (python-copr) is
available for Fedora19,20,21 and Epel6,7 (published to the updates
repositories). If anybody interested please test it.
--
Best regards,
Gologuzov Valentin.
8 years, 11 months
Deploy copr to a VPS. Original: [Re: hi]
by Valentin Gologuzov
Hi Ray,
Right now Copr is mainly developed and provided as a service.
Unfortunately we don't have a goal (and resources) to release
stand-alone application/container etc.
By design, to deploy copr you need at least two hosts for frontend and
backend, than you need an instance of OpenStack (or something similar)
to provide virtual machines for builders. It is POSSIBLE to run
everything on a single machine, but it's not practical (poor performance).
https://git.fedorahosted.org/cgit/copr.git/tree/copr-setup.txt is
usually outdated, and doesn't describe everything (.
You could look at our Ansible playbooks, which is used to deploy Copr to
the Fedora-infrastructure cloud:
http://infrastructure.fedoraproject.org/infra/ansible/playbooks/groups/co...
http://infrastructure.fedoraproject.org/infra/ansible/playbooks/groups/co...
p.s.: added copr-devel@ mail-list to cc:
On 01/01/2015 05:52 AM, Ray Dobie wrote:
> I had read the doc
> <https://git.fedorahosted.org/cgit/copr.git/tree/copr-setup.txt> and find
> it was so hard for a fish like me,lol.
> Is there a CentOS docker for it?
>
> On Thu Jan 01 2015 at 下午12:29:36 Ray Dobie <tvvocold(a)gmail.com> wrote:
>
>> hi Gologuzov,
>>
>> My name is Ray and i am a member of fedora-chinese-group, now i got action
>> to build a rpm repo server for fedora chinese user. and i checked ur
>> project Copr <https://git.fedorahosted.org/cgit/copr.git/> is cool,is
>> that a opensource project? could i use it? and how to install /set it up in
>> a vps(in China) ?
>>
>> Thx!
>> Happy new year!
>>
>> --
>> Ray
>>
>>
>
--
Best regards,
Gologuzov Valentin.
8 years, 11 months
