delete work space config not working

31 views
Skip to first unread message

Doug Whitfield

unread,
Mar 23, 2021, 8:03:46 PM3/23/21
to Jenkins Users
I have a customer that when she tries to enable the setting ‘Delete work space before build starts’ and hit save the setting is not set properly when going back to the config. Neither of us see an error or indication as to why so far. There is nothing in the logs that would indicate some went wrong. All other settings seem to save correctly. Only settings in the ‘build environment’ section of the configuration don’t seem to get saved.

This happens in multiple browsers.

Is there any user-level info I should be looking at? As far as I am aware, this only happens to one user.

Thanks!

Here is the list of active plugins:
ace-editor:1.1
active-directory:2.23
all-changes:1.5
allure-jenkins-plugin:2.29.0
analysis-model-api:9.8.1
ansicolor:0.7.5
ant:1.11
antisamy-markup-formatter:2.1
anything-goes-formatter:1.0
apache-httpcomponents-client-4-api:4.5.13-1.0
appaloosa-plugin:1.4.11
artifactdeployer:1.2
async-http-client:1.9.40.0
audit-trail:3.8
authentication-tokens:1.4
authorize-project:1.4.0
basic-branch-build-strategies:1.3.2
bitbucket:1.1.27
bootstrap4-api:4.6.0-2
bouncycastle-api:2.20
branch-api:2.6.3
build-cause-run-condition:0.1
build-flow-plugin:0.20
build-metrics:1.3
build-name-setter:2.1.0
build-pipeline-plugin:1.5.8
build-timeout:1.20
build-user-vars-plugin:1.7
build-view-column:0.3
build-with-parameters:1.5
buildgraph-view:1.8
built-on-column:1.1
checks-api:1.6.0
clearcase:1.6.6
cloudbees-bitbucket-branch-source:2.9.7
cloudbees-folder:6.15
cmakebuilder:2.6.3
cobertura:1.16
code-coverage-api:1.3.2
command-launcher:1.5
conditional-buildstep:1.4.1
config-file-provider:3.7.0
configuration-as-code:1.47
copyartifact:1.46
cppcheck:1.25
credentials:2.3.15
credentials-binding:1.24
custom-job-icon:0.2
cvs:2.18
dashboard-view:2.15
data-tables-api:1.10.23-3
database:1.7
database-postgresql:1.2
deployed-on-column:1.8
deployer-framework:1.3
disk-usage:0.28
display-url-api:2.3.4
docker-commons:1.17
docker-java-api:3.0.14
docker-workflow:1.26
downstream-ext:1.8
doxygen:0.18
dtkit-api:3.0.0
durable-task:1.35
echarts-api:5.0.1-1
email-ext:2.82
emailext-template:1.2
embeddable-build-status:2.0.3
emma:1.29
envinject:2.4.0
envinject-api:1.7
extended-choice-parameter:0.82
extended-read-permission:3.2
extensible-choice-parameter:1.7.0
external-monitor-job:1.7
font-awesome-api:5.15.2-2
forensics-api:1.0.0
git:4.6.0
git-client:3.6.0
git-parameter:0.9.13
git-server:1.9
github:1.33.1
github-api:1.123
github-branch-source:2.10.2
gitlab-merge-request-jenkins:2.0.0
gitlab-plugin:1.5.19
global-build-stats:1.5
global-variable-string-parameter:1.2
gradle:1.36
greenballs:1.15.1
handlebars:1.1.1
handy-uri-templates-2-api:2.1.8-1.0
html5-notifier-plugin:1.5
htmlpublisher:1.25
hudson-pview-plugin:1.8
hudson-wsclean-plugin:1.0.8
ignore-committer-strategy:1.0.4
ivy:1.28
jackson2-api:2.12.1
javadoc:1.6
jaxb:2.3.0.1
jdk-tool:1.5
jenkins-jira-issue-updater:1.18
jenkins-multijob-plugin:1.36
jira:3.2
jjwt-api:0.11.2-9.c8b45b8bb173
job-import-plugin:3.4
jobConfigHistory:2.26
join:1.21
jquery:1.12.4-1
jquery-detached:1.2.1
jquery3-api:3.5.1-3
jsch:0.1.55.2
jsunit:1.6
junit:1.49
klocwork:2020.3.1
ldap:1.26
locale:1.4
lockable-resources:2.10
log-parser:2.1
mail-watcher-plugin:1.16
mailer:1.32.1
mapdb-api:1.0.9.0
matrix-auth:2.6.6
matrix-project:1.18
maven-plugin:3.10
maven-repo-cleaner:1.2
mercurial:2.12
metrics:4.0.2.7
momentjs:1.1.1
monitoring:1.76.0
msbuild:1.30
mstest:1.0.0
mstestrunner:1.3.0
ncover:0.3
nodejs:1.3.5
nodelabelparameter:1.7.2
okhttp-api:3.14.9
p4:1.11.3
pam-auth:1.6
Parameterized-Remote-Trigger:3.1.5.1
parameterized-scheduler:0.9.2
parameterized-trigger:2.40
pipeline-build-step:2.13
pipeline-github-lib:1.0
pipeline-graph-analysis:1.10
pipeline-input-step:2.12
pipeline-milestone-step:1.3.2
pipeline-model-api:1.8.4
pipeline-model-definition:1.8.4
pipeline-model-extensions:1.8.4
pipeline-rest-api:2.19
pipeline-stage-step:2.5
pipeline-stage-tags-metadata:1.8.4
pipeline-stage-view:2.19
plain-credentials:1.7
plugin-util-api:2.0.0
popper-api:1.16.1-2
postbuild-task:1.9
prereq-buildstep:1.1
progress-bar-column-plugin:1.0
project-stats-plugin:0.4
promoted-builds:3.9
publish-over:0.22
publish-over-cifs:0.12
publish-over-ssh:1.22
python:1.3
rebuild:1.32
repo:1.14.0
resource-disposer:0.15
role-strategy:3.1.1
ruby-runtime:0.12
run-condition:1.5
run-condition-extras:0.3
saml:2.0.2
schedule-build:0.5.1
scm-api:2.6.4
script-security:1.76
shelve-project-plugin:3.1
sidebar-link:1.12.0
simpleclearcase:1.2.2
sloccount:1.24
snakeyaml-api:1.27.0
sonar:2.13
ssh:2.6.1
ssh-agent:1.17
ssh-credentials:1.18.1
ssh-slaves:1.29.4
structs:1.22
subversion:2.14.0
support-core:2.72.1
svn-tag:1.18
template-project:1.5.2
testcomplete-xunit:1.1
tfs:5.157.1
throttle-concurrents:2.0.2
timestamper:1.12
token-macro:2.15
translation:1.16
trilead-api:1.0.13
unique-id:2.2.0
uno-choice:2.5.5
urltrigger:0.48
valgrind:0.28
validating-string-parameter:2.8
variant:1.4
view-job-filters:2.3
warnings-ng:8.10.1
windows-slaves:1.7
workflow-aggregator:2.6
workflow-api:2.41
workflow-basic-steps:2.23
workflow-cps:2.90
workflow-cps-global-lib:2.18
workflow-durable-task-step:2.38
workflow-job:2.40
workflow-multibranch:2.22
workflow-scm-step:2.12
workflow-step-api:2.23
workflow-support:3.8
ws-cleanup:0.39
xunit:1.102
xvnc:1.25
zephyr-enterprise-test-management:2.2


Doug

Mark Waite

unread,
Mar 24, 2021, 12:42:10 AM3/24/21
to Jenkins Users
If they are using Jenkins 2.277.1 then they will need to remove the TFS plugin.  It has a known security vulnerability and a known issue with the Jenkins 2.277.1 configuration form modernization.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/8da88f8d-5951-4122-8283-517b107463a8n%40googlegroups.com.

Doug Whitfield

unread,
Mar 24, 2021, 9:17:30 AM3/24/21
to Jenkins Users
Thanks Mark! The version rolled off the log, but the customer removed the plugin and that resolved the problem. For anyone else that runs into this, here's the relevant JIRA: https://issues.jenkins.io/browse/JENKINS-65141
Reply all
Reply to author
Forward
0 new messages