Versions Compared

Old Version 10

changes.mady.by.user Former user

Saved on

compared with

New Version 11

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Once a file has been moved to the archive folder it should no longer be modified. In the event that a file is updated in the archive folder there are a could couple of methods for fixing.

Archive files have been modified error

...

  1. On the packaging branch, find the commitID prior to when the archive file was modified.

    1. This commit containing the modified archive file should be present in the log in the section PACKAGING ORDER FOR COMMIT FILES.

    2. Image RemovedImage Added

      Look in SCM commit history or use ‘git log’ to find the commit prior to the archive file commit.

  2. Rename the existing packaging branch to eg. <branch>-archive. Instructions:

    1. Code Block
      git checkout <branch>
git branch -m <branch>-archive
git push origin -u <branch>-archive
git push origin --delete <branch>

  3. Create a new git branch from the commitID found in step 1. Use the original branch name. Instructions:

    1. Code Block
      git checkout <branch>-archive
git checkout -b <branch> <commit_id_prior_to_commit_where_archive_file_was_modified>
git push origin -u <branch>

    2. You should not need to update the deployPackager.properties <branch>.sqlScmLastImportID as you do in Method 1. That commitID should still be present in the branch you’ve just created.

  4. Run a Packaging job.

  5. Any SQL file changes made after the commitID will no longer be in the branch. They will needed to be added back. The <branch>-archive branch should be available for reference.

  6. Commit back to source control after adding back the changes and run Packaging job again.

...