Should Jenkins be run inside development/deployment environment or on standalone box -


i using vagrant provide 'synchronised' , standardised development/test/uat/staging , production environments.

i looking @ how standardise ci build process. of jenkins confused best way deploy is. should have deployed in stand-alone ci box or install on various environments?

i guess little confused here. appreciated, thanks

the standard approach stand-alone ci server shared development team. common server (at known url) provides development dashboard team , authorized way publish release repository (developers not allowed publish directly)

you go credit , setup instance of sonar in opinion better suited development dashboard, providing richer set of metrics , serves historicial record development.

finally jenkins simple setup, there nothing stopping developers running own instances. find sonar matters less , less build run, once release credentials controlled. in fact attitude important prevents build server turning delicate snowflake :-)

update

there's vagrant plugin jenkins might prove useful in running current processes.


Comments