Versions Compared

Key

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

...

  • DevOps will only be used on the following University of Sydney projects:

  • For the initial release we will not be implementing destructiveChanges, but the implementation is scalable to do so.

    Status
    colourYellow
    titleCOMING SOON

...

  • If there are instances where only your project wanted to go to PROD, you would need to create a release/ branch

    • this ensures that only those items that you want to deploy (i.e. only the files that your team created) were deployed to PROD

  • branch out of master and name it as release/xxxxx (replace xxxxx with an identifier e.g. release/SPM_Release2)

  • update the .forceignore file with the files that you don’t want to include to your release. These are the files that are not part of the feature you wanted to release to PROD

    • Image RemovedImage Added
  • check out the newly created release/xxxxx branch and then merge uat into this branch

    • Most of the time, this will cause merge conflicts. Fix conflicts accordingly

    • you will still see the ignored files. That’s okay because when the package is validated, all the files you put on .forceignore will be ignored

  • once conflicts are resolved, push this to remote and do a Pull Request between the release branch and the master

  • You can check the package to be deployed listed as a manifest on the Pull Request by clicking the cat ./manifest/package/package.xml section

    • Image RemovedImage Added
  • You can also download the logs so you can copy the manifest and confirm the items that you are about to deploy before you commit

    • Image RemovedImage Added
  • approve and merge as per normal

...