continuous integration - Is there a way to prevent a project from not having access to another project files in Jenkins CI? -
continuous integration - Is there a way to prevent a project from not having access to another project files in Jenkins CI? -
i trying setup jenkins/hudson ci in distributed environment. curious next questions:
1) slave business relationship need root/administrator account? if lower privilege can run whats minimum access?
2) on slave node, 1 projects jobs have access project files built on same node? how prevent this?
3) how secure not beingness able format disk bat file running in pre or post build script?
1) slave business relationship not have root or administrator. needs total access folder give in "remote fs root" field of slave configuration.
2) yes does. each project folder owned user used run slave. can access other project folders using relative paths: $workspace/../other_project/. i'm not sure if there default way prevent this. however, have 2 options:
delete workspace after build (use plugin workspace cleanup plugin) create separate slave/user combination each project - slave can same, you'd have create separate user each project.3) formatting disk require privileged access. should not give slave user rights. i'm not sure whether slave unix or windows based, either way, should able prevent user beingness allowed such task. stated in a1, slave user needs plenty access able read/write/execute in "remote fs root" folder.
just out of curiosity - os running on slave?
jenkins continuous-integration hudson master-slave
Comments
Post a Comment