Development process optimization method and device and storage medium

Abstract

The embodiment of the invention discloses a development process optimization method and device and a storage medium and relates to the technical field of software development. The method comprises the steps that first terminals where multiple first components are respectively located update source codes of the first components respectively corresponding to the first terminals based on respectively-obtained and modified source codes of second components associated with the first components; then after it is detected that update is completed, the first terminals where the multiple first components are respectively located send a source code merging request to second terminals where the second components are located, so that the second terminals receive the source code merging request sent by the first terminals where the multiple first components are respectively located and then issue the versions of the second components, wherein the versions of the second components include source codes modified by all the second components. Therefore, one-time version issuing of the second components is achieved, repeated version issuing is not needed, and the whole development process is optimized.

Description

technical field [0001] The present invention relates to the technical field of software development, in particular to a development process optimization method, device and storage medium. Background technique [0002] With the popularity of iOS or Android componentization, more and more teams are beginning to use componentized management tools such as Cocoapods. However, the Cocoapods-based component development solution has a problem that leads to low development efficiency, that is, after a large project is split into several components, version management across components is very troublesome. If component A depends on component B, if component B cannot meet the requirements of component A, then A needs to notify the maintainer of component B to update component B, then release a new version of component B, and then assign the new version number Tell the developer of component A, and the developer of component A will pull the new version of component B. It can be seen t...

AI Technical Summary

Problems solved by technology

It can be seen that there are many links. If the maintainers of component B have tasks with higher priority to be processed, then all the developers of component A will not be able to continue their work. They have to wait for the maintainers of component B until they update component B.

At the same time, if component C also depends on component B, component C also needs to update component B after the maintainer of component B releases a new version, then component B will be updated and a new version will be released at this time, which shows that the frequency of repeated releases is very high. high

Images