[Cialug] Release Management

[Eric Junker]

If the developers have any automated tests (unit tests, Selenium tests, 
etc.) then you should setup a "continuous integration" environment. 
Automatically deploy the code every X minutes, run the automated tests 
and mark the build as failed if any of the tests fail. Jenkins works 
well for this.

You will probably also want a separate environment that doesn't get 
automated deploys but allows you to deploy a specific tag or branch to 
test. For example, tag the code, release it to the QA/staging 
environment and if it passes then release it to production.

Eric

On 8/21/14, 10:12 AM, Todd Walton wrote:
> <snip>
>
> I'm considering whether or not developers should be able to push their own
> code to testing, but still restrict their access to the testing servers.
> Like, some automated button they can push that takes dev and puts it in
> qa/test, but they can't go and fiddle with server settings.
>
> --
> Todd
> _______________________________________________
> Cialug mailing list
> Cialug at cialug.org
> http://cialug.org/mailman/listinfo/cialug