Repository navigation
[JENKINS-53284] Changing default layout for workspace and builds should not be a warning for first time startup #19968
Description
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)
Originally reported by 
batmat, imported from: Changing default layout for workspace and builds should not be a warning for first time startup
- assignee: charanbir
- status: Fixed but Unreleased
- priority: Minor
- component(s): core
- label(s): evergreen, evergreen-triggered, newbie-friendly
- resolution: Fixed
- resolved: 2019-01-22T11:53:01+00:00
- votes: 0
- watchers: 2
- imported: 2025-11-24
Raw content of original issue
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)
Activity
jenkins-infra-bot commentedon Aug 28, 2018
Remote link associated with this issue:
jenkins-infra-bot commentedon Nov 9, 2018
charanbir:
Raw content of original comment:
Hi, this is my first time contributing to open source. I have submitted a pull request for this issue. Please let me know if there are any concerns.
jenkins-infra-bot commentedon Jan 22, 2019
Raw content of original comment:
charanbir we're almost there, see the updated PR. Hopefully, it should be mergeable today or so. Thanks again for your much appreciated work and your patience, sorry for the latency!