CN115291935A

CN115291935A - Component updating method, component updating device, equipment and storage medium

Info

Publication number: CN115291935A
Application number: CN202210949904.3A
Authority: CN
Inventors: 郭文超; 杨丹
Original assignee: Ping An Life Insurance Company of China Ltd
Current assignee: Ping An Life Insurance Company of China Ltd
Priority date: 2022-08-09
Filing date: 2022-08-09
Publication date: 2022-11-04

Abstract

The embodiment of the invention provides a component updating method, a component updating device, equipment and a storage medium, and relates to the technical field of computers. Updating and applying a Fastlane tool to manage the components, and acquiring a source code file of a server; the source code file comprises an index file and a dependency relationship file, whether a new component exists in the source code file is detected according to the index file, if the new component exists, a preset component configuration table is read, the version number of the new component is obtained, the dependency relationship file is analyzed according to the version number, a target dependency relationship analysis result between the new component and the preset component is obtained, and the dependency relationship file is updated according to the analysis result. According to the embodiment, the dependency relationship file is automatically analyzed, the component configuration information is obtained, manual modification conflict is avoided, the operation process is simplified, the operation complexity is reduced, meanwhile, manual searching and modification of the configuration information are not needed, errors are avoided, the working efficiency of developers is improved, and the project development cost is reduced.

Description

Component updating method, component updating device, equipment and storage medium

Technical Field

The present invention relates to the field of computer technologies, and in particular, to a component updating method, a component updating apparatus, a device, and a storage medium.

Background

With the rapid development of computer technology, development requirements for different application programs are increasing, a large number of third party libraries are generally referred in the development process of the application programs, the third party libraries are managed conveniently and uniformly, the dependency relationship between the third party libraries and development projects and relevant information such as version relationships are defined by using the dependency relationship file, and a CocoaPods management tool is used for managing the dependent third party libraries.

However, a project usually needs multiple members to complete together, each member needs to maintain the same dependency file, and the usage specification of CocoaPods indicates that the dependency file should not be modified directly, but needs to be modified by a Pod install or Pod update command. In the process of collaboration among a plurality of teams, a large number of component version conflict situations can occur, the Podfile can not be directly modified through the two commands, in order to solve component conflicts, members need to manually complete modification, but the configuration file generally contains thousands of configuration information, the manual completion often takes half a day or even longer, the operation is troublesome, mistakes are easy to occur, the working efficiency can not be improved, and the project development cost is high.

Disclosure of Invention

The embodiment of the invention mainly aims to provide a component updating method, a component updating device, equipment and a storage medium, so that the operation complexity is reduced, the learning cost is saved, the working efficiency of developers is improved, and the project development cost is reduced.

To achieve the above object, a first aspect of the embodiments of the present invention provides a component updating method applied to a Fastlane tool, including:

acquiring a source code file of a server side; the source code files comprise index files and dependency relationship files;

detecting whether a new component exists in the source code file according to the index file;

if the new component exists, reading a preset component configuration table to obtain the version number of the new component, wherein the version number is used for representing the latest version number of the new component;

analyzing the dependency relationship file according to the version number to obtain an analysis result, wherein the analysis result is the version number;

updating the dependency relationship file according to the target dependency relationship;

and installing the new component according to the dependency relationship file.

In some embodiments, the parsing the dependency relationship file according to the version number to obtain a parsing result includes:

reading the component configuration table to obtain description information, wherein the description information comprises: first information, second information, and third information; the first information is used for indicating that the referenced version number is equal to the version number of the new component, the referenced version number indicates that the preset component refers to the version number of the new component, the second information is used for indicating that the referenced version number is greater than the version number of the new component, and the third information is used for indicating that the referenced version number is less than the version number of the new component;

obtaining the analysis result according to the description information, wherein the analysis result comprises: updating the dependency files and generating conflict information.

In some embodiments, the updating the dependency file according to the parsing result includes:

if the description information is the first information, updating the dependency relationship file;

if the description information is the second information, the dependency relationship file is not updated;

and if the description information is the third information, generating conflict information.

In some embodiments, after installing the new component according to the dependency file, the method further includes: performing annotation processing on the dependency relationship file, specifically including:

acquiring modification information of the dependency relationship file;

generating annotation information according to the modification information;

and annotating the annotation information in the dependency relationship file.

In some embodiments, after installing the new component according to the dependency file, the method further includes:

generating a push command;

and pushing the dependency relationship file to the server by using the push command.

In some embodiments, before the obtaining the source code file of the server, the method further includes:

detecting the code state of a local end; wherein the code state comprises an edit state;

and clearing the code in the editing state.

In some embodiments, the source code file further includes branch information, and after the obtaining of the source code file at the server side, the method further includes:

acquiring current project branch information of a local end;

carrying out consistency comparison on the branch information and the current branch information;

and if the original branch information is inconsistent with the current project branch information, the source code file is obtained again.

In order to achieve the above object, a second aspect of the present invention provides a device for updating a component, which is applied to a Fastlane tool, and comprises:

the source code file acquisition module is used for acquiring a source code file of a server side; the source code file comprises an index file and a dependency relationship file;

the component detection module is used for detecting whether a new component exists in the source code file according to the index file;

the version number reading module is used for reading a preset component configuration table to obtain the version number of a new component if the new component exists;

the dependency relationship file analysis module is used for analyzing the dependency relationship file according to the version number to obtain an analysis result;

the dependency relationship file updating module is used for updating the dependency relationship file according to the analysis result;

and the component installation module is used for installing the new component according to the dependency relationship file. Analyzing result of target dependency relationship between new component and preset component

To achieve the above object, a third aspect of the present invention provides an electronic apparatus comprising:

at least one memory;

at least one processor;

at least one program;

the program is stored in the memory and the processor executes the at least one program to implement the method of the invention as described in the above first aspect.

To achieve the above object, a fourth aspect of the present invention proposes a storage medium which is a computer-readable storage medium storing computer-executable instructions for causing a computer to execute:

the method of the first aspect as described above.

The component updating method, the device, the equipment and the storage medium provided by the embodiment of the invention are managed by using a Fastlane tool, and a source code file of a server side is obtained; the source code file comprises an index file and a dependency relationship file, whether a new component exists in the source code file is detected according to the index file, if the new component exists, a preset component configuration table is read, the version number of the new component is obtained, the dependency relationship file is analyzed according to the version number, an analysis result is obtained, and the dependency relationship file is updated according to the analysis result. According to the method and the device, the component configuration information is acquired by automatically analyzing the dependency relationship file, manual modification conflict is avoided, the operation flow is simplified, the operation complexity is reduced, meanwhile, manual searching for modification configuration information is not needed, errors are avoided, the working efficiency of developers is improved, and the project development cost is reduced.

Drawings

Fig. 1 is a flowchart of a component update method according to an embodiment of the present invention.

Fig. 2 is a flowchart of a component update method according to another embodiment of the present invention.

Fig. 3 is a flowchart of a component update method according to another embodiment of the present invention.

Fig. 4 is a flowchart of a component update method according to another embodiment of the present invention.

Fig. 5 is a schematic diagram illustrating an interaction between a server and a local end by applying a component updating method according to another embodiment of the present invention.

Fig. 6 is a block diagram of a component update apparatus according to another embodiment of the present invention.

Fig. 7 is a schematic diagram of a hardware structure of an electronic device according to an embodiment of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

It should be noted that although functional blocks are partitioned in a schematic diagram of an apparatus and a logical order is shown in a flowchart, in some cases, the steps shown or described may be performed in a different order than the partitioning of blocks in the apparatus or the order in the flowchart.

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. The terminology used herein is for the purpose of describing embodiments of the invention only and is not intended to be limiting of the invention.

First, several terms related to the present invention are analyzed:

cocoaPods: cocoaPods is a dependency management tool for developing a third party library of OS X and iOS applications. The CocoaPods can be used for defining the dependency relationship of the CocoaPods, version management of the third-party libraries is very convenient in the whole development environment, source codes of the libraries are downloaded, and the third-party libraries are connected with engineering by creating a Xcode word, so that development and use are convenient.

Git: git is the most popular distributed version control system at present, and can effectively process the version management of various projects at high speed. The method has the advantages of suitability for distributed development, no too large pressure on the public server, high speed, easiness in conflict resolution and the like.

Pods: the dependencies defined by CocoaPods are utilized. When an application program is developed, a source code program corresponding to the development of the application program can be understood as a project, one project can comprise a plurality of projects, a dependency relationship table between the projects is defined as Podfile, a dependency relationship table between components is defined as Podspec, and after a Pod install related command is executed, a total dependency relationship file is generated by combining the plurality of dependency relationship tables of Podfile and Podspec and is defined as a Podfle. The lock file is used to confirm that each member of the same under-project team has the same version of the Pods installed components.

Assembly of: is an object, a component is a simple encapsulation of data and methods, and a component is a specific object derived from TComponent. The components can have their own properties and methods, the properties are simple visitors of component data, the methods are some simple and visible functions of the components, and drag-and-drop programming, rapid property processing and true object-oriented design can be realized by using the components.

Warehouse: when a developer creates a project, a Code Repository (Code reproducibility) and a configuration Repository (Code reproducibility) can be created in an area where a private library can be created. Wherein Code Repository is generally understood as a Code Repository to which Code generated when a project is created can be uploaded. Code hierarchy is generally understood as a configuration Repository to which configuration information about a project can be uploaded, for example the component name, version can be stored in the configuration Repository, which is used to store component dependency files (Podspec files). The content in the Podspec file is dependency information for one component, and the dependency information may include a source file depended by the component, a third-party component depended by the component, a download address of the component, a version of the component, and other information. The code repository and the configuration repository may be created locally and on the server side, that is, the Podspec file of the configuration repository is stored locally and on the server side.

Fastlane: the system is a complete set of client CI tool set, replaces the tedious tasks in the process of processing, constructing and releasing App by developers, can very quickly and simply build an automatic releasing service, and supports Android, iOS and MacOS. Fastlane itself does not have a special set of syntax, the Ruby language used.

With the rapid development of computer technology, development requirements for different application programs are increasing, a large number of third-party libraries are generally introduced in the development process of the application programs, the third-party libraries are managed conveniently and uniformly, the dependency relationship between the third-party libraries and development projects and related information such as version relationship are defined by using a dependency relationship file, and a CocoaPods management tool is used for managing the dependency libraries.

However, a project usually needs multiple members to complete together, each member needs to maintain the same dependency file, and the usage specification of CocoaPods indicates that the dependency file should not be modified directly, but needs to be modified by a Pod install or Pod update command. In the process of collaboration among a plurality of teams, a large number of component version conflict situations occur, at this time, the Podfile file cannot be directly modified through the two commands, in order to solve the component conflict, a member needs to manually complete modification, and the general modification steps include: 1) Finding conflicting components; 2) Comparing the version difference of the component in the two teams; 3) Selecting a latest version of the component; 4) Manually searching the dependency relationship file for the place where the component is referenced; 5) It is determined empirically whether replacement is necessary. Generally, the configuration file of the dependency relationship file contains thousands of configuration information, if the configuration file is manually completed, half a day or even longer time is often needed, the operation is troublesome, time and labor are wasted, errors are easy to occur, the working efficiency cannot be improved, and the project development cost is high.

Based on this, the embodiment of the present invention provides a component updating method, apparatus, device and storage medium, which applies a Fastlane tool to perform management, and obtains a source code file of a server; the source code file comprises an index file and a dependency relationship file, whether a new component exists in the source code file is detected according to the index file, if the new component exists, a preset component configuration table is read, the version number of the new component is obtained, the dependency relationship file is analyzed according to the version number, an analysis result is obtained, and the dependency relationship file is updated according to the analysis result. According to the embodiment, the dependency relationship file is automatically analyzed, the component configuration information is obtained, manual modification conflict is avoided, the operation process is simplified, the operation complexity is reduced, meanwhile, manual searching and modification of the configuration information are not needed, errors are avoided, the working efficiency of developers is improved, and the project development cost is reduced.

The embodiment of the present invention provides a component updating method, a device, an apparatus, and a storage medium, which are specifically described in the following embodiments, and first, a component updating method in the embodiment of the present invention is described.

The embodiment of the invention provides a component updating method, relates to the technical field of computers, and particularly relates to the technical field of software development. The component updating method provided by the embodiment of the invention can be applied to a terminal, a server side and software running in the terminal or the server side. Wherein the terminal communicates with the server via a network. The component update method may be performed by the terminal or the server, or by cooperation of the terminal and the server. Here, the component update method is explained using an example of terminal execution: the terminal obtains the source code file of the server by applying a Fastlane tool and obtains the source code file of the server; the source code file comprises an index file and a dependency relationship file, whether a new component exists in the source code file is detected according to the index file, if the new component exists, a preset component configuration table is read, the version number of the new component is obtained, the dependency relationship file is analyzed according to the version number, an analysis result is obtained, and the dependency relationship file is updated according to the analysis result. According to the method and the device, the configuration information of the component is acquired by automatically analyzing the dependency relationship file, so that manual modification conflict is avoided, the operation flow is simplified, and the operation complexity is reduced.

In some embodiments, the terminal may be a smartphone, tablet, laptop, desktop computer, or smart watch, among others. The server can be an independent server, and can also be a cloud server providing basic cloud computing services such as cloud service, a cloud database, cloud computing, a cloud function, cloud storage, network service, cloud communication, middleware service, domain name service, security service, content Delivery Network (CDN), big data and artificial intelligence platform and the like; or may be service nodes in a blockchain system, where a Peer-To-Peer (P2P) network is formed among the service nodes in the blockchain system, and the P2P Protocol is an application layer Protocol operating on a Transmission Control Protocol (TCP). The server may be installed with a server of the demand management system, and the server may interact with the terminal through the server, for example, corresponding software is installed on the server, and the software may be an application that implements a component update method, but is not limited to the above form. The terminal and the server may be connected through communication connection manners such as bluetooth, USB (Universal Serial Bus), or network, which is not limited herein.

The invention is operational with numerous general purpose or special purpose computing system environments or configurations. For example: personal computers, server computers, hand-held or portable devices, tablet-type devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like. The invention may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

In an embodiment, the component update method is based on a mode of a CocoaPods management component, integrates a mode that Fastlane is used as a front-end driver, and Python is used as a back-end implementation mode, so that the expansion of a component management function of CocoaPods is enhanced. The fast integrates the Git function, so that the control on the source code can be increased in the whole process, the manual input of a user is reduced from another aspect, and the time cost of returning due to the fact that the manual input of a certain step is wrong is reduced. The whole process is realized in an automatic mode, and an intelligent detection and judgment step is added in the whole process, so that the dependency relationship file (namely the Podfile. Lock file) can be penetrated more accurately. Fig. 1 is an alternative flowchart of a component updating method according to an embodiment of the present invention, where the method in fig. 1 may include, but is not limited to, steps S110 to S160.

Step S110: and acquiring a source code file of the server.

Step S120: and detecting whether the source code file has a new component or not according to the index file.

Step S130: and if the new component exists, reading a preset component configuration table to obtain the version number of the new component.

Step S140: and analyzing the dependency relationship file according to the version number to obtain an analysis result.

Step S150: and updating the dependency relationship file according to the analysis result.

Step S160: and installing the new component according to the dependency relationship file.

In step S110, the server refers to a code server repository, i.e. a Git repository, the local end refers to a developer computer, and the developer uses a "Git pull" command to pull the source code file from the server at the local end. The specific process is as follows: when a required third-party library related file is imported from a Git warehouse of a server side according to requirements, a corresponding Git warehouse is found according to an address Git of the third-party library, corresponding version submission information is located according to a corresponding version number (if the version number is not specified, the latest version is downloaded), the suffix is in the version submission information, a Podspec component dependency relationship file is found, after the Podspec file is found, whether a component name is consistent with the dependency relationship file (Podfle. And if the verification is successful, finding the source code file to be imported according to the source code folder in the component dependency relationship file, finding the corresponding configuration file and resource file through other data, and finally downloading the configuration file and the resource file to a local project, namely obtaining the source code file of the server. In this embodiment, the dependency relationship file is a form commonly maintained by developers in the whole project, and the downloaded source code file includes an index file and a dependency relationship file.

In one embodiment, the content of a docoapods pods podfile is as follows:

target'Project'do

use_frameworks！

Pod'ModuleA'，:Git＝>'ssh://Git@xxxxxx/Module.Git'，:tag＝>'2.0.0'

end

wherein, the file refers to integrating Module components in project engineering and giving the Git warehouse address and tag version information of the Module. Wherein the Git address points to the code management library of the module and is used for pulling the source code file of the submodule. And tag is a snapshot of the Git version library, and points to a commit pointer, which is used to indicate version information. The version information can also be represented by a branch, the branch corresponds to a series of commit, is a line formed by connecting a plurality of points, has a HEAD pointer and can be moved by means of the HEAD pointer.

In an embodiment, in order to ensure the consistency of codes at two ends in the development process, before any operation is performed at the local end, the latest source code file needs to be pulled from the server end. In order to ensure higher consistency when the source code file is pulled, referring to fig. 2, before step S110, the component updating method further includes step S111 and step S112.

Step S111: and detecting the code state of the local end.

Step S112: and judging the branch information of the current item.

In step S111 of an embodiment, the purpose of this step is to make the local working area have no code being edited. The code state comprises an editing state, and the code in the editing state is cleared. The status of the file in the local working area is checked by executing a 'Git status' command by using a script, the status command can display the status of a working directory and a temporary storage area, whether codes which are being edited exist in the local working area is judged by using a return result of the command, and the source code file pulled by the server end and the file which is being modified locally can be prevented from colliding only if the development environment of the local end is clean and the working area does not have the codes which are being edited.

In step S112 of an embodiment, after the embodiment obtains the source code file of the server, the embodiment obtains the current item branch information of the local end, then obtains the branch information in the source code file, and compares the branch information with the current branch information in a consistency manner, and if the branch information is not consistent with the current item branch information, the embodiment obtains the source code file again.

In one embodiment, a development project may include a large number of branches, such as main branches, development branches, property branches, version branches, etc., so as to prevent related code from being wrongly submitted to other places, and therefore, the accuracy of the branches can be ensured by comparing the detection of the branches with the branch information in the configuration file related to the source code file.

In one embodiment, the script is used to read out the branch of the current project, and then the branch is compared with the branch information in the configuration file related to the source code file.

In step S120, in an embodiment, whether the source code file contains a new component, i.e., implementation of minimum granularity of functions, is detected according to the index file, where the new component may be a newly developed function in the project. The process by which CocoaPods adds new components is: copying the source code of a new component to an internal network, then marking a tag with the version number plus 1 on the component, installing the component in a Demo engineering file, wherein the corresponding version submission information contains a component dependency relationship file with the suffix Podspec, finally modifying the version number in the component dependency relationship file, pointing the Git address in the component dependency relationship file to a source code warehouse, locally verifying whether the new version can be normally installed, and after the verification is passed, transmitting the Podspec to a configuration warehouse by using a command. The index file of the source code file obtained by pulling in step S110 may direct the configuration repository, so as to determine whether there is a new component in the source code file.

In one embodiment, in an embodiment step S130, the new component includes a component with a completely new functionality and an updated old version component. Reading the component configuration table to obtain the version number of the new component, wherein the version number is used for representing the latest version number of the new component.

In an embodiment, referring to fig. 3, step S130 of the component updating method further includes step S131 and step S132.

Step S131: and reading the component configuration table to obtain the description information.

Step S132: and analyzing the description information to obtain an analysis result.

In one embodiment, the description information is mainly used for describing version number information, where the description information about the version number information includes: the first information, the second information and the third information, and the analysis result is used for judging whether to update the dependency relationship file.

In this embodiment, the first information is used to indicate that the version number referenced by other components in the dependency relationship is equal to the version number of the new component, and is expressed as: = Version: equal to the version number, the referenced version number indicates that the preset component references the version number of the new component, expressed as: (Version).

The second information is used for indicating that the referenced version number is larger than the version number of the new component, and is represented as follows: v > Version: greater than the version number.

The third information is for indicating that the referenced Version number is smaller than the Version number of the new component, and is expressed as < Version: indicating a smaller version number.

In addition, the above information is the description information of the component itself in the podfile.

It should be understood that the above description is illustrative only, and is not intended to represent the only form in which the information may be presented.

After the version number of the component is acquired, the dependency relationship file is parsed, and the process proceeds to step S140.

In step S140 in an embodiment, the configuration of the component is analyzed line by analyzing a podfile.lock dependency relationship file, and the analysis result is whether to update the dependency relationship file, where a preset component is other components in the project, and the purpose of this step is to obtain a target dependency relationship between the other components and the new component. The specific analysis process is as follows:

in step S150 in an embodiment, it is determined whether there is a new component that is dependent on another component according to the configuration information in the dependency file, that is, there is a dependency relationship between the new component and another component, and if there is a new component, the version reference relationships between different components will be different, so that the dependency file is modified according to the version number of the new component and the component dependency relationship.

And if other components depend on the new component, if the description information is the first information, updating the dependency relationship file according to the analysis result.

If other components depend on the new component, if the description information is the second information, the dependency relationship file is not updated according to the analysis result, namely if the referenced version is larger than the new version, the dependency relationship file does not need to be changed, and the other components reference the latest version.

If other components depend on the new component, if the description information is third information, conflict information is generated according to the analysis result, and the third information indicates that the referenced version number is smaller than the version number of the new component, the version conflict exists, and the conflict information needs to be sent to a related engineer to be correspondingly modified.

In step S160, a new component is installed according to the target dependency file, and the new component is installed by executing the command "Pod install".

In an embodiment, after the step S160 has completed installing the new component, the component updating method further includes: and performing annotation processing on the dependency relationship file, namely generating annotation information according to the modification information of the dependency relationship file and performing annotation.

In the embodiment, modification information of the dependency relationship file is acquired, annotation information is generated according to the modification information, and the annotation information is annotated in the dependency relationship file. According to the embodiment, the command 'gitadd & gitcommit' is executed to generate the annotation information from the modification information of the corresponding component, and the annotation information is added to the annotation position, so that other members of the project group can visually know the modification information of the component according to the annotation information, and the readability of the project is improved.

In an embodiment, after the step S160 has completed installing the new component, the component updating method further includes: and pushing the dependency relationship file to a server side.

In the embodiment, a push command is generated in the local segment, the dependency relationship file is pushed to the server side by the push command, that is, the modification of the local dependency relationship file is pushed to the server side by the Git push command, that is, the Git side, so that other members of the project can be ensured to perform subsequent development on the basis of the update, and the project development process is promoted. The lock file is most useful for development by multiple persons, if the versions of the pots are not specified in the podfiles, the latest version of the current trilateral library is obtained by default, after one person in the team executes the Podinstall command, the generated podfile.lock records the version of the current latest Podfile dependency, at this time, after the project containing the podfile.lock file is pulled by other developers in the project, the project is executed to execute the Podinstall command, the obtained version of the pode dependency library is consistent with the version obtained by the initial user, and if no podfile.lock file exists, all subsequently executed podistall can obtain the dependency of the latest version, so that the versions of the dependency libraries used in one team are inconsistent, and the development process is seriously influenced.

In an embodiment, after pushing the dependency relationship file to the server, the component updating method further includes: and executing the environment cleaning code to ensure that no un-pushed legacy file exists in the local working area.

In this embodiment, the environment cleaning code is used to ensure that the local working environment is clean and there is no left-over file that is not pushed after the push operation is completed.

In one embodiment, the above steps can be automatically performed by using a Fastlane tool setting script, wherein the specific operations, condition judgment, and the like are automatically performed in the script. The penetration technology aiming at the locked file can intelligently identify the components needing to be updated in the project and dynamically complete the updating of the components for developers. For example, a developer need only trigger a command to update a component, such as "fastlane update xxx", where "xxx" represents the name of the component, and its subsequent operations are automatically completed by the script. If the above steps are completed manually, half a day or longer time is often needed, and the method of the embodiment can be completed by only executing one line of commands, so that the learning cost of a CocoaPods mechanism is saved, the time of a developer is liberated from conflict resolution, the configuration is read line by line in a script mode, and the components are matched according to a given rule, so that the mental burden of reading the configuration by the developer can be reduced, the manual modification conflict is avoided, the operation flow is simplified, the operation complexity is reduced, meanwhile, the configuration information is not required to be searched and modified manually, errors are avoided, the working efficiency of developers is improved, the project development cost is reduced, the developer can put more time and more energy on optimization of service logic and project experience, a more delicate product is manufactured, and the user satisfaction is improved.

Referring to fig. 4, a flowchart of a component update method according to an embodiment of the present application is shown. It can be seen that it includes steps S410 to S460.

Step S410: and acquiring the index file related to the component.

According to the embodiment, whether the new component exists in the source code file is judged according to the index file of the source code file, and the configuration warehouse can be guided in the index file of the source code file obtained through pulling, so that whether the new component exists in the source code file can be judged according to the index file.

Step S420: component configuration information is read.

In this embodiment, the component configuration table is read to obtain the description information, and the description information is analyzed to obtain an analysis result.

In one embodiment, the description information is mainly used for describing version number information, where the description information about the version number information includes: first information, second information, and third information. In this embodiment, the first information is used to indicate that the version number referenced by other components in the dependency is equal to the version number of the new component, and is expressed as: = Version: equal to the version number, the referenced version number indicates that the preset component references the version number of the new component, expressed as: (Version). The second information is used for indicating that the referenced version number is larger than the version number of the new component, and is represented as follows: - > Version: greater than the version number. The third information is for indicating that the referenced Version number is smaller than the Version number of the new component, and is expressed as < Version: indicating a smaller version number. The above information is description information of the component itself in the podfile.

Step S430: and analyzing the dependency relationship file.

In this embodiment, the configuration of the component is analyzed line by analyzing the podfile.lock dependency relationship file, and whether the dependency relationship file needs to be updated is determined according to the acquired version number information.

Step S440: and updating the dependency relationship file.

In this embodiment, whether another component depends on the new component is determined according to the configuration information in the dependency relationship file, that is, a dependency relationship exists between the new component and the other component, and the dependency relationship file is updated.

If other components depend on the new component, if the description information is third information, conflict information is generated according to the analysis result, the third information indicates that the referenced version number is smaller than the version number of the new component, the version conflict exists, and the conflict information needs to be sent to a related engineer for corresponding modification.

Step S450: and installing the components according to the dependency relationship file.

In this embodiment, a command "Pod install" is executed to install a new component according to the latest dependency file. After the new component is installed. And generating annotation information according to the modification information of the new component and performing annotation. And generating annotation information from the modification information of the corresponding component by executing a command of 'gitadd & gitcommit', and adding the annotation information to an annotation position, so that other members of the project group can intuitively know the modification information of the component according to the annotation information, and the readability of the project is improved.

Step S460: and pushing the dependency relationship file to a server side.

In the embodiment, the modification of the local dependency relationship file is pushed to the server side, namely the Git side, so that other members of the project can be ensured to perform subsequent development on the basis of the update, and the development process of the project is promoted.

Fig. 5 is a schematic diagram illustrating interaction between a server and a local end according to an embodiment of the present application.

In fig. 5, the server side refers to a code server warehouse, i.e., a Git warehouse, stores a source code file (repo), a dependency relationship table (Podspec) between components, a dependency relationship table (Podfile) between projects, and a dependency relationship file (Podfile. The local end refers to a developer computer, when the developer needs to update the components, the developer locally utilizes a 'gitpull' command to pull the source code file from the server end, then updates and configures the dependency relationship file according to the dependency relationship table among the components, and finally installs the new components. Because the dependency relationship table (Podspec) among the new component pair components, the dependency relationship table (Podfle) among the projects and the dependency relationship file (Podfle. Lock) are all associated and modified, the modification of the local dependency relationship file is pushed to the server by using a 'Git push' command after the installation is finished.

According to the technical scheme provided by the embodiment of the invention, a Fastlane tool is applied for management, and the source code file of the server end is obtained; the source code file comprises an index file and a dependency relationship file, whether a new component exists in the source code file is detected according to the index file, if the new component exists, a preset component configuration table is read, the version number of the new component is obtained, the dependency relationship file is analyzed according to the version number, an analysis result is obtained, and the dependency relationship file is updated according to the analysis result. According to the method and the device, the component configuration information is acquired by automatically analyzing the dependency relationship file, manual modification conflict is avoided, the operation flow is simplified, the operation complexity is reduced, meanwhile, manual searching for modification configuration information is not needed, errors are avoided, the working efficiency of developers is improved, and the project development cost is reduced.

The method can be completed only by executing a line of commands, the learning cost of a CocoaPods mechanism is saved, the time of a developer is liberated from solving the conflict, the configuration is read line by line in a script mode, the components are matched according to the given rules, the mental burden of reading the configuration by the developer can be reduced, the manual modification conflict is avoided, the operation flow is simplified, the operation complexity is reduced, meanwhile, the configuration information is not required to be manually searched and modified, errors are avoided, the working efficiency of the developer is improved, the project development cost is reduced, the developer can put more time and energy on the optimization of business logic and project experience, a more delicate product is made, and the user satisfaction is improved.

An embodiment of the present invention further provides a component update apparatus, which can implement the component update method described above, and with reference to fig. 6, the apparatus includes:

a source code file obtaining module 610, configured to obtain a source code file of a server; the source code file comprises an index file and a dependency relationship file.

In this embodiment, when the source code file obtaining module 610 imports a required third party repository related file from a Git repository of a server according to a requirement, first find a corresponding Git repository according to an address Git of the third party repository, then locate corresponding version submission information according to a corresponding version number (if no version number is specified, a latest version is downloaded), where the version submission information has a suffix of a Podspec component dependency relationship file, find the Podspec file, first verify whether a component name is consistent with a dependency relationship file (podfile.lock file), and if not, report an error statement is not found. And if the verification is successful, finding the source code file to be imported according to the source code folder in the component dependency relationship file, finding the corresponding configuration file and resource file through other data, and finally downloading the configuration file and the resource file to a local project, namely obtaining the source code file of the server.

And the component detection module 620 is configured to detect whether a new component exists in the source code file according to the index file.

In this embodiment, the component detection module 620 obtains the configuration repository pointed by the source code file according to the index file of the source code file obtained by pulling, so as to determine whether there is a new component in the source code file.

A version number reading module 630, configured to read a preset component configuration table to obtain a version number of the new component if the new component exists, where the version number is used to indicate a latest version number of the new component.

In this embodiment, if there is a new component, the version number reading module 630 reads the component configuration table to obtain the version number of the new component. The new components include components of entirely new functionality and updated old version components. Reading the component configuration table to obtain the version number of the new component. The method mainly comprises the steps of obtaining description information in a dependency relationship file according to a component configuration table, and obtaining a version number of a new component according to the description information. Wherein the description information includes: first information, second information, and third information. In this embodiment, the first information is used to indicate that the version number referenced by other components in the dependency relationship is equal to the version number of the new component, and is expressed as: = Version: equal to the version number, the referenced version number indicates that the preset component references the version number of the new component, expressed as: (Version). The second information is used for indicating that the referenced version number is larger than the version number of the new component, and is represented as follows: - > Version: greater than the version number. The third information is for indicating that the referenced Version number is smaller than the Version number of the new component, and is expressed as < Version: indicating a smaller version number. In addition, the above information is the description information of the component itself in the podfile.

The dependency relationship file analyzing module 640 is configured to analyze the dependency relationship file according to the version number to obtain an analysis result, where the analysis result indicates whether to update the dependency relationship file.

In this embodiment, the dependency relationship file parsing module 640 determines whether there is another component that depends on the new component according to the configuration information in the dependency relationship file, that is, there is a dependency relationship between the new component and the other component. And if other components depend on the new component, if the description information is the first information, updating the dependency relationship file according to the analysis result. If other components depend on the new component, if the description information is the second information, the dependency relationship file is not updated according to the analysis result, namely if the referenced version is larger than the new version, the dependency relationship file does not need to be changed, and the other components reference the latest version. If other components depend on the new component, if the description information is third information, conflict information is generated according to the analysis result, and the third information indicates that the referenced version number is smaller than the version number of the new component, the version conflict exists, and the conflict information needs to be sent to a related engineer to be correspondingly modified.

And the dependency relationship file updating module 650 is configured to update the dependency relationship file according to the parsing result.

And the component installation module 660 is used for installing the new component according to the dependency relationship file.

In this embodiment, the component installation module 660 executes the command "Pod install" to install a new component, and according to the latest dependency file, if other components having dependencies are also updated, the new component may be installed together. After the new component is installed. And generating annotation information according to the modification information of the new component and performing annotation. And generating annotation information from the modification information of the corresponding component by executing a command of 'gitadd & gitcommit', and adding the annotation information to an annotation position, so that other members of the project group can visually know the modification information of the component according to the annotation information, and the readability of the project is improved.

The specific implementation of the component updating apparatus of this embodiment is substantially the same as the specific implementation of the component updating method, and is not described herein again.

An embodiment of the present invention further provides an electronic device, including:

at least one memory;

at least one processor;

at least one program;

the programs are stored in the memory and the processor executes at least one of the programs to implement the component update methods of the present invention as described above. The electronic device can be any intelligent terminal including a mobile phone, a tablet computer, a Personal DiGital Assistant (PDA for short), a vehicle-mounted computer and the like.

Referring to fig. 7, fig. 7 illustrates a hardware structure of an electronic device according to another embodiment, where the electronic device includes:

the processor 701 may be implemented by a general-purpose CPU (central processing unit), a microprocessor, an Application Specific Integrated Circuit (ASIC), or one or more integrated circuits, and is configured to execute a relevant program to implement the technical solution provided in the embodiment of the present invention;

the memory 702 may be implemented in a ROM (read only memory), a static memory device, a dynamic memory device, or a RAM (random access memory). The memory 702 may store an operating system and other application programs, and when the technical solution provided by the embodiments of the present disclosure is implemented by software or firmware, the relevant program codes are stored in the memory 702 and called by the processor 701 to execute the component updating method according to the embodiments of the present disclosure;

an input/output interface 703 for realizing information input and output;

the communication interface 704 is used for realizing communication interaction between the device and other devices, and can realize communication in a wired manner (for example, USB, network cable, etc.) or in a wireless manner (for example, mobile network, WIFI, bluetooth, etc.); and

a bus 705 that transfers information between the various components of the device (e.g., the processor 701, the memory 702, the input/output interface 703, and the communication interface 704);

wherein the processor 701, the memory 702, the input/output interface 703 and the communication interface 704 are communicatively connected to each other within the device via a bus 705.

An embodiment of the present invention further provides a storage medium, which is a computer-readable storage medium, where the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are configured to enable a computer to execute the component updating method.

The component updating method, the component updating device, the electronic equipment and the storage medium provided by the embodiment of the invention are managed by using a Fastlane tool, and a source code file of a server side is obtained; the source code file comprises an index file and a dependency relationship file, whether a new component exists in the source code file is detected according to the index file, if the new component exists, a preset component configuration table is read, the version number of the new component is obtained, the dependency relationship file is analyzed according to the version number, an analysis result is obtained, and the dependency relationship file is updated according to the analysis result. According to the embodiment, the dependency relationship file is automatically analyzed, the component configuration information is obtained, manual modification conflict is avoided, the operation process is simplified, the operation complexity is reduced, meanwhile, manual searching and modification of the configuration information are not needed, errors are avoided, the working efficiency of developers is improved, and the project development cost is reduced.

The method can be completed only by executing one line of commands, the learning cost of a CocoaPods mechanism is saved, the time of a developer is liberated from solving the conflict, the configuration is read line by line in a script mode, the matching component is matched according to a given rule, the mental burden of reading the configuration of the developer is reduced, the manual modification conflict is avoided, the operation flow is simplified, the operation complexity is reduced, meanwhile, the configuration information is not required to be manually searched and modified, errors are avoided, the working efficiency of the developer is improved, the project development cost is reduced, the developer can place more time and energy on the optimization of service logic and project experience, a more delicate product is made, and the user satisfaction is improved.

The memory, which is a non-transitory computer readable storage medium, may be used to store non-transitory software programs as well as non-transitory computer executable programs. Further, the memory may include high speed random access memory, and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, the memory optionally includes memory located remotely from the processor, and these remote memories may be connected to the processor through a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The embodiment described in the embodiment of the present invention is for more clearly illustrating the technical solution of the embodiment of the present invention, and does not constitute a limitation to the technical solution provided in the embodiment of the present invention, and it can be known by those skilled in the art that the technical solution provided in the embodiment of the present invention is also applicable to similar technical problems with the evolution of technology and the occurrence of new application scenarios.

It will be appreciated by those skilled in the art that the solutions shown in fig. 1-7 are not intended to limit the embodiments of the present invention, and may include more or fewer steps than those shown, or some of the steps may be combined, or different steps may be included.

The above-described embodiments of the apparatus are merely illustrative, wherein the units illustrated as separate components may or may not be physically separate, i.e. may be located in one place, or may also be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment.

One of ordinary skill in the art will appreciate that all or some of the steps of the methods, systems, functional modules/units in the devices disclosed above may be implemented as software, firmware, hardware, and suitable combinations thereof.

The terms "first," "second," "third," "fourth," and the like in the description of the invention and in the drawings described above, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

It is to be understood that, in the present invention, "at least one" means one or more, "a plurality" means two or more. "and/or" is used to describe the association relationship of the associated object, indicating that there may be three relationships, for example, "a and/or B" may indicate: only A, only B and both A and B are present, wherein A and B may be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of single item(s) or plural items. For example, at least one (one) of a, b, or c, may represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", wherein a, b, c may be single or plural.

In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one position, or may be distributed on multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes multiple instructions for enabling an electronic device (which may be a personal computer, a server, or a network device) to perform all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing programs, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The preferred embodiments of the present invention have been described above with reference to the accompanying drawings, and are not intended to limit the scope of the embodiments of the invention. Any modifications, equivalents and improvements that may occur to those skilled in the art without departing from the scope and spirit of the embodiments of the present invention are intended to be within the scope of the claims of the embodiments of the present invention.

Claims

1. A component update method for a Fastlane tool, comprising:

acquiring a source code file of a server side; the source code file comprises an index file and a dependency relationship file;

detecting whether a new component exists in the source code file or not according to the index file

If a new component exists, reading a preset component configuration table to obtain the version number of the new component;

analyzing the dependency relationship file according to the version number to obtain an analysis result;

updating the dependency relationship file according to the analysis result;

and installing the new component according to the dependency relationship file.

2. The component updating method according to claim 1, wherein parsing the dependency file according to the version number to obtain a parsing result includes:

and obtaining the analysis result according to the description information, wherein the analysis result is used for judging whether to update the dependency relationship file.

3. The component updating method according to claim 2, wherein the updating the dependency file according to the parsing result includes:

4. The component updating method according to any one of claims 1 to 3, wherein after installing the new component according to the dependency file, the method further comprises: performing annotation processing on the dependency relationship file, specifically including:

acquiring modification information of the dependency relationship file;

generating annotation information according to the modification information;

and annotating the annotation information in the dependency relationship file.

5. The component updating method according to any one of claims 1 to 3, wherein after installing the new component according to the dependency file, the method further comprises:

generating a push command;

6. The component update method according to claim 1, wherein before acquiring the source code file of the server, the method further comprises:

and clearing the code in the editing state.

7. The component updating method according to claim 1, wherein the source code file further includes branch information, and after obtaining the source code file of the server, the method further includes:

acquiring current project branch information of a local end;

and if the branch information is inconsistent with the current project branch information, the source code file is obtained again.

8. A component update apparatus for use in a Fastlane tool, comprising:

and the component installation module is used for installing the new component according to the dependency relationship file.

9. An electronic device comprising a processor and a memory;

the memory is used for storing programs;

the processor is configured to execute the component update method according to the program according to any one of claims 1 to 7.

10. A computer-readable storage medium storing computer-executable instructions for performing the component update method of any one of claims 1 to 7.