Need to configure Jenkins Jobs for pushing changes to the envs

Registered by Anastasia Kuznetsova on 2014-12-08

We need to have at list two Jenkins jobs:

The first job:
This jobs will deploys staging env from the current code in repo, push changes from master to our staging env, restart application or recreate db. It will allow to reduce manual intervention in the envs.

The second one:
Deploys any commit which went through testing to production, this job can has a parameter - change id or link to the pull request and prepares application from this commit in production env. Also it will help us to do a back up.

Blueprint information

Status:
Not started
Approver:
Timur Nurlygayanov
Priority:
Medium
Drafter:
Anastasia Kuznetsova
Direction:
Approved
Assignee:
None
Definition:
Discussion
Series goal:
None
Implementation:
Not started
Milestone target:
None

Related branches

Sprints

Whiteboard

dmitryme: we might not need it, hence moving to 'Discussion' state

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.