Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
pcm32 authored Feb 11, 2024
1 parent 65c2ca8 commit 3f18415
Showing 1 changed file with 16 additions and 0 deletions.
16 changes: 16 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,22 @@ For development installation, we suggest following the github actions python-pac

Currently, tests run on python 3.9, so those are the recommended versions if not installing via conda. BKNN doesn't currently install on Python 3.10 due to a skip in Bioconda.

## How to update

Updating the stack that depends on this script is unfortunately complex, it gets all the way to Galaxy tools using this for production pipelines in at least two different institutions.

1. Open a branch here from develop
2. Change the conda dependencies versions desired in the test-env.yaml file (if any)
3. Make your changes in the branch (including adding any tests to the bats files for new areas or functionalities).
4. Iterate with the CI on the branch until all test pass with the new changes and dependencies.
5. Get reviews and merge to develop.
6. Open a bump branch in bioconda, making sure that it points to the develop branch of this repo rather than the pypi release and that all dependencies in bioconda reflect what is currently in the test-env.yaml file of this repo (which was used to test in the feature branch here in points 2 to 4).
7. Once the tests pass in bioconda, ask the bot to fetch the artifacts, download the linux artifact. Leave the bioconda branch in waiting, do not merge it (and probably add a message saying so)
8. Use the image .tar.gz inside the artifact to create a new local docker container on the linux machine where you intend to test the Galaxy tools.
9. Open a local feature branch on container-galaxy-sc repo to start trying the changes.
10. Change the scanpy-scripts macro2 requirements part to point to the newly created container.
11. Run planemo test, it should use the local container.

## Test installation

There is an example script included:
Expand Down

0 comments on commit 3f18415

Please sign in to comment.