On Sun, Feb 3, 2013 at 2:10 PM, Pierre Joye <pierre....@gmail.com> wrote:
> hi, > > On Sun, Feb 3, 2013 at 1:33 PM, Ferenc Kovacs <tyr...@gmail.com> wrote: > > On Sun, Feb 3, 2013 at 1:30 PM, jenkins <jenk...@ci.qa.php.net> wrote: > > > >> this account will be used to keep the ci.qa.php.net jenkins > >> installation\'s config file in sync with the web/jenkins git repo. > >> > >> > >> -- > >> PHP Internals - PHP Runtime Development Mailing List > >> To unsubscribe, visit: http://www.php.net/unsub.php > >> > >> > > hi, > > > > I requested this one, please approve it and also grant him karma for > > web/jenkins.git > > I really do not think that we should give write access to some web > exposed bot to any of your repositories. We never allowed that in the > past and I do not think we should begin to do that. > > For what I understand from Ferenc's explanation on IRC, it is about > being to store the configuration changed done via the web frontend in > git. As the idea itself is good (having that in the repo is good), I > would rather go the other way round, modify the configuration in the > repo by human being. Configurations can be exported or fetched > relatively easily. > > Cheers, > -- > Pierre > > @pierrejoye > Hi, 99% of the changes to the jenkins configuration files (/config.xml, /job/*/config.xml) will be done through the admin interface, and I don't think that anybody here would be able to edit these files manually without tripping over something. So the other was around solution would require either 1, to have a development environment, where you do the changes, then fetch the changes in the xml files, then commit and push those changes, then log in to the jenkins admin and pull the changes (then restart jenkins if required). or 2, to change it on the jenkins admin, then fetch the changes in the xml files(this would require having ssh account there), then commit & push. I think that 1, is would be too cumbersome to be used and 2, would require giving out ssh accounts and would prone people not fetching and pushing the changes when they do change something. The plugin that I wanted to use ( https://wiki.jenkins-ci.org/display/JENKINS/SCM+Sync+configuration+plugin) would allow the changes to be pushed/pulled from the jenkins allow interface and would also show the current status (changes not pushed, etc.) so it is less likely to we forget to do it. Personally I'm not convinced about the security implications (as this is a separate repository and nothing else would use this repo for anything else), but if you think this is a major concern, I can use my personal github account for storing the configs for the time being. I just thought that it would be better to keep them on git.php.net, thats all. ps: some background info: some of the config files were lost when the previous ci.qa.php.net went down and I want to prevent that from happening ever again. -- Ferenc Kovács @Tyr43l - http://tyrael.hu
