|
bufferUnderrun opened 12 months ago
|
||||
|
Commit history accessing already exposes the source info to some extent. |
||||
|
|
Could you be more precise ? |
||||
|
|
I mean commit history including commit message should also be considered as part of source info. |
||||
|
|
When i talk about commit history in that case, i mean only commit message and description. Not about related source code. So, it could be possible to accès commit message only with associated job (depending job acces in onedev role). Result as a working role for support who could run job without repas code source access. |
||||
|
OneDev changed state to 'Closed' 12 months ago
|
||||
|
|
State changed as code fixing the issue is committed (690a6ed5) |
||||
|
|
OneDev changed state to 'Released' 12 months ago
|
||||
|
|
State changed as build #3659 is successful |
||||
|
|
It is now possible to run build directly from builds page without accessing commits page. |
||||
|
|
Just upgrade to v8.2.7 and works as perfect. Thanks Robin, you rocks as always !! |
| Type |
New Feature
|
| Priority |
Normal
|
| Assignee |
Hi,
I'm trying to create a role for the support.
I want to allow support executed specific job without having to enable read code access : source code is private and must be out of bound for support.
One could be achieve using the commit list page : they could access to the commit history list and run the corresponding job but not explore source code.
Thanks