Managing software assets installed in an integrated development environment

• US 10,365,919 B1
• Filed: 05/17/2017
• Issued: 07/30/2019
• Est. Priority Date: 03/09/2016
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google LLC (Alphabet Inc.)
• Inventors: Mandrika, Konstantin V., Willis, Matthew Ryan, Shah, Hemal, Sason, Tali Jill, Adib, Artur Borges
• Primary Examiner(s): Wang, Philip
• Application Number:
  US15/597,258
• Time in Patent Office: 804 Days
• Field of Search: None
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

A software plugin integrated with the development environment maintains a list of independently managed assets that are installed within the development environment. The independently managed assets are provided by an entity with which the software plugin can communicate to determine whether newer versions of the assets have been released. The software plugin automatically downloads and installs the newer version of the assets with minimal, if any, user intervention. Further, the software plugin monitors the interdependencies between different assets installed within the development environment. When updating to a newer version of an asset, the software plugin identifies any conflicts that may occur with regards to the interdependencies when the asset is updated.

Claims

1. A computer-implemented method comprising:

providing, to a device associated with a user of an integrated development environment (IDE), an asset management user interface that identifies one or more independently managed software assets that are (i) published to an asset database by an asset tracking system, (ii) not currently installed in the IDE, and (iii) available for download;

receiving data identifying a particular software asset that was selected through the asset management user interface;

in response to receiving the data identifying the particular software asset, providing, to the device associated with the user of the IDE and through the asset management user interface, a representation of an asset-specific onboarding flow associated with the particular software asset, the onboarding flow including a control for initiating installation of the particular software asset within the IDE;

receiving data indicating a selection of the control for initiating installation of the particular software asset within the IDE; and

in response to receiving the data indicating the selection of the control for initiating installation of the particular software asset within the IDE, providing, to the device associated with the user of the IDE and through the asset management user interface, an indication that the particular software asset has been installed within the IDE.

2. The method of claim 1, comprising, in response to receiving the data indicating the selection of the control for initiating installation of the particular software asset within the IDE, triggering the IDE to download files associated with the particular software asset from the asset database.

3. The method of claim 2, comprising:

in response to receiving the data indicating the selection of the control for initiating installation of the particular software asset within the IDE, analyzing the downloaded files associated with the particular software asset from the asset database; and

based on analyzing the downloaded files associated with the particular software asset from the asset database, initializing the asset-specific onboarding flow associated with the particular software asset.

4. The method of claim 3, comprising, in response to initializing the asset-specific onboarding flow associated with the particular software asset, providing, to the device associated with the user of the IDE and through the asset management user interface, control for one or more of viewing information associated with the particular software asset and configuring attributes associated with the particular software asset.

5. The method of claim 1, comprising updating the asset management user interface that identifies one or more independently managed software assets to indicate that (i) the particular software asset has been installed within the IDE and (ii) a version identifier associated with a version of the particular software asset has been installed within the IDE.

6. The method of claim 1, comprising:

generating, by the asset management user interface, a function name for instantiating the installation of the of the particular software asset within the IDE, the function name corresponding to a name of the particular software asset; and

in response to receiving the data indicating the selection of the control for initiating installation of the particular software asset within the IDE, calling the function to (i) initialize the asset-specific onboarding flow associated with the particular software asset and (ii) inject the asset-specific onboarding flow associated with the particular software asset into the asset management user interface.

7. The method of claim 1, wherein providing, to the device associated with the user of the IDE and through the asset management user interface, the representation of an asset-specific onboarding flow associated with the particular software asset comprises providing one or more representations including readme text associated with the particular software asset, a dependency of the particular software asset, a current version of the particular software asset, and version history of the particular software asset.

8. A system comprising:

one or more computers and one or more storage devices storing instructions that are operable, when executed by the one or more computers, to cause the one or more computers to perform operations comprising;

providing, to a device associated with a user of an integrated development environment (IDE), an asset management user interface that identifies one or more independently managed software assets that are (i) published to an asset database by an asset tracking system, (ii) not currently installed in the IDE, and (iii) available for download,

receiving data identifying a particular software asset that was selected through the asset management user interface,

in response to receiving the data identifying the particular software asset, providing, to the device associated with the user of the IDE and through the asset management user interface, a representation of an asset-specific onboarding flow associated with the particular software asset, the onboarding flow including a control for initiating installation of the particular software asset within the IDE,

receiving data indicating a selection of the control for initiating installation of the particular software asset within the IDE, and

in response to receiving the data indicating the selection of the control for initiating installation of the particular software asset within the IDE, providing, to the device associated with the user of the IDE and through the asset management user interface, an indication that the particular software asset has been installed within the IDE.

9. The system of claim 8, wherein the operations comprise, in response to receiving the data indicating the selection of the control for initiating installation of the particular software asset within the IDE, triggering the IDE to download files associated with the particular software asset from the asset database.

10. The system of claim 9, wherein the operations comprise:

in response to receiving the data indicating the selection of the control for initiating installation of the particular software asset within the IDE, analyzing the downloaded files associated with the particular software asset from the asset database; and

based on analyzing the downloaded files associated with the particular software asset from the asset database, initializing the asset-specific onboarding flow associated with the particular software asset.

11. The system of claim 10, wherein the operations comprise, in response to initializing the asset-specific onboarding flow associated with the particular software asset, providing, to the device associated with the user of the IDE and through the asset management user interface, control for one or more of viewing information associated with the particular software asset and configuring attributes associated with the particular software asset.

12. The system of claim 8, wherein the operations comprise updating the asset management user interface that identifies one or more independently managed software assets to indicate that (i) the particular software asset has been installed within the IDE and (ii) a version identifier associated with a version of the particular software asset has been installed within the IDE.

13. The system of claim 8, wherein the operations comprise:

generating, by the asset management user interface, a function name for instantiating the installation of the of the particular software asset within the IDE, the function name corresponding to a name of the particular software asset; and

in response to receiving the data indicating the selection of the control for initiating installation of the particular software asset within the IDE, calling the function to (i) initialize the asset-specific onboarding flow associated with the particular software asset and (ii) inject the asset-specific onboarding flow associated with the particular software asset into the asset management user interface.

14. The system of claim 8, wherein the operation of providing, to the device associated with the user of the IDE and through the asset management user interface, the representation of an asset-specific onboarding flow associated with the particular software asset comprises providing one or more representations including readme text associated with the particular software asset, a dependency of the particular software asset, a current version of the particular software asset, and version history of the particular software asset.

15. A non-transitory computer-readable medium storing software comprising instructions executable by one or more computers which, upon such execution, cause the one or more computers to perform operations comprising:

providing, to a device associated with a user of an integrated development environment (IDE), an asset management user interface that identifies one or more independently managed software assets that are (i) published to an asset database by an asset tracking system, (ii) not currently installed in the IDE, and (iii) available for download;

receiving data identifying a particular software asset that was selected through the asset management user interface;

in response to receiving the data identifying the particular software asset, providing, to the device associated with the user of the IDE and through the asset management user interface, a representation of an asset-specific onboarding flow associated with the particular software asset, the onboarding flow including a control for initiating installation of the particular software asset within the IDE;

receiving data indicating a selection of the control for initiating installation of the particular software asset within the IDE; and

in response to receiving the data indicating the selection of the control for initiating installation of the particular software asset within the IDE, providing, to the device associated with the user of the IDE and through the asset management user interface, an indication that the particular software asset has been installed within the IDE.

16. The non-transitory computer-readable medium of claim 15, wherein the operations comprise, in response to receiving the data indicating the selection of the control for initiating installation of the particular software asset within the IDE, triggering the IDE to download files associated with the particular software asset from the asset database.

17. The non-transitory computer-readable medium of claim 16, wherein the operations comprise:

in response to receiving the data indicating the selection of the control for initiating installation of the particular software asset within the IDE, analyzing the downloaded files associated with the particular software asset from the asset database; and

based on analyzing the downloaded files associated with the particular software asset from the asset database, initializing the asset-specific onboarding flow associated with the particular software asset.

18. The non-transitory computer-readable medium of claim 17, wherein the operations comprise, in response to initializing the asset-specific onboarding flow associated with the particular software asset, providing, to the device associated with the user of the IDE and through the asset management user interface, control for one or more of viewing information associated with the particular software asset and configuring attributes associated with the particular software asset.

19. The non-transitory computer-readable medium of claim 15, wherein the operations comprise updating the asset management user interface that identifies one or more independently managed software assets to indicate that (i) the particular software asset has been installed within the IDE and (ii) a version identifier associated with a version of the particular software asset has been installed within the IDE.

20. The non-transitory computer-readable medium of claim 15, wherein the operations comprise:

generating, by the asset management user interface, a function name for instantiating the installation of the of the particular software asset within the IDE, the function name corresponding to a name of the particular software asset; and

in response to receiving the data indicating the selection of the control for initiating installation of the particular software asset within the IDE, calling the function to (i) initialize the asset-specific onboarding flow associated with the particular software asset and (ii) inject the asset-specific onboarding flow associated with the particular software asset into the asset management user interface.