Versions Compared

Old Version 49

changes.mady.by.user Anton Vinogradov

Saved on

compared with

New Version 50

changes.mady.by.user Denis Magda

Saved on

Key

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

...

  • Fix / implement JIRA ticket in your fork. Provide Java docs whenever required. If you add a new package make sure that package-info.java file in it is in place with a description. Commit branch to origin (origin = your fork). It's recommended to develop IGNITE-xxx ticket at ignite-xxx branch.
  • Create pull request from the new remote branch in the fork to master of Apache Ignite mirror. Please, start a title of the pull request from 'IGNITE-xxx'. An email about the pull request will be send to dev-list and the same JIRA comment will be added to the IGNITE-xxx ticket.
  • Trigger all the validation of those test suites validation that have been affected by your changes on TeamCity:
    • Locate "Run All" row and press on a test suite you have to check, press button named "..." that is located on the left of "Run" button. If you're sure that there is no need to check all the suites then trigger a particular test suite only"Run custom build" dialog will appear;
    • Go to "Changes" tab and choose "pull/<pull-request-number>/head" in "Build branch" dropdown list;
    • Press "Run build" button and monitor tests results. 
  • Once tests are passed, the pull request can be reviewed and merged by a committer.

...