[JIRA] (JENKINS-59734) mailer/email-ext settings persist after removing from JCasC yaml

16 views
Skip to first unread message

jonathan@riv.al (JIRA)

unread,
Oct 10, 2019, 4:52:03 PM10/10/19
to jenkinsc...@googlegroups.com
Jonathan B created an issue
 
Jenkins / Bug JENKINS-59734
mailer/email-ext settings persist after removing from JCasC yaml
Issue Type: Bug Bug
Assignee: Alex Earl
Components: email-ext-plugin, mailer-plugin
Created: 2019-10-10 20:51
Environment: Jenkins 2.190.1
mailer-plugin 1.29
email-ext 2.66
Priority: Minor Minor
Reporter: Jonathan B

We recently switched our existing Jenkins server over to configuration-as-code. Prior to the change, we had mailer and email-ext configured in a certain way. The new configuration yaml omits any configuration for those plugins because we no longer wish to configure them.

However, the Jenkins settings page (in the web UI) still shows the configuration that existed before, for both plugins. The files hudson.plugins.emailext.ExtendedEmailPublisher.xml and hudson.tasks.Mailer.xml in the Jenkins home directory both still exist and are populated.

Is this expected behavior?
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

slide.o.mix@gmail.com (JIRA)

unread,
Oct 10, 2019, 5:17:03 PM10/10/19
to jenkinsc...@googlegroups.com
Alex Earl commented on Bug JENKINS-59734
 
Re: mailer/email-ext settings persist after removing from JCasC yaml

If the files exist then they will be deserialized and the configuration will be populated. This is expected behavior.

slide.o.mix@gmail.com (JIRA)

unread,
Oct 10, 2019, 5:17:03 PM10/10/19
to jenkinsc...@googlegroups.com
Alex Earl closed an issue as Not A Defect
 
Change By: Alex Earl
Status: Open Closed
Resolution: Not A Defect

jonathan@riv.al (JIRA)

unread,
Oct 10, 2019, 5:21:02 PM10/10/19
to jenkinsc...@googlegroups.com
Jonathan B edited a comment on Bug JENKINS-59734
 
Re: mailer/email-ext settings persist after removing from JCasC yaml
The expectation is that, by omitting the files from configuration-as-code yaml , the plugin's configuration files on disk should be removed.

jonathan@riv.al (JIRA)

unread,
Oct 10, 2019, 5:21:03 PM10/10/19
to jenkinsc...@googlegroups.com

The expectation is that, by omitting the files from configuration-as-code, the plugin's configuration files on disk should be removed.

slide.o.mix@gmail.com (JIRA)

unread,
Oct 10, 2019, 5:45:03 PM10/10/19
to jenkinsc...@googlegroups.com

You would need to clean your JENKINS_HOME, configuration as code will not remove anything as far as I know.

jonathan@riv.al (JIRA)

unread,
Oct 11, 2019, 10:24:02 AM10/11/19
to jenkinsc...@googlegroups.com

Okay, thanks for your input.

Tim Jacomb Oleg Nenashev does this behavior sound correct to you? Would you consider it a bug in configuration-as-code?

o.v.nenashev@gmail.com (JIRA)

unread,
Oct 11, 2019, 10:32:01 AM10/11/19
to jenkinsc...@googlegroups.com

jonathan@riv.al (JIRA)

unread,
Oct 11, 2019, 10:36:02 AM10/11/19
to jenkinsc...@googlegroups.com

Thanks!
Reply all
Reply to author
Forward
0 new messages