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

Allow designation of one JDK, Maven version, etc. as the default assigned to projects when the value is unspecified

    • Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Major Major
    • maven-plugin
    • None
    • Platform: All, OS: All

      Right now, we rely on envars in the script used to start Hudson to setup these
      default values, such as JDK and Maven version. This means each change requires
      restarting Hudson (a big task when you have a very heavily loaded server). It
      also means it's very difficult for the average user to find out what version of
      what tool is being used for a build.

      Instead, it would be nice to have a way to select which JDK, Maven version, Ant
      version, etc. one wants to use as the default, for cases where builds using that
      tool don't specify an explicit version. A simple radio group or drop-down
      selector for each tool type would probably be perfect, as long as Hudson can
      manage this default behavior.

          [JENKINS-4373] Allow designation of one JDK, Maven version, etc. as the default assigned to projects when the value is unspecified

          There are no comments yet on this issue.

            Unassigned Unassigned
            jdcasey jdcasey
            Votes:
            3 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: