CN114115982A - Code issuing method, device, equipment and storage medium - Google Patents
Code issuing method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN114115982A CN114115982A CN202111463271.7A CN202111463271A CN114115982A CN 114115982 A CN114115982 A CN 114115982A CN 202111463271 A CN202111463271 A CN 202111463271A CN 114115982 A CN114115982 A CN 114115982A
- Authority
- CN
- China
- Prior art keywords
- code
- sdk
- file
- library
- source
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 98
- 238000003860 storage Methods 0.000 title claims abstract description 18
- 238000012545 processing Methods 0.000 claims abstract description 60
- 230000010354 integration Effects 0.000 claims description 43
- 238000004590 computer program Methods 0.000 claims description 17
- 238000004806 packaging method and process Methods 0.000 claims description 10
- 238000009826 distribution Methods 0.000 claims description 6
- 238000013461 design Methods 0.000 description 16
- 238000010586 diagram Methods 0.000 description 13
- 230000006870 function Effects 0.000 description 12
- 238000007726 management method Methods 0.000 description 10
- 238000004891 communication Methods 0.000 description 7
- 244000299461 Theobroma cacao Species 0.000 description 5
- 235000009470 Theobroma cacao Nutrition 0.000 description 5
- 238000012827 research and development Methods 0.000 description 5
- 238000011161 development Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 4
- 238000012360 testing method Methods 0.000 description 4
- 208000033748 Device issues Diseases 0.000 description 2
- 230000001419 dependent effect Effects 0.000 description 2
- 235000019800 disodium phosphate Nutrition 0.000 description 2
- 230000014509 gene expression Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 239000012141 concentrate Substances 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The application provides a code publishing method, a device, equipment and a storage medium, which relate to the technical field of computers, and the method comprises the following steps: acquiring a code release instruction, wherein the code release instruction comprises: the method comprises the steps of obtaining source code files to be issued and issuing types, wherein the issuing types are used for indicating to issue to an open source library or a closed source library, processing the source code files based on the issuing types, generating SDK integrated files, and issuing the SDK integrated files to a target code library corresponding to the issuing types. In the technical scheme, a user does not need to add an operation library and fill in configuration, codes are integrated by one key, a source closing library is built once, all sdk exist in a frame (frame) form, a source code file can be accurately issued to an open source library or a closed source library, the processing efficiency and the issuing success rate are improved, and the problems of low processing efficiency and low issuing success rate in the existing code issuing process are solved.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method, an apparatus, a device, and a storage medium for code distribution.
Background
With the rapid development of computer technology, products are iterated rapidly, and in order to adapt to new business requirements and implement new functions, research and development personnel can develop new codes and generate tool packages or dependency libraries of some third-party applications for use by internal personnel or external personnel. Thus, after a developer develops new code, how to release it is critical.
In the prior art, the code release process mainly depends on coco codes and git library implementation. Specifically, the git library is a library for storing codes, the coco libraries are tools for managing a third-party dependency library, the coco libraries can be used for solving the dependency relationship among different git libraries, and source codes in the git library are used for establishing a Software Development Kit (SDK) so as to be released.
However, when the docapod is used for creating and using the SDK project, the steps are complex, a large number of commands need to be input, if the code is issued mistakenly, the mixed memory needs to be checked and cleaned manually, the problem of low processing efficiency exists, the git library needs to be created and associated manually, the output speed of the SDK project is limited, and moreover, the git management code is used in the same project, so that the code is inconvenient to reuse, and the problem of low reuse efficiency exists. Namely, the existing code issuing method has the problems of low processing efficiency and low issuing success rate.
Disclosure of Invention
The application provides a code publishing method, a device, equipment and a storage medium, which are used for solving the problems of low processing efficiency and low publishing success rate in the existing code publishing process.
In a first aspect, the present application provides a code publishing method, including:
acquiring a code release instruction, wherein the code release instruction comprises: the method comprises the steps that a source code file to be issued and an issuing type are used for indicating to issue to an open source library or to issue to a closed source library;
processing the source code file based on the release type to generate a Software Development Kit (SDK) integrated file;
and issuing the SDK integrated file to a target code library corresponding to the issuing type.
In one possible design of the first aspect, the publication type is used to indicate publication to an open source library;
correspondingly, the processing the source code file based on the release type to generate a software development kit SDK integrated file includes:
generating an SDK project based on the release type and a preset project creation template, wherein the SDK project is provided with SDK project file directories, and the SDK project file directories comprise: a presentation project folder, sdk code folder, sdk resource folder;
based on the source code file, acquiring a system dependency library and a compiling command of the source code file;
and editing SDK codes in the SDK engineering according to the system dependency library and the compiling command to generate the SDK integration file.
In another possible design of the first aspect, the issue type is used to indicate that the source code file is issued to a closed source library, and the source code file is an open source library code;
correspondingly, the processing the source code file based on the release type to generate a software development kit SDK integrated file includes:
generating an SDK project based on the release type and a preset project creation template, wherein the SDK project is provided with SDK project file directories, and the SDK project file directories comprise: a presentation project folder, sdk code folder, sdk resource folder;
packaging the open source library code into a closed source framework;
acquiring a demonstration version project file corresponding to the open source library code from an open source library;
and generating the SDK integration file according to the dependency library configuration of the open source library code, the closed source frame and the demonstration version engineering file.
Optionally, before the publishing the SDK integration file to the target code library corresponding to the publishing type, the method further includes:
checking the code integrity of the SDK integration file;
when the code of the SDK integration file is incomplete, outputting an error prompt, wherein the error prompt comprises: error location and/or error type;
when the code of the SDK integrated file is complete, storing the code of the SDK integrated file into a git library;
and adding a label to the SDK integration file according to a preset engineering configuration file.
Optionally, the method further includes:
and when the release of the SDK integrated file fails, removing cache information corresponding to the SDK integrated file.
In yet another possible design of the first aspect, before the processing the source code file based on the release type to generate a software development kit SDK integration file, the method further includes:
decoupling the source code file to obtain at least two types of source codes;
storing the at least two types of source code into at least two git libraries, respectively;
determining a library reference relationship between the at least two git libraries.
In yet another possible design of the first aspect, before the obtaining the code release indication, the method further includes:
capturing code usage events for a plurality of code resources;
determining a resource path of each code resource based on the code use event and the library type corresponding to each code resource;
and acquiring the source code file generated based on the plurality of code resources, wherein the source code file carries the resource path of each code resource.
In a second aspect, the present application provides a code distribution apparatus, including:
an obtaining module, configured to obtain a code release instruction, where the code release instruction includes: the method comprises the steps that a source code file to be issued and an issuing type are used for indicating to issue to an open source library or to issue to a closed source library;
the processing module is used for processing the source code file based on the release type to generate a Software Development Kit (SDK) integrated file;
and the issuing module is used for issuing the SDK integrated file to a target code base corresponding to the issuing type.
In one possible design of the second aspect, the publication type is to indicate publication to an open source repository;
correspondingly, the processing module is specifically configured to:
generating an SDK project based on the release type and a preset project creation template, wherein the SDK project is provided with SDK project file directories, and the SDK project file directories comprise: a presentation project folder, sdk code folder, sdk resource folder;
based on the source code file, acquiring a system dependency library and a compiling command of the source code file;
and editing SDK codes in the SDK engineering according to the system dependency library and the compiling command to generate the SDK integration file.
In another possible design of the second aspect, the issue type is used to indicate that the source code file is issued to a closed source library, and the source code file is open source library code;
correspondingly, the processing module is specifically configured to:
generating an SDK project based on the release type and a preset project creation template, wherein the SDK project is provided with SDK project file directories, and the SDK project file directories comprise: a presentation project folder, sdk code folder, sdk resource folder;
packaging the open source library code into a closed source framework;
acquiring a demonstration version project file corresponding to the open source library code from an open source library;
and generating the SDK integration file according to the dependency library configuration of the open source library code, the closed source frame and the demonstration version engineering file.
Optionally, the processing module is further configured to:
checking the code integrity of the SDK integration file;
when the code of the SDK integration file is incomplete, outputting an error prompt, wherein the error prompt comprises: error location and/or error type;
when the code of the SDK integrated file is complete, storing the code of the SDK integrated file into a git library;
and adding a label to the SDK integration file according to a preset engineering configuration file.
Optionally, the processing module is further configured to clear cache information corresponding to the SDK integrated file when the release of the SDK integrated file fails.
In yet another possible design of the second aspect, the processing module is further configured to:
decoupling the source code file to obtain at least two types of source codes;
storing the at least two types of source code into at least two git libraries, respectively;
determining a library reference relationship between the at least two git libraries.
In yet another possible design of the second aspect, the processing module is further configured to capture code usage events of a plurality of code resources, and determine a resource path of each code resource based on the code usage events and a library type corresponding to each code resource;
the obtaining module is further configured to obtain the source code file generated based on the plurality of code resources, where the source code file carries a resource path of each code resource.
In a third aspect, the present application provides an electronic device, comprising: a processor, a memory and computer program instructions stored on the memory and executable on the processor, when executing the computer program instructions, implementing the method as described above in the first aspect and in various possible designs of the first aspect.
Alternatively, the processor may be a chip.
In a fourth aspect, the present application provides a computer-readable storage medium having stored thereon computer instructions which, when executed by a processor, are adapted to implement a method as described above in the first aspect and in various possible designs of the first aspect.
In a fifth aspect, the present application provides a computer program product comprising a computer program which, when executed by a processor, implements the method of the first aspect described above and various possible designs of the first aspect.
According to the code release method, the code release device, the code release equipment and the storage medium, the code release instruction is acquired, and comprises the following steps: the method comprises the steps of obtaining source code files to be issued and issuing types, wherein the issuing types are used for indicating to issue to an open source library or a closed source library, processing the source code files based on the issuing types, generating SDK integrated files, and issuing the SDK integrated files to a target code library corresponding to the issuing types. According to the technical scheme, a user does not need to add an operation library and fill in configuration, codes are integrated by one key, a source closing library is built once, all sdk exist in a frame form, a source code file can be accurately issued to an open source library or a closed source library, the processing efficiency and the issuing success rate are improved, and the problems of low processing efficiency and low issuing success rate in the existing code issuing process are solved.
Drawings
Fig. 1 is a schematic view of an application scenario to which a code publishing method provided in an embodiment of the present invention is applied;
fig. 2 is a schematic flowchart of a first embodiment of a code issuing method provided in the present application;
fig. 3 is a schematic view of a building flow of a basic environment to which the code issuing method provided by the present application is applied;
FIG. 4 is a schematic diagram illustrating a process of publishing to an open source library in the code publishing method provided by the present application;
FIG. 5 is a schematic diagram of an SDK engineering catalog established in an open source library publishing process;
FIG. 6 is a schematic flow chart illustrating a process of publishing to a closed-source library in the code publishing method provided by the present application;
fig. 7 is a flowchart illustrating a second embodiment of a code issuing method provided in the present application;
fig. 8 is a schematic structural diagram of a first code distribution apparatus according to an embodiment of the present application;
fig. 9 is a schematic structural diagram of an embodiment of an electronic device provided in the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Before introducing the application scenarios and technical solutions of the present application, the terms and expressions referred to in the embodiments of the present application are explained first:
APP is an abbreviation of application software;
mac apple computer, using macos system;
sdk: a software development kit;
framework: in particular static libraries of iOS;
flutter: for creating high performance, cross-platform mobile applications;
and iOS: an operating system of the iphone;
opening a source: code source files are visible;
closing a source: hiding the code source file;
and (3) Cocoapod: the system is a third-party library management tool and is widely used for the management of iOS codes;
git is an open-source, distributed version control system for expeditiously and efficiently processing any item, small or large. The Git library is an open source version control software that can store the generated code files.
With the rapid development of network technology and communication technology, mobile terminals are also gradually popularized, and application programs of the mobile terminals are more and more abundant, which have gradually become internet terminals. In order to adapt to new business requirements of the internet terminal and further realize new functions, research and development personnel can develop new codes and generate tool kits or dependency libraries of some third-party applications for use by internal personnel or external personnel. Thus, after a developer develops new code, how to publish it is critical.
Illustratively, the code publishing scene can be the financial industry, and the technical scheme of the application can be applied to the management of the mobile-end iOS application code base of the financial industry.
In the prior art, the code release process mainly depends on coco codes and git library implementation. But has the problems of low processing efficiency and inconvenient code reuse. Aiming at the problems in the prior art, the application provides a specific implementation scheme. The following brief explanation of the problems of the prior art and the solutions of the present application is provided, in particular:
1. when the docapod method is used for creating and using sdk projects, a large number of commands need to be input, the steps are complex, quick processing cannot be performed when errors occur in code release, mixed memory needs to be checked and cleaned manually, and the storage processing efficiency is low. Furthermore, the git library needs to be created and associated manually, not suitable for the rapid production of large quantities of sdk projects. The code publishing method provided by the application can be used for generating the created project and the git library by one key, and is rapid and convenient.
2. In the prior art, an open source library is mainly packaged and is not suitable for secret release, and the prior method can not generate a closed source code packet by one key and can not synchronize demo of an open source and a closed source. According to the technical scheme, the closed source library codes can be generated by one key, demo information can be automatically synchronized, and the like can be set.
3. Because the file reference paths of the open source library and the closed source library are different, the existing method is difficult to generate the open source library and the closed source library by using the same set of codes, and is inconvenient to maintain. The application provides a file resource reference processor, which can generate an open source library and a closed source library only by one set of codes and has low maintenance cost.
4. The dependence of sdk on a system library needs to be manually searched and added in the prior art, the method is very troublesome and easy to miss, the dependence library can be automatically inquired and filled in, developers only need to concentrate on writing codes, and configuration problems do not need to be concerned.
5. The pod has a use _ frames! And use _ modulated _ headers! The two citation modes, generally the sdk library only supports one citation mode, and simultaneously supports the code needing to be changed.
In view of the foregoing technical problems and the objects to be achieved by the present application, the present application provides a code issuing method, where a code issuing instruction is obtained, where the code issuing instruction includes: the source code file to be issued and the issue type, wherein the issue type includes any one of the following types: and issuing the source code file to an open source library and issuing the source code file to a closed source library, processing the source code file based on the issuing type to generate an SDK integrated file, and then issuing the SDK integrated file to a target code library corresponding to the issuing type.
Specifically, the technical scheme of the application is realized under a mac environment, based on the coco, some configuration information is added and added, so that sdk management is more convenient, and the method is different from a traditional code management scheme, a user does not need to add a runtime library and fill in configuration, codes are integrated by one key, a packaging closed source library is built, all sdk exist in a framework form, and the created package can be used for application of iOS and flute.
According to the technical scheme, codes are decoupled, a basic code library, a ui layer library and the like are separated according to functions, the base code library and the ui layer library can be used for realizing other libraries depending on the own library, each library code library is created in the form of sdk, output is convenient, based on cocopod and git management, each sdk is divided into two libraries again, one is an open source library, the open source library is used for development and use of internal personnel, the other is a closed source library, the closed source library is provided for external use, the codes of the base library can be protected, the closed source library can be generated in one key, and the problem of complexity in the prior art is solved. Moreover, the technical scheme comprises version management, and updating and rollback are convenient during use.
Fig. 1 is a schematic view of an application scenario to which the code publishing method provided by the embodiment of the present invention is applied. Referring to fig. 1, the application scenario diagram may include: a plurality of terminal devices (illustratively, terminal device 111 and terminal device 112) used by the developer, and an electronic device 12 connected to each terminal device.
In practical application, a developer can develop codes on a terminal device to generate a source code file. Specifically, a developer writes codes in a terminal device, or may obtain part of codes in a closed source library or an open source library from other devices, for example, an electronic device, and modify the codes to generate a source code file.
It can be understood that the embodiment of the present application does not limit the generation manner or the generation process of the source code file.
Optionally, in an embodiment of the present application, the electronic device may execute the technical solution of the present application, that is, the electronic device is in a Mac environment and is installed with a cocoa tool, and the cocoa tool may be used to manage codes on the electronic device.
Optionally, in an embodiment of the present application, the application scenario diagram may further include a terminal device used by a user, which illustratively includes: terminal device 113 and terminal device 114. The terminal device 113 and the terminal device 114 may obtain the issued code information from the open source library or the closed source library of the electronic device 12 so as to implement some service functions.
It is to be understood that the scene diagram shown in fig. 1 is only an exemplary illustration. In practical application, the scene schematic diagram may further include other devices, for example, a storage device, and the like, which may be specifically adjusted according to actual requirements, and the embodiment of the present application is not limited thereto.
In the scene diagram shown in fig. 1, the embodiment of the present application is not limited to the specific representation form of each device, for example, the electronic device 21 may be a computer device or a server, and the terminal device may be a mobile phone, a tablet computer, a PC terminal, and the like, which are not illustrated here.
It can be understood that, in practical applications, the terminal device may also execute the technical solution of the present application and achieve the purpose of code distribution, and the embodiment of the present application is not limited thereto.
The following describes the technical solution of the present invention in detail by using a specific embodiment with reference to the scene diagram shown in fig. 1. It should be noted that the following specific embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments.
Fig. 2 is a flowchart illustrating a first embodiment of a code issuing method provided by the present application. As shown in fig. 2, the code issuing method may include the steps of:
s201, obtaining a code release instruction, wherein the code release instruction comprises: the method comprises the steps of a source code file to be issued and an issuing type, wherein the issuing type is used for indicating to issue to an open source library or to issue to a closed source library.
In the embodiment of the application, when a research and development staff develops a new code based on a function to be realized and needs to issue the new code, the research and development staff may issue a code issuing instruction, so that the electronic device obtains an instructed source code file to be issued and a target source library to be issued.
Optionally, the target source library may be an open source library or a closed source library. Namely, the source code file developed by the research and development personnel can be published to the closed source library for use by the internal personnel, and can also be published to the open source library for use by other third parties. It can be appreciated that the source code files typically need to be published to the open-source library first, and then the source code files in the open-source library are instructed to be published to the closed-source library. The embodiment of the present application does not limit the release type of the source code file, and details are not described here.
Optionally, in an embodiment of the present application, the code release is implemented on the premise that the source code file is in a set basic environment. Thus, before the electronic device issues the code for the first time, a base environment needs to be built first.
Exemplarily, fig. 3 is a schematic view of a building flow of a basic environment to which the code publishing method provided by the present application is applicable. As shown in fig. 3, when building a foundation environment, a cocoa tool is installed first, and then a git library is built, specifically, on one hand, a group (group) of an open source library and a repo of the open source library are built on the git library, and on the other hand, a group (group) of a closed source library and a repo of the closed source library are built on the git library.
Specifically, the cocoa tool can be downloaded and installed according to instructions in the official website.
And (3) establishing a git library: since the code management is based on git, the group of the open source library is added to git to store the open source code, the group of the closed source library is added to git to store the closed source code, then the repo of the open source library is established to manage the version release of the open source code, and the repo of the closed source library is established to manage the version release of the closed source code. Wherein, the repo is a loop in the management of the cocoapod and is used for recording the version.
Furthermore, when the basic environment is built, a user-defined template, namely a configuration template used when the cocoa builds engineering, can be built. Optionally, in the custom template, sdk supported system versions can be specified, a demonstration version (demo) project can be automatically established when the specification is established, and an object-c language is used as a default language.
S202, processing the source code file based on the release type to generate an SDK integrated file.
Optionally, in an embodiment of the present application, the issue type may be used to instruct to issue to an open-source library, and may also be used to instruct to issue to a closed-source library. When the meaning of the publication type indication is different, the above S202 may be implemented in different ways.
As an example, when the publishing type is used to indicate publishing to the open source library, the above S202 may be implemented by:
and A1, generating the SDK project based on the release type and the preset project creation template. Wherein the SDK project has SDK project file directories, the SDK project file directory including: a presentation project folder, sdk code folder, sdk resource folder.
And A2, acquiring a system dependency library and a compiling command of the source code file based on the source code file.
A3, editing SDK codes in the SDK project according to the system dependency library and the compiling command to generate an SDK integration file.
Fig. 4 is a schematic flowchart illustrating a process of publishing to an open source library in the code publishing method provided by the present application. As shown in fig. 4, for the establishment and release of the open source library, firstly, a project is created SDK, the SDK code is edited, then a demo (demo) test is written, then the SDK integrated file is edited through the dependent library and the command scan, and finally the SDK integrated file is checked and released to the established open source library repo.
Specifically, create sdk project: the project is created sdk by using sdk creator one key, and the git address in the project is automatically modified sdk by adopting the self-defined template to be the specified address, wherein the address is the group name + the project name in git. In practical applications, the SDK creator automatically creates git projects and initializes SDK documents by simply entering the project name into the SDK creator, and the integration method in the SDK document is automatically written, but the method of use needs to be filled out later.
The custom template specifies sdk the system version supported by the project, the demo name, the naming header of the test libraries and the source files, e.g., all source files are JCxxx, beginning with JC.
Optionally, the created sdk project file directory includes: demo project folder, sdk code folder, sdk resource folder,. spec integrated configuration file,. git file,. gitmore file,. travis.yml file, etc.
Optionally, after the SDK project is successfully created, two folders are automatically generated, one for storing SDK code files and one for storing SDK resource files. Furthermore, after the SDK project is created, the demo project has automatically created and associated SDK code and resources, and then SDK code can be written along with the demo test.
Illustratively, fig. 5 is a schematic diagram of an SDK engineering catalog established in the open source library publishing process. As shown in fig. 5, in the SDK project directory, an instance (example) is used to store a demo program, a JC framework (jcfounation) is used to store source code and resource files, the JC framework (jcfounation) is the name of this SDK project, and a JC framework version file (jcfounation. podspec) is used to store SDK configuration files; the software LICENSE (LICENSE) represents proof of allowing software access and the read file mark (READEMD) is an introductory document for the project.
Optionally, in the process of issuing the open source library, the electronic device has an SDK dependency file automatic importer (function), that is, some system dependency libraries and some compiling commands in the source code codes obtained by the SDK project may be automatically scanned, and the system dependency libraries and some compiling commands are automatically filled in the integration description file after the system dependency libraries and the compiling commands are obtained, so as to generate the SDK integration file.
The compiling command comprises some compiling frameworks and special compiling instructions which need to be removed, and the compiling instructions can be automatically filled in when c + + codes, extension classes and the like are found through scanning. It will be appreciated that the sdk-dependent file auto-importer was developed based on the python language by scanning project configuration files, matching and filling in corresponding system library names.
As another example, the issue type is used to indicate that the source code file is issued to a closed source library, and accordingly, the source code file is open source library code. Accordingly, the above S202 can be implemented by the following steps:
and B1, generating the SDK project based on the release type and the preset project creation template.
Wherein the SDK project has SDK project file directories, SDK project file directories including: a presentation project folder, sdk code folder, sdk resource folder.
B2, packaging the open source library codes into a closed source framework;
b3, acquiring a demonstration version project file corresponding to the open source library code from the open source library;
and B4, generating an SDK integration file according to the dependency library configuration of the open source library code, the closed source framework and the demonstration version engineering file.
Fig. 6 is a schematic flowchart illustrating a process of publishing to a closed-source library in the code publishing method provided by the present application. As shown in fig. 6, for the establishment and release of the closed source library, firstly, SDK engineering is created, the open source library code is packaged, the demonstration version (demo) is copied, and then the integration file editor generates an editing SDK integration file, and finally, the integration file is checked and released to the established closed source library repo.
Specifically, in the embodiment of the present application, sdk engineering is created: the project is created sdk by using sdk creator one key, and the git address in the project is automatically modified sdk by adopting the self-defined template to be the specified address, wherein the address is the group name + the project name in git. In practical applications, the SDK creator automatically creates git projects and initializes SDK documents by simply entering the project name into the SDK creator, and the integration method in the SDK document is automatically written, but the method of use needs to be filled out later.
The custom template specifies sdk the system version supported by the project, the demo name, the naming header of the test libraries and the source files, e.g., all source files are JCxxx, beginning with JC.
Optionally, the created sdk project file directory includes: demo project folder, sdk code folder, sdk resource folder,. spec integrated configuration file,. git file,. gitmore file,. travis.yml file, etc.
Optionally, after the SDK project is successfully created, two folders are automatically generated, one for storing SDK code files and one for storing SDK resource files.
A code packer: and automatically packaging the codes of the open source library into a closed source framework (frame), only exposing the header file, not exposing the specific implementation of the codes, and conveniently providing the codes for external use. When the source library code is packaged, the simulator structure of the arm64 is automatically removed, and the error report of packaging and subsequent integration is reduced. And (4) providing a rule optional parameter which can be selected according to different scenes, wherein the data source of the packager is a private git source and a github source (code for referring to a third party). The packaging device automatically excludes the third-party library files, a subsequent dependence mode is adopted, the third-party library is convenient to upgrade, and conflicts with the local library are reduced.
And the intelligent demo synchronizer is used for synchronizing demo implementation in the open source library.
An integrated file editor: firstly, the configuration of a dependency base in an open source file is synchronized, the address and the type of a resource file are automatically edited according to the analysis of a closed source frame, and a pair of user _ frames! And use _ modulated _ headers! The integration support of the SDK integration file is added to the support of the flutter, so that the SDK integration file is generated.
And S203, issuing the SDK integrated file to a target code library corresponding to the issuing type.
Optionally, in the embodiment of the present application, for the source code file to be published, after the SDK integrated file is generated, the source code file may be published according to a publishing type. Illustratively, when the release type is used for indicating to release to the open source library, the SDK integrated file is released to the established open source library repo; and when the release type is used for indicating to release to the closed-source library, the SDK integrated file is released to the established closed-source library repo.
According to the code release method provided by the embodiment of the application, by obtaining the code release instruction, the code release instruction comprises the following steps: the method comprises the steps of obtaining source code files to be issued and issuing types, wherein the issuing types are used for indicating to issue to an open source library or a closed source library, processing the source code files based on the issuing types, generating SDK integrated files, and issuing the SDK integrated files to a target code library corresponding to the issuing types. According to the technical scheme, a user does not need to add an operation library and fill in configuration, codes are integrated by one key, a source closing library is built once, all sdk exist in a frame form, a source code file can be accurately issued to an open source library or a closed source library, and processing efficiency and issuing success rate are improved.
On the basis of the above embodiment, after the SDK integrated file is generated, in order to avoid the problem of being unusable after being issued, the SDK integrated file may be checked before being issued. See in particular the embodiment shown in figure 7 described below.
Fig. 7 is a flowchart illustrating a second embodiment of a code issuing method provided by the present application. As shown in fig. 7, before S203, the method may further include the following steps:
s701, checking the code integrity of the SDK integrated file;
s702, when the code of the SDK integrated file is incomplete, outputting an error prompt, wherein the error prompt comprises the following steps: error location and/or error type;
and S703, when the code of the SDK integrated file is complete, storing the code of the SDK integrated file into a git library, and adding a label to the SDK integrated file according to a preset engineering configuration file.
Specifically, whether the code of the SDK integrated file can be run is checked, and when the code can be run, the code of the SDK integrated file is firstly issued to the git library, and a tag is automatically added to the SDK integrated file according to a preset engineering configuration file, and then the following step S704 is executed.
And S704, issuing the SDK integrated file added with the label to a corresponding repo.
For example, a source file that is distributed to an open source repository is distributed to a repo of the open source repository, and a source file that is distributed to a closed source repository is distributed to a repo of the closed source repository.
Accordingly, in an embodiment of the present application, after the above S704, the method may further include the following steps:
when the SDK integrated file is successfully issued, ending;
s705, when the release of the SDK integrated file fails, the cache information corresponding to the SDK integrated file is cleared.
In the embodiment of the application, after the electronic device issues the SDK integrated file, whether the SDK integrated file is successfully issued can be detected, and if the SDK integrated file is successfully issued, the electronic device is ended; if the failure occurs, on one hand, an error prompt can be sent out, namely an error is reported, and an error is prompted to be issued; and on the other hand, the label of the SDK integrated file added with the label is removed, and the SDK integrated file is returned to the last available version, namely the cache information corresponding to the SDK integrated file is removed, so that the SDK integrated file can be released again after being modified.
In the code issuing method provided by the embodiment of the present application, before issuing the generated SDK integrated file to the target code library corresponding to the issue type, the code integrity of the SDK integrated file is checked first, and when the code of the SDK integrated file is incomplete, an error prompt is output, where the error prompt includes: and when the code of the SDK integrated file is complete, storing the code of the SDK integrated file into a git library, adding a label to the SDK integrated file according to a preset engineering configuration file, and after the generated SDK integrated file is issued into a target code library corresponding to the issue type, if the SDK integrated file fails to be issued, clearing the cache information corresponding to the SDK integrated file. According to the technical scheme, the code integrity of the SDK integrated file can be automatically detected, whether rollback is needed or not is determined based on whether the SDK integrated file is successfully issued, and the updating and rollback convenience during use is improved.
Further, in an embodiment of the present application, before the above S202, the code issuing method may further include the following steps:
decoupling the source code file to obtain at least two types of source codes;
respectively storing at least two types of source codes into at least two git libraries;
a library reference relationship between at least two git libraries is determined.
Illustratively, after the electronic device acquires the source code file, the decoupling processing is firstly carried out on the source code file, the basic public code, the UI layer code and the like are separated and independent into libraries, the independent functions are independent into libraries, the libraries are mutually quoted, and the codes are independent, so that the electronic device can be used independently and can also be matched to form more complete functions. Facilitating on-demand output sdk of the integrated file.
Optionally, in another possible design of the embodiment of the present application, before the step S201 (obtaining the code release instruction), the code release method may further include the following steps:
capturing code usage events for a plurality of code resources;
determining a resource path of each code resource based on the code use event and the library type corresponding to each code resource;
and acquiring the source code file generated based on a plurality of code resources, wherein the source code file carries the resource path of each code resource.
Specifically, in the embodiment of the application, because file reference paths of the open source library and the closed source library are different, so that codes referenced by the open source library and the closed source library to files are also different.
Optionally, the file resource reference handler is used in identifying the source of the code resource during the development process sdk. According to the technical scheme, the file resource reference processor is provided, the open source library and the closed source library can be generated only by one set of codes, and maintenance cost is reduced.
Further, in the embodiment of the present application, when the issued source code file is subsequently used, a Mac environment needs to be relied on, that is, only the cocoapod needs to be installed and the code authority of the corresponding closed-source library or open-source library needs to be obtained, the repo of the corresponding closed-source library or open-source library is used as a resource (source) of the cocoapod, then the code library and the version which need to be used are written, and finally the function corresponding to the source code file can be installed by one key by using the installation command provided by the cocoapod.
The following are embodiments of the apparatus of the present application that may be used to perform embodiments of the method of the present application. For details which are not disclosed in the embodiments of the apparatus of the present application, reference is made to the embodiments of the method of the present application.
Fig. 8 is a schematic structural diagram of a first code issuing apparatus according to an embodiment of the present application. As shown in fig. 8, the code issuing apparatus may include:
an obtaining module 801, configured to obtain a code release instruction, where the code release instruction includes: the method comprises the steps that a source code file to be issued and an issuing type are used for indicating to issue to an open source library or to issue to a closed source library;
a processing module 802, configured to process the source code file based on the release type, and generate an SDK integration file of a software development kit;
the issuing module 803 is configured to issue the SDK integrated file to a target code library corresponding to the issue type.
In one possible design of the embodiment of the present application, the publishing type is used to indicate publishing to an open source library;
correspondingly, the processing module 802 is specifically configured to:
generating an SDK project based on the release type and a preset project creation template, wherein the SDK project is provided with SDK project file directories, and the SDK project file directories comprise: a presentation project folder, sdk code folder, sdk resource folder;
based on the source code file, acquiring a system dependency library and a compiling command of the source code file;
and editing SDK codes in the SDK engineering according to the system dependency library and the compiling command to generate the SDK integration file.
In another possible design of the embodiment of the present application, the release type is used to indicate that the source code is released to a closed source library, and the source code file is an open source library code;
correspondingly, the processing module 802 is specifically configured to:
generating an SDK project based on the release type and a preset project creation template, wherein the SDK project is provided with SDK project file directories, and the SDK project file directories comprise: a presentation project folder, sdk code folder, sdk resource folder;
packaging the open source library code into a closed source framework;
acquiring a demonstration version project file corresponding to the open source library code from an open source library;
and generating the SDK integration file according to the dependency library configuration of the open source library code, the closed source frame and the demonstration version engineering file.
Optionally, the processing module 802 is further configured to:
checking the code integrity of the SDK integration file;
when the code of the SDK integration file is incomplete, outputting an error prompt, wherein the error prompt comprises: error location and/or error type;
when the code of the SDK integrated file is complete, storing the code of the SDK integrated file into a git library;
and adding a label to the SDK integration file according to a preset engineering configuration file.
Optionally, the processing module 802 is further configured to clear cache information corresponding to the SDK integrated file when the release of the SDK integrated file fails.
In yet another possible design of the embodiment of the present application, the processing module 802 is further configured to:
decoupling the source code file to obtain at least two types of source codes;
storing the at least two types of source code into at least two git libraries, respectively;
determining a library reference relationship between the at least two git libraries.
In yet another possible design of the embodiment of the present application, the processing module 802 is further configured to capture a code usage event of a plurality of code resources, and determine a resource path of each code resource based on the code usage event and a library type corresponding to each code resource;
the obtaining module 801 is further configured to obtain the source code file generated based on the multiple code resources, where the source code file carries a resource path of each code resource.
The apparatus provided in the embodiment of the present application may be configured to implement the technical solution of the method embodiment, and the implementation principle and the technical effect are similar, which are not described herein again.
It should be noted that the division of the modules of the above apparatus is only a logical division, and the actual implementation may be wholly or partially integrated into one physical entity, or may be physically separated. And these modules can be realized in the form of software called by processing element; or may be implemented entirely in hardware; and part of the modules can be realized in the form of calling software by the processing element, and part of the modules can be realized in the form of hardware. For example, the processing module may be a separate processing element, or may be integrated into a chip of the apparatus, or may be stored in a memory of the apparatus in the form of program code, and a processing element of the apparatus calls and executes the functions of the above determination module. Other modules are implemented similarly. In addition, all or part of the modules can be integrated together or can be independently realized. The processing element described herein may be an integrated circuit having signal processing capabilities. In implementation, each step of the above method or each module above may be implemented by an integrated logic circuit of hardware in a processor element or an instruction in the form of software.
For example, the above modules may be one or more integrated circuits configured to implement the above methods, such as: one or more Application Specific Integrated Circuits (ASICs), or one or more microprocessors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs), among others. For another example, when some of the above modules are implemented in the form of a processing element scheduler code, the processing element may be a general-purpose processor, such as a Central Processing Unit (CPU) or other processor that can call program code. As another example, these modules may be integrated together, implemented in the form of a system-on-a-chip (SOC).
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
Fig. 9 is a schematic structural diagram of an embodiment of an electronic device provided in the present application. As shown in fig. 9, the electronic device may include: a processor 901, memory 902, a communication interface 903, and a system bus 904. The memory 902 and the communication interface 903 are connected to the processor 901 through the system bus 904 to complete communication between the two devices, the memory 902 is used for storing computer program instructions, the communication interface 903 is used for communicating with other devices, and the processor 901 implements the technical solution of the above method embodiment when executing the computer program instructions.
The system bus mentioned in fig. 9 may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The system bus may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown, but this does not mean that there is only one bus or one type of bus. The communication interface is used for realizing communication between the database access device and other equipment (such as a client, a read-write library and a read-only library). The memory may comprise Random Access Memory (RAM) and may also include non-volatile memory (non-volatile memory), such as at least one disk memory.
The processor may be a general-purpose processor, including a central processing unit CPU, a Network Processor (NP), and the like; but also a digital signal processor DSP, an application specific integrated circuit ASIC, a field programmable gate array FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components.
Optionally, an embodiment of the present application further provides a computer-readable storage medium, where computer instructions are stored in the computer-readable storage medium, and when the computer-readable storage medium runs on a computer, the computer is enabled to execute the technical solution of the above method embodiment.
Optionally, an embodiment of the present application further provides a chip for executing the instruction, where the chip is used to execute the technical solution of the method embodiment.
The embodiment of the present application further provides a computer program product, which includes a computer program, where the computer program is stored in a computer-readable storage medium, and at least one processor can read the computer program from the computer-readable storage medium, and when the at least one processor executes the computer program, the at least one processor can implement the technical solutions of the above method embodiments.
In the present application, "at least one" means one or more, "a plurality" means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone, wherein A and B can be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship; in the formula, the character "/" indicates that the preceding and following related objects are in a relationship of "division". "at least one of the following" or similar expressions refer to any combination of these items, including any combination of the singular or plural items.
It is to be understood that the various numerical references referred to in the embodiments of the present application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of the present application. In the embodiment of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiment of the present application.
Finally, it should be noted that: the above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present application.
Claims (17)
1. A method for code distribution, comprising:
acquiring a code release instruction, wherein the code release instruction comprises: the method comprises the steps that a source code file to be issued and an issuing type are used for indicating to issue to an open source library or to issue to a closed source library;
processing the source code file based on the release type to generate a Software Development Kit (SDK) integrated file;
and issuing the SDK integrated file to a target code library corresponding to the issuing type.
2. The method of claim 1, wherein the publication type is used to indicate publication to an open source repository;
correspondingly, the processing the source code file based on the release type to generate a software development kit SDK integrated file includes:
generating an SDK project based on the release type and a preset project creation template, wherein the SDK project is provided with SDK project file directories, and the SDK project file directories comprise: a presentation project folder, sdk code folder, sdk resource folder;
based on the source code file, acquiring a system dependency library and a compiling command of the source code file;
and editing SDK codes in the SDK engineering according to the system dependency library and the compiling command to generate the SDK integration file.
3. The method of claim 1, wherein the release type is used to indicate release to a closed source library, and the source code file is open source library code;
correspondingly, the processing the source code file based on the release type to generate a software development kit SDK integrated file includes:
generating an SDK project based on the release type and a preset project creation template, wherein the SDK project is provided with SDK project file directories, and the SDK project file directories comprise: a presentation project folder, sdk code folder, sdk resource folder;
packaging the open source library code into a closed source framework;
acquiring a demonstration version project file corresponding to the open source library code from an open source library;
and generating the SDK integration file according to the dependency library configuration of the open source library code, the closed source frame and the demonstration version engineering file.
4. The method according to claim 2 or 3, wherein before the publishing the SDK integration file into the target code library corresponding to the publishing type, the method further comprises:
checking the code integrity of the SDK integration file;
when the code of the SDK integration file is incomplete, outputting an error prompt, wherein the error prompt comprises: error location and/or error type;
when the code of the SDK integrated file is complete, storing the code of the SDK integrated file into a git library;
and adding a label to the SDK integration file according to a preset engineering configuration file.
5. A method according to claim 2 or 3, characterized in that the method further comprises:
and when the release of the SDK integrated file fails, removing cache information corresponding to the SDK integrated file.
6. The method according to any one of claims 1 to 3, wherein before the processing the source code file based on the release type to generate a Software Development Kit (SDK) integration file, the method further comprises:
decoupling the source code file to obtain at least two types of source codes;
storing the at least two types of source code into at least two git libraries, respectively;
determining a library reference relationship between the at least two git libraries.
7. The method of any of claims 1 to 3, wherein prior to said obtaining a code release indication, the method further comprises:
capturing code usage events for a plurality of code resources;
determining a resource path of each code resource based on the code use event and the library type corresponding to each code resource;
and acquiring the source code file generated based on the plurality of code resources, wherein the source code file carries the resource path of each code resource.
8. A code distribution apparatus, comprising:
an obtaining module, configured to obtain a code release instruction, where the code release instruction includes: the method comprises the steps that a source code file to be issued and an issuing type are used for indicating to issue to an open source library or to issue to a closed source library;
the processing module is used for processing the source code file based on the release type to generate a Software Development Kit (SDK) integrated file;
and the issuing module is used for issuing the SDK integrated file to a target code base corresponding to the issuing type.
9. The apparatus of claim 8, wherein the publication type is used to indicate publication to an open source library;
correspondingly, the processing module is specifically configured to:
generating an SDK project based on the release type and a preset project creation template, wherein the SDK project is provided with SDK project file directories, and the SDK project file directories comprise: a presentation project folder, sdk code folder, sdk resource folder;
based on the source code file, acquiring a system dependency library and a compiling command of the source code file;
and editing SDK codes in the SDK engineering according to the system dependency library and the compiling command to generate the SDK integration file.
10. The apparatus of claim 8, wherein the release type is used to indicate release to a closed source library, and the source code file is open source library code;
correspondingly, the processing module is specifically configured to:
generating an SDK project based on the release type and a preset project creation template, wherein the SDK project is provided with SDK project file directories, and the SDK project file directories comprise: a presentation project folder, sdk code folder, sdk resource folder;
packaging the open source library code into a closed source framework;
acquiring a demonstration version project file corresponding to the open source library code from an open source library;
and generating the SDK integration file according to the dependency library configuration of the open source library code, the closed source frame and the demonstration version engineering file.
11. The apparatus of claim 9 or 10, wherein the processing module is further configured to:
checking the code integrity of the SDK integration file;
when the code of the SDK integration file is incomplete, outputting an error prompt, wherein the error prompt comprises: error location and/or error type;
when the code of the SDK integrated file is complete, storing the code of the SDK integrated file into a git library;
and adding a label to the SDK integration file according to a preset engineering configuration file.
12. The apparatus according to claim 9 or 10, wherein the processing module is further configured to clear the cache information corresponding to the SDK integrated file when the SDK integrated file fails to be issued.
13. The apparatus of any one of claims 8 to 10, wherein the processing module is further configured to:
decoupling the source code file to obtain at least two types of source codes;
storing the at least two types of source code into at least two git libraries, respectively;
determining a library reference relationship between the at least two git libraries.
14. The apparatus according to any one of claims 8 to 10, wherein the processing module is further configured to capture code usage events of a plurality of code resources, and determine a resource path of each code resource based on the code usage events and a library type corresponding to each code resource;
the obtaining module is further configured to obtain the source code file generated based on the plurality of code resources, where the source code file carries a resource path of each code resource.
15. An electronic device, comprising: a processor, a memory, and computer program instructions stored on the memory and executable on the processor, the processor when executing the computer program instructions implementing the method of any of claims 1 to 7.
16. A computer-readable storage medium having stored thereon computer instructions for implementing the method of any one of claims 1 to 7 when executed by a processor.
17. A computer program product, characterized in that it comprises a computer program which, when being executed by a processor, carries out the method of any one of the preceding claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111463271.7A CN114115982A (en) | 2021-12-02 | 2021-12-02 | Code issuing method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111463271.7A CN114115982A (en) | 2021-12-02 | 2021-12-02 | Code issuing method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114115982A true CN114115982A (en) | 2022-03-01 |
Family
ID=80366615
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111463271.7A Pending CN114115982A (en) | 2021-12-02 | 2021-12-02 | Code issuing method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114115982A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117033287A (en) * | 2023-10-08 | 2023-11-10 | 易方信息科技股份有限公司 | Multi-bus communication method, system, equipment and storage medium based on SDK (software development kit) package |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108037927A (en) * | 2017-12-29 | 2018-05-15 | 有米科技股份有限公司 | Kit packaging method, system, readable storage medium storing program for executing and computer equipment |
| CN110058860A (en) * | 2019-03-16 | 2019-07-26 | 平安城市建设科技(深圳)有限公司 | A kind of automatic delivery method of code, device, equipment and computer storage medium |
| CN112052037A (en) * | 2020-09-07 | 2020-12-08 | 北京达佳互联信息技术有限公司 | Application software development method, device, equipment and medium |
| US20210014062A1 (en) * | 2019-07-10 | 2021-01-14 | Mastercard International Incorporated | Systems and Methods for Managing User Identities in Networks |
| CN112380145A (en) * | 2021-01-15 | 2021-02-19 | 树根互联技术有限公司 | SDK generation method, device, equipment and readable storage medium |
| CN113296796A (en) * | 2020-02-24 | 2021-08-24 | 京东安联财产保险有限公司 | Project release method, device, system, storage medium and electronic equipment |
| CN113360156A (en) * | 2020-03-04 | 2021-09-07 | 武汉斗鱼鱼乐网络科技有限公司 | IOS compiling method and related equipment |
-
2021
- 2021-12-02 CN CN202111463271.7A patent/CN114115982A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108037927A (en) * | 2017-12-29 | 2018-05-15 | 有米科技股份有限公司 | Kit packaging method, system, readable storage medium storing program for executing and computer equipment |
| CN110058860A (en) * | 2019-03-16 | 2019-07-26 | 平安城市建设科技(深圳)有限公司 | A kind of automatic delivery method of code, device, equipment and computer storage medium |
| US20210014062A1 (en) * | 2019-07-10 | 2021-01-14 | Mastercard International Incorporated | Systems and Methods for Managing User Identities in Networks |
| CN113296796A (en) * | 2020-02-24 | 2021-08-24 | 京东安联财产保险有限公司 | Project release method, device, system, storage medium and electronic equipment |
| CN113360156A (en) * | 2020-03-04 | 2021-09-07 | 武汉斗鱼鱼乐网络科技有限公司 | IOS compiling method and related equipment |
| CN112052037A (en) * | 2020-09-07 | 2020-12-08 | 北京达佳互联信息技术有限公司 | Application software development method, device, equipment and medium |
| CN112380145A (en) * | 2021-01-15 | 2021-02-19 | 树根互联技术有限公司 | SDK generation method, device, equipment and readable storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 郭红;余涛;顾行发;李家国;张树凡;高玉川;: "基于ArcEngine的海洋溢油监测管理信息系统研究", 计算机工程与设计, no. 03, 16 March 2011 (2011-03-16) * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117033287A (en) * | 2023-10-08 | 2023-11-10 | 易方信息科技股份有限公司 | Multi-bus communication method, system, equipment and storage medium based on SDK (software development kit) package |
| CN117033287B (en) * | 2023-10-08 | 2024-02-13 | 易方信息科技股份有限公司 | Multi-bus communication method, system, equipment and storage medium based on SDK (software development kit) package |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108964968B (en) | Service access management method and system in container cloud environment | |
| CN106559438B (en) | Program uploading method and device based on target network platform | |
| US7877732B2 (en) | Efficient stress testing of a service oriented architecture based application | |
| US11481200B1 (en) | Checking source code validity at time of code update | |
| US8843904B2 (en) | Automated building and retargeting of architecture-dependent assets | |
| US10585655B2 (en) | Systems and methods for automated retrofitting of customized code objects | |
| CN106775744B (en) | Method and device for generating static library | |
| US10666744B2 (en) | Managing discovery and selection of service interface specifications | |
| US20170054790A1 (en) | System and Method for Object Compression and State Synchronization | |
| CN106990960A (en) | Code dispositions method and device | |
| CN111259406A (en) | Automatic construction method and system for cloud native application vulnerability reproduction environment | |
| US11328021B2 (en) | Automatic resource management for build systems | |
| CN113778445A (en) | Cross-platform component generation method and device, electronic equipment and storage medium | |
| US10459698B2 (en) | Framework for generating adapters in an integrated development environment | |
| US11099837B2 (en) | Providing build avoidance without requiring local source code | |
| CN117112060A (en) | Component library construction method and device, electronic equipment and storage medium | |
| CN115658496A (en) | Extensible Web automatic test method, system, equipment and storage medium | |
| CN114115982A (en) | Code issuing method, device, equipment and storage medium | |
| CN113778897A (en) | Automatic test method, device, equipment and storage medium of interface | |
| CN111240987B (en) | Method and device for detecting migration program, electronic equipment and computer readable storage medium | |
| US11947966B2 (en) | Identifying computer instructions enclosed by macros and conflicting macros at build time | |
| US10802810B2 (en) | Consuming persistent library bundles | |
| US10146529B2 (en) | Monitoring rules declaration and automatic configuration of the monitoring rules | |
| CN115048083A (en) | Visualization method and device for assembly, storage medium and electronic equipment | |
| CN113504904A (en) | User-defined function implementation method and device, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |