The development of large projects with partial access to the code?

Very interesting how the development of large projects, as is the source code for autsorserom/freelancers. What system is used for this? How does the testing of the written code? Any documentation or book you should read to figure this out? How the theft protection code, which have access to a large number of people?!
September 26th 19 at 06:27
3 answers
September 26th 19 at 06:33
Plus the version control system of type bitbucket and JIRA bugtracker type.
Explain and it is here at all ? - Leone.Olson32 commented on September 26th 19 at 06:36
providing employees/freelancers access to the code. Typically, each new task is implemented in a new code branch, and after a successful implementerade and testing, it back flows into the main master branch.
In large projects without it anywhere. - kenton77 commented on September 26th 19 at 06:39
Here it is not clear how the cover-up. The branch does not hide the fact from which branches off. An example at random. - Leone.Olson32 commented on September 26th 19 at 06:42
Why hide the code need to work? If the freelancer can't see any code, don't give him access to this repository.
Branches are needed to separate the code into tasks so that none of the programmers do not interfere with each other.
Everyone knows that working in the same branch or a single SVN uncomfortable. - kenton77 commented on September 26th 19 at 06:45
have you ever read the original question? This is its essence //_-. How to organize partial access to the code. - Leone.Olson32 commented on September 26th 19 at 06:48
All I read: "how is the source code for autsorserom/freelancers". All through Git. - Gideon_Bartoletti commented on September 26th 19 at 06:51
September 26th 19 at 06:29
Solution
Well nasadka - svn (with the division of the rights on the directories) + green trunk + the tests for the entire project in some teamcity during Assembly.
"green-trunk" what's that? - Leone.Olson32 commented on September 26th 19 at 06:32
well, svn is trunk and brunches. Trunk - a La the master. So he always needs to gather a whole (in the sense of components of your entire system out should always be collected). Green == passed all tests after build, otherwise nothing at all releases. - kenton77 commented on September 26th 19 at 06:35
and something like this in git you have? - Leone.Olson32 commented on September 26th 19 at 06:38
in Gita there is a master branch and brunches.
Another issue is that with git it is impossible in a single repository to give different rights to different directories. So the build system more complicated - have to collect from multiple repositories. - kenton77 commented on September 26th 19 at 06:41
September 26th 19 at 06:31
1. Ready the environment for execution of code the programmer (testing)
2. The division of the project into the system (a clear description of the API between the systems)
3. Delegating the development of different systems from different developers, and that they did not know each other and communicated only through the Manager.
And what to do if there is a developing backend? - Leone.Olson32 commented on September 26th 19 at 06:34
Who needs your backend business logic on the server ? - kenton77 commented on September 26th 19 at 06:37
So the backend and expects all, there are all the formulas are the business logic. Of course, without the together with the front end, not so obvious, and visualize business logic, but there it laid. - Leone.Olson32 commented on September 26th 19 at 06:40
Sorry. Beguiled the backend with freedom. So I have the answer and wrote about the backend (separate system apart, and do not let to assemble parts into a unified whole by someone other than you) - kenton77 commented on September 26th 19 at 06:43

Find more questions by tags FreelanceProgramming