Build Continues Delivery and DevOpos Server for PHP Applications

Hi, Everyone. It's a very small job of few hours. I'm looking for a Microsoft Azure expert who can help me to build the fully automated continuous development environment based server. - Server requirements with the following "Workflow" and "Process" I would like to call this server "Care Dev". It will be a complete development server with continues development, integration & build automation system. Technically, this development server will be based on PHP, MySQL, PHPMyAdmin, Git Lab, Send mail, Phabricator (or any other alternate if best), Jenkins (or any other for build automation if best), JIRA type issue tracking with Sprint/Agile methodology and more third parties may require as well. Finally, once the server is ready to use. The administrator will create developers account in Git Lab in order to give them repository access accordingly. An email will be also sent after granting access on repositories as well. On the other side, developers will be also able to log into their Git Lab accounts to clone the repositories, see the last commits, sending the PRs (Pull Requests) and more. Developers will just do push code from their accounts. After this, they will log into official care dev portal ([login to view URL]) in order to create the test build from there account. After pressing this button. The build will be started on screen for testing the whole code including test cases execution and deployment on some URL. An email will be also sent as well. All developers will be able to access this URL to verify the changes. Now, once the feature is implemented. The developer will go back to his Git Lab account to send PR (Pull Request) for this. Similarly, the developer will also log into Phabricator (or any other if best) to mark the issue as completed as well. In the last stage, the reviewer will review the code to verify the quality of PR (Pull Request) and QA will verify the changes. Once the change is verified QA will put his status "Verified", similarly, the reviewer will also mark the code as "Reviewed" to close the ticket completely. Now, this code is 100% ready to deploy on "Production" server. The administrator will simply merge the PR (Pull Request) into Production Master branch. Once the branch is merged, the same process of loop will be revised in system like (verifying the changes on Production, see the code coverage on production and etc) It's a long time job. We have many Azure small jobs which you will keep getting in the timely fashion. So please ONLY experts are welcome and bring your Azure experience profiles. Include this sentence "I'm Azure Export" in your proposals to consider this for me. Thanks.