August 9, 2019, Shanghai affected by Typhoon Lekima, the evening winds heavy rain.
Temporary work, cooperation channels WB report on micro-channel group in line accidents question: Grilled hurry to see the log records, the log shows everything is normal, I do not see where the bug in, WB did not claim that our CI received callback request. 7pm much, the stomach has been hungry, WB to say, look at the log CI nothing issue, first dismissed.
After time in the company building a corner, feeling faint this case the code of configuration items will not be a problem, and he was disturbed, and went back the rain. Turn on the computer, and then stroked it again when the code, bug like a dagger piercing the heart: FML, this path is actually testing path environment! The project team is the company's agile development teams, five will have a production version is released quickly to greet the staff responsible for version control, wait a minute, take a ride every week.
After determining the configuration path there is a problem: Urgent clear that inter-service call is to take the network or go outside the network, you do not NG forward, do not go away esb, communication is not to apply for permission. Briefly describe the times WB request: WB request of CI NG -------- "NG forward Mule service to the CI ----------" Mule service call Gateway ----- ----- "Gateway forwarded to applied micro services application ---------" Mule perform asynchronous callback service after application service response --------- "Mule WB service request interface address. Firewalls and related rights intermediate time being ignored, the current problem is: Mule perform asynchronous callback service after Application service response, what the Mule service specification is the internal interface address, the system will be responsible for the maintenance of some colleagues confirmed, we decided to go inside net Mulef5, this time responsible for maintaining the distribution center colleagues have work, and hard-coded priority method first on.
More than nine home, I feel the need to re-set the legacy of why this bug, 2018 Nian 11 month entered the CI's agile development teams. I started going to the Secretary fundamental lack of understanding of agile development, and later found that this is a near pipeline development model. As a developer can be a non-stop multi-threaded, from a cooperative business development needs to be involved in communication, network applications, application firewall permissions, configuration maintenance, data maintenance, multi-environment testing the FBI, online support. Every day was bombed various cooperative groups of micro letter, sometimes staring at the development of the document and the document needs analysis to cross-examine the correctness of the demand, and sometimes had to answer some questions on the business needs and develop ideas easily interrupted. For individual channels of cooperation fast speed pursuit docking omitted various documents and unit testing, the lack of review and management code. Rapid iteration, online support, this company level is no way to improve the short-term, in this mode, you should tease out the standard workflow patterns, in strict accordance with the process model to review before on-line, in order to avoid easy to overlook the small problem.
Case for the WB:
Phase One: On the stage of cooperation
Pre CI branch operations personnel and WB entered into a collaboration, cooperation determine product direction.
Phase II: On the demand stage
CI needs human intervention, through communication and scene analysis, reference WB cooperation interface documentation, analysis CI interface mapping relations, business related fields, to draw up a document for the development of needs analysis test.
Phase Three: Program to determine the stage
This stage developers have begun to develop, the development of needs analysis document confirming some problem and WB-party developers and CI-side demand and business people, developers at this stage mainly to solve the encryption and decryption, signing endorsement test, the test environment to apply. CI business people cooperation programs specifically WB WB cooperation agency information, CI business people synchronization programs and agencies and information to the test system.
Phase IV: Developer development phase
This stage is substantially divided into three sections: a first, Mule development; second, application development; third, CI maintenance.
Stage 5: Testing the FBI stage
This phase of the development environment is responsible for both the network rights, Ng forwarding path, Api open access rights, data maintenance. Testers involved in testing locally, through local testing, WB parties involved in the FBI.
Stage Six: production preparation stage
Test and production environments are very different in the network firewall permissions and control, mainly privileges and maintenance parameters. Shall process of combing all aspects permissions are opened, the parameters and WB to provide production parameters is different from mine. Confirmation performed on-line.