[PATCH] [backend] broadcast both submitter and owner to fedmsg
by Ralph Bean
Back in commit 1a4473e7a4dc1adbff5868ae0395625bef78d17a, a change was
introduced that changed the 'user' field in fedmsg represent the person who
kicked off a build instead of the person who owned the particular copr.
This broke code in other fedmsg consumers that tried to build links from
that user field to https://copr.fedoraproject.org/$USER/$COPR
This change re-introduces the copr owner's username to the message.
---
backend/backend/dispatcher.py | 3 +++
1 file changed, 3 insertions(+)
diff --git a/backend/backend/dispatcher.py b/backend/backend/dispatcher.py
index 52777e9..45429d5 100644
--- a/backend/backend/dispatcher.py
+++ b/backend/backend/dispatcher.py
@@ -191,6 +191,7 @@ class Worker(multiprocessing.Process):
" build:{build} ip:{ip} pid:{pid}"
content = dict(user=job.submitter, copr=job.project_name,
+ owner=job.project_owner,
build=job.build_id, ip=ip, pid=self.pid)
self.event("build.start", template, content)
@@ -198,6 +199,7 @@ class Worker(multiprocessing.Process):
"copr:{copr} build:{build} ip:{ip} pid:{pid}"
content = dict(chroot=job.chroot, user=job.submitter,
+ owner=job.project_owner,
copr=job.project_name, build=job.build_id,
ip=ip, pid=self.pid)
@@ -216,6 +218,7 @@ class Worker(multiprocessing.Process):
" ip:{ip} pid:{pid} status:{status}"
content = dict(user=job.submitter, copr=job.project_name,
+ owner=job.project_owner,
build=job.build_id, ip=ip, pid=self.pid,
status=job.status, chroot=job.chroot)
self.event("build.end", template, content)
--
1.9.3
9 years
[PATCH] add support for kerberos authentication
by Pavel Raiskup
Hi all, could we consider the two following patches? We need something
like that for our internal Copr instance and having it upstream would
simplify a lot our downstream maintenance; it could be useful for
somebody anyway.
> 0001-frontend-do-not-strictly-resist-on-Fedora-s-OpenID.patch
Patch tries to untie Fedora's AuthN and Copr database a little to allow
different types of authentication. Only the "user" part is stored in
db when applied (not whole http://user.id.fedoraproject.org/).
> 0002-frontend-support-for-kerberos-authentication.patch
Adds alternative (configurable) kerberos authentication. It would be nice
if OpenID was generalized the same way, I'll possibly try to look at it
when somebody will be interested.
Paael
9 years, 1 month
Timeout in Copr
by Adam Samalik
Hello everyone,
I have just deployed a new version of backend - which includes build timeout. The current value is set to 6 hours.
It will also deal with cloud failures much better - there shouldn't be stucked tasks anymore.
Have a nice weekend
Adam Samalik
9 years, 1 month
Trying to use COPR with DNF on F20
by Nick Coghlan
I'm not sure if this should go to the DNF lists or here, as I'm not sure
who maintains the DNF COPR plugin. Posting here since I'm already
subscribed :)
Peter Hutterer is running a libinput user study
(http://libinput-whot.rhcloud.com/) and using COPR to distribute the
testing software.
I decided to try using dnf's copr plugin to install it rather than the
curl/yum commands in Peter's installation instructions, but ran into
some usability problems with it.
* First usability problem:
- "sudo dnf copr --help" just reported unknown command, without
suggesting installing "dnf-plugins-core"
- I vaguely remembered a previous mention of plugins, and found the
right package via "yum search dnf"
* Second usability problem:
- The following command sequence initially didn't work:
$ sudo dnf copr enable whot/libinput-userstudy
$ sudo dnf install libinput-userstudy
- there was no indication that metadata for the new repo had been
retrieved, and the second command reported "unknown package"
- "dnf makecache" didn't help either
- today, running "dnf repolist" triggered a metadata update, and now the
install command works
Is it possible there's an issue with "copr enable" not triggering a
metadata update for the newly enable repo?
Note that I'm generally using a mixture of dnf and yum commands on this
system, since I'm only using dnf for the COPR plugin.
Regards,
Nick.
--
Nick Coghlan
Red Hat Hosted & Shared Services
Software Engineering & Development, Brisbane
HSS Provisioning Architect
9 years, 1 month
[PATCH] frontend: make all html tags to have the same left-padding
by Pavel Raiskup
Previously, headers on /coprs/ URI got sticked absolutely to left:
https://praiskup.fedorapeople.org/persist/bugreports/copr-left-sticking-h...
---
frontend/coprs_frontend/coprs/static/copr.css | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/frontend/coprs_frontend/coprs/static/copr.css b/frontend/coprs_frontend/coprs/static/copr.css
index c697ec4..2e7dcd4 100644
--- a/frontend/coprs_frontend/coprs/static/copr.css
+++ b/frontend/coprs_frontend/coprs/static/copr.css
@@ -163,9 +163,9 @@ a.coprs-list {
display: block;
}
-div.copr p {
- padding-left: 1em;
- padding-right: 1em;
+div.copr p, div.copr h1, div.copr h2, div.copr h3 {
+ padding-left: 15px;
+ padding-right: 15px;
margin-top: 0.3em;
margin-bottom: 0.3em;
}
@@ -249,7 +249,7 @@ div.pkg-url-list {
}
div.shift-right {
- margin-left: 1em;
+ margin-left: 15px;
}
dt.field-label {
--
1.9.3
9 years, 1 month
New api proposal
by Valentin Gologuzov
Hi,
I've just split copr-cli into the python client and cli tool itself,
hence a lot of interaction with api.
I disliked its current state, and would like to implement a new api.
Here is my proposal in form of the documentation outline:
https://gist.github.com/evilkost/20190b8b190c905266ab
Please let me know what you think!
--
Best regards,
Gologuzov Valentin.
9 years, 1 month
Feature request: User feedback - "I'm using this repository"
by Miro Hrončok
Hi,
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.
Advantages:
* The maintainer would know that his/her repo has user(s) and how many
* Better selection for Fedora Playground
Disadvantages:
* 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.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
9 years, 1 month