Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-66477

Add support for changing NODE_NAME

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: ec2-plugin
    • Labels:
      None
    • Environment:
      Jenkins 2.289.2
      EC2 Plugin 1.63
    • Similar Issues:

      Description

      Nodes are currently named using this pattern:

      EC2 (Your cloud name) - Your AMI Name (i-123456)

      There is other software that consumes `env.NODE_NAME` (like the P4 Plugin) and the spaces can cause problems. Can we have support for changing the node naming pattern?

      I notice that if `Jenkins.checkGoodName()` fails, it will name the node after the instanceId alone. If I knew of a way to short-circuit that method I could achieve this without any code changes.

      This blocks us from using the EC2 Plugin as we are unable to get the nodes to play nicely with our source control system (Perforce).

        Attachments

          Activity

          Hide
          raihaan Raihaan Shouhell added a comment -

          Sounds like the P4 plugin, probably should fix its behaviour with env.NODE_NAME

          Show
          raihaan Raihaan Shouhell added a comment - Sounds like the P4 plugin, probably should fix its behaviour with env.NODE_NAME

            People

            Assignee:
            thoulen FABRIZIO MANFREDI
            Reporter:
            jazzyjayx Jay Spang
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated: