Skip to content

Procedures do not respect resource pool specified at configuration #96

@nikhilv

Description

@nikhilv

At the EC Hackathon (July) we saw this. Since not all agents are 5.4 and greater we really do need the ability to run on a certain set of resources.

We ask for the resource pool in the configuration and should select a resource from the pool at run time for all of our procedures.

To reproduce:

  1. Configure default pool to have pre 5.4 agents
  2. Attempt to create an S3 configuration
  3. Specify a pool that has 5.4 + agents in the configuration screen.

EXPECTED RESULT:
Configuration is created

ACTUAL RESULT:
Pool specified in step 3 is not honored and "cannot find ec-groovy" error message appears.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions