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

configuration is lost, and no new configuration possible

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • build-pipeline-plugin
    • None
    • ubuntu

      after updateing the build-pipeline to 1.3.4.1. And jenkins to 1.520 all my pipline configuration are gone. Any new configuration have no affect. On the pipline page there is this error message:

      makeStaplerProxy('/$stapler/bound/d3fbd014-3909-4a15-9246-39f5fd687e2e','95e5bbc943cc4cda47bb2806d8975deb',['triggerManualBuild','retryBuild','rerunBuild']), Handlebars.compile(buildCardTemplateSource), Handlebars.compile(projectCardTemplateSource), 3000);

          [JENKINS-18553] configuration is lost, and no new configuration possible

          Skuli Arnlaugsson added a comment - - edited

          I have the same result. Downgrading doesn't fix this.
          This plugin is vital to our process.

          The pipeline view appears like this now:
          http://www.webpagescreenshot.info/img/51d3f5a13d4a28-22873914

          Skuli Arnlaugsson added a comment - - edited I have the same result. Downgrading doesn't fix this. This plugin is vital to our process. The pipeline view appears like this now: http://www.webpagescreenshot.info/img/51d3f5a13d4a28-22873914

          My screen looks exactly like yours and downgrading doesn't help either

          Torsten Zander added a comment - My screen looks exactly like yours and downgrading doesn't help either

          Wojciech Żarski added a comment - - edited

          The same with my big installation. It happens after update to 1.520. Downgrade is useless.

          Wojciech Żarski added a comment - - edited The same with my big installation. It happens after update to 1.520. Downgrade is useless.

          Michael Chamberlain added a comment - I think this is the same as: https://issues.jenkins-ci.org/browse/JENKINS-18510 ??

          Geoff Bullen added a comment -

          Can someone confirm that this is resolved in 1.3.5?

          Geoff Bullen added a comment - Can someone confirm that this is resolved in 1.3.5?

          Yes, it's fixed now. Thank you!!

          Michael Chamberlain added a comment - Yes, it's fixed now. Thank you!!

          Same here, fixed after 1.3.5 update - note that the configuration (start/initial job for example) is still lost, but adding them again fixes the view.

          Skuli Arnlaugsson added a comment - Same here, fixed after 1.3.5 update - note that the configuration (start/initial job for example) is still lost, but adding them again fixes the view.

            Unassigned Unassigned
            torstenzander Torsten Zander
            Votes:
            10 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated:
              Resolved: