CN114296753A - File publishing method and device, storage medium and electronic device - Google Patents
File publishing method and device, storage medium and electronic device Download PDFInfo
- Publication number
- CN114296753A CN114296753A CN202111424207.8A CN202111424207A CN114296753A CN 114296753 A CN114296753 A CN 114296753A CN 202111424207 A CN202111424207 A CN 202111424207A CN 114296753 A CN114296753 A CN 114296753A
- Authority
- CN
- China
- Prior art keywords
- version
- file
- directory
- identifier
- 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
Links
Images
Abstract
The disclosure discloses a file publishing method, a file publishing device, a storage medium and an electronic device. Wherein, the method comprises the following steps: acquiring first version identification information of a version file to be released, wherein the first version identification information comprises: the system comprises a branch identifier and a first time identifier, wherein the branch identifier is used for describing a distribution channel of a version file, and the first time identifier is used for describing the packaging time of the version file; creating a corresponding version directory for the version files to be released in a shared directory according to the first version identification information, wherein the shared directory is a directory area shared by the version directories corresponding to different version files to be released at the server side; outputting the version file to a version directory; and uploading the version file to the server through the version directory so that the server releases the version file. The method and the device solve the technical problem that the page fault occurs due to file deletion or modification in the publishing process in the file publishing method in the prior art.
Description
Technical Field
The present disclosure relates to the field of software updating technologies, and in particular, to a file publishing method, device, storage medium, and electronic device.
Background
The mainstream server used in the deployment of the scripting language is passer, which is an open-source efficient Web server and supports multiple programming languages, such as: ruby, Python, NodeJS, etc., and can serve a plurality of application programs simultaneously, which is very convenient for the deployment and the expansion of the programs.
However, in the prior art, the main flow of the distribution process of the script language application is to push the latest front-end and back-end codes to the Passenger server, file comparison is involved in the process, then the files are covered or deleted, after all the files of the application are replaced by the latest versions, the initialization scripts related to the versions are executed, and finally the application is reloaded.
In view of the above problems, no effective solution has been proposed.
Disclosure of Invention
The embodiment of the disclosure provides a file publishing method, a file publishing device, a storage medium and an electronic device, so as to at least solve the technical problem that a page error occurs due to file deletion or modification in a publishing process in a file publishing method in the prior art.
According to an aspect of the embodiments of the present disclosure, a file publishing method is provided, where first version identification information of a version file to be published is obtained, where the first version identification information includes: the system comprises a branch identifier and a first time identifier, wherein the branch identifier is used for describing a distribution channel of the version file, and the first time identifier is used for describing the packaging time of the version file; creating a corresponding version directory for the version file to be released in a shared directory according to the first version identification information, wherein the shared directory is a directory area shared by version directories corresponding to different version files to be released; outputting the version file to the version directory; and uploading the version file to a server through the version directory so that the server issues the version file.
According to another aspect of the embodiments of the present disclosure, there is also provided a file publishing device, including: the system comprises an acquisition module and a release module, wherein the acquisition module is used for acquiring first version identification information of a version file to be released, and the first version identification information comprises: the system comprises a branch identifier and a first time identifier, wherein the branch identifier is used for describing a distribution channel of the version file, and the first time identifier is used for describing the packaging time of the version file; the creating module is used for creating a corresponding version directory for the version files to be released in a shared directory according to the first version identification information, wherein the shared directory is a directory area shared by version directories corresponding to different version files to be released; the output module is used for outputting the version file to the version directory; and the release module is used for uploading the version file to a server through the version directory so as to enable the server to release the version file.
According to another aspect of the embodiments of the present disclosure, there is also provided a non-volatile storage medium having a computer program stored therein, wherein the computer program is configured to execute any one of the above file distribution methods when running.
According to another aspect of the embodiments of the present disclosure, there is also provided a processor, configured to execute a program, where the program is configured to execute any one of the file publishing methods described above when running.
According to another aspect of the embodiments of the present disclosure, there is also provided an electronic apparatus, including a memory and a processor, where the memory stores a computer program, and the processor is configured to execute the computer program to perform any one of the file publishing methods described above.
In an embodiment of the present disclosure, first version identification information of a version file to be published is obtained, where the first version identification information includes: the system comprises a branch identifier and a first time identifier, wherein the branch identifier is used for describing a distribution channel of the version file, and the first time identifier is used for describing the packaging time of the version file; creating a corresponding version directory for the version file to be released in a shared directory according to the first version identification information, wherein the shared directory is a directory area shared by version directories corresponding to different version files to be released; outputting the version file to the version directory; the version files are uploaded to the server side through the version directory, so that the server side issues the version files, the purpose that the new version files cannot cover the old version files in the issuing process is achieved, the technical effect of avoiding script errors or style disorder caused by deleting the old version files is achieved, and the technical problem that page errors occur due to file deletion or modification in the issuing process of a file issuing method in the prior art is solved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the disclosure and together with the description serve to explain the disclosure and not to limit the disclosure. In the drawings:
FIG. 1 is a flow diagram of a file publication method according to an embodiment of the disclosure;
FIG. 2 is a schematic diagram illustrating an alternative deployment scenario of files of different versions in the same server according to an embodiment of the present disclosure;
FIG. 3 is a schematic diagram of an alternative version file deletion flow according to an embodiment of the present disclosure;
FIG. 4 is a schematic diagram of an alternative version file update or rollback flow according to an embodiment of the present disclosure;
FIG. 5 is a schematic diagram of an alternative version file deployment flow diagram according to an embodiment of the present disclosure;
fig. 6 is a schematic structural diagram of a document issuing apparatus according to an embodiment of the present disclosure.
Detailed Description
In order to make the technical solutions of the present disclosure better understood by those skilled in the art, the technical solutions of the embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in the embodiments of the present disclosure, and it is obvious that the described embodiments are only some embodiments of the present disclosure, not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments disclosed herein without making any creative effort, shall fall within the protection scope of the present disclosure.
It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the disclosure described herein are capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
In accordance with an embodiment of the present disclosure, there is provided a method embodiment of file publication, it should be noted that the steps illustrated in the flowchart of the drawings may be performed in a computer system, such as a set of computer-executable instructions, and that while a logical order is illustrated in the flowchart, in some cases the steps illustrated or described may be performed in an order different than here.
The technical scheme of the method embodiment can be executed in a mobile terminal, a computer terminal or a similar arithmetic device. Taking the example of the Mobile terminal running on the Mobile terminal, the Mobile terminal may be a terminal device such as a smart phone (e.g., an Android phone, an iOS phone, etc.), a tablet computer, a palm computer, a Mobile Internet device (MID for short), a PAD, and the like. The mobile terminal may include one or more processors (which may include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), a Digital Signal Processing (DSP) chip, a Microprocessor (MCU), a programmable logic device (FPGA), a neural Network Processor (NPU), a Tensor Processor (TPU), an Artificial Intelligence (AI) type processor, etc.) and a memory for storing data. Optionally, the mobile terminal may further include a transmission device, an input/output device, and a display device for a communication function. It will be understood by those skilled in the art that the foregoing structural description is only illustrative and not restrictive of the structure of the mobile terminal. For example, the mobile terminal may also include more or fewer components than described above, or have a different configuration than described above.
The memory may be used to store computer programs, for example, software programs and modules of application software, such as computer programs corresponding to the file distribution method in the embodiments of the present disclosure, and the processor executes various functional applications and data processing by running the computer programs stored in the memory, that is, implements the file distribution method described above. The memory may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory may further include memory located remotely from the processor, and these remote memories may be connected to the mobile terminal through a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The transmission device is used to receive or transmit data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider of the mobile terminal. In one example, the transmission device includes a Network adapter (NIC) that can be connected to other Network devices through a base station to communicate with the internet. In one example, the transmission device may be a Radio Frequency (RF) module, which is used for communicating with the internet in a wireless manner. The technical scheme of the embodiment of the method can be applied to various communication systems, such as: a Global System for Mobile communications (GSM) System, a Code Division Multiple Access (CDMA) System, a Wideband Code Division Multiple Access (WCDMA) System, a General Packet Radio Service (GPRS), a Long Term Evolution (Long Term Evolution, LTE) System, a Frequency Division Duplex (FDD) System, a Time Division Duplex (TDD), a Universal Mobile Telecommunications System (UMTS), a Worldwide Interoperability for Microwave Access (WiMAX) communication System, or a 5G System. Optionally, Device-to-Device (D2D for short) communication may be performed between multiple mobile terminals. Alternatively, the 5G system or the 5G network is also referred to as a New Radio (NR) system or an NR network.
The display device may be, for example, a touch screen type Liquid Crystal Display (LCD) and a touch display (also referred to as a "touch screen" or "touch display screen"). The liquid crystal display may enable a user to interact with a user interface of the mobile terminal. In some embodiments, the mobile terminal has a Graphical User Interface (GUI) with which a user can interact by touching finger contacts and/or gestures on a touch-sensitive surface, where the human-machine interaction function optionally includes the following interactions: executable instructions for creating web pages, drawing, word processing, making electronic documents, games, video conferencing, instant messaging, emailing, call interfacing, playing digital video, playing digital music, and/or web browsing, etc., for performing the above-described human-computer interaction functions, are configured/stored in one or more processor-executable computer program products or readable computer-readable storage media.
The file publishing method in one embodiment of the disclosure can be operated on a terminal device or a server. The terminal device may be a local terminal device, and the server may be a cloud server, a server of a distributed system, or a server combining a block chain. When the file publishing method is operated on a server, the method can be implemented and executed based on a cloud interaction system, wherein the cloud interaction system comprises the server and the client device.
In the technical scheme of the disclosure, the acquisition, storage, application and the like of the personal information of the related user all accord with the regulations of related laws and regulations, and do not violate the good customs of the public order.
In one possible implementation, the disclosed embodiments provide a file publishing method, it should be noted that the steps shown in the flowchart of the figure may be performed in a computer system such as a set of computer executable instructions, and that while a logical order is shown in the flowchart, in some cases the steps shown or described may be performed in an order different than here.
Fig. 1 is a flowchart of a file publishing method according to an embodiment of the present disclosure, as shown in fig. 1, the method including the steps of:
step S102, obtaining first version identification information of a version file to be released, wherein the first version identification information comprises: the system comprises a branch identifier and a first time identifier, wherein the branch identifier is used for describing a distribution channel of the version file, and the first time identifier is used for describing the packaging time of the version file;
step S104, according to the first version identification information, creating a corresponding version directory for the version file to be released in a shared directory, wherein the shared directory is a directory area shared by version directories corresponding to different version files to be released;
step S106, outputting the version file to the version directory;
step S108, uploading the version file to a server through the version directory, so that the server issues the version file.
In the embodiment of the disclosure, a client is adopted to obtain first version identification information of a version file to be published, the client creates a corresponding version directory for the version file to be published in a shared directory according to the first version identification information and outputs the version file to the version directory, the client uploads the version file to a server through the version directory, and the server publishes the version file.
It should be noted that the first version identification information, i.e., the version number, includes: the system comprises a branch identifier and a first time identifier, wherein the branch identifier is used for describing a distribution channel of the version file, and the first time identifier is used for describing the packaging time of the version file; the distribution channel of the version file may include: a formal release channel or a gray level test release channel; the shared directory is a directory area shared by version directories corresponding to different version files to be released.
In the embodiment of the present disclosure, a version file to be published in a file publishing system formed by a client and a server may have multiple function branch versions, for example: the formal version, the gray function 1 version, the gray function 2 version and the like generate a time-sequence-increasing version number, namely the first version identification information, each time when different versions of files are released, wherein the version number comprises the branch identification and the first time identification, and the version numbers of the functional version and the gray version packaged at 17 o' clock 30 of 7 th month 1in 2021 are release-2107011730 and gray-2107011730 respectively.
As an optional embodiment, in the embodiment of the present disclosure, an output directory of a compilation target (version file) of a client is adjusted to a version directory by adjusting configuration information (such as Webpack) of a client packaging plug-in, a corresponding version directory is created by using a server, and version files such as a client css and a static file js are output to different version directories; the server side obtains the corresponding latest client side code in the corresponding version directory according to the first version identification information, analyzes the version number generated by the client side, saves the version number of the version file into a configuration file, then combines the corresponding files of the client side, and completes the release of the version file. Compared with the existing file release technology which uses a new version file to cover an old version file, the method avoids the situation that the JS file is replaced or the system script is deleted to cause errors in the file release process.
For the problems in the prior art, as an optional embodiment, for the deployment of multiple instances (i.e., files of different versions), each instance needs to copy and compare version files, and a large number of version files consume a transmission interface IO very much in the copying and comparing process; the method has the advantages that the file release process is carried out by introducing versions, a unique and increasing version number is generated every time the versions are released, and the client static files are compiled under the version numbers, so that the situation that files of the old version are covered in the release process can not occur due to different version directories of the static files of the front and rear versions, and the problem of script errors or style disorder caused by the fact that the static files are deleted in the release process is solved by means of retaining the files of the old version in the release process of the script of the released version files.
It should be noted that the version file may be generated according to a functional branch in the file distribution system plus a sequentially increasing version number.
Optionally, in the file publishing system, the request of the same user may be fixed to a server through a session sticky technique, so as to solve the technical problem of request errors caused by inconsistent versions of the page and the interface request in the cluster mode. And when the continuous integration CI process is started, setting the load balance to be a Session sticky Session still mode, and recovering the load balance configuration after the continuous integration process is completed.
It should be noted that, in the file distribution system, security and isolation of version file data need to be considered, and for different instances (i.e. version files), configuration of the database and configuration of the function switch are different; however, for the same functional branch, the code of the corresponding instance may be the same, as in the schematic diagram of file deployment situations with different versions in the same server shown in fig. 2, for instance 1instance1 and instance 2instance 2in the same server, if the functional versions of instance1 and instance2 are consistent, their codes are the same, and there is a difference in configuration files; in addition, because the client is a single-page application, the mainstream packaging mode in the prior art is to compile the file content by using an information summarization algorithm md5 and then add the file content to a file name suffix, for example, the file content is compiled into app.7s6ae43 … js; therefore, in the prior art, as long as the content of the version file is modified every time the version file is released, the file name is changed, so that the calculation amount in the process of comparing the file difference during the release is greatly increased, the version file needs to run the version initialization script after the version file is processed, the whole file release process is long, and the user experience is seriously influenced.
Optionally, the client directory may be shared in a soft link manner in the file publishing system, and all the client files are stored, and because the client directory is determined according to the version number, the version files with different function branch identifiers or different time identifiers are stored in different directories, and will not affect each other. In addition, in the process of releasing the version file each time, as long as the version directory of the target version is detected not to be in the shared directory, the whole directory is copied into the shared directory, file comparison is not needed, and the file releasing time is greatly saved.
In an alternative embodiment, the number of version directories stored in the shared directory is determined by a preset number of rollback versions and the branch identifier.
In the embodiment of the present disclosure, copying the entire version directory into the shared directory may cause that version files of the client in the shared directory are more and more, and therefore, as an optional embodiment, the shared directory may be cleared after the release of the version files is completed.
In an optional embodiment, after the version file is uploaded to a server through the version directory, so that the server issues the version file, the method further includes:
step S202, obtaining the rollback times of the preset version and the branch identification;
step S204, selecting the version directory to be reserved from the shared directory according to the preset version rollback times and the branch identification, and deleting other unselected version directories to obtain an updated version directory.
Optionally, the version directory to be retained is selected from the shared directory, and may be determined based on a product of the number of rollback times of the preset version and the branch identifier, for example, after the updated version directory is obtained, if the number of rollback times of the preset version is one, the function branch corresponding to each branch identifier retains the version directory and a previous version directory of the version directory, and deletes the other version directories that are not selected, so as to obtain the updated version directory. If the number of rollback times of the preset version is multiple, the functional branch corresponding to each branch identifier keeps the version directory and the previous version directory of the version directory, deletes other version directories which are not selected, and multiplies the number of the branch identifiers by the number of rollback times of the preset version to obtain an updated version directory.
As shown in fig. 3, the old version directory 301 (Release-21070117307.1 version) of the client is deleted after Release, and the last version directory 302 (Release-21070817307.8 version) of the newly released new version directory 303 (Release-21071517307.15 version) of the client can be kept after Release, as shown in fig. 3. As an optional embodiment, in the embodiment of the present disclosure, after the version directory is updated, the old version directory before updating still exists, the previous version file and the latest release version can be distinguished according to the version directory, and a situation that the version file is covered does not occur, so that it can be ensured that, in the release process of the version file, before the formal version of the Passenger service of the server is reloaded and applied, the client can correctly obtain the static file of the old version directory to continue to serve the user, and the problem of script error or style disorder caused by deletion or coverage of the version file is solved.
In an optional embodiment, outputting the version file to the version directory corresponding to the first version identification information includes:
step S302, based on the first version identification information, adjusting the output directory of the version file to the version directory;
step S304, copy the version file to the version directory.
In the embodiment of the present disclosure, by adjusting the configuration (such as Webpack) of the client packaging plug-in, based on the branch identification information and the time identification information, the output directory of the compiled target (version file) of the client is adjusted to be the version directory, and a server is adopted to create a corresponding version directory, and output the version files such as the client css and the static file js to different and corresponding version directories.
In an alternative embodiment, the branch identifier comprises one of: formal issuing branch marks and gray level issuing branch marks.
In an optional embodiment, the file publishing method further includes:
step S402, sending an access request message to the server, wherein the access request message is used for acquiring target operation data from the server;
step S404, receiving a response message returned by the server, where the information carried in the response message includes: the target operation data and second version identification information, where the second version identification information includes: the branch identifier and the second time identifier;
step S406, determining the prompt information to be issued based on the comparison result between the first time identifier and the second time identifier.
In this disclosure, the client is adopted to send an access request message to the server, the server adopts a filter to process each request, a version stored in a configuration file when each request is packaged is returned to the client through a Response Header, and the client receives a Response message returned by the server and compares the second time identifier carried in the Response message with the first time identifier.
Optionally, when the client accesses the server for the first time, the second version identification information returned by the server is stored in the browser, each subsequent request of the client compares whether the current version identification information is consistent with the version identification information returned by the server, and the prompt information to be issued is determined based on the comparison result of the version identification information.
In an optional embodiment, the determining, based on the comparison result between the first time identifier and the second time identifier, the prompt message to be issued includes:
step S502, when the first time identifier is earlier than the second time identifier, determining that the prompt information to be issued is first prompt information, where the first prompt information is used to prompt to update the first version identifier information to the second version identifier information;
step S504, when the first time identifier is later than the second time identifier, determining that the to-be-released prompt message is a second prompt message, where the second prompt message is used to prompt to roll back the first version identifier to the second version identifier.
In this disclosure, when the first time identifier is earlier than the second time identifier, determining that the prompt message to be issued is a first prompt message; when the first time identifier is later than the second time identifier, determining the prompt message to be issued as a second prompt message; updating or rolling back the version identification information according to the prompt information; if the prompt message to be issued is a first prompt message, updating the first version identification message to the second version identification message; and if the prompt message to be issued is a second prompt message, rolling back the first version identification message to the second version identification message.
Optionally, as shown in the schematic flow diagram of version file update or rollback shown in fig. 4, after the client sends the request, the stored current version identification information (i.e., the version number) is compared with the version identification information returned by the server, and if the time identifier of the version identification information returned by the service segment is larger, it indicates that a new version is issued, and immediately prompts the user whether to refresh the page; if the time identification of the version identification information returned by the server side is smaller, the rollback is applied to the old version. If the user does not use the system for a long time, the latest version number is obtained by accessing the background through the focus event of the window when the user activates the system window, and then whether the version numbers are consistent or not is judged.
According to the version file deployment process diagram shown in fig. 5, the server is adopted to publish the version file to be published acquired from the version directory, so that the copy and comparison processes of the version file are reduced, the old version file is reserved in the publishing process, and the problem of script errors or style disorder caused by deletion of the static file is avoided. The file release system is characterized in that more than 500 application examples are deployed on 30 left and right servers, the applications comprise formal versions, gray function 1 versions, gray function 2 versions and the like, the release time after adjustment is reduced from more than 20 minutes to about ten minutes, and the file release time is greatly saved. By adopting a rolling updating mode, the release process has almost no influence on the use of a user, the release of the version file is not required to be selected to be released in idle, and the user interface is not disordered or reported due to the change of the static file in the release process; after the application is released, the version is applied to the whole period of the user session, the change of the version number is monitored, and the user is prompted to refresh the page and pull the latest client code; if the user does not refresh the whole page all the time, the user can be reminded in time, and the user determines whether to refresh the page or not, so that the user experience is improved.
According to an embodiment of the present disclosure, an apparatus embodiment for implementing the file publishing method is further provided, and fig. 6 is a schematic structural diagram of a file publishing apparatus according to an embodiment of the present disclosure, and as shown in fig. 6, the file publishing apparatus includes: an acquisition module 60, a creation module 62, an output module 64, and a publishing module 66, wherein:
an obtaining module 60, configured to obtain first version identification information of a version file to be released, where the first version identification information includes: the system comprises a branch identifier and a first time identifier, wherein the branch identifier is used for describing a distribution channel of the version file, and the first time identifier is used for describing the packaging time of the version file;
a creating module 62, configured to create a corresponding version directory for the version file to be published in a shared directory according to the first version identification information, where the shared directory is a directory area shared by version directories corresponding to different version files to be published;
an output module 64, configured to output the version file to the version directory;
the publishing module 66 is configured to upload the version file to the server through the version directory, so that the server publishes the version file.
It should be noted that the above-mentioned obtaining module 60, creating module 62, outputting module 64 and publishing module 66 can be implemented by software or hardware, for example, for the latter, the following manner can be implemented: the modules can be located in the same processor; alternatively, the modules may be located in different processors in any combination.
It should be noted here that the document issuing apparatus corresponds to steps S102 to S108 in the method embodiment, and the modules are the same as the examples and application scenarios realized by the corresponding steps, but are not limited to the disclosure of the method embodiment. It should be noted that the modules described above may be implemented in a computer terminal as part of an apparatus.
It should be noted that, for alternative or preferred embodiments of the present embodiment, reference may be made to the related description in the method embodiment, and details are not described herein again.
The file distribution device may further include a processor and a memory, and the file distribution device and the like are stored in the memory as a program unit, and the processor executes the program unit stored in the memory to realize corresponding functions.
The processor comprises a kernel, and the kernel calls a corresponding program unit from the memory, wherein one or more than one kernel can be arranged. The memory may include volatile memory in a computer readable medium, Random Access Memory (RAM) and/or nonvolatile memory such as Read Only Memory (ROM) or flash memory (flash RAM), and the memory includes at least one memory chip.
According to an embodiment of the present disclosure, there is also provided a computer-readable storage medium embodiment. Optionally, in this embodiment, the computer-readable storage medium includes a stored program, where when the program runs, the apparatus where the computer-readable storage medium is located is controlled to execute any one of the file publishing methods.
Optionally, in this embodiment, the computer-readable storage medium may be located in any one of a group of computer terminals in a computer network or in any one of a group of mobile terminals, and the computer-readable storage medium includes a stored program.
Optionally, the program when executed controls an apparatus in which the computer-readable storage medium is located to perform the following functions: acquiring first version identification information of a version file to be released, wherein the first version identification information comprises: the system comprises a branch identifier and a first time identifier, wherein the branch identifier is used for describing a distribution channel of the version file, and the first time identifier is used for describing the packaging time of the version file; creating a corresponding version directory for the version file to be released in a shared directory according to the first version identification information, wherein the shared directory is a directory area shared by version directories corresponding to different version files to be released; outputting the version file to the version directory; and uploading the version file to a server through the version directory so that the server issues the version file.
Optionally, the program when executed controls an apparatus in which the computer-readable storage medium is located to perform the following functions: acquiring the rollback times of the preset version and the branch identification; and selecting a version directory to be reserved from the shared directory according to the preset version rollback times and the branch identification, and deleting other unselected version directories to obtain an updated version directory.
Optionally, the program when executed controls an apparatus in which the computer-readable storage medium is located to perform the following functions: adjusting the output directory of the version file to the version directory based on the first version identification information; and copying the version file to the version directory.
Optionally, the program when executed controls an apparatus in which the computer-readable storage medium is located to perform the following functions: sending an access request message to the server, wherein the access request message is used for acquiring target operation data from the server; receiving a response message returned by the server, wherein the information carried in the response message includes: the target operation data and second version identification information, where the second version identification information includes: the branch identifier and the second time identifier; and determining prompt information to be issued based on the comparison result of the first time identifier and the second time identifier.
Optionally, the program when executed controls an apparatus in which the computer-readable storage medium is located to perform the following functions: when the first time identifier is earlier than the second time identifier, determining that the prompt message to be issued is a first prompt message, wherein the first prompt message is used for prompting to update the first version identifier message to the second version identifier message; and when the first time identifier is later than the second time identifier, determining that the prompt message to be issued is a second prompt message, wherein the second prompt message is used for prompting to roll back the first version identifier message to the second version identifier message.
According to an embodiment of the present disclosure, there is also provided an embodiment of a processor. Optionally, in this embodiment, the processor is configured to execute a program, where the program executes any one of the file publishing methods.
An embodiment of the present disclosure provides an electronic device, including a memory and a processor, where the memory stores a computer program, and the processor is configured to run the computer program to execute any one of the file publishing methods.
The present disclosure also provides a computer program product adapted to perform a program for initializing the following method steps when executed on a data processing device: determining a target evaluation question from the at least one evaluation question; sequentially determining a target evaluation object to be currently evaluated from the plurality of evaluation objects corresponding to the target evaluation questions; determining a target evaluation option corresponding to the target evaluation object from the plurality of evaluation options to be selected corresponding to the target evaluation subject, and switching from the target evaluation object to a next evaluation object so as to determine a target evaluation option corresponding to the next evaluation object from the plurality of evaluation options to be selected until all the evaluation objects are evaluated; and acquiring a file release result of each evaluation object based on the target evaluation option corresponding to each evaluation object in the plurality of evaluation objects.
Optionally, the program, when executed on a data processing device, is adapted to perform a procedure for initializing the following method steps: acquiring the rollback times of the preset version and the branch identification; and selecting a version directory to be reserved from the shared directory according to the preset version rollback times and the branch identification, and deleting other unselected version directories to obtain an updated version directory.
Optionally, the program, when executed on a data processing device, is adapted to perform a procedure for initializing the following method steps: adjusting the output directory of the version file to the version directory based on the first version identification information; and copying the version file to the version directory.
Optionally, the program, when executed on a data processing device, is adapted to perform a procedure for initializing the following method steps: sending an access request message to the server, wherein the access request message is used for acquiring target operation data from the server; receiving a response message returned by the server, wherein the information carried in the response message includes: the target operation data and second version identification information, where the second version identification information includes: the branch identifier and the second time identifier; and determining prompt information to be issued based on the comparison result of the first time identifier and the second time identifier.
Optionally, the program, when executed on a data processing device, is adapted to perform a procedure for initializing the following method steps: when the first time identifier is earlier than the second time identifier, determining that the prompt message to be issued is a first prompt message, wherein the first prompt message is used for prompting to update the first version identifier message to the second version identifier message; and when the first time identifier is later than the second time identifier, determining that the prompt message to be issued is a second prompt message, wherein the second prompt message is used for prompting to roll back the first version identifier message to the second version identifier message.
The above-mentioned serial numbers of the embodiments of the present disclosure are merely for description and do not represent the merits of the embodiments.
In the above embodiments of the present disclosure, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
In the embodiments provided in the present application, it should be understood that the disclosed technology can be implemented in other ways. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units may be a logical division, and in actual implementation, there may be another division, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, units or modules, and may be in an electrical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present disclosure may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present disclosure may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present disclosure. And the aforementioned storage medium includes: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.
The foregoing is merely a preferred embodiment of the present disclosure, and it should be noted that modifications and embellishments could be made by those skilled in the art without departing from the principle of the present disclosure, and these should also be considered as the protection scope of the present disclosure.
Claims (10)
1. A method for publishing a file, comprising:
acquiring first version identification information of a version file to be released, wherein the first version identification information comprises: the branch identifier is used for describing a distribution channel of the version file, and the first time identifier is used for describing the packaging time of the version file;
creating a corresponding version directory for the version file to be released in a shared directory according to the first version identification information, wherein the shared directory is a directory area shared by version directories corresponding to different version files to be released;
outputting the version file to the version directory;
and uploading the version file to a server through the version directory so that the server issues the version file.
2. The file publishing method according to claim 1, wherein the number of version directories stored in the shared directory is determined by a preset number of rollback versions and the branch identifier.
3. The file publishing method according to claim 2, wherein after the version file is uploaded to a server via the version directory so that the server publishes the version file, the method further comprises:
acquiring the rollback times of the preset version and the branch identification;
and selecting the version directory to be reserved from the shared directory according to the rolling-back times of the preset version and the branch identification, and deleting other version directories which are not selected to obtain an updated version directory.
4. The file publishing method according to claim 1, wherein outputting the version file to the version directory corresponding to the first version identification information comprises:
adjusting the output directory of the version file to the version directory based on the first version identification information;
copying the version file to the version directory.
5. The file publication method according to claim 1, wherein the branch identification comprises one of:
formal issuing branch marks and gray level issuing branch marks.
6. The file publishing method according to claim 1, further comprising:
sending an access request message to the server, wherein the access request message is used for acquiring target operation data from the server;
receiving a response message returned by the server, wherein the information carried in the response message includes: the target operation data and second version identification information, the second version identification information including: the branch identification and the second time identification;
and determining prompt information to be issued based on the comparison result of the first time identifier and the second time identifier.
7. The file publishing method according to claim 6, wherein determining the prompt message to be published based on the comparison result of the first time identifier and the second time identifier comprises:
when the first time identifier is earlier than the second time identifier, determining that the prompt information to be issued is first prompt information, wherein the first prompt information is used for prompting to update the first version identifier information to the second version identifier information;
and when the first time identifier is later than the second time identifier, determining that the prompt message to be issued is a second prompt message, wherein the second prompt message is used for prompting to roll back the first version identifier to the second version identifier.
8. A document issuing apparatus, characterized by comprising:
the system comprises an acquisition module and a release module, wherein the acquisition module is used for acquiring first version identification information of a version file to be released, and the first version identification information comprises: the branch identifier is used for describing a distribution channel of the version file, and the first time identifier is used for describing the packaging time of the version file;
the creating module is used for creating a corresponding version directory for the version files to be released in a shared directory according to the first version identification information, wherein the shared directory is a directory area shared by version directories corresponding to different version files to be released;
the output module is used for outputting the version file to the version directory;
and the release module is used for uploading the version file to a server through the version directory so as to enable the server to release the version file.
9. A non-volatile storage medium, characterized in that a computer program is stored in the storage medium, wherein the computer program is arranged to execute the file distribution method of any of claims 1 to 7 when running.
10. An electronic device comprising a memory and a processor, wherein the memory has stored therein a computer program, and the processor is configured to execute the computer program to perform the file distribution method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111424207.8A CN114296753A (en) | 2021-11-26 | 2021-11-26 | File publishing method and device, storage medium and electronic device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111424207.8A CN114296753A (en) | 2021-11-26 | 2021-11-26 | File publishing method and device, storage medium and electronic device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114296753A true CN114296753A (en) | 2022-04-08 |
Family
ID=80964770
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111424207.8A Pending CN114296753A (en) | 2021-11-26 | 2021-11-26 | File publishing method and device, storage medium and electronic device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114296753A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115408047A (en) * | 2022-08-11 | 2022-11-29 | 北京大氪信息科技有限公司 | Version release method and device and electronic equipment |
| CN115543394A (en) * | 2022-12-01 | 2022-12-30 | 云账户技术(天津)有限公司 | APP dynamic update management method and system, electronic device and readable storage medium |
-
2021
- 2021-11-26 CN CN202111424207.8A patent/CN114296753A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115408047A (en) * | 2022-08-11 | 2022-11-29 | 北京大氪信息科技有限公司 | Version release method and device and electronic equipment |
| CN115543394A (en) * | 2022-12-01 | 2022-12-30 | 云账户技术(天津)有限公司 | APP dynamic update management method and system, electronic device and readable storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10713034B2 (en) | Updating web resources | |
| US10694353B2 (en) | Updating web resources | |
| CN114296753A (en) | File publishing method and device, storage medium and electronic device | |
| US9792623B2 (en) | Advertisement processing method and apparatus | |
| US20140351807A1 (en) | Method and communication device for updating web application | |
| CN108520059A (en) | Loading method, system, computer equipment and the storage medium of the client H5 pages | |
| CN108874426B (en) | Application program updating method and device and readable storage medium | |
| CN104731869B (en) | The page shows method and device | |
| CN109522500B (en) | Webpage display method, device, terminal and storage medium | |
| CN111897564A (en) | Application updating method and system | |
| CN104809011B (en) | A kind of management method of application program | |
| CN107844306A (en) | Restorative procedure, device, storage medium and the terminal of application program | |
| CN103218221A (en) | Control switching method and device of software interface | |
| CN108132832B (en) | Application program starting method and device | |
| US20180341426A1 (en) | Method and device for clearing data and electronic device | |
| CN110874345A (en) | Data processing method, device and system in distributed storage system | |
| US9614932B2 (en) | Managing and implementing web application data snapshots | |
| CN110737852A (en) | Information processing method, information processing apparatus, electronic device, and medium | |
| CN109901849A (en) | Application program installation method, device, electronic equipment and storage medium | |
| CN110209402B (en) | Application installation method, electronic device and computer storage medium | |
| CN113326186A (en) | Software testing method and device, electronic equipment and storage medium | |
| CN112882733B (en) | Application updating method and device, electronic equipment and storage medium | |
| CN114281459B (en) | Resource acquisition method and related product | |
| CN113836875B (en) | Text processing method, system, device and storage medium | |
| CN112436953B (en) | Page data backup and disaster recovery page display method and device |
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 |