Uploaded image for project: 'Indy Node'
  1. Indy Node
  2. INDY-1133

Optimize multiple agents per build usage by indy CI on Hyperledger Jenkins

    XMLWordPrintable

Details

    • Task
    • Status: Complete
    • Medium
    • Resolution: Done
    • None
    • None
    • None
    • None
    • Sprint 18.03 Stability, DKMS, Sprint 18.04

    Description

      Our pipelines for indy core have several stages each processed on Jenkins agents which are one-time on-demand OpenStack minions on Hyperledger Jenkins.

      As long as new agent launching is quite slow operation need to:

      • investigate how it actually happens on Hyperledger Jenkins for our case
      • optimize

      Optimization options:

      • optimize pipelines according to Hyperledger Jenkins specific
      • ask Hyperledger Jenkins admins to make number of hyp-x agents always available
      • ask Hyperledger Jenkins admins to allow reuse of launched agents

      Attachments

        Issue Links

          Activity

            People

              VladimirWork Vladimir Shishkin
              andkononykhin Andrey Kononykhin
              Andrey Kononykhin, Vladimir Shishkin
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: