CN115857962A - Software project processing method and device, electronic equipment and readable storage medium - Google Patents

Software project processing method and device, electronic equipment and readable storage medium Download PDF

Info

Publication number
CN115857962A
CN115857962A CN202310135245.4A CN202310135245A CN115857962A CN 115857962 A CN115857962 A CN 115857962A CN 202310135245 A CN202310135245 A CN 202310135245A CN 115857962 A CN115857962 A CN 115857962A
Authority
CN
China
Prior art keywords
software
project
software project
item
server
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
Application number
CN202310135245.4A
Other languages
Chinese (zh)
Inventor
郗子硕
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Aijiwei Consulting Xiamen Co ltd
Original Assignee
Aijiwei Consulting Xiamen Co ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Aijiwei Consulting Xiamen Co ltd filed Critical Aijiwei Consulting Xiamen Co ltd
Priority to CN202310135245.4A priority Critical patent/CN115857962A/en
Publication of CN115857962A publication Critical patent/CN115857962A/en
Pending legal-status Critical Current

Links

Images

Landscapes

  • Stored Programmes (AREA)

Abstract

The embodiment of the application discloses a software project processing method, a device, an electronic device and a readable storage medium, which comprises the following steps: acquiring a plurality of software projects stored in the same workspace; updating version information of the item of software in response to a modification operation for the item of software; compiling and running the updated software project based on the updated version information, and sending the compiled and run software project to a server so that the server can generate and return a project file meeting the preset specification; and displaying the project file in a sharing interface. The scheme can improve the efficiency of software release.

Description

Software project processing method and device, electronic equipment and readable storage medium
Technical Field
The present application relates to the field of information processing technologies, and in particular, to a software project processing method and apparatus, an electronic device, and a readable storage medium.
Background
In the current program development project management mode, a plurality of code modules are generally stored in one code warehouse for management, and by uniformly converging each package in a single warehouse, the dependence, construction, development/debugging, testing, version and release of each software project are uniformly and comprehensively managed on an upper layer, so that a more elegant multi-package management and cooperation scheme is provided.
As software projects become increasingly complex, multi-package management becomes complex, especially managing project dependencies and software package releases. In the current management mode, only specific files can be identified, and when software packages are released, version numbers of the software packages need to be modified one by one, so that the current release process is complicated, and the release efficiency is low.
Disclosure of Invention
In view of this, the present application provides a software project processing method, a software project processing apparatus, an electronic device, and a readable storage medium, which can simplify a software project processing flow and improve software publishing efficiency.
The application provides a software project processing method, which comprises the following steps:
acquiring a plurality of software projects stored in the same workspace;
updating version information of the item of software in response to a modification operation for the item of software;
compiling and running the updated software project based on the updated version information, and sending the compiled and run software project to a server so that the server can generate and return a project file meeting the preset specification;
and displaying the project file in a sharing interface.
Optionally, in some embodiments of the present application, the updating the version information of the item of software in response to the modification operation on the item of software includes:
responding to the modification operation aiming at the software project, and acquiring a script file;
and when the script file is operated, modifying the codes of the software project and/or modifying the codes of the association relation of the software project, and updating the version number of the software project.
Optionally, in some embodiments of the present application, the compiling and running the updated software project based on the updated version information includes:
comparing the updated version information with the version information stored in the working space;
and compiling and running the updated software project when the updated version information is different from the version information stored in the working space.
Optionally, in some embodiments of the present application, the method further includes:
responding to a release operation, and acquiring the name of a software project corresponding to the release operation and the version number of the software project from the workspace;
and releasing the software project according to the name and the version number.
Optionally, in some embodiments of the present application, said issuing the software item according to the name and the version number includes:
detecting whether the code of the software project is correct;
when the code of the software project is detected to be correct, the software project is issued;
and when the code error of the software project is detected, acquiring the historical version number corresponding to the software project, and when the historical version number corresponding to the software project is detected to be correct, issuing the software project.
Optionally, in some embodiments of the present application, the method further includes:
determining an association relation among a plurality of software packages in the software project, wherein the association relation is a relation between a dependent package on which the software package depends and the software package;
installing the dependency package into a project catalog of the software project according to the incidence relation;
the step of sending the compiled and operated software project to the server so that the server can generate and return a project file meeting the preset specification comprises the following steps: and sending the compiled and operated software items and the item directories corresponding to the software items to a server so that the server can generate and return item files meeting preset specifications.
Correspondingly, the present application also provides a software project processing apparatus, comprising:
the acquisition module is used for acquiring a plurality of software projects stored in the same workspace;
the updating module is used for responding to the modification operation aiming at the software project and updating the version information of the software project;
the compiling module is used for compiling and running the updated software project based on the updated version information;
the sending module is used for sending the compiled and operated software project to the server so that the server can generate and return a project file meeting the preset specification;
and the display module is used for displaying the project file in a sharing interface.
Optionally, in some embodiments of the present application, the update module includes:
the acquisition unit is used for responding to the modification operation aiming at the software project and acquiring the script file;
and the updating unit is used for modifying the codes of the software items and/or modifying the codes of the association relation of the software items and updating the version numbers of the software items when the script files are operated.
The present application further provides an electronic device comprising a memory and a processor, wherein the memory stores a computer program, and the processor executes the steps of the software item processing method of the above embodiment.
The present application also provides a readable storage medium storing a computer program which, when executed by a processor, implements the above-described method.
The application provides a software project processing method, a device, an electronic device and a readable storage medium, wherein the software project processing method comprises the following steps: the software publishing method comprises the steps of obtaining a plurality of software projects stored in the same working space, responding to modification operation aiming at the software projects, updating version information of the software projects, compiling and operating the updated software projects based on the updated version information, sending the compiled and operated software projects to a server, enabling the server to generate and return project files meeting preset specifications, and displaying the project files in a sharing interface.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
FIG. 1 is a schematic view of a scenario of a software project processing method provided in an embodiment of the present application;
FIG. 2 is a schematic flow chart diagram of a software project processing method provided in an embodiment of the present application;
FIG. 3 is a schematic structural diagram of a software project processing apparatus provided in an embodiment of the present application;
fig. 4 is another schematic structural diagram of a software project processing apparatus according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application are clearly and completely described below with reference to the accompanying drawings, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the 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. The following embodiments and their technical features may be combined with each other without conflict.
It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope herein. The word "if" as used herein may be interpreted as "at" \8230; "or" when 8230; \8230; "or" in response to a determination ", depending on the context. Also, as used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context indicates otherwise. It will be further understood that the terms "comprises," "comprising," "includes" and/or "including," when used in this specification, specify the presence of stated features, steps, operations, elements, components, items, species, and/or groups, but do not preclude the presence, or addition of one or more other features, steps, operations, elements, components, items, species, and/or groups thereof. The terms "or," "and/or," "including at least one of the following," and the like, as used herein, are to be construed as inclusive or mean any one or any combination. For example, "includes at least one of: A. b, C "means" any of the following: a; b; c; a and B; a and C; b and C; a and B and C ", again for example," a, B or C "or" a, B and/or C "means" any one of the following: a; b; c; a and B; a and C; b and C; a and B and C'. An exception to this definition will occur only when a combination of elements, functions, steps or operations are inherently mutually exclusive in some way.
It should be understood that, although the steps in the flowcharts in the embodiments of the present application are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and may be performed in other orders unless explicitly stated herein. Moreover, at least some of the steps in the figures may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, in different orders, and may be performed alternately or partially with other steps or at least some of the sub-steps or stages of other steps.
The words "if", as used herein, may be interpreted as "at \8230; \8230when" or "when 8230; \823030, when" or "in response to a determination" or "in response to a detection", depending on the context. Similarly, the phrases "if determined" or "if detected (a stated condition or event)" may be interpreted as "when determined" or "in response to a determination" or "when detected (a stated condition or event)" or "in response to a detection (a stated condition or event)", depending on the context.
It should be noted that, step numbers such as 101, 102, etc. are used herein for the purpose of more clearly and briefly describing the corresponding content, and do not constitute a substantial limitation on the sequence, and those skilled in the art may perform 101 and then 102, etc. in the specific implementation, but these shall be within the protection scope of the present application.
The application provides a software project processing method, a software project processing device, electronic equipment and a readable storage medium.
The software project processing apparatus may be specifically integrated in a server, where the server may include an independently operating server or a distributed server, or may include a server cluster including a plurality of servers, and the server may be connected to an electronic device in a wired or wireless manner, and the electronic device may include a mobile phone, a tablet Computer, or a Personal Computer (PC).
For example, referring to fig. 1, the present application provides a software project processing apparatus, which is integrated in an electronic device a, the electronic device a is connected to a server S, the electronic device a updates version information of a software project in response to a modification operation for the software project after acquiring a plurality of software projects stored in a same workspace, and then, the electronic device a compiles and runs the updated software project based on the updated version information, and sends the compiled and run software project to the server S, so that the server S generates and returns a project file meeting a preset specification, and finally, the electronic device a displays the project file in a shared interface.
According to the software publishing scheme, when the software is published, the version numbers of the software packages do not need to be modified one by one, so that the software publishing process can be simplified, and the software publishing efficiency is improved.
The following are detailed below. It should be noted that the description sequence of the following embodiments is not intended to limit the priority sequence of the embodiments.
A software project processing method, comprising: acquiring a plurality of software projects stored in the same workspace; updating version information of the software project in response to the modification operation for the software project; compiling and running the updated software project based on the updated version information, and sending the compiled and run software project to a server so that the server can generate and return a project file meeting the preset specification; and displaying the project file in the sharing interface.
Referring to fig. 2, fig. 2 is a flowchart illustrating a software project processing method according to an embodiment of the present disclosure. The specific flow of the software project processing method can be as follows:
101. a software project is obtained that includes a plurality of software items stored within the same workspace.
The workspace is also called a multi-project repository (workplace), which may be understood as a repository for storing software projects, and multiple different projects, multiple versions of projects, or only one project may be stored in the workspace.
The software packages are uniformly converged in a single warehouse, and the dependence, construction, development/debugging, testing, version and release of each software project are uniformly and comprehensively managed on the upper layer, so that a more elegant multi-package management and cooperation scheme is provided.
102. Version information of the item of software is updated in response to a modification operation for the item of software.
Before software is released, operation and maintenance personnel can modify a software project according to actual requirements, and version information specifically comprises a major version number, a minor version number and a revision number, wherein the major version number is API modification incompatible with operation, the minor version number is functional addition compatible with operation downwards, and the revision number is problem modification compatible with operation downwards.
Specifically, the step of "updating the version information of the software project in response to the modification operation on the software project" may specifically include:
(11) Responding to modification operation aiming at the software project, and acquiring a script file;
(12) And when the script file is operated, modifying the codes of the software project and/or modifying the codes of the association relation of the software project, and updating the version number of the software project.
For example, in particular, the script file may be executed in response to a code modification of the sub-item and/or a code modification of the association of the software item and an update of the version of the software item, and then the updated software item may be compiled, i.e., step 103 is performed.
103. And compiling and running the updated software project based on the updated version information, and sending the compiled and run software project to a server so that the server can generate and return a project file meeting the preset specification.
After obtaining the updated version information of the software project, compiling and running the updated software project by using the compiling script, it should be noted that, since a large number of software packages and software projects may be stored in the workspace, and different users may store the software packages constructed by the software packages in the workspace, in order to prevent the waste of computing resources caused by repeated compiling, before compiling, it may be checked whether the updated version information is the same as the version information of the workspace, and the updated software project is compiled and run based on the comparison result, that is, optionally, in some embodiments, the step "compiling and running the updated software project based on the updated version information" may specifically include:
(21) Comparing the updated version information with the version information stored in the working space;
(22) And when the updated version information is different from the version information stored in the working space, compiling and running the updated software project.
Compiling (build ): 1. a process for generating an object program from a source program written in a source language using a compiler. 2. The act of generating the object program with the compiler. Compiling is to change a high-level language into a 2-system language which can be recognized by a computer, the computer only recognizes 1 and 0, and a compiler program changes a familiar language into a 2-system language. The compiler program translates a source program into a target program and has five stages: lexical analysis; analyzing the grammar; semantic checking and intermediate code generation; optimizing codes; and generating an object code. The method mainly comprises the steps of lexical analysis and syntactic analysis, namely source program analysis, wherein syntactic errors are found in the analysis process, and prompt information is given.
After the updated software project is compiled and operated, the operated software project is sent to a server, a log plug-in configured in the server generates a project file meeting a preset specification, the project file comprises a code corresponding to the software project, a version number of the software project, updated content of the software project and the like, and different project files are output according to the same format, namely the project file A and the project file B are different in file content and the same in format arrangement. And restricting the format of the project file according to the preset specification, so that a user can conveniently check the version log, check the updated content, position the problem and rollback the code.
Optionally, in some embodiments, the software project processing method of the present application may further include:
(31) Determining an incidence relation among a plurality of software packages in the software project;
(32) And installing the dependency packages into the item catalog of the software item according to the association relation.
Wherein, the association relationship is a relationship between a dependent package and a software package, and the step "sending the compiled and run software project to the server so that the server generates and returns a project file meeting a preset specification" may specifically include: and sending the compiled and operated software items and the item directories corresponding to the software items to a server so that the server can generate and return item files meeting the preset specification.
It should be noted that a software project may include a plurality of software packages, and a software package (package) is a modularized idea that one of software design ideas is, that is, codes of different functions are respectively stored in different files and classes, and each file and class is a module with a single function. The software package is one embodiment of the modularization idea, namely, codes with single functions are divided into one software package, and other modules can refer to the software package, so that the code reuse rate is improved, and the maintenance cost of the codes is reduced. Package dependencies mean that the validation of one package requires another package as a basis. The software package dependencies are divided into development environment dependencies (devdependences) and production environment dependencies (dependences) from the runtime viewpoint. Development environment dependencies refer to software packages needed in the development of project software; production environment dependencies refer to software packages that are needed when a project is actually running. The software package dependence is divided into external dependence and internal dependence from the software package owner, wherein the external dependence is the software package developed and maintained by other people, and the internal dependence is the software package developed by the developer and used by the internal development of the project group.
When a developer develops a multi-package project, for example, the project includes a core package and a plurality of auxiliary function packages. The core package will typically reference other auxiliary function packages, i.e. there are dependencies (internal dependencies) inside the project. A lerna instruction is required to associate an internal dependent packet when using lerna. Management of internal dependencies can be complex, and particularly in a TypeScript software package, situations often occur in which no internal dependencies can be found, resulting in a project being reported incorrectly. The lerna open source tool gives only one example of a directory structure, and the engineering process of each software package is not implemented, especially compilation management. But developing compilation management in the front end (e.g., compiling javascript and TypeScript code using webpack or rolup) is a necessary process.
104. And displaying the project file in the sharing interface.
For example, specifically, when a project file returned by a server is received, a display instruction for the project file may be triggered, a sharing interface is output according to the display instruction, and the project file is displayed in the sharing interface, which is convenient for other users to obtain related information of the project file, for example, a user u1 modifies a software project to obtain a project file a1, a user u2 modifies a software project to obtain a2, a terminal c1 corresponding to the user u1 may upload the project file a1 to a file sharing platform for display, a terminal c2 corresponding to the user u2 may upload the project file a2 to the file sharing platform for display, and the user u1 may obtain information of the project file a1 in the file sharing platform and information of the project file a2 in the file sharing platform; similarly, the user u2 can acquire the information of the project file a1 in the file sharing platform and the information of the project file a2 in the file sharing platform, so that the information sharing of the project file can be realized, and when the project file is shared, the user can know whether the modification of the project file is a patch, a small change, a large change or a self-set change, so that the communication cost among the users can be reduced, the release of the software project is facilitated, and the release efficiency of the software project is improved.
Optionally, in some embodiments, the software project processing method provided by the present application may further include:
(41) Responding to the release operation, and acquiring the name of the software project and the version number of the software project corresponding to the release operation from the workspace;
(42) The software items are released according to the name and version number.
For example, specifically, the user may select a name and a version number of the software item to be released, such as manually inputting or by checking, in response to the releasing operation, obtain the software item corresponding to the name and the version number, and release the software item.
It may be understood that, when a user performs a publishing operation, it may occur that a code of a software item that the user desires to publish does not meet a publishing requirement, and therefore, when publishing, a code of the software item also needs to be detected, that is, optionally, in some embodiments, the step "publish the software item according to a name and a version number" may specifically include:
(51) Detecting whether the code of the software project is correct;
(52) When the code of the software project is detected to be correct, the software project is released;
(53) And when the code error of the software item is detected, acquiring the historical version number corresponding to the software item, and when the historical version number corresponding to the software item is detected to be correct, issuing the software item.
For example, the version of the software project corresponding to the release operation is a V5 version, and when it is detected that a bug occurs in the software project due to an error in a code of the software project, a historical version corresponding to each software package of the software project is detected, for example, the software project of the V5 version includes a software package a, a software package b, and a software package c, and under the software project of the V5 version, the code of the software package a is correct, the code of the software package b is correct, and the code of the software package c is incorrect, the code of the software package c is returned to the code of the correct version, and the software project is released based on the software package a, the software package b, and the software package c after the version is returned.
The software project processing flow of the present application is completed above.
According to the software project processing method, after a plurality of software projects stored in the same working space are obtained, the modification operation aiming at the software projects is responded, the version information of the software projects is updated, then the updated software projects are compiled and operated based on the updated version information, the compiled and operated software projects are sent to a server, so that the server can generate and return project files meeting preset specifications, and finally the project files are displayed in a shared interface.
Referring to fig. 3, fig. 3 is a schematic structural diagram of a software project processing apparatus according to an embodiment of the present application, where the software project processing apparatus may specifically include: the obtaining module 301, the updating module 302, the compiling module 303, the sending module 304 and the displaying module 305 may specifically be as follows:
the acquiring module 301 is configured to acquire a plurality of software items stored in the same workspace.
The workspace is also called a multi-project repository (workplace), which may be understood as a repository for storing software projects, and multiple different projects, multiple versions of projects, or only one project may be stored in the workspace.
An update module 302 for updating version information of the item of software in response to a modification operation on the item of software.
Specifically, the automated process may be executed by executing the file to implement the response code, so as to update the version information of the software project, that is, optionally, in some embodiments, the updating module 302 may specifically include:
the acquisition unit is used for responding to modification operation aiming at the software project and acquiring the script file;
and the updating unit is used for modifying the codes of the software items and/or modifying the codes of the association relation of the software items and updating the version numbers of the software items when the script files are operated.
And the compiling module 303 is configured to compile and run the updated software project based on the updated version information.
Optionally, in some embodiments, the compiling module 303 may be specifically configured to: comparing the updated version information with the version information stored in the working space; and when the updated version information is different from the version information stored in the working space, compiling and running the updated software project.
The sending module 304 is configured to send the compiled and run software project to the server, so that the server generates and returns a project file meeting a preset specification.
A presentation module 305 for presenting the project file in the sharing interface.
Optionally, in some embodiments, the software project processing apparatus of the present application may further include an installation module, where the installation module may be specifically configured to: determining an incidence relation among a plurality of software packages in the software project; and installing the dependency packages into the item catalog of the software item according to the association relation.
Optionally, in some embodiments, referring to fig. 4, the software project processing apparatus of the present application may further specifically include a detection module 306, where the detection module 306 may be configured to: responding to the release operation, and acquiring the name of the software project and the version number of the software project corresponding to the release operation from the workspace; the software items are released according to the name and version number.
Optionally, in some embodiments, the detection module 306 may be specifically configured to: detecting whether the code of the software project is correct; when the code of the software project is detected to be correct, the software project is released; and when the code error of the software item is detected, acquiring the historical version number corresponding to the software item, and when the historical version number corresponding to the software item is detected to be correct, issuing the software item.
According to the software project processing method, after the acquisition module 301 acquires a plurality of software projects stored in the same working space, the update module 302 updates version information of the software projects in response to modification operation for the software projects, then the compiling module 303 compiles and runs the updated software projects based on the updated version information, then the sending module 304 sends the compiled and run software projects to a server, so that the server generates and returns project files meeting preset specifications, and finally the showing module 305 shows the project files in a shared interface.
The present application further provides an electronic device, where the electronic device includes a memory and a processor, and an interface processing program is stored in the memory, and when the interface processing program is executed by the processor, the steps of the interface processing method in any of the above embodiments are implemented.
The present application further provides a readable storage medium, where an interface processing program is stored on the readable storage medium, and when the interface processing program is executed by a processor, the interface processing program implements the steps of the interface processing method in any of the above embodiments.
In the embodiments of the electronic device and the readable storage medium provided in the present application, all technical features of any one of the embodiments of the interface processing method may be included, and the expanding and explaining contents of the specification are substantially the same as those of the embodiments of the method, and are not described herein again.
Embodiments of the present application also provide a computer program product, which includes computer program code, when the computer program code runs on a computer, the computer is caused to execute the method in the above various possible embodiments.
Embodiments of the present application further provide a chip, which includes a memory and a processor, where the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that a device in which the chip is installed executes the method in the above various possible embodiments.
It is to be understood that the foregoing scenarios are only examples, and do not constitute a limitation on application scenarios of the technical solutions provided in the embodiments of the present application, and the technical solutions of the present application may also be applied to other scenarios. For example, as can be known by those skilled in the art, with the evolution of system architecture and the emergence of new service scenarios, the technical solution provided in the embodiments of the present application is also applicable to similar technical problems.
The above-mentioned serial numbers of the embodiments of the present application are merely for description, and do not represent the advantages and disadvantages of the embodiments.
The steps in the method of the embodiment of the application can be sequentially adjusted, combined and deleted according to actual needs.
The units in the device in the embodiment of the application can be merged, divided and deleted according to actual needs.
In the present application, the same or similar descriptions of terms, technical solutions and/or application scenarios will generally be described in detail only when they occur for the first time, and when they occur repeatedly later, they will not be repeated again for brevity, and in understanding the technical solutions and the like of the present application, reference may be made to the related detailed descriptions and the like before the same or similar descriptions of terms, technical solutions and/or application scenarios and the like which are not described in detail later.
In the present application, each embodiment is described with emphasis, and reference may be made to the description of other embodiments for parts that are not described or illustrated in any embodiment.
The technical features of the technical solution of the present application may be arbitrarily combined, and for brevity of description, all possible combinations of the technical features in the embodiments are not described, however, as long as there is no contradiction between the combinations of the technical features, the scope of the present application should be considered as being described in the present application.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, a controlled terminal, or a network device) to execute the method of each embodiment of the present application.
In the above embodiments, all or part of the implementation may be realized by software, hardware, firmware, or any combination thereof. When implemented in software, it 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. The procedures or functions according to the embodiments of the present application are all or partially generated when the computer program instructions are loaded and executed on a computer. 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 on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (e.g., coaxial cable, fiber optic, digital subscriber line) or wirelessly (e.g., infrared, wireless, microwave, etc.). Computer-readable storage media can be any available media that can be accessed by a computer or a data storage device, such as a server, data center, etc., that includes one or more available media. The usable medium may be a magnetic medium (e.g., floppy Disk, memory Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid State Disk (SSD)), among others.
The above description is only a preferred embodiment of the present application, and not intended to limit the scope of the present application, and all modifications of equivalent structures and equivalent processes, which are made by the contents of the specification and the drawings of the present application, or which are directly or indirectly applied to other related technical fields, are included in the scope of the present application.

Claims (10)

1. A method of processing a software project, comprising:
acquiring a plurality of software projects stored in the same workspace;
updating version information of the item of software in response to a modification operation for the item of software;
compiling and running the updated software project based on the updated version information, and sending the compiled and run software project to a server so that the server can generate and return a project file meeting the preset specification;
and displaying the project file in a sharing interface.
2. The method of claim 1, wherein updating version information of the item of software in response to the modification operation on the item of software comprises:
responding to the modification operation aiming at the software project, and acquiring a script file;
and when the script file is operated, modifying the codes of the software project and/or modifying the codes of the association relation of the software project, and updating the version number of the software project.
3. The method of claim 1, wherein compiling and running the updated software project based on the updated version information comprises:
comparing the updated version information with the version information stored in the working space;
and compiling and running the updated software project when the updated version information is different from the version information stored in the working space.
4. The method of any of claims 1 to 3, further comprising:
responding to a release operation, and acquiring the name of a software project corresponding to the release operation and the version number of the software project from the workspace;
and releasing the software project according to the name and the version number.
5. The method of claim 4, wherein said publishing said item of software according to said name and version number comprises:
detecting whether the code of the software project is correct;
when the code of the software project is detected to be correct, the software project is issued;
and when the code error of the software project is detected, acquiring the historical version number corresponding to the software project, and when the historical version number corresponding to the software project is detected to be correct, issuing the software project.
6. The method of any of claims 1 to 3, further comprising:
determining an association relation among a plurality of software packages in the software project, wherein the association relation is a relation between a dependent package on which the software package depends and the software package;
installing the dependency package into a project catalog of the software project according to the incidence relation;
the step of sending the compiled and operated software project to the server so that the server can generate and return a project file meeting a preset specification comprises the following steps: and sending the compiled and operated software items and the item directories corresponding to the software items to a server so that the server can generate and return item files meeting preset specifications.
7. A software project processing apparatus, comprising:
the acquisition module is used for acquiring a plurality of software projects stored in the same workspace;
the updating module is used for responding to the modification operation aiming at the software project and updating the version information of the software project;
the compiling module is used for compiling and running the updated software project based on the updated version information;
the sending module is used for sending the compiled and operated software project to the server so that the server can generate and return a project file meeting the preset specification;
and the display module is used for displaying the project file in a sharing interface.
8. The apparatus of claim 7, wherein the update module comprises:
the acquisition unit is used for responding to modification operation aiming at the software project and acquiring a script file;
and the updating unit is used for modifying the codes of the software items and/or modifying the codes of the association relation of the software items and updating the version numbers of the software items when the script files are operated.
9. An electronic device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor realizes the steps of the item of software processing method of any one of claims 1 to 6 when executing the computer program.
10. A readable storage medium, characterized in that it stores a computer program which, when executed by a processor, implements the software item processing method of any one of claims 1 to 6.
CN202310135245.4A 2023-02-20 2023-02-20 Software project processing method and device, electronic equipment and readable storage medium Pending CN115857962A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310135245.4A CN115857962A (en) 2023-02-20 2023-02-20 Software project processing method and device, electronic equipment and readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310135245.4A CN115857962A (en) 2023-02-20 2023-02-20 Software project processing method and device, electronic equipment and readable storage medium

Publications (1)

Publication Number Publication Date
CN115857962A true CN115857962A (en) 2023-03-28

Family

ID=85658433

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310135245.4A Pending CN115857962A (en) 2023-02-20 2023-02-20 Software project processing method and device, electronic equipment and readable storage medium

Country Status (1)

Country Link
CN (1) CN115857962A (en)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110283252A1 (en) * 2010-05-11 2011-11-17 Microsoft Corporation Change notification and information update based on uncompiled software development project
CN110442371A (en) * 2019-08-05 2019-11-12 武汉斗鱼网络科技有限公司 A kind of method, apparatus of release code, medium and computer equipment
CN111694592A (en) * 2020-06-24 2020-09-22 深圳壹账通智能科技有限公司 Management method and system for project version release
CN112558980A (en) * 2020-12-15 2021-03-26 建信金融科技有限责任公司 Multi-software-package management method and device
CN115599437A (en) * 2022-10-26 2023-01-13 北京领雁科技股份有限公司(Cn) Software version processing method and device, electronic equipment and storage medium

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110283252A1 (en) * 2010-05-11 2011-11-17 Microsoft Corporation Change notification and information update based on uncompiled software development project
CN110442371A (en) * 2019-08-05 2019-11-12 武汉斗鱼网络科技有限公司 A kind of method, apparatus of release code, medium and computer equipment
CN111694592A (en) * 2020-06-24 2020-09-22 深圳壹账通智能科技有限公司 Management method and system for project version release
CN112558980A (en) * 2020-12-15 2021-03-26 建信金融科技有限责任公司 Multi-software-package management method and device
CN115599437A (en) * 2022-10-26 2023-01-13 北京领雁科技股份有限公司(Cn) Software version processing method and device, electronic equipment and storage medium

Similar Documents

Publication Publication Date Title
US20220222170A1 (en) Software development framework for a cloud computing platform
US11429365B2 (en) Systems and methods for automated retrofitting of customized code objects
US10481884B2 (en) Systems and methods for dynamically replacing code objects for code pushdown
US20190034189A1 (en) Systems and methods for transformation of reporting schema
US20240045850A1 (en) Systems and methods for database orientation transformation
US7614040B2 (en) System and method for efficiently analyzing and building interdependent resources in a software project
US10331425B2 (en) Automated source code adaption to inject features between platform versions
US8433687B1 (en) Off-line indexing for client-based software development tools
US8255883B2 (en) Translating late bound LINQ expressions into database queries
US20080276221A1 (en) Method and apparatus for relations planning and validation
US9965257B2 (en) Automatic configuration of project system from project capabilities
US9311077B2 (en) Identification of code changes using language syntax and changeset data
CN110673837B (en) Code repairing method and device, electronic equipment and computer readable storage medium
CN111679852B (en) Detection method and device for conflict dependency library
CN116560683A (en) Software updating method, device, equipment and storage medium
KR102352265B1 (en) System and method for providing web application development platform
US20200097260A1 (en) Software application developer tools platform
CN113377342B (en) Project construction method and device, electronic equipment and storage medium
CN111352631B (en) Interface compatibility detection method and device
CN110334031A (en) Memory Allocation code detection method, device, computer equipment and storage medium
CN115857962A (en) Software project processing method and device, electronic equipment and readable storage medium
CN113032004B (en) Method, apparatus and program product for managing development jobs in a development environment
CN114527993A (en) Application deployment method, device, equipment and medium
CN111400396A (en) Method and device for generating data synchronization script and computer readable storage medium
CN110737431A (en) Software development method, development platform, terminal device 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