Hi, 

For a project I work on, we have set up Jenkins, using the GitHub Branch 
Source Plugin, to do automatic builds for pushes to our repository, 
including test builds for pull requests. This is all working, but I am 
concerned about the security implications for the pull requests. It is my 
understanding that Jenkins will protect the Jenkinsfile itself against 
changes by non-privileged users, but as far as I can tell there is no such 
protection of other files critical to the build process, for example the 
CMakeLists we use to define most of our build with cmake. Is this not 
actually the problem I think it is, is there some way to instruct Jenkins 
to ignore changes to additional build files, or is there some other 
practical method for aborting builds when these files have changed? I tried 
to implement the last of these with logic built into the Jenkinsfile, but I 
got out of my depth trying to coax the necessary information out of git.

Chris Weaver

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/0986f350-db59-4e44-8bc9-4fb33f911ab8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to