Added task reference.
Tue, Jun 20
Fri, Jun 16
Thu, Jun 15
Fixed main source COPY instruction as well
Wed, Jun 14
Mon, Jun 12
Wed, Jun 7
Added task to summary
Thu, Jun 1
Wed, May 31
Tue, May 30
Thu, May 25
May 23 2017
Fixed docker/compiler import paths
May 11 2017
Hmm... now to wrestle with import paths.
@mobrovac and I discussed Blubber requirements today regarding local development use cases. Among other things, we discussed the need for a Node base image with Wikimedia APT sources included and nodejs and related packages installed.
Apr 20 2017
Over the past few days I've been experimenting with a general build configuration format and wrote a build tool in Go—because, well, I unabashedly wanted to learn something new while experimenting; please don't judge my awful Go code :)—codenamed Blubber that spits out a Dockerfile.
Apr 19 2017
Apr 17 2017
Mar 29 2017
Looks like there's a Docker Pipeline plugin that might provide what we need for this.
There's now a ci-staging-docker-registry instance running in ci-staging with the new role::ci::docker::registry applied. I've verified that it's working by pulling down the latest Debian image from dockerhub and pushing it to ci-staging-docker-registry.ci-staging.eqiad.wmflabs:
Mar 28 2017
This idea is essentially superseded by the Release Pipeline which will undoubtedly incorporate or interact with a k8s cluster in one way or another.
Also needed add an annotation to the default namespace to satisfy our custom RegistryEnforcer admin controller:
So I think I got most of what was required for setup into the submitted puppet patch. The only other manual steps include:
Mar 16 2017
Also, it's probably worth pointing out at this point that 'manifest' is not really the right word for what we're talking about here; a manifest as it's defined in all of the existing specifications is actually a bundled filesystem image (agnostic to how it was built) and runtime metadata about how to set up the container and how to invoke some application binary. What we've been discussing is a slightly higher level abstraction that covers the metadata but also system level package dependencies. The manifest + image will be a product of our build step.
Some related reading material on container standards (both de facto and burgeoning) that illustrates their separation of concerns and overlap.
Feb 22 2017
Feb 16 2017
Feb 14 2017
Feb 13 2017
@Halfak: The Deployment Cabal discussed this a bit more in our meeting this morning and decided that disallowing/excluding empty groups may indeed be a better long-term fix since empty input could lead to further unexpected behavior if left unvalidated.
Feb 9 2017
Oh and one little nit about the commit message: Please use the "Refs T123" or "Fixes T123" auto-close syntax to reference tasks. See https://secure.phabricator.com/book/phabricator/article/diffusion_autoclose/
To clarify: I think your changes are beneficial and should stay as well. :) Can you please add a unit test to tests/scap/test_targets.py to verify the edge case? Thanks!
I think the correct fix here would be to ensure a non-zero group size in the first place. Any idea how that may have happened? I suspect a percentage failure_rate that was converted to an integer and floored to 0 perhaps...
Feb 8 2017
Feb 7 2017
An additional follow up to make the prompt conditional more clear
Implemented suggested re-prompting following bad prompt input