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

Changing default layout for workspace and builds should not be a warning for first time startup

    • Evergreen - Milestone 1, Evergreen - Milestone 2
    • (towards) Jenkins 2.162

      Problem

      Currently, since JENKINS-50164, the messages Changing workspaces directories from ${JENKINS_HOME}/workspace/${ITEM_FULL_NAME} to ... and Changing builds directories from ${ITEM_ROOTDIR}/builds to /evergreen/data/jenkins/var/jobs/${ITEM_FULL_NAME}/builds will be always issued as a WARNING.

      Acceptance criteria

      • WARNING if:
        • any change on an already initialized JENKINS_HOME
      • NO WARNING if:
        • no JENKINS_HOME was initialized, i.e. it is a fresh first startup (e.g. like done for Jenkins Evergreen)

          [JENKINS-53284] Changing default layout for workspace and builds should not be a warning for first time startup

          Baptiste Mathus created issue -
          Baptiste Mathus made changes -
          Link New: This issue relates to JENKINS-50164 [ JENKINS-50164 ]
          Jesse Glick made changes -
          Link New: This issue relates to JENKINS-21942 [ JENKINS-21942 ]
          Baptiste Mathus made changes -
          Link New: This issue relates to JENKINS-53251 [ JENKINS-53251 ]
          R. Tyler Croy made changes -
          Sprint Original: Evergreen - Milestone 1 [ 511 ] New: Evergreen - Milestone 1, Evergreen - Milestone 2 [ 511, 516 ]
          R. Tyler Croy made changes -
          Assignee New: Baptiste Mathus [ batmat ]
          Baptiste Mathus made changes -
          Labels Original: evergreen evergreen-triggered New: evergreen evergreen-triggered newbie-friendly
          Baptiste Mathus made changes -
          Assignee Original: Baptiste Mathus [ batmat ]
          Baptiste Mathus made changes -
          Description Original: h3. Problem

          Currently, since JENKINS-50164, the message {{Changing workspaces directories from ${JENKINS_HOME}/workspace/${ITEM_FULL_NAME} to ...}} will be always issued as a WARNING.

          h3. Expected

          It should only be a WARNING for non-fresh startups changes. For all first time uses (like for Jenkins Evergreen), it should be only logged as {{INFO}}.
          New: h3. Problem

          Currently, since JENKINS-50164, the message {{Changing workspaces directories from ${JENKINS_HOME}/workspace/${ITEM_FULL_NAME} to ...}} will be always issued as a WARNING.

          h3. Acceptance criteria

          * WARNING if:
          ** any change on an already initialized JENKINS_HOME
          **
          * NO WARNING if:
          ** no JENKINS_HOME was initialized, i.e. it is a fresh first startup (e.g. like done for Jenkins Evergreen)
          Baptiste Mathus made changes -
          Description Original: h3. Problem

          Currently, since JENKINS-50164, the message {{Changing workspaces directories from ${JENKINS_HOME}/workspace/${ITEM_FULL_NAME} to ...}} will be always issued as a WARNING.

          h3. Acceptance criteria

          * WARNING if:
          ** any change on an already initialized JENKINS_HOME
          **
          * NO WARNING if:
          ** no JENKINS_HOME was initialized, i.e. it is a fresh first startup (e.g. like done for Jenkins Evergreen)
          New: h3. Problem

          Currently, since JENKINS-50164, the messages {{Changing workspaces directories from ${JENKINS_HOME}/workspace/${ITEM_FULL_NAME} to ...}} and {{Changing builds directories from ${ITEM_ROOTDIR}/builds to /evergreen/data/jenkins/var/jobs/${ITEM_FULL_NAME}/builds}} will be always issued as a WARNING.

          h3. Acceptance criteria

          * WARNING if:
          ** any change on an already initialized JENKINS_HOME
          **
          * NO WARNING if:
          ** no JENKINS_HOME was initialized, i.e. it is a fresh first startup (e.g. like done for Jenkins Evergreen)
          Baptiste Mathus made changes -
          Description Original: h3. Problem

          Currently, since JENKINS-50164, the messages {{Changing workspaces directories from ${JENKINS_HOME}/workspace/${ITEM_FULL_NAME} to ...}} and {{Changing builds directories from ${ITEM_ROOTDIR}/builds to /evergreen/data/jenkins/var/jobs/${ITEM_FULL_NAME}/builds}} will be always issued as a WARNING.

          h3. Acceptance criteria

          * WARNING if:
          ** any change on an already initialized JENKINS_HOME
          **
          * NO WARNING if:
          ** no JENKINS_HOME was initialized, i.e. it is a fresh first startup (e.g. like done for Jenkins Evergreen)
          New: h3. Problem

          Currently, since JENKINS-50164, the messages {{Changing workspaces directories from ${JENKINS_HOME}/workspace/${ITEM_FULL_NAME} to ...}} and {{Changing builds directories from ${ITEM_ROOTDIR}/builds to /evergreen/data/jenkins/var/jobs/${ITEM_FULL_NAME}/builds}} will be always issued as a WARNING.

          h3. Acceptance criteria

          * WARNING if:
          ** any change on an already initialized JENKINS_HOME

          * NO WARNING if:
          ** no JENKINS_HOME was initialized, i.e. it is a fresh first startup (e.g. like done for Jenkins Evergreen)

            charanbir C R
            batmat Baptiste Mathus
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: