How to test a Merge Request or a new, unfinished feature [Instruction]

There might be some features that are in development that you might want to test. Now that we have this amazing system with CI pipelines that create a proper Krita build for Windows and Linux for every Merge Request, you can easily test a feature without building Krita yourself, even if that feature isn’t finished yet.

It’s not very obvious how to get from a Merge Request to a downloadable file though, hence this topic.

Note that the builds only last for a week (or two?..), so if a Merge Request wasn’t worked on for some time, or you want to test an older commit, in which case you need to ask a developer to rerun the pipeline for you (it doesn’t have to be the same developer, just someone with the rights to rerun it).

  1. Find the Merge Request you’re interested in on the list: Merge requests · Graphics / Krita · GitLab and click on it (or get the link from Feature Requests category etc.).

  2. Click Pipelines:

  3. Click on the latest pipeline → find a number that starts from # and click on it (it should be just underneath the Merge Request title, next to a MR number and a commit hash; none of the other numbers start with #, thankfully)

  4. Click windows-build or linux-build or or macos-build any of the android-builds (try to match your architecture). If your choice is blue or yellow, wait until it becomes a different color; if it’s red, complain to the person giving you the link; if it’s green, go ahead.

  5. On the right, you’ll see section called “Job Artifacts”, click “Browse”

  6. On Linux, first click the _packaging folder:


    And then the .AppImage file:

    Then give it execution rights and run it.

  7. On Windows:


    Then unpack the .zip file and run the krita.exe file.

  8. On MacOS:

  9. On Android:



    Then install the .apk file.

If you are curious to try it but don’t know what to test, you can try my current MR for the comic panels: Draft: Add Knife Tool prototype to Krita (!2331) · Merge requests · Graphics / Krita · GitLab

11 Likes

Perhaps it’s important to add how to make Krita use a different config and resource folder for testing, to not accidentally brake or change the current installation.

6 Likes

Which MR do you want to test?

(In that instance you’d need to have a developer’s account I think to run it, but asking a developer to run it is fine too).

There are Android builds here:

A developer’s account is basically any KDE’s contributor’s account that got rights to merge things into KDE’s source repositories. It’s not just Krita’s core team, you can just be a contributor and get this access. I think traditionally it required three non-trivial contributions plus you need a “mentor“ or “sponsor“ aka a person who will vouch for you that you should get it.