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

mailer/email-ext settings persist after removing from JCasC yaml

    XMLWordPrintable

Details

    Description

      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?

      Attachments

        Activity

          slide_o_mix Alex Earl added a comment -

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

          slide_o_mix Alex Earl added a comment - If the files exist then they will be deserialized and the configuration will be populated. This is expected behavior.
          jonathanb1 Jonathan B added a comment - - edited

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

          jonathanb1 Jonathan B added a comment - - edited The expectation is that, by omitting the files from configuration-as-code yaml, the plugin's configuration files on disk should be removed.
          slide_o_mix Alex Earl added a comment -

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

          slide_o_mix Alex Earl added a comment - You would need to clean your JENKINS_HOME, configuration as code will not remove anything as far as I know.
          jonathanb1 Jonathan B added a comment -

          Okay, thanks for your input.

          timja oleg_nenashev does this behavior sound correct to you? Would you consider it a bug in configuration-as-code?

          jonathanb1 Jonathan B added a comment - Okay, thanks for your input. timja oleg_nenashev does this behavior sound correct to you? Would you consider it a bug in configuration-as-code?
          oleg_nenashev Oleg Nenashev added a comment - Please seeĀ  https://github.com/jenkinsci/configuration-as-code-plugin/issues/191 jonathanb1
          jonathanb1 Jonathan B added a comment -

          Thanks!

          jonathanb1 Jonathan B added a comment - Thanks!

          People

            slide_o_mix Alex Earl
            jonathanb1 Jonathan B
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: