|
Artur opened 3 years ago
|
||||
|
OneDev changed state to 'Closed' 3 years ago
|
||||
|
|
OneDev changed state to 'Released' 3 years ago
|
||||
|
|
Could you please describe briefly how it works now? |
||||
|
When import the template build spec, there is an additional option "access token secret" expecting a secret pointing to an access token able to read code of the template project. So you do not need to make the template project public now. |
||||
|
|
This works perfectly well ! Thank you. |
| Type |
Improvement
|
| Priority |
Normal
|
| Assignee |
Issue Votes (1)
Watchers (3)
Right now the project "commons" as described in the online guide: https://medium.com/nerd-for-tech/ci-cd-configuration-reuse-in-onedev-c8110b709614 has to have a public code read access in order to reuse build templates.
For some templates it is not a problem, but some build types would be better to keep non-public.
Ideal solution would be similar to GitLab which has very rich "groups" implementation and each group can have own project templates.
However, a simpler solution which gives access to the build templates only to selected people would be good enough.