Allow Picasso to build images from Tutor main (not only released tags) #49
Description
We are using Picasso to build Tutor-based images for our Open edX deployment and our goal is to stay aligned with the latest platform code (edx-platform master).
Right now Picasso is tied to released Tutor versions (e.g. v20.0.2). There is a build problem affecting our images when using edx-platform master that is already fixed on Tutor main, but that fix is not yet included in v20.0.2. This leaves us in a gap where:
- v20.0.2 is supported by Picasso, but still has the build issue.
- Tutor main contains the fix, but Picasso cannot consume it.
Current behavior
- Picasso builds images only from released Tutor tags (such as v20.0.2).
- Builds for our current platform branch fail due to an issue that has already been addressed in Tutor main.
Expected/desired behavior
One of the following (any would solve our need):
- Picasso can be configured to pull Tutor from a branch or commit, for example:
- A specific branch like main.
- Or a specific commit SHA, so we can temporarily track the fix before a new release is cut.
Alternatively, a new Tutor v20.0.x release is published including the fix currently in main, and Picasso is updated to support that version.
Why this matters
Our requirement is to keep our Open edX deployment close to upstream, using recent master changes. Without the ability to use Tutor main (or a newer 20.0.x tag including the fix), we are blocked by the existing build issue in v20.0.2.
Any guidance or supported workflow for this (even if “experimental”) would be very helpful.