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

Empty MAVEN_OPTS getting added to every node configuration

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • gradle-plugin
    • None
    • gradle-plugin 2.3.2

      Ever since we upgraded to the gradle plugin 2.3, we get the following configuration entry for every node configuration.

      The global MAVEN_OPTS variable is empty. However even after configuring some value the global variable, the local node-specific entries will still stay empty.

      When I remove the configuration from the nodes, it will reappear after a Jenkins restart.

          [JENKINS-70663] Empty MAVEN_OPTS getting added to every node configuration

          Joerg Schwaerzler created issue -
          Joerg Schwaerzler made changes -
          Component/s New: gradle-plugin [ 15547 ]
          Component/s Original: core [ 15593 ]
          Description Original: Ever since we upgraded to Jenkins 2.375.3 (from 2.375.2), and upgraded the following plugins to the versions listed above (at the same time unfortunately), we get the following configuration entry for every node configuration.


          {code}
          snakeyaml-api.jpi
          kubernetes.jpi
          kubernetes-client-api.jpi
          timestamper.jpi
          throttle-concurrents.jpi
          resource-disposer.jpi
          workflow-multibranch.jpi
          workflow-cps.jpi
          pipeline-build-step.jpi
          workflow-basic-steps.jpi
          workflow-durable-task-step.jpi
          pipeline-graph-view.jpi
          performance.jpi
          okhttp-api.jpi
          junit.jpi
          javax-mail-api.jpi
          javax-activation-api.jpi
          jakarta-mail-api.jpi
          jakarta-activation-api.jpi
          gradle.jpi
          embeddable-build-status.jpi
          email-ext.jpi
          {code}

           !image-2023-02-21-19-27-21-840.png|thumbnail!

          The global MAVEN_OPTS variable is empty. However even after configuring some value the global variable, the local node-specific entries will still stay empty.

          When I remove the configuration from the nodes, it will reappear after a Jenkins restart.

          I am not 100% sure that this relates to the Jenkins update. However all the updated plugins do not seem to relate to this, either.

          Somehow I do not believe that this works as expected.
          New: Ever since we upgraded to the gradle plugin 2.3, we get the following configuration entry for every node configuration.

          !image-2023-02-21-19-27-21-840.png|thumbnail!

          The global MAVEN_OPTS variable is empty. However even after configuring some value the global variable, the local node-specific entries will still stay empty.

          When I remove the configuration from the nodes, it will reappear after a Jenkins restart.
          Jens Beyer made changes -
          Link New: This issue is related to JENKINS-70692 [ JENKINS-70692 ]
          Alexey Venderov made changes -
          Assignee New: Alexey Venderov [ avenderov ]
          Alexey Venderov made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Alexey Venderov made changes -
          Status Original: In Progress [ 3 ] New: In Review [ 10005 ]
          Alexey Venderov made changes -
          Released As New: gradle-plugin 2.3.2
          Resolution New: Fixed [ 1 ]
          Status Original: In Review [ 10005 ] New: Resolved [ 5 ]
          Alexey Venderov made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]

            avenderov Alexey Venderov
            macdrega Joerg Schwaerzler
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: