EC2-plugin not spooling up stopped nodes, starting new nodes instead

This issue is archived. You can view it, but you can't modify it. Learn more

ExportXMLWordPrintable

      The Jenkins EC2 plugin isn't starting existing (stopped) nodes, instead, it always starts a new one. I can see the past instances as offline in the nodes tab, but instead of starting these nodes, the plugin always starts a new instance instead.

            Assignee:
            Unassigned
            Reporter:
            Bruno Esteves
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: