Answer the question
In order to leave comments, you need to log in
How to integrate a version control system into the development process?
How to integrate a version control system into company processes?
Initial data:
Regional web studio, bitrix and modx projects.
There are several dedicated servers and more than a hundred small projects.
3 back-end, 2 front-end developers, 1 pure support.
We (oh my) have not yet come to the use of a version control system, we do not have unit testing projects, we do not have test servers (we use several test domains and subdirectories).
And to be honest, it’s still hard to imagine how to integrate GIT, a test server, into company processes.
Please tell me or direct where and what to read on this topic.
Or share how your project development structure is organized
front-end, bild => back-end => testing => production.
Answer the question
In order to leave comments, you need to log in
Just like we do - toroid.org/ams/git-website-howto . This is the deployment process. I added two remotes to my local repository - prod & test. Sobsno, first I upload it for testing with one command
, then, if everything is fine, already for production
. If any post-processing is needed, then they occur on the server through the hooks of the git.
I would start with a public service like Github. So many tools are already there. You can also create private repositories. It is paid but not expensive. Doesn't stress me out.
Github can also be quickly integrated into various services, such as Windows Azure. If you have a server there, then you can organize an automatic scan in one click to configure. That is, one moment after you have sent everything to the github, it is already available on the server for manual testing.
If you want a unit test or the like, since there are a lot of different solutions now and different ones are good for different tasks, then you need to use grunt or better gulp. This will automate the testing and deployment process.
Finally, a motivator. I remember when we also worked without a version control system. And I remember how hard it was to introduce new technology into the usual production process. It even seemed that it only interferes and reduces productivity. But over time, when everyone is used to it, we cannot imagine the process without it. And we are so glad that we switched to these technologies.
So good luck.
https://about.gitlab.com/gitlab-ce/ - deployed somewhere and drive the development process.
If you want something really simple, then go here: https://bitnami.com/stack/gitlab/virtual-machine and download the finished image to virtualbox (if you are developing locally) or installer https://bitnami.com/stack /gitlab/installer and download it to a free machine or vps from one of the cloud hosts.
There are already GitLab CE and GitLab CI inside, tests (if any) should be run on another server.
If GitLab CI does not suit you, then there is Jenkins https://bitnami.com/stack/jenkins and a plugin for it for convenience https://wiki.jenkins-ci.org/display/JENKINS/Gitlab...
In general, be sure to put the process on vcs.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question