Page MenuHomePhabricator

[Investigation: Timebox 8 hrs] Investigate Challenges of Bleeding Edge Docker Images
Closed, InvalidPublic

Description

We want to support iterative/agile release of WBManifest, and one possible alternative to waiting until the 1.35 Docker release of Wikibase is some form of bleeding edge images. At the moment, there are no bleeding edge Docker images for Wikibase. If we want to be able to release WBManifest as we go along, we probably want something that is regularly built from Master. We should investigate how this could work and how difficult it would be, or determine if it would work at all.

Images that only have a "latest" tag, or images that could have a tag that includes code from Master that we don't currently have.

Start here

  • What would be the downsides & challenges of this approach (e.g. supporting another Docker bundle)
  • Do others generate bleeding edge Docker images? How do they do it? (e.g. Python, PHP... some other MediaWiki extension?)

Look into this if there is time

  • Which pieces of software should be bleeding edge version vs which should be fixed version?
  • How regularly should the bleeding edge version be made? (e.g. commit-based or time-based)

Event Timeline

Samantha_Alipio_WMDE renamed this task from Investigate Challenges of Bleeding Edge Docker Images to [Investigation: Timebox Needed] Investigate Challenges of Bleeding Edge Docker Images.Aug 26 2020, 11:11 AM
Samantha_Alipio_WMDE renamed this task from [Investigation: Timebox Needed] Investigate Challenges of Bleeding Edge Docker Images to [Investigation: Timebox 8 hrs] Investigate Challenges of Bleeding Edge Docker Images.Aug 31 2020, 10:38 AM
Samantha_Alipio_WMDE updated the task description. (Show Details)

We decided that we don't want to investigate any more since we won't need it for the test system