Project new version verification device, method, electronic equipment and storage medium

Abstract

The application relates to a project new version verification device, method, electronic equipment and storage medium. A code deployment script with a project new version storage command is developed in advance, and is uploaded to a test end together with the project new version. The test end has a version library, receives the storage command, backs up each project new version, and when the deployed project new version has a problem, the last project new version in the version library is called to be deployed, so that the problem that the original environment cannot be quickly and completely returned is solved.

Description

Technical Field

[0001] This invention relates to the field of version update technology, specifically to a verification device, method, electronic device, and storage medium for a new version of a project. Background Technology

[0002] In e-commerce systems that provide website functionality to end-users, including mobile and PC terminals, there are often differences between the development and client sides in terms of website display, text content, layout, and unknown bugs after upgrades. This can lead to a very poor user experience, and in severe cases, it can leave system vulnerabilities, causing losses to project operations. Furthermore, it is impossible to quickly revert to the original environment, requiring manual code restoration and data deletion, making a complete restoration impossible. Summary of the Invention

[0003] The purpose of this invention is to provide a verification device, method, electronic device, and storage medium for new project versions, addressing existing technologies. By advancing the verification process, it reduces issues such as website display problems, text content issues, layout problems, and unknown bugs after client version updates, thus minimizing impacts on user experience and economic benefits. The testing terminal of this invention has a version repository that receives storage commands to back up each new project version. When a problem arises with the deployed new project version, it calls the previous version from the repository for deployment, resolving the issue of being unable to quickly revert to the original environment and fully restore the original data.

[0004] Specifically, a verification device for a new version of a project includes: The development side is used to develop new versions of the project according to development needs and package them; upload packaged files and deployment files; The testing end is used to pre-store development requirements as verification parameters; receive the uploaded packaged files and deployment files; deploy the new version of the project and compare it with the pre-stored verification parameters for verification; The deployment file is used to deploy the new version of the project and to store the new version of the project in the command test terminal storage unit.

[0005] Furthermore, the new version of the project includes application code and database data.

[0006] Furthermore, the development end includes an encryption unit for encrypting new versions of the project; the testing end includes a decryption unit for decrypting new versions of the project.

[0007] Furthermore, the development end includes a compression unit; the compression unit is used to compress the packaged new version of the project; the testing end includes a decompression unit; the decompression unit is used to decompress the packaged new version of the project file.

[0008] Specifically, the verification method using a new version of the verification device for a project includes the following steps: Pre-store development requirements as verification parameters; Develop and package a new version of the project based on development requirements; Upload the packaged files and deployment files to the test server; Deploy and store the new version of the project; Verify that the new version of the project meets the development requirements.

[0009] Furthermore, the process of developing a new version of the project according to development needs also includes encrypting the new version of the project; and decrypting the new version of the project after uploading the packaged file to the test terminal.

[0010] Furthermore, the packaged project is compressed after the new version is released; the packaged file is decompressed after being uploaded to the test server.

[0011] Furthermore, verifying whether the new version of the project meets the development requirements includes: comparing the deployed new version of the project with the pre-stored verification parameters to determine whether the deployed new version of the project meets the development requirements; if it does, the current new version of the project is deployed to the test end, and code and data are updated, while the operations team deploys the current new version of the project to the client; if it does not, code and data are rolled back to the test end.

[0012] Specifically, an electronic device is characterized by comprising: a memory and at least one processor; wherein the memory stores computer-executable instructions; and the at least one processor executes the computer-executable instructions stored in the memory, causing the at least one processor to execute the verification method for a new version of the project as described above.

[0013] Specifically, a computer-readable storage medium is characterized in that it stores computer-executable instructions, which, when executed by a processor, implement the verification method for the new version of the project as described above.

[0014] The advantages of this invention are: This invention verifies updated versions on the testing side, moving the verification process forward. This reduces issues such as website display problems, text content issues, layout problems, and unknown bugs after upgrades, which can impact user experience and economic benefits. The invention pre-develops a code deployment script with a new project version storage command. This script is uploaded to the testing side along with the new project version. The testing side has a version control repository that receives the storage command and backs up each new project version. When a problem is found with the deployed new project version, the previous version from the repository is used for deployment, solving the problem of not being able to quickly revert to the original environment and fully restore the original data. To ensure the security and reliability of data transmission and installation / deployment, the new project version is encrypted during development and decrypted before being transmitted to the testing side. To speed up transmission, the packaged new project version is compressed during development and decompressed before being transmitted to the testing side. Attached Figure Description

[0015] Figure 1 This is a flowchart of a method for verifying a new version of a project. Figure 2 This is a schematic diagram of an interface for uploading a new version of a project package file and its corresponding deployment files; Figure 3 This is a schematic diagram of an interface used to store the packaged files for each new version of the built-in project. Figure 4 This is a schematic diagram of an embodiment of the computer device of the present invention. Detailed Implementation

[0016] The present invention will now be described in detail with reference to specific embodiments. These embodiments will help those skilled in the art to further understand the present invention, but do not limit the invention in any way. It should be noted that those skilled in the art can make several changes and improvements without departing from the concept of the present invention. These all fall within the protection scope of the present invention.

[0017] As used herein, the term "comprising" and its variations indicate open inclusion, meaning "including but not limited to". Unless otherwise stated, the terms "one example embodiment" and "an embodiment" mean "at least one example embodiment". The term "another embodiment" means "at least one additional embodiment", and so on, and may refer to different or the same objects. Other explicit and implicit definitions may also be included below.

[0018] This invention relates to the verification of automated deployment of new versions of e-commerce platform websites within an e-commerce new product launch system environment. It is understood that this invention involves the pre-developed code deployment script. This script can package and record each project version update and push it synchronously to the test server along with the new project version. The test server includes a decompression unit that automatically or manually decompresses the new project version file and deployment file, deploying the code of the new project version file to the test server, i.e., setting the new project version file as the deployment version. Simultaneously, the packaged new project version file includes configuration data, such as CMS content, product settings, and promotional configurations, which are updated to the test server.

[0019] All development in this invention is based on a fundamental development platform. Developers need to download the basic development components and develop in their local environment (e.g., a PHP framework). After development, the developed package is packaged and uploaded to the testing server for deployment and verification. This invention can be developed using a standard PHP framework, allowing for local code development and demonstration of database connection development. Deployment is automated.

[0020] This invention creates a database data storage design through a custom primary key architecture. All business operations use a non-auto-incrementing primary key design, and data records are stored by forcibly identifying the primary key, ensuring that data transfer and restoration are not affected by database limitations.

[0021] This invention provides a verification device for a new version of a project, comprising: The development side is used to develop new versions of the project according to development needs and package them; the development side uploads the packaged files and deployment files to the testing side.

[0022] The testing end is used to pre-store development requirements as verification parameters; receive the uploaded packaged files and deployment files; deploy the new version of the project and compare it with the pre-stored verification parameters for verification.

[0023] The deployment file is used to deploy the new version of the project and to store the new version of the project in the command test terminal storage unit, such as a version control repository. The new version of the project includes application code and database data. The database data is collected according to development requirements, converted into standard SQL statements, and for data security, time-saving, and convenience during transmission, the SQL statements are packaged together with the application code and compressed after built-in encryption. When the test terminal decompresses the SQL statements, it decrypts them to restore the original dataset and performs configuration.

[0024] Another embodiment provides a verification device for a new version of a project. The development end includes an encryption unit and a compression unit. The development end is used to develop a new version of the project according to development requirements. The encryption unit is used to encrypt the new version of the project, such as encrypting data. The encrypted new version of the project is then packaged and compressed. The development end displays the completed new version of the project package and the corresponding deployment files as follows: Figure 2 Upload the application to the test server via an interface such as a development package for testing.

[0025] The test server receives uploaded packaged files and deployment files. The deployment file is used to deploy the new version of the project and to send instructions to store the new version. The test server includes storage units, such as a version control repository, to pre-store development requirements as verification parameters and to store the new version's packaged file according to the instructions sent from the deployment file. The deployment file deploys the new version of the project on the test server. The deployment display results and configured data, including potential issues on mobile and PC terminals such as website display, text content, and unknown bugs after upgrades, are compared with the pre-stored verification parameters to determine whether the deployment of the new version meets the development requirements.

[0026] This invention provides a verification method using a verification device for a new version of a project, comprising the following steps: S110: Pre-store development requirements as verification parameters. Specifically, for projects that require version updates, pre-store development requirements as verification parameters on the testing side.

[0027] S120: Develop and package a new version of the project according to development requirements. This includes encrypting the new version and compressing it after packaging. The new version includes configurable data, display layout format, and initialization data.

[0028] S130: Upload the packaged files and deployment files to the test server.

[0029] S140: Deploy and store the new version of the project. This process on the test side includes receiving the packaged file uploaded by the development side, backing up the packaged file of the new version of the built-in project, and decompressing the packaged file to obtain the decompressed file (i.e., the new version of the project). The decompressed file is then decrypted. The test side includes a version control repository to store the packaged files of each new version of the built-in project, as shown in the attached document. Figure 3 .

[0030] S150: Verify whether the new version of the project meets the development requirements. Specifically, this includes comparing the deployed new version of the project with the pre-stored verification parameters to determine whether the deployed new version of the project meets the development requirements. If it does, the new version of the current project is deployed to the test server, and code and data are updated. The operations team then deploys the new version of the current project to the client. If it does not meet the requirements, code and data are rolled back to the test server, and the operations team does not update the version on the client.

[0031] For example, such as Figure 3 The platform needs to add a link to a cup for the Double Eleven shopping festival. A development requirements document should be created based on the cup's color, size, shape, and display format, and stored on the testing side as verification parameters. The development team receives the requirements, develops a new version of the project, and encrypts and packages the new version, including configurable data, display layout format, and initialization data. The packaged file is then compressed. The compressed packaged file and the corresponding deployment files are then... Figure 2 As shown, the package is uploaded to the test server via an interface, such as the development package. After receiving the packaged file from the development server, the deployment file sends a storage instruction to the test server. The test server receives the storage instruction from the deployment file and backs up the packaged file containing the new version of the project. The test server also decompresses the packaged file. After decompression, it decrypts the encrypted files and deploys them as shown. Figure 3 Version 1.3. Reviewers compare pre-stored verification parameters with the automatically deployed new project version to determine if the deployed new version meets development requirements. For example, they check if the display format of the cup exhibit and the cup's configurable data (such as color, size, and shape) meet the development requirements. If the new project version fully meets the development requirements (i.e., the display format of the cup exhibit and the cup's configurable data all meet the development requirements), the current new project version overrides the previous new project version, with both code and data updated. If the new project version fails to meet one development requirement—for example, the display format of the cup exhibit meets the requirements, but the cup's size in the configurable data does not—then the code is rolled back and the data is rolled back to the previous version. Figure 3 Version 1.2. Since the test server has a repository that backs up the packaged files of each new version of the built-in project, if any item in the current new version of the project does not meet the development requirements during the verification process, the previous new version file of the project in the repository will be called to overwrite the deployment, i.e., code rollback and data rollback.

[0032] like Figure 4As shown, based on the same concept, the present invention also provides a computer device 400, which may vary considerably due to different configurations or performance. It may include one or more central processing units (CPUs) 410 (e.g., one or more processors) and a memory 420, and one or more storage media 430 (e.g., one or more mass storage devices) storing application programs 433 or data 432. The memory 420 and storage media 430 may be temporary or persistent storage. The program stored in the storage media 430 may include one or more modules (not shown in the figure), each module including a series of instruction operations on the computer device 400. Furthermore, the processor 410 may be configured to communicate with the storage media 430 and execute the series of instruction operations in the storage media 430 on the computer device 400.

[0033] Computer device 400 may also include one or more power supplies 440, one or more wired or wireless network interfaces 450, one or more input / output interfaces 460, and / or one or more operating systems 431, such as Windows Server, Mac OS X, Unix, Linux, FreeBSD, etc.

[0034] Those skilled in the art will understand that Figure 4 The computer device structure shown does not constitute a limitation on the computer device and may include more or fewer components than shown, or combinations of certain components, or different component arrangements.

[0035] When the computer-readable instructions are executed by the processor, the processor performs the following steps: pre-stores development requirements as verification parameters; develops and packages a new version of the project according to the development requirements; uploads the packaged file and deployment file to the test terminal; deploys and stores the new version of the project; and verifies whether the new version of the project meets the development requirements.

[0036] In one embodiment, a readable storage medium is provided, wherein when the computer-readable instructions are executed by one or more processors, the one or more processors perform the above-described steps, the specific steps of which will not be repeated here.

[0037] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0038] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0039] The above-described embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A verification device for a new version of a project, characterized in that, include: The development side is used to develop new versions of the project according to development needs and package them; upload packaged files and deployment files; The testing side is used to pre-store development requirements as verification parameters; Receive the uploaded packaged file and deployment file; deploy the new version of the project and compare it with the pre-stored verification parameters for verification; The deployment file is used to deploy the new version of the project and to command the test terminal storage unit to store the new version of the project. The configurable data, display layout format, and initialization data of the new version of the project are encrypted and packaged. The new version of the project includes application code and database data. The database data is collected according to the development requirements, and the development requirements are stored in advance on the test terminal as verification parameters. The data is converted into standard SQL statements. The SQL statements have built-in key encryption processing and are then packaged together with the application code and compressed. Verify whether the new version of the project meets the development requirements. This verification includes: comparing the deployed new version of the project with the pre-stored verification parameters to determine whether the display format and configurable data of the deployed new version of the project meet the development requirements; if they do, then deploy the current new version of the project to the test end, update the code and data, and the operations team will deploy the current new version of the project to the client. If the conditions are not met, code and data rollback will be performed on the test side.

2. The verification device for a new version of a project according to claim 1, characterized in that, The development end includes an encryption unit for encrypting new versions of the project; the testing end includes a decryption unit for decrypting new versions of the project.

3. The verification device for a new version of a project according to claim 1 or 2, characterized in that, The development end includes a compression unit; the compression unit is used to compress the packaged new version of the project; the testing end includes a decompression unit; the decompression unit is used to decompress the packaged new version of the project files.

4. A verification method using a verification device for a new version of a project as described in any one of claims 1-3, characterized in that, Includes the following steps: Pre-store development requirements as verification parameters; Develop and package a new version of the project based on development requirements; Upload the packaged files and deployment files to the test server; Deploy and store the new version of the project; Verify that the new version of the project meets the development requirements.

5. An electronic device, characterized in that, include: A memory and at least one processor; wherein the memory stores computer-executable instructions; and the at least one processor executes the computer-executable instructions stored in the memory, causing the at least one processor to perform the verification method for a new version of the project as described in claim 4.

6. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, implement the verification method for the new version of the project as described in claim 4.

Images