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

Warnings plugin does not save regexp list of files to ignore

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • warnings-plugin
    • None
    • Debian-based Linux x86_64
      Kernel 3.19.0-22-generic
      Java version 1.7.0_79
      Jenkins 1.627 (direct)
      Warnings plugin 4.49
      Google Chrome 5.0.2454.85 m (64-bit)

      When editing a project in the web ui, anything written in the field for files to ignore is then gone when the configuration view is opened again.
      Also, they are not applied (verified by executing a build and noticing warnings that should be ignored are back again). Plugins were updated this weekend. Everything worked last week.
      Also, by editing the config.xml by hand to get this field back:
      <excludePattern>./EEPROM\.h,./Dns\.cpp,./socket\.cpp,./util\.h,./Servo\.cpp,./Adafruit_NeoPixel\.cpp</excludePattern>
      and then reloading config from disk in Jenkins UI, job is working as expected again. And the patterns are visible when opening the job configuration in the ui, but if the job config is "saved" or "applied" in the web ui, the excludePattern tag is then removed completly from the job config file and the job breaks again.

          [JENKINS-30329] Warnings plugin does not save regexp list of files to ignore

          Patrick Fallberg added a comment -

          That was fast
          Any info on which version this is fixed in?

          Patrick Fallberg added a comment - That was fast Any info on which version this is fixed in?

          Ulli Hafner added a comment -

          https://github.com/jenkinsci/warnings-plugin/commits/master

          Ulli Hafner added a comment - https://github.com/jenkinsci/warnings-plugin/commits/master

          Patrick Fallberg added a comment -

          Excellent!

          Patrick Fallberg added a comment - Excellent!

          Patrick Fallberg added a comment -

          Should I close it, once I get hold of 4.50 and verify it? Or is the workflow different?

          Patrick Fallberg added a comment - Should I close it, once I get hold of 4.50 and verify it? Or is the workflow different?

          Ulli Hafner added a comment -

          Well, if you find the time, that would be great. But normally nobody has that time so most issues are still just resolved...

          Ulli Hafner added a comment - Well, if you find the time, that would be great. But normally nobody has that time so most issues are still just resolved...

          Patrick Fallberg added a comment -

          Of course I will in that case. If you have the time to fix an issue I report. I have the time to follow up on it.
          I will await for it to arrive "the official way" and test it, then I will close this issue if it works as before. If not, I will update the issue accordingly.
          Thanks for the fix!

          Patrick Fallberg added a comment - Of course I will in that case. If you have the time to fix an issue I report. I have the time to follow up on it. I will await for it to arrive "the official way" and test it, then I will close this issue if it works as before. If not, I will update the issue accordingly. Thanks for the fix!

          Patrick Fallberg added a comment -

          I have verified the fix in release 4.50. Thanks!

          Patrick Fallberg added a comment - I have verified the fix in release 4.50. Thanks!

            drulli Ulli Hafner
            fallberg Patrick Fallberg
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: