| 30 Oct 2022 |
|  @rimuru:gentoo.chat changed their profile picture. | 23:34:06 |
| @rimuru:gentoo.chat changed their display name from Rimuru to spooky spook 🎃. | 23:45:35 |
| 31 Oct 2022 |
|  @tinybronca:sibnsk.net changed their display name from underpantsgnome! to underpantsgnome. | 20:18:56 |
|  kiber_ogur4ik joined the room. | 20:24:29 |
| 1 Nov 2022 |
| @rimuru:gentoo.chat removed their display name spooky spook 🎃. | 23:45:13 |
| @rimuru:gentoo.chat set their display name to rimuru. | 23:48:46 |
| @rimuru:gentoo.chat changed their profile picture. | 23:52:40 |
| 8 Nov 2022 |
|  pbsds changed their profile picture. | 00:46:21 |
| @rimuru:gentoo.chat changed their profile picture. | 12:32:37 |
| 13 Nov 2022 |
|  penglei joined the room. | 16:54:09 |
|  @nahfe:nahfe.xyz joined the room. | 19:35:28 |
| 15 Nov 2022 |
|  aciceri joined the room. | 10:31:32 |
| aciceri | Someone knows if there is a way to configure which jobsets a user can restart? | 10:39:01 |
| aciceri | Or more generally permissions management for for single jobsets | 10:39:54 |
| aciceri | Or even by project | 10:41:02 |
 das_j | I only know of the db table, I'm not aware of config in the frontend | 10:41:24 |
| aciceri | Do you mean that the table has a schema that captures these informations? | 10:42:00 |
| aciceri | I mean permissions per jobsets | 10:42:14 |
| das_j | hydra=# table projectmembers ;
project | username
---------+----------
(0 rows)
| 10:42:35 |
| das_j | that's the best I know | 10:42:45 |
| aciceri | does this mean that the a user cannot have different permissions o | 10:44:53 |
| aciceri | * does this mean that the a user cannot have different permissions for different projects? | 10:45:02 |
| aciceri | * does this mean that the an user cannot have different permissions for different projects? | 10:45:10 |
| das_j | I have no idea tbh | 10:45:29 |
| aciceri | Frankly I'm only interested into the restart-jobs role, I would like to have the same user able to restart jobs from jobsets from a project but not from another project | 10:46:28 |
| aciceri | I would like to manage these users (and which which jobsets they can restart) declaratively using an module option | 10:50:33 |
 @linus:schreibt.jetzt | sub mayRestartJobs {
my ($c, $project) = @_;
return
$c->user_exists &&
(isAdmin($c) ||
hasRestartJobsRole($c) ||
isProjectOwner($c, $project));
}
| 10:54:01 |
| @linus:schreibt.jetzt | That's the entire logic Hydra uses to determine whether a user can restart jobs. | 10:54:16 |
| aciceri | In reply to @janne.hess:helsinki-systems.de
hydra=# table projectmembers ;
project | username
---------+----------
(0 rows)
suppose there is only a row which puts in relation 'alice' to project and suppose that alice has the restart-jobs role. What happens when another project is created (without writing a new row in projectmembers I mean)? alice is able to restart jobs from this other project? | 10:54:24 |
| @linus:schreibt.jetzt | (/src/lib/Hydra/Helper/CatalystUtils.pm) | 10:54:52 |
