CN116302075B - Software product management method and related equipment - Google Patents
Software product management method and related equipment Download PDFInfo
- Publication number
- CN116302075B CN116302075B CN202310556429.8A CN202310556429A CN116302075B CN 116302075 B CN116302075 B CN 116302075B CN 202310556429 A CN202310556429 A CN 202310556429A CN 116302075 B CN116302075 B CN 116302075B
- Authority
- CN
- China
- Prior art keywords
- software product
- product
- target storage
- storage address
- warehouse
- 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.)
- Active
Links
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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/219—Managing data history or versioning
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Abstract
The invention discloses a software product management method and related equipment, relating to the technical field of software deployment, wherein the software product management method comprises the following steps: responding to the authentication instruction of the product warehouse, and accessing the product warehouse according to the authentication information of the product warehouse; responding to a configuration instruction of the application program, and configuring an application model and a middleware model of the application program; determining a target storage address of the software product in the product warehouse according to project information and type information of the software product in response to a storage instruction of the software product; the software product and the application model and middleware model of the application are stored to a target storage address in the product repository. The technical problem that the version of the delivered object is disordered due to the fact that the version of the service image stored in the product warehouse is more is solved.
Description
Technical Field
The application relates to the technical field of software deployment, in particular to a software product management method and related equipment.
Background
Software product management is the management of software products built during the software development process. The software product refers to a binary file generated by compiling and packaging source codes, and comprises an installation package, a test report, a configuration file and the like. Different development languages correspond to different formats of binary files, which can typically run directly on a server. The product warehouse is used for storing and distributing software products constructed after source code compiling, and different product warehouses can manage the software products of respective development language types. As the demand of the software product is continuously changed, the number of iterative release times of the software product is increased, so that more versions of service images stored in the product warehouse are caused, and the versions of delivered objects are disordered, so that the operation and maintenance difficulty is increased.
Disclosure of Invention
The invention aims to overcome the defects of the prior art, provides a software product management method and related equipment, and aims to solve the technical problem that the version of a delivered object is disordered due to the fact that the version of a service mirror image stored in a product warehouse is more.
In order to solve the technical problem, the present invention provides a software product management method, applied to an electronic device side, the software product management method comprising: responding to the authentication instruction of the product warehouse, and accessing the product warehouse according to the authentication information of the product warehouse; responding to a configuration instruction of the application program, and configuring an application model and a middleware model of the application program; determining a target storage address of the software product in the product warehouse according to project information and type information of the software product in response to a storage instruction of the software product; the software product and the application model and middleware model of the application are stored to a target storage address in the product repository.
By adopting the software product management method of the embodiment, the target storage address of the software product in the product warehouse is determined according to the project information and the type information of the software product, then the application model and the middleware model of the software product and the application program are stored in the target storage address of the product warehouse, and the software product is classified and stored, so that each version of the software product can be managed in order, and the software product of each version can be easily inquired and traced, thereby improving the management and operation and maintenance efficiency of the software product. Moreover, storing the software product and the application model and middleware model at the target storage address facilitates managing and scheduling the resources of the application program.
A second aspect of the present application provides an electronic device, where the electronic device includes a processor and a memory, and the processor executes a computer program or code stored in the memory to implement a software product management method according to an embodiment of the present application.
A third aspect of the present application provides a computer-readable storage medium storing a computer program or code which, when executed by a processor, implements a software product management method of an embodiment of the present application.
It is appreciated that the specific embodiments and advantages of the electronic device provided in the second aspect and the computer readable storage medium provided in the third aspect of the present application are substantially the same as those of the software product management method provided in the first aspect of the present application, and are not described herein.
Drawings
In order to more clearly illustrate the embodiments of the invention or the technical solutions in the prior art, the drawings which are required in the description of the embodiments or the prior art will be briefly described, it being obvious that the drawings in the description below are only some embodiments of the invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic structural diagram of an electronic device provided in the present application.
FIG. 2 is a flow chart of a software product management method provided by one embodiment of the present application.
Fig. 3 is a schematic illustration of an authentication interface for an article warehouse provided in accordance with an embodiment of the present application.
Fig. 4a is a schematic view of a management interface for an article warehouse provided in an embodiment of the present application.
Fig. 4b is a schematic view of a management interface for an article warehouse provided in accordance with another embodiment of the present application.
Fig. 4c is a schematic view of a management interface for an article warehouse provided in accordance with another embodiment of the present application.
Fig. 4d is a schematic view of a management interface for an article warehouse provided in accordance with another embodiment of the present application.
Fig. 5 is a flow chart of substeps of step S203 shown in fig. 2 provided in an embodiment of the present application.
Fig. 6 is a flowchart of the substeps of step S203 shown in fig. 2 provided in another embodiment of the present application.
Fig. 7 is a flowchart of the substeps of step S203 shown in fig. 2 provided in another embodiment of the present application.
Fig. 8 is a flowchart of a software product management method according to another embodiment of the present application.
FIG. 9 is a flow chart of a software product management method provided by one embodiment of the present application.
Fig. 10 is a schematic view of a software product management method according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
Some technical terms of the present application are described below.
1. Software product
The software product of an application (app) refers to a binary file generated by source code compilation packaging, and may include the following types: installation packages, image files, configuration files, database files, test reports, operating manuals, and the like.
After passing the audit, the software product of the application program can be released as a delivery object.
2. Installation bag
An installation package refers to an installation file of an application.
3. Mirror image file
The image file refers to an image file on which an application program depends when in containerized deployment. Containerized deployment refers to creating a container process on an operating system that isolates applications from surrounding computing environments so that running applications within the container process is not affected by the surrounding computing environment.
4. Configuration file
The configuration file includes the connection configuration parameters of the application and the configuration parameters of the application model and the middleware model that the application depends on at run-time. The connection configuration parameters of the application may include network connection parameters and application programming interface (Application Programming Interface, API) configuration parameters.
The application model is used for controlling the life cycle of the application program, including controlling the installation, updating, deleting and the like of the application program.
The middleware model is used for providing resources required by an application program at the running time, such as providing database services, function call services and the like.
5. Database file
The database file is used for storing data of the application program, and can comprise a database initialization file and a database change file. The database initialization file is used to store data required by the application at runtime. The database change file is used to store data that the application generates or updates at runtime.
6. Test report
The test report refers to a test document generated by the application program through performance test.
7. Operating manual
The operation manual refers to the instruction of application programs provided by the developer.
8. Product warehouse
The product repository is used to store and distribute software products built after source code compilation.
9. Mirror image warehouse
The image warehouse is used for storing image files of the software products. The image files of the specified version may be pushed to the image repository or pulled from the image repository.
As the demand of the software product is continuously changed, the number of iterative release times of the software product is increased, so that more versions of service images stored in the product warehouse are caused, and the versions of delivered objects are disordered, so that the operation and maintenance difficulty is increased.
Based on the above, the application provides a software product management method and related equipment, which determine the target storage address of the software product in the product warehouse according to the project information and the type information of the software product, store the application model and the middleware model of the software product and the application program to the target storage address in the product warehouse, and store the software product in a classified manner, so that each version of the software product can be managed in order, and each version of the software product can be easily queried and traced, thereby improving the management and operation and maintenance efficiency of the software product. Moreover, storing the software product and the application model and middleware model at the target storage address facilitates managing and scheduling the resources of the application program.
The electronic device provided in the present application is briefly described below.
Fig. 1 is a schematic structural diagram of an electronic device 100 provided in the present application.
Referring to fig. 1, an electronic device 100 may include a processor 110 and a memory 120. The processor 110 may execute a computer program or code stored in the memory 120, to implement the software product management method of the embodiment of the present application.
Processor 110 may include one or more processing units. For example, the processor 110 may include, but is not limited to, an application processor (Application Processor, AP), a modem processor, a graphics processor (Graphics Processing Unit, GPU), an image signal processor (Image Signal Processor, ISP), a controller, a video codec, a digital signal processor (Digital Signal Processor, DSP), a baseband processor, a Neural-Network Processor (NPU), and the like. Wherein the different processing units may be separate devices or may be integrated in one or more processors.
A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that the processor 110 has just used or recycled. If the processor 110 needs to reuse the instruction or data, it can be called directly from the memory.
In some embodiments, the processor 110 may include one or more interfaces. The interfaces may include, but are not limited to, integrated circuit (Inter-Integrated Circuit, I2C) interfaces, integrated circuit built-in audio (Inter-Integrated Circuit Sound, I2S) interfaces, pulse code modulation (Pulse Code Modulation, PCM) interfaces, universal asynchronous receiver Transmitter (Universal Asynchronous Receiver/Transmitter, UART) interfaces, mobile industry processor interfaces (Mobile Industry Processor Interface, MIPI), general-Purpose Input/Output (GPIO) interfaces, subscriber identity module (Subscriber Identity Module, SIM) interfaces, universal serial bus (Universal Serial Bus, USB) interfaces, and the like.
It should be understood that the interfacing relationship between the modules illustrated in the embodiments of the present application is only illustrative, and does not limit the structure of the electronic device 100. In other embodiments, the electronic device 100 may also employ different interfaces in the above embodiments, or a combination of interfaces.
Memory 120 may include an external memory interface and an internal memory. The external memory interface may be used to connect to an external memory card, such as a Micro SD card, to extend the memory capabilities of the electronic device 100. The external memory card communicates with the processor 110 through an external memory interface to implement data storage functions. The internal memory may be used to store computer-executable program code that includes instructions. The internal memory may include a stored program area and a stored data area. The storage program area may store an application program (e.g., a sound playing function, an image playing function, etc.) required for at least one function of the operating system, etc. The storage data area may store data (e.g., audio data, image data, etc.) created during use of the electronic device 100, and so forth. In addition, the internal memory may include a high-speed random access memory, and may also include a nonvolatile memory, such as at least one disk storage device, a flash memory device, or a universal flash memory (Universal Flash Storage, UFS), or the like. The processor 110 performs various functional applications of the electronic device 100 and data processing, such as implementing the software product management methods of the embodiments of the present application, by executing instructions stored in an internal memory, and/or instructions stored in a memory provided in the processor 110.
It is to be understood that the structure illustrated in the embodiments of the present application does not constitute a specific limitation on the electronic device 100. In other embodiments, electronic device 100 may include more or fewer components than shown, or certain components may be combined, or certain components may be split, or different arrangements of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.
The electronic device 100 may include, but is not limited to, at least one of a smart phone, a tablet computer, a personal computer (Personal Computer, PC), an electronic book reader, a workstation, a server, a personal digital assistant (Personal Digital Assistant, PDA), a portable multimedia player (Portable Multimedia Player, PMP), an ambulatory medical device, a camera, and a wearable device. The wearable Device includes at least one of an accessory type (e.g., a watch, a ring, a bracelet, a chain of feet, a necklace, glasses, a contact lens, or a Head Mounted Device (HMD)), a fabric or garment integrated type (e.g., electronic garment), a body Mounted type (e.g., skin pad or tattoo), and a bioimplantable type (e.g., implantable circuit).
The software product management method provided in the present application is specifically described below.
FIG. 2 is a flow chart of a software product management method provided by one embodiment of the present application.
Referring to fig. 2, a software product management method may be applied to the electronic device 100, and the software product management method may include the steps of:
s201, in response to the authentication instruction of the product warehouse, accessing the product warehouse according to the authentication information of the product warehouse.
It is understood that the product repository may store software products of at least one application. The electronic device 100 may install an application for managing the product repository, and when the application is started, the display of the electronic device 100 presents an authentication interface for the product repository.
In some embodiments, the authentication information of the artifact repository may include a registered user name and password.
For example, as shown in FIG. 3, the authentication interface of the artifact repository may include a user name input field 301, a password input field 302, and a login control 303. The user may enter a registered user name and password in the user name entry field 301 and password entry field 302, respectively, and then trigger an authentication instruction for the artifact repository by clicking or touching the login control 303. When the user name and password are verified, the electronic device 100 may obtain access rights of the product repository in response to the authentication instruction of the product repository, and the display screen of the electronic device 100 may switch from the authentication interface of the product repository to the management interface of the product repository.
S202, an application model and a middleware model of the application program are configured in response to a configuration instruction of the application program.
It is understood that the electronic device 100 may manage software products of at least one application in the product repository through an application for managing the product repository.
In this embodiment, the electronic device 100 may manage and schedule the resources of the application by configuring the application model and the middleware model of at least one application in the artifact repository.
For example, after the display screen of the electronic device 100 switches from the certification interface of the artifact repository to the management interface of the artifact repository, as shown in fig. 4a, the management interface of the artifact repository may include a selection control 401 of an application program, a selection control 402 of an application model, a selection control 403 of a middleware model, and a configuration control 404 of an application program. A user may first select an application from a plurality of applications by clicking or touching a selection control 401 of the application, then select one or more application models from the plurality of application models by clicking or touching a selection control 402 of the application model, then select one or more middleware models from the plurality of middleware models by clicking or touching a selection control 403 of the middleware model, and then trigger a configuration instruction of the application by clicking or touching a configuration control 404 of the application. The electronic device 100 may establish a data association record of an application model and a middleware model of an application program in response to a configuration instruction of the application program, so that when the application program runs, the corresponding application model and middleware model may be called according to the data association record, thereby implementing management and resource scheduling of the application program.
It is to be appreciated that the data association record can include an identification of at least one application model and an identification of at least one middleware model. The identification of the application model is used to distinguish between different application models and may include the name or identification number of the application model. The identification of the middleware model is used to distinguish between different middleware models and may include the name or identification number of the middleware model.
S203, in response to the storage instruction of the software product, determining a target storage address of the software product in the product warehouse according to the project information and the type information of the software product.
It will be appreciated that the artifact store manages the software artifact by creating items, the item information being used to determine the network address of the artifact store.
Wherein the project information of the software product may include a project identity and a project version identity. Item identification is used to distinguish between different items and may include an item name or identification number. The item version identification is used to distinguish between different versions of an item and may include an item version name or identification number.
The type information of the software product may include at least one of: installation package, image file, configuration file, database file, test report, and operation manual.
In this embodiment, the electronic device 100 may determine a target storage address of the software product in the product warehouse according to item information and type information of the software product, may store the software product in a classified manner, may manage each version of the software product in order, and may easily query and trace the software product of each version, thereby improving management and operation efficiency of the software product.
S204, storing the software product, the application model of the application program and the middleware model into a target storage address in a product warehouse.
In this embodiment, the electronic device 100 stores the software product, the application model and the middleware model of the application program in the target storage address in the product repository, and can call the application model and the middleware model required by the running of the application program when the software product is called, so that the resources of the application program can be managed and scheduled easily.
For example, referring to fig. 4b, the display of the electronic device 100 presents a management interface for the product repository, which also includes a storage control 405 for the software product. After triggering the configuration instructions of the application, the user may trigger the storage instructions of the software product by clicking or touching the storage control 405 of the software product. The electronic device 100 may first determine a target storage address for the software product in the product repository in response to the storage instructions for the software product, and then store the software product and the application model and middleware model for the application program to the target storage address in the product repository.
S205, obtaining an image file of the software product.
In some embodiments, the electronic device 100 may build an image file of the software product. For example, electronic device 100 may build an image file of a software product by executing a dock build instruction.
In other embodiments, the electronic device 100 may pull the image file of the software product from the image repository. For example, electronic device 100 may pull an image file of a software product from an image library by executing a dock pull instruction.
S206, responding to the inquiry instruction of the software product, and inquiring the target storage address of the software product in the product warehouse.
It will be appreciated that the electronic device 100, after storing the software product in a sorted manner, may verify the integrity of the software product, i.e., query the target storage address for storing the software product.
S207, confirming whether the target storage address stores the software product.
In this embodiment, the electronic device 100 may query the object storage address of the software product in the product repository to confirm whether the object storage address stores the software product. When the target memory address has stored the software product, it is stated that the software product is complete. When the target memory address does not store the software product, it is interpreted that the software product is incomplete.
If the target storage address stores the software product, step S208 is executed; if not, step S209 is performed.
S208, storing the mirror image file to the target storage address.
In this embodiment, the electronic device 100 stores an image file at a target storage address in the product repository, and may query the software product to retrieve the image file of the software product, so that the image repository may be pushed with the image file of the software product with the specified version.
S209, sending out a prompt message.
In this embodiment, when the target storage address does not store the software product, the electronic device 100 may issue a voice prompt message or present the prompt message on a display screen. Wherein the hint message is used to hint that the software product is incomplete and to confirm to the user whether to store the image file to the target storage address.
S210, confirming whether the mirror image file is stored in the target storage address.
If it is confirmed that the image file is stored in the target storage address, step S208 is executed; if not, ending.
For example, referring to fig. 4c, the display of the electronic device 100 presents a management interface for the product repository, which also includes a query control 406 for the software product. After triggering the stored instructions of the software product, the user may trigger the query instructions of the software product by clicking or touching the query control 406 of the software product. The electronic device 100 may query the object storage address of the software product in the product repository in response to the query instruction of the software product, thereby confirming whether the object storage address stores the software product. When the target storage address has stored the software product, the electronic device 100 stores the image file to the target storage address. When the target storage address does not store a software product, referring to fig. 4d, the management interface of the product repository presents a prompt window 407, the prompt window 407 comprising a prompt message 408 and a confirmation control 409. The hint message 408 may exhibit the following: the software product is incomplete and please confirm whether the image file is stored. The confirm control 409 may include a yes control and a no control, and the user may confirm whether to store the image file by clicking or touching the yes control or the no control. When the user clicks or touches the yes control, a yes instruction may be triggered and the electronic device 100 may confirm storing the image file in response to the yes instruction. When the user clicks or touches the no control, a no instruction may be triggered, and the electronic device 100 may confirm that the image file is not stored in response to the no instruction.
Fig. 5 is a flow chart of substeps of step S203 shown in fig. 2 provided in an embodiment of the present application.
Referring to fig. 5, determining a target storage address of a software product in a product warehouse according to project information and type information of the software product may include the steps of:
s501, determining a first layer path of a target storage address according to item information of a software product.
Wherein the first tier path is a network address of the product warehouse.
S502, determining a second layer path of the target storage address according to the type information of the software product.
Wherein the second layer path is a sub-path of the first layer path.
The target storage address is a folder address of a first-layer path nested second-layer path.
In this embodiment, the electronic device 100 establishes the target storage address of the software product in the product warehouse in a two-layer path structure, and can store the software products of different projects in a classified manner.
Specifically, the electronic device 100 may first create a folder of item information with a folder path of item information as a first-layer path of a target storage address in response to a storage instruction of a software product. And then creating a subfolder of the type information in the folder of the item information, and taking the subfolder path of the type information as a second-layer path of the target storage address.
Fig. 6 is a flowchart of the substeps of step S203 shown in fig. 2 provided in another embodiment of the present application.
Referring to fig. 6, determining a target storage address of a software product in an article warehouse according to item information and type information of the software product may include the steps of:
s601, determining a first layer path of a target storage address according to item identification of a software product.
Wherein the first tier path is a network address of the product warehouse.
S602, determining a second-layer path of the target storage address according to the item version identification of the software product.
Wherein the second layer path is a sub-path of the first layer path.
S603, determining a third layer path of the target storage address according to the type information of the software product.
Wherein the third layer path is a sub-path of the second layer path.
The target storage address is a folder address of a first-layer path nested second-layer path and a second-layer path nested third-layer path.
In this embodiment, the electronic device 100 establishes the target storage address of the software product in the product warehouse in a three-layer path structure, and can store the software products of different versions of the project in a classified manner.
Specifically, the electronic device 100 may first create a folder of item identifications with the folder path of the item identifications as a first-tier path of the target storage address in response to a storage instruction of the software product. And then creating a subfolder of the project version identifier in the folder of the project identifier, and taking the subfolder path of the project version identifier as a second-layer path of the target storage address. And creating a subfolder of the type information in the subfolder of the item version identification, and taking the subfolder path of the type information as a third layer path of the target storage address.
Fig. 7 is a flowchart of the substeps of step S203 shown in fig. 2 provided in another embodiment of the present application.
Referring to fig. 7, determining a target storage address of a software product in an article warehouse according to item information and type information of the software product may include the steps of:
s701, determining a first layer path of a target storage address according to item identification of a software product.
Wherein the first tier path is a network address of the product warehouse.
S702, determining a second-layer path of the target storage address according to the item version identification of the software product.
Wherein the second layer path is a sub-path of the first layer path.
S703, determining a third layer path of the target storage address according to the type information of the software product.
Wherein the third layer path is a sub-path of the second layer path.
S704, determining a fourth layer path of the target storage address according to the identification of the software product.
The fourth layer path is a sub-path of the third layer path. The identification of the software product is used to distinguish between different software products and may include the name or identification number of the software product.
The target storage address is a folder address of a first-layer path nested second-layer path, a second-layer path nested third-layer path and a third-layer path nested fourth-layer path.
In this embodiment, the electronic device 100 establishes the target storage address of the software product in the product warehouse in a four-layer path structure, and may store the software products of different versions of the project in a classified manner, and may store different software products of one type.
Specifically, the electronic device 100 may first create a folder of item identifications with the folder path of the item identifications as a first-tier path of the target storage address in response to a storage instruction of the software product. And then creating a subfolder of the project version identifier in the folder of the project identifier, and taking the subfolder path of the project version identifier as a second-layer path of the target storage address. And creating a subfolder of the type information in the subfolder of the item version identification, and taking the subfolder path of the type information as a third layer path of the target storage address. Creating a subfolder of the software product identification in the subfolder of the type information, and taking the subfolder path of the software product identification as a fourth layer path of the target storage address.
Fig. 8 is a flowchart of a software product management method according to another embodiment of the present application.
Referring to fig. 8, after step S205 shown in fig. 2, that is, after the image file of the software product is obtained, the software product management method further includes the steps of:
s801, responding to the authentication instruction of the mirror image warehouse, and accessing the mirror image warehouse according to the authentication information of the mirror image warehouse.
It is understood that the image repository may store image files corresponding to software products of at least one application.
In some embodiments, the electronic device 100 may set the management controls of the mirror warehouse in the management interface of the work in process warehouse. When the user clicks or touches the management control of the mirror image warehouse, a management instruction of the mirror image warehouse is triggered, and the display screen of the electronic device 100 is switched from the management interface of the product warehouse to the authentication interface of the mirror image warehouse.
In other embodiments, the electronic device 100 may install an application for managing the image repository, and when the application is started, the display of the electronic device 100 presents the authentication interface of the image repository.
It can be understood that the authentication manner of the mirror warehouse in step S801 is substantially the same as that of the product warehouse in step S201 shown in fig. 2, and will not be described herein.
S802, determining a target storage address of an image file of the software product in an image warehouse according to item information and type information of the software product.
It can be appreciated that the manner of determining the target storage address of the image file in the image repository in step S802 is substantially the same as the manner of determining the target storage address of the software product in the product repository in step S203 shown in fig. 2, and will not be described herein.
S803, inquiring the target storage address of the software product in the product warehouse.
S804, confirming whether the target storage address in the product warehouse stores the software product.
If the target storage address in the product repository has stored the software product, then step S805 is performed; if not, step S806 is performed.
It can be understood that steps S803 to S804 query the target storage address of the software product in the product warehouse, so as to confirm whether the target storage address stores the software product in the same manner as steps S206 to S207 shown in fig. 2, and will not be repeated here.
S805, storing the mirror image file of the software product to a target storage address in a mirror image warehouse.
In this embodiment, the electronic device 100 stores the image file at the target storage address in the image repository, and may pull the image file of the software product from the image repository.
S806, sending out a prompt message.
It is understood that the manner of sending the prompting message in step S806 is substantially the same as that of step S209 shown in fig. 2, and will not be described herein.
S807, confirming whether the image file of the software product is stored to the target storage address in the image warehouse.
If it is confirmed that the image file is stored in the target storage address in the image repository, step S805 is executed; if not, ending.
It is understood that the manner of confirming whether to continue the storage in step S807 is substantially the same as that of step S210 shown in fig. 2, and will not be described here again.
FIG. 9 is a flow chart of a software product management method provided by one embodiment of the present application.
Referring to fig. 9, the software product management method further includes the steps of:
s901, the electronic device 100 responds to a deployment request of a software product sent by the requesting device 200, and queries a network address of the requesting device 200 based on a MAC address in the deployment request, where the deployment request includes the MAC address of the requesting device 200 and a name of the software product to be deployed.
In this embodiment, referring to fig. 10, the electronic device 100 is communicatively connected to the requesting device 200, and the requesting device 200 may send a deployment request for the software product to the electronic device 100. Wherein the deployment request for the software product is for requesting that the software product be stored to the product repository of the requesting device 200.
In some embodiments, the electronic device 100 responds to a deployment request of the software product by querying the network address of the requesting device 200 through the MAC address in the deployment request.
S902, the electronic device 100 sends, to the requesting device 200, an authentication request of the product warehouse of the requesting device 200 based on the deployment request, and the requesting device 200 sends, to the electronic device 100, authentication information of the product warehouse of the requesting device 200 based on the authentication request of the product warehouse of the requesting device 200;
in other embodiments, an authentication request is generated on the electronic device 100 and the authentication request of the product repository of the requesting device 200 is sent to the requesting device 200. Wherein the authentication request of the product repository is used to request acquisition of authentication information of the product repository of the requesting device 200. The requesting device 200, after receiving the authentication request of the product warehouse, transmits authentication information of the product warehouse to the electronic device 100. The electronic device 100 then receives authentication information for the product warehouse from the requesting device 200.
It is understood that the structure of the requesting device 200 is substantially the same as that of the electronic device 100, and will not be described herein.
S903, the electronic device 100 accesses the product repository of the requesting device 200 according to the network address of the requesting device 200 and the authentication information of the product repository of the requesting device 200.
In this embodiment, after acquiring the network address of the requesting device 200, the display screen of the electronic device 100 may switch from the management interface of the product warehouse of the electronic device 100 to the authentication interface of the product warehouse of the requesting device 200.
It can be understood that the authentication method of the product warehouse of the requesting device 200 in step S903 is substantially the same as the authentication method of the product warehouse of the electronic device 100 in step S201 shown in fig. 2, and will not be described herein.
S904, determining a target storage address of the software product in the product warehouse of the request device 200 according to the project information and the type information of the software product corresponding to the name of the software product to be deployed.
S905 stores the software product, and the application model and middleware model of the application program, to the target storage address in the product repository of the requesting device 200.
It can be understood that the storage manner of the software product in the product warehouse of the requesting device 200 in steps S904 to S905 is substantially the same as the storage manner of the software product in the product warehouse of the electronic device 100 in steps S203 to S204 shown in fig. 2, and will not be repeated here.
In the present embodiment, the requesting device 200 requests to store the software product to the product warehouse of the requesting device 200, the electronic device 100 stores the software product to the product warehouse of the requesting device 200 according to the item information and the type information of the software product, so that the target storage address of the software product in the product warehouse of the requesting device 200 is substantially the same as the target storage address in the product warehouse of the electronic device 100, when the software product of the target storage address in the product warehouse of the electronic device 100 has a problem, it can be confirmed that the same problem occurs to the software product of the target storage address in the product warehouse of the requesting device 200, and repeated investigation is not required in the product warehouse of the requesting device 200 for the problem occurring to the software product in the product warehouse of the electronic device 100, so that the operation and maintenance efficiency of the software product can be improved.
The present application also provides a computer-readable storage medium storing a computer program or code that, when executed by a processor, implements the software product management method of the embodiments of the present application.
Computer-readable storage media include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data. Computer-readable storage media includes, but is not limited to, random access Memory (Random Access Memory, RAM), read-Only Memory (ROM), electrically-charged erasable programmable Read-Only Memory (EEPROM), flash Memory or other Memory, compact disk Read-Only Memory (CD-ROM), digital versatile disks (Digital Versatile Disc, DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer.
In addition, the foregoing has outlined rather broadly the more detailed description of embodiments of the invention in order that the detailed description of the principles and embodiments of the invention may be implemented in conjunction with the present examples, the above examples being provided to facilitate the understanding of the method and core concepts of the invention; meanwhile, as those skilled in the art will have variations in the specific embodiments and application scope in accordance with the ideas of the present invention, the present description should not be construed as limiting the present invention in view of the above.
Claims (7)
1. A software product management method applied to an electronic device side, the method comprising:
responding to an authentication instruction of a product warehouse, and accessing the product warehouse according to authentication information of the product warehouse;
configuring an application model and a middleware model of an application program in response to a configuration instruction of the application program;
determining a target storage address of the software product in the product warehouse according to project information and type information of the software product in response to a storage instruction of the software product;
storing the software product and the application model and middleware model of the application program to a target storage address in the product repository;
the method further comprises the steps of:
the method comprises the steps that an electronic device responds to a deployment request of a software product sent by a request device, and inquires a network address of the request device based on a MAC address in the deployment request, wherein the deployment request comprises the MAC address of the request device and the name of the software product to be deployed;
the electronic equipment sends an authentication request of the product warehouse of the request equipment to the request equipment based on the deployment request, and the request equipment sends authentication information of the product warehouse of the request equipment to the electronic equipment based on the authentication request of the product warehouse of the request equipment;
the electronic equipment accesses the product warehouse of the request equipment according to the network address of the request equipment and the authentication information of the product warehouse of the request equipment;
determining a target storage address of the software product in a product warehouse of the request equipment according to project information and type information of the software product corresponding to the name of the software product to be deployed;
storing the software product and the application model and middleware model of the application program to a target storage address in a product repository of the requesting device;
the structure of the request device is the same as that of the electronic device; the electronic equipment stores the software product into the product warehouse of the request equipment according to item information and type information of the software product, so that the target storage address of the software product in the product warehouse of the request equipment is identical to the target storage address in the product warehouse of the electronic equipment, and when the software product with the target storage address in the product warehouse of the electronic equipment has a problem, the same problem occurs to the software product with the target storage address in the product warehouse of the request equipment, and repeated checking is not needed in the product warehouse of the request equipment for the problem of the software product in the product warehouse of the electronic equipment;
the method further comprises the steps of:
acquiring an image file of the software product;
storing the image file to a target storage address in the product warehouse;
the storing the image file to a target storage address in the artifact repository comprises:
responding to a query instruction of a software product, and querying a target storage address of the software product in the product warehouse;
confirming whether the target storage address stores the software product;
if the target storage address stores the software product, storing the image file to the target storage address;
and if the target storage address does not store the software product, a prompt message is sent out and whether the mirror file is stored in the target storage address is confirmed.
2. The software product management method of claim 1, wherein said determining a target storage address of said software product in said product repository based on project information and type information of said software product comprises:
determining a first layer path of the target storage address according to item information of the software product;
determining a second-layer path of the target storage address according to the type information of the software product, wherein the second-layer path is a sub-path of the first-layer path;
and the target storage address is a folder address of the first-layer path nested with the second-layer path.
3. The software product management method of claim 1, wherein the item information includes an item identification and an item version; the determining the target storage address of the software product in the product warehouse according to the project information and the type information of the software product comprises the following steps:
determining a first layer path of the target storage address according to the item identification of the software product;
determining a second-layer path of the target storage address according to the item version identification of the software product, wherein the second-layer path is a sub-path of the first-layer path;
determining a third layer path of the target storage address according to the type information of the software product, wherein the third layer path is a sub-path of the second layer path;
and the target storage address is a folder address of the first-layer path nested with the second-layer path and the second-layer path nested with the third-layer path.
4. The software product management method of claim 1, wherein the item information includes an item identification and an item version; the determining the target storage address of the software product in the product warehouse according to the project information and the type information of the software product comprises the following steps:
determining a first layer path of the target storage address according to the item identification of the software product;
determining a second-layer path of the target storage address according to the item version identification of the software product, wherein the second-layer path is a sub-path of the first-layer path;
determining a third layer path of the target storage address according to the type information of the software product, wherein the third layer path is a sub-path of the second layer path;
determining a fourth-layer path of the target storage address according to the identification of the software product, wherein the fourth-layer path is a sub-path of the third-layer path;
and the target storage address is a folder address of the first-layer path nested with the second-layer path, the second-layer path nested with the third-layer path and the third-layer path nested with the fourth-layer path.
5. The software product management method of claim 1, wherein after obtaining the image file of the software product, the method further comprises:
responding to an authentication instruction of the mirror image warehouse, and accessing the mirror image warehouse according to authentication information of the mirror image warehouse;
determining a target storage address of an image file of the software product in the image warehouse according to the item information and the type information of the software product;
querying a target storage address of the software product in the product repository;
confirming whether a target storage address in the product repository stores the software product;
if the target storage address in the product warehouse already stores the software product, storing an image file of the software product to the target storage address in the image warehouse;
and if the target storage address in the product warehouse does not store the software product, a prompt message is sent out and whether the mirror image file of the software product is stored in the target storage address in the mirror image warehouse is confirmed.
6. An electronic device comprising a processor and a memory, wherein the processor runs a computer program or code stored in the memory, implementing the software product management method according to any one of claims 1 to 5.
7. A computer readable storage medium storing a computer program or code which, when executed by a processor, implements the software product management method of any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310556429.8A CN116302075B (en) | 2023-05-17 | 2023-05-17 | Software product management method and related equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310556429.8A CN116302075B (en) | 2023-05-17 | 2023-05-17 | Software product management method and related equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116302075A CN116302075A (en) | 2023-06-23 |
| CN116302075B true CN116302075B (en) | 2023-08-04 |
Family
ID=86781863
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310556429.8A Active CN116302075B (en) | 2023-05-17 | 2023-05-17 | Software product management method and related equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116302075B (en) |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115617788A (en) * | 2022-12-20 | 2023-01-17 | 广州嘉为科技有限公司 | Product cleaning method and device and computer readable storage medium |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20010052110A1 (en) * | 2000-02-14 | 2001-12-13 | Julian Orbanes | System and method for graphically programming operators |
| CN105653901A (en) * | 2015-12-29 | 2016-06-08 | 深圳市科漫达智能管理科技有限公司 | Component repository management method and system |
| CN111629058A (en) * | 2020-05-27 | 2020-09-04 | 广东浪潮大数据研究有限公司 | Mirror image uploading method, device and system and back-end equipment |
| CN113961311A (en) * | 2021-10-27 | 2022-01-21 | 阿波罗智联(北京)科技有限公司 | Service data processing method, device, electronic equipment and medium |
| CN115098437A (en) * | 2022-05-31 | 2022-09-23 | 中科曙光国际信息产业有限公司 | Mirror image management method and device and server |
| CN115407971A (en) * | 2022-08-18 | 2022-11-29 | 朗新数据科技有限公司 | Software product generation method and device |
-
2023
- 2023-05-17 CN CN202310556429.8A patent/CN116302075B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115617788A (en) * | 2022-12-20 | 2023-01-17 | 广州嘉为科技有限公司 | Product cleaning method and device and computer readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116302075A (en) | 2023-06-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2018137564A1 (en) | Service processing method and apparatus | |
| CN113110941B (en) | Managing delivery of code and dependency data using application containers | |
| US20180196665A1 (en) | Managing, using, and updating application resources | |
| US10827036B2 (en) | Version control machine | |
| CN111176802B (en) | Task processing method and device, electronic equipment and storage medium | |
| WO2020081453A1 (en) | Human-computer interaction processing system, method, storage medium and electronic device | |
| US10135940B2 (en) | Subscribing to event notifications using object instances | |
| CN103984538A (en) | Application scenario identification method, power consumption management method, devices and terminal equipment | |
| EP3304286A1 (en) | Data binding dependency analysis | |
| US20180101574A1 (en) | Searching index information for application data | |
| CN111400681B (en) | Data authority processing method, device and equipment | |
| CN101965561A (en) | Declarative support for asynchronous methods | |
| CN102591710B (en) | Shared object represents | |
| CN109933381A (en) | A kind of loading method and device of kernel | |
| CN112817657A (en) | Application program starting item loading method, device and system and storage medium | |
| CN108845864B (en) | Spring frame-based JVM garbage recycling method and device | |
| CN111935353B (en) | Mobile terminal and short message display method thereof | |
| CN107633080B (en) | User task processing method and device | |
| CN116302075B (en) | Software product management method and related equipment | |
| US20230139886A1 (en) | Device control method and device | |
| CN114358936A (en) | Intelligent contract operation method based on micro-service block chain | |
| CN112181407A (en) | Service implementation processing method, device, system, electronic equipment and storage medium | |
| CN112131000B (en) | Memory release method and device for plug-in application program | |
| CN111273910B (en) | Method, device and storage medium for acquiring resource number identifier | |
| WO2024046260A1 (en) | Hotfix method and related apparatus |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |