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

Mandatory field Maven version, prevents from running in different nodes

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Blocker
    • Resolution: Unresolved
    • Component/s: maven-plugin
    • Labels:
      None
    • Environment:
      Jenkins ver. 2.73.3
    • Similar Issues:

      Description

      as you can see in the screenshot, at build step of a maven project there is a mandatory filed called maven version, that we didn't have in the past.
      This causes the following problem:
      let's say we have multiple OS nodes (windows, linux, macOS), and you want to run a specific job. By choosing a maven version though, you automatically choose explicitly which nodes are possible candidates for the job.
      What can be done?

        Attachments

          Activity

          Hide
          oleg_nenashev Oleg Nenashev added a comment -
          Show
          oleg_nenashev Oleg Nenashev added a comment - CC Arnaud Héritier
          Hide
          aheritier Arnaud Héritier added a comment -

          I'm not aware of any change about this Stelios Pap

          Which version of the maven plugin are you using ?

          Didn't you add new installers in the Tools Configuration because AFAIR this option appears only if you defined more than 1 Maven installer ?

          Show
          aheritier Arnaud Héritier added a comment - I'm not aware of any change about this Stelios Pap Which version of the maven plugin are you using ? Didn't you add new installers in the Tools Configuration because AFAIR this option appears only if you defined more than 1 Maven installer ?

            People

            • Assignee:
              Unassigned
              Reporter:
              steliosp Stelios Pap
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: