Method for automated software dependency adaptation

A method for adapting, in a first server computer,

• application software to a change in a dependency software component, the application software executing on a second server computer, the method comprising:
• obtaining by the first server computer a dependency descriptor comprising
• information identifying a plurality of dependency software components of the application software and, for each of the dependency software components of the plurality of the dependency software components:
• a third server computer associated with the dependency software component;
• and
• in-use version information identifying an in-use version of the dependency software component that was in use when the application software was last built,
• wherein each of the dependency software components comprises a software component that the application software uses during execution;
• for each of the dependency software components of the plurality of the dependency software components:
• obtaining by the first server computer current version information identifying a current version of the dependency software component from the third server computer associated with the dependency software component;
• comparing by the first server computer the current version information and the in-use version information to determine whether the current version is more recent than the in-use version;
• and
• if the current version is more recent than the in-use version, identifying by the first server computer the dependency software component as a changed dependency software component;
• obtaining by the first server computer the changed dependency software component, based on the information identifying the changed dependency software component;
• generating by the first server computer rebuilt application software by rebuilding source code of the application software using the changed dependency software component;
• determining by the first server computer whether the rebuilt application software was successfully generated;
• if the rebuilt application software was not successfully generated, sending by the first server computer a rebuild failure message to a user of the first server computer;
• and
• if the rebuilt application software was successfully generated:
• testing by the first server computer the rebuilt application software;
• determining by the first server computer whether testing of the rebuilt application software was successful;
• if the testing of the rebuilt application software was not successful, sending by the first server computer a testing failure message to the user of the first server computer;
• and
• if the testing of the rebuilt application software was successful, sending by the first server computer one or more messages configured to cause initiation of execution of the rebuilt application software.

A method for adapting, in a first server computer, application software to a change in a dependency software component, the application software executing on a second server computer, the method comprising:

• obtaining by the first server computer information identifying a changed dependency software component, where the changed dependency software component comprises a software component that the application software uses during execution;
• obtaining by the first server computer the changed dependency software component, based on the information identifying the changed dependency software component;
• entering a first loop for generating rebuilt application software, the first loop comprising:
• generating by the first server computer the rebuilt application software by
• rebuilding source code of the application software using the changed dependency software component;
• determining by the first server computer whether the rebuilt application software was successfully generated;
• exiting the first loop if the rebuilt application software was successfully generated;
• requesting by the first server computer rewritten source code from a user of the first server computer if the rebuilt application software was not successfully generated;
• receiving by the first server computer the rewritten source code from the user of the first server computer;
• and
• replacing by the first server computer the source code of the application software with the rewritten source code;
• entering a second loop for testing the rebuilt application software, the second loop comprising:
• testing by the first server computer the rebuilt application software to generate a tested rebuilt application software;
• determining by the first server computer whether testing of the rebuilt application software was successful;
• exiting the second loop if the testing of the rebuilt application software was successful;
• requesting by the first server computer the rewritten source code from the user of the first server computer if the testing of the rebuilt application software was not successful;
• receiving by the first server computer the rewritten source code from the user of the first server computer;
• replacing by the first server computer the source code of the application software with the rewritten source code;
• and
• exiting the second loop and restarting the first loop;
• and
• sending by the first server computer one or more messages configured to cause initiation of execution of the tested rebuilt application software.