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

Upgrading to 1.2.0 of the liquibase plugin may result in old-data warning

    Details

    • Similar Issues:

      Description

      This may also manifest itself in seeing the message "No changesets executed" on previously executed rollback jobs. Which is technically correct, but a message that was not shown in previous versions.

      Mainly a cosmetic issue.

      The problem was introduced when ExecutedChangesetAction#rollbackOnly was renamed but not accounted. (see https://wiki.jenkins-ci.org/display/JENKINS/Hint+on+retaining+backward+compatibility ).

      Resolution will involve providing migration in a readResolve method.

        Attachments

          Activity

          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: propspero238
          Path:
          src/main/java/org/jenkinsci/plugins/liquibase/evaluator/ExecutedChangesetAction.java
          http://jenkins-ci.org/commit/liquibase-runner-plugin/a764793f69d59364cb14235fdda25e19e5886980
          Log:
          JENKINS-40919
          provide migration for rollbackOnly field

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: propspero238 Path: src/main/java/org/jenkinsci/plugins/liquibase/evaluator/ExecutedChangesetAction.java http://jenkins-ci.org/commit/liquibase-runner-plugin/a764793f69d59364cb14235fdda25e19e5886980 Log: JENKINS-40919 provide migration for rollbackOnly field

            People

            • Assignee:
              prospero238 Keith Collison
              Reporter:
              prospero238 Keith Collison
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: