Skip to content

DevBranch.md

Latest commit

 

History

History
68 lines (43 loc) · 4.03 KB

DevBranch.md

File metadata and controls

68 lines (43 loc) · 4.03 KB

Development branch

Attention: Dev branch is for the further development of AAPS only. It should be used on a separate phone for testing not for actual looping!

The most stable version of AAPS to use is that in the Master branch. It is advised to stay on the Master branch for actual looping.

The dev version of AAPS is only for developers and testers comfortable dealing with stacktraces, looking through log files and maybe firing up the debugger to produce bug reports that are helpful to the developers (in short: people that know what they are doing without being assisted!). Therefore many unfinished features are disabled. To enable these features enter Engineering Mode by creating a file named engineering_mode in directory /AAPS/extra . Enabling the engineering mode might break the loop entirely.

However, the Dev branch is a good place to see what features are being tested and to help iron out the bugs and give feedback on how the new features work in practice. Often people will test the Dev branch on an old phone and pump until they are confident it is stable - any use of it is at your own risk. When testing any new features, remember that you are choosing to test a still-in-development feature. Do so at your own risk & with due diligence to keep yourself safe.

If you find a bug or think something wrong has happened when using the Dev branch, then view the issues tab to check whether anyone else has found it, or add it yourself if not. The more information you can share here the better (don't forget you may need to share your log files. The new features can also be discussed on discord.

A dev version has an expiration date. This seems inconvenient when using it satisfactorily, but serves a purpose. When a single dev version doing the rounds, it is easier to keep track of bugs that people are reporting. The developers do not want to be in a position where there are three versions of dev in the wild where bugs are fixed in some and not others, and people continue to report the fixed ones.

(branch-ci-test)=

Test a specific branch (branch-ci)

To build a test branch, select branch-ci, which allows you to choose a specific branch for APK creation. You can use this method when you need to test the dev branch.

aaps_ci_branch_ci1

aaps_ci_branch_ci2

(github-pr-test)=

Test items in a pull request (GitHub CI actions deploy)

Available from 3.3.2.1.dev

  • Suitable for testers or those helping with testing.
.. raw:: html

    <!--crowdin: exclude-->
    <div align="center" style="max-width: 360px; margin: auto; margin-bottom: 2em;">
      <div style="position: relative; width: 100%; aspect-ratio: 9/16;">
        <iframe
          src="https://www.dailymotion.com/embed/video/x9rdx1q"
          style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"
          frameborder="0"
          allowfullscreen>
        </iframe>
      </div>
    </div>

aaps_ci_pr_ci

  • PR number: Please enter the PR number that you want to test.

  • PR reference types: PR reference types include two options:

    • head:

    • Fetches the actual content from the PR author’s branch (i.e., the original commit history without any merge operations).

    • This is equivalent to the original state of the PR branch, as if it were fetched directly from a fork or feature branch.

    • merge:

    • Fetches the result of GitHub’s pre-simulated merge of the PR into the target branch (e.g., dev).

    • This is a virtual merge commit automatically created by GitHub.

    • This commit only exists when the PR has no conflicts and is mergeable.

    • variant:

    • Please refer to