dduvall (Dan Duvall)
Automation Engineer

Today

  • Clear sailing ahead.

Tomorrow

  • Clear sailing ahead.

Friday

  • Clear sailing ahead.

User Details

User Since
Oct 7 2014, 4:24 PM (189 w, 15 h)
Availability
Available
IRC Nick
marxarelli
LDAP User
Dduvall
MediaWiki User
DDuvall (WMF)

Recent Activity

Sun, May 20

dduvall committed rGBLBR798f96381057: Bump config version to v2 (authored by dduvall).
Bump config version to v2
Sun, May 20, 9:55 AM
dduvall committed rGBLBRddf8bee001c3: Add now mandatory version config field to README (authored by Gilles).
Add now mandatory version config field to README
Sun, May 20, 9:47 AM
dduvall closed D1052: Add now mandatory version config field to README.
Sun, May 20, 9:46 AM · Release-Engineering-Team
dduvall committed rGBLBRfdcd9be3c96a: Refactor config for node app dependencies (authored by dduvall).
Refactor config for node app dependencies
Sun, May 20, 9:42 AM
dduvall closed D1058: Refactor config for node app dependencies.
Sun, May 20, 9:41 AM · Release-Engineering-Team
dduvall committed rGBLBR96de90b36408: Add support for Builder arbitrary build commands (authored by Gilles).
Add support for Builder arbitrary build commands
Sun, May 20, 9:37 AM
dduvall committed rGBLBR8025356d5506: Add support for Builder arbitrary build commands (authored by dduvall).
Add support for Builder arbitrary build commands
Sun, May 20, 9:23 AM
dduvall closed D1054: Add support for Builder arbitrary build commands.
Sun, May 20, 9:23 AM · Release-Engineering-Team
dduvall accepted D1054: Add support for Builder arbitrary build commands.
Sun, May 20, 9:22 AM · Release-Engineering-Team
dduvall updated the diff for D1054: Add support for Builder arbitrary build commands.
  • Example for builder configuration
Sun, May 20, 9:22 AM · Release-Engineering-Team

Sat, May 19

dduvall added a comment to D1056: Unconditionally copy npm-shrinkwrap.json.

I've uploaded D1058: Refactor config for node app dependencies which I think is a more complete implementation of what we discussed.

Sat, May 19, 9:19 PM · Release-Engineering-Team
dduvall committed rGBLBR1b6a7003486b: Add a pip install step (authored by akosiaris).
Add a pip install step
Sat, May 19, 9:15 PM
This revision was not accepted when it landed; it landed in state Needs Review.
Sat, May 19, 9:15 PM · Release-Engineering-Team
dduvall updated the diff for D1057: Add a pip install step.

Slightly modified the implementation to exclude PIP_NO_INDEX when not building wheels and installing, and implemented tests

Sat, May 19, 8:58 PM · Release-Engineering-Team
dduvall requested review of D1058: Refactor config for node app dependencies.
Sat, May 19, 8:15 PM · Release-Engineering-Team
dduvall added a comment to T194973: Hackathon scholarship process review.

@Bmueller would you be open to moving rooms? We're hoping to reschedule our session (T194940: Wikimedia Continuous Delivery Pipeline: Say What?) to after lunch, but we'd like the room with video recording if possible.

Sat, May 19, 2:07 PM · Wikimedia-Hackathon-2018
dduvall updated the task description for T193824: Determine a standard way of installing MediaWiki lib/extension dependencies within containers.
Sat, May 19, 11:11 AM · Release-Engineering-Team (Kanban), Release Pipeline
dduvall added a comment to T166956: Cannot use Composer's CLI to manage a project's dependencies.

Release Engineering is interested in this work for the purposes of CI and the new deployment pipeline. The current approach, which is to rely on test dependencies defined via a Python global in integration/config, is certainly not ideal and not viable for the pipeline. See T193824: Determine a standard way of installing MediaWiki lib/extension dependencies within containers for possible solutions we've been discussing.

Sat, May 19, 11:09 AM · TechCom, Wikimedia-Hackathon-2018, MediaWiki-General-or-Unknown, Composer
dduvall updated the task description for T195050: Refactor pipeline build step to be more isolated/secure/scalable.
Sat, May 19, 11:00 AM · Release-Engineering-Team (Kanban), Release Pipeline
dduvall updated subscribers of T195050: Refactor pipeline build step to be more isolated/secure/scalable.
Sat, May 19, 11:00 AM · Release-Engineering-Team (Kanban), Release Pipeline
dduvall created T195050: Refactor pipeline build step to be more isolated/secure/scalable.
Sat, May 19, 10:58 AM · Release-Engineering-Team (Kanban), Release Pipeline
dduvall accepted D1052: Add now mandatory version config field to README.
Sat, May 19, 10:19 AM · Release-Engineering-Team
dduvall awarded D1054: Add support for Builder arbitrary build commands a Like token.
Sat, May 19, 10:18 AM · Release-Engineering-Team
dduvall added a comment to D1054: Add support for Builder arbitrary build commands.

Booya! Just needs a couple of edits to the inline comments and I think it's good to merge.

Sat, May 19, 10:14 AM · Release-Engineering-Team

Fri, May 18

dduvall added a comment to T194940: Wikimedia Continuous Delivery Pipeline: Say What?.

Hello!
This session is in a room with video recording capabilities. Would you like this session recorded for YouTube / Commons?
Pinging @bcampbell as he will be helping with this.

Fri, May 18, 2:54 PM · Wikimedia-Hackathon-2018, User-zeljkofilipin, Services (watching), Release-Engineering-Team (Kanban), Release Pipeline
dduvall updated the task description for T194940: Wikimedia Continuous Delivery Pipeline: Say What?.
Fri, May 18, 12:46 PM · Wikimedia-Hackathon-2018, User-zeljkofilipin, Services (watching), Release-Engineering-Team (Kanban), Release Pipeline

Fri, May 4

dduvall triaged T193824: Determine a standard way of installing MediaWiki lib/extension dependencies within containers as Normal priority.
Fri, May 4, 1:13 AM · Release-Engineering-Team (Kanban), Release Pipeline
dduvall added a parent task for T193824: Determine a standard way of installing MediaWiki lib/extension dependencies within containers: T187105: Get MediaWiki running in Docker with Blubber.
Fri, May 4, 1:12 AM · Release-Engineering-Team (Kanban), Release Pipeline
dduvall added a subtask for T187105: Get MediaWiki running in Docker with Blubber: T193824: Determine a standard way of installing MediaWiki lib/extension dependencies within containers.
Fri, May 4, 1:12 AM · Release-Engineering-Team (Kanban), Release Pipeline
dduvall created T193824: Determine a standard way of installing MediaWiki lib/extension dependencies within containers.
Fri, May 4, 1:12 AM · Release-Engineering-Team (Kanban), Release Pipeline
dduvall triaged T187105: Get MediaWiki running in Docker with Blubber as Normal priority.
Fri, May 4, 12:44 AM · Release-Engineering-Team (Kanban), Release Pipeline
dduvall added a parent task for T187105: Get MediaWiki running in Docker with Blubber: T193777: FY2017/18-Q4: Prove viability of testing staged service containers alongside MediaWiki extension containers.
Fri, May 4, 12:43 AM · Release-Engineering-Team (Kanban), Release Pipeline
dduvall added a subtask for T193777: FY2017/18-Q4: Prove viability of testing staged service containers alongside MediaWiki extension containers: T187105: Get MediaWiki running in Docker with Blubber.
Fri, May 4, 12:43 AM · Release-Engineering-Team, Release Pipeline
dduvall triaged T193777: FY2017/18-Q4: Prove viability of testing staged service containers alongside MediaWiki extension containers as Normal priority.
Fri, May 4, 12:42 AM · Release-Engineering-Team, Release Pipeline
dduvall added a parent task for T193777: FY2017/18-Q4: Prove viability of testing staged service containers alongside MediaWiki extension containers: T170481: FY2017/18 Program 6 - Outcome 2 - Objective 2: Set up a continuous integration and deployment pipeline.
Fri, May 4, 12:42 AM · Release-Engineering-Team, Release Pipeline
dduvall added a subtask for T170481: FY2017/18 Program 6 - Outcome 2 - Objective 2: Set up a continuous integration and deployment pipeline: T193777: FY2017/18-Q4: Prove viability of testing staged service containers alongside MediaWiki extension containers.
Fri, May 4, 12:42 AM · Epic, Release-Engineering-Team, Services (watching), Operations

Thu, May 3

dduvall updated the task description for T193777: FY2017/18-Q4: Prove viability of testing staged service containers alongside MediaWiki extension containers.
Thu, May 3, 5:59 PM · Release-Engineering-Team, Release Pipeline
dduvall created T193777: FY2017/18-Q4: Prove viability of testing staged service containers alongside MediaWiki extension containers.
Thu, May 3, 5:57 PM · Release-Engineering-Team, Release Pipeline

Wed, May 2

dduvall moved T186547: Blubber should support php/composer from Doing to Backlog on the Release Pipeline (Blubber) board.
Wed, May 2, 7:35 PM · Release Pipeline (Blubber), Release-Engineering-Team (Kanban)
dduvall placed T186547: Blubber should support php/composer up for grabs.
Wed, May 2, 7:35 PM · Release Pipeline (Blubber), Release-Engineering-Team (Kanban)

Mon, Apr 30

dduvall committed rGBLBR71f24e2bcaf4: Ensure non-interactive front-end for APT (authored by dduvall).
Ensure non-interactive front-end for APT
Mon, Apr 30, 9:06 PM
dduvall closed D1032: Ensure non-interactive front-end for APT.
Mon, Apr 30, 9:05 PM · Release-Engineering-Team

Fri, Apr 27

dduvall edited P7048 Blubbering with MediaWiki.
Fri, Apr 27, 11:02 PM
dduvall requested review of D1032: Ensure non-interactive front-end for APT.
Fri, Apr 27, 10:15 PM · Release-Engineering-Team
dduvall closed T191327: Come up with a decent method of declaring helm chart path/version in service repo as Resolved.
Fri, Apr 27, 9:47 PM · Patch-For-Review, Release-Engineering-Team (Kanban), Release Pipeline
dduvall closed T191327: Come up with a decent method of declaring helm chart path/version in service repo, a subtask of T188935: modify service-pipeline to include helm install/helm test, as Resolved.
Fri, Apr 27, 9:47 PM · Patch-For-Review, Release-Engineering-Team (Kanban), Release Pipeline
dduvall moved T186547: Blubber should support php/composer from Backlog to In-progress on the Release-Engineering-Team (Kanban) board.
Fri, Apr 27, 9:17 PM · Release Pipeline (Blubber), Release-Engineering-Team (Kanban)
dduvall claimed T186547: Blubber should support php/composer.
Fri, Apr 27, 9:17 PM · Release Pipeline (Blubber), Release-Engineering-Team (Kanban)

Apr 18 2018

dduvall accepted D1026: Log check output when check succeeds..
Apr 18 2018, 8:15 PM · Release-Engineering-Team

Apr 12 2018

dduvall added a comment to T191327: Come up with a decent method of declaring helm chart path/version in service repo.

In today's SSD (aka CD Pipeline, aka Release Pipeline) Meeting, we agreed to implement option #1 after charts were published to https://releases.wikimedia.org/charts/ (done!).

Apr 12 2018, 9:50 PM · Patch-For-Review, Release-Engineering-Team (Kanban), Release Pipeline
dduvall added a parent task for T191327: Come up with a decent method of declaring helm chart path/version in service repo: T188935: modify service-pipeline to include helm install/helm test.
Apr 12 2018, 9:42 PM · Patch-For-Review, Release-Engineering-Team (Kanban), Release Pipeline
dduvall added a subtask for T188935: modify service-pipeline to include helm install/helm test: T191327: Come up with a decent method of declaring helm chart path/version in service repo.
Apr 12 2018, 9:42 PM · Patch-For-Review, Release-Engineering-Team (Kanban), Release Pipeline
dduvall closed T191821: Host packaged helm charts at https://releases.wikimedia.org/charts as Resolved.

@Dzahn thanks for the quick merge!

Apr 12 2018, 9:41 PM · Patch-For-Review, Release-Engineering-Team (Kanban), Release Pipeline
dduvall closed T191821: Host packaged helm charts at https://releases.wikimedia.org/charts, a subtask of T191327: Come up with a decent method of declaring helm chart path/version in service repo, as Resolved.
Apr 12 2018, 9:41 PM · Patch-For-Review, Release-Engineering-Team (Kanban), Release Pipeline

Apr 9 2018

dduvall moved T191821: Host packaged helm charts at https://releases.wikimedia.org/charts from Backlog to In-progress on the Release-Engineering-Team (Kanban) board.
Apr 9 2018, 5:46 PM · Patch-For-Review, Release-Engineering-Team (Kanban), Release Pipeline
dduvall triaged T191821: Host packaged helm charts at https://releases.wikimedia.org/charts as Normal priority.
Apr 9 2018, 5:46 PM · Patch-For-Review, Release-Engineering-Team (Kanban), Release Pipeline
dduvall added a parent task for T191821: Host packaged helm charts at https://releases.wikimedia.org/charts: T191327: Come up with a decent method of declaring helm chart path/version in service repo.
Apr 9 2018, 5:45 PM · Patch-For-Review, Release-Engineering-Team (Kanban), Release Pipeline
dduvall added a subtask for T191327: Come up with a decent method of declaring helm chart path/version in service repo: T191821: Host packaged helm charts at https://releases.wikimedia.org/charts.
Apr 9 2018, 5:45 PM · Patch-For-Review, Release-Engineering-Team (Kanban), Release Pipeline
dduvall created T191821: Host packaged helm charts at https://releases.wikimedia.org/charts.
Apr 9 2018, 5:45 PM · Patch-For-Review, Release-Engineering-Team (Kanban), Release Pipeline
dduvall added a comment to T191327: Come up with a decent method of declaring helm chart path/version in service repo.

So if we're following option #1, we'll need to expose packaged charts somewhere central. Does https://integration.wikimedia.org/charts/ seem like an appropriate location for these, at least for the purposes of pre-prod helm deployments?

Apr 9 2018, 5:06 PM · Patch-For-Review, Release-Engineering-Team (Kanban), Release Pipeline

Apr 5 2018

dduvall committed rGBLBRea364b2f417e: Refactor validation tests without YAML parsing (authored by dduvall).
Refactor validation tests without YAML parsing
Apr 5 2018, 10:49 PM
dduvall closed D1023: Refactor validation tests without YAML parsing.
Apr 5 2018, 10:48 PM · Release-Engineering-Team
dduvall updated the diff for D1023: Refactor validation tests without YAML parsing.

Last jeebie

Apr 5 2018, 10:46 PM · Release-Engineering-Team
dduvall updated the diff for D1023: Refactor validation tests without YAML parsing.

Missed a jeebie

Apr 5 2018, 10:43 PM · Release-Engineering-Team
dduvall updated the diff for D1023: Refactor validation tests without YAML parsing.

Removed the underscores, removed the jeebies.

Apr 5 2018, 10:42 PM · Release-Engineering-Team
dduvall requested review of D1023: Refactor validation tests without YAML parsing.
Apr 5 2018, 10:13 PM · Release-Engineering-Team
dduvall committed rGBLBR26b998456a56: Introduce strict/versioned config parsing (authored by dduvall).
Introduce strict/versioned config parsing
Apr 5 2018, 8:27 PM
dduvall closed T191460: Blubber should error on unknown/obsolete config fields as Resolved by committing rGBLBR26b998456a56: Introduce strict/versioned config parsing.
Apr 5 2018, 8:26 PM · Release-Engineering-Team (Kanban), Release Pipeline (Blubber)
dduvall closed D1021: Introduce strict/versioned config parsing.
Apr 5 2018, 8:26 PM · Release-Engineering-Team
dduvall updated the diff for D1021: Introduce strict/versioned config parsing.

Reimplemented version field using a separate struct so that validation of the field may happen independent of the entire config and before strict unmarshaling occurs.

Apr 5 2018, 8:10 PM · Release-Engineering-Team
Dzahn awarded T191453: grant thcipriani RelEng root on contint1001 a Mountain of Wealth token.
Apr 5 2018, 4:10 AM · Release-Engineering-Team, SRE-Access-Requests, Continuous-Integration-Infrastructure, Operations

Apr 4 2018

dduvall requested review of D1021: Introduce strict/versioned config parsing.
Apr 4 2018, 10:35 PM · Release-Engineering-Team
dduvall added a revision to T191460: Blubber should error on unknown/obsolete config fields: D1021: Introduce strict/versioned config parsing.
Apr 4 2018, 10:35 PM · Release-Engineering-Team (Kanban), Release Pipeline (Blubber)
dduvall edited P6946 bad mathoid blubber config.
Apr 4 2018, 10:25 PM
dduvall moved T191460: Blubber should error on unknown/obsolete config fields from Backlog to In-progress on the Release-Engineering-Team (Kanban) board.
Apr 4 2018, 10:02 PM · Release-Engineering-Team (Kanban), Release Pipeline (Blubber)
dduvall claimed T191460: Blubber should error on unknown/obsolete config fields.
Apr 4 2018, 10:02 PM · Release-Engineering-Team (Kanban), Release Pipeline (Blubber)
dduvall committed rGBLBR589b23aeb3cd: Include git as a build dependency (authored by dduvall).
Include git as a build dependency
Apr 4 2018, 9:10 PM
dduvall closed T191462: Git commit is missing from compiled Blubber version when packaged for Debian as Resolved.

Added to debian/control.

Apr 4 2018, 9:06 PM · Release-Engineering-Team (Kanban), Release Pipeline (Blubber)
dduvall created T191462: Git commit is missing from compiled Blubber version when packaged for Debian.
Apr 4 2018, 7:24 PM · Release-Engineering-Team (Kanban), Release Pipeline (Blubber)
dduvall created T191460: Blubber should error on unknown/obsolete config fields.
Apr 4 2018, 7:21 PM · Release-Engineering-Team (Kanban), Release Pipeline (Blubber)
dduvall created T191453: grant thcipriani RelEng root on contint1001.
Apr 4 2018, 6:08 PM · Release-Engineering-Team, SRE-Access-Requests, Continuous-Integration-Infrastructure, Operations

Apr 3 2018

dduvall added a comment to T191327: Come up with a decent method of declaring helm chart path/version in service repo.

Added a third option.

Apr 3 2018, 7:30 PM · Patch-For-Review, Release-Engineering-Team (Kanban), Release Pipeline
dduvall updated the task description for T191327: Come up with a decent method of declaring helm chart path/version in service repo.
Apr 3 2018, 7:30 PM · Patch-For-Review, Release-Engineering-Team (Kanban), Release Pipeline
dduvall moved T191327: Come up with a decent method of declaring helm chart path/version in service repo from Backlog to In-progress on the Release-Engineering-Team (Kanban) board.
Apr 3 2018, 6:43 PM · Patch-For-Review, Release-Engineering-Team (Kanban), Release Pipeline
dduvall claimed T191327: Come up with a decent method of declaring helm chart path/version in service repo.
Apr 3 2018, 6:43 PM · Patch-For-Review, Release-Engineering-Team (Kanban), Release Pipeline
dduvall created T191327: Come up with a decent method of declaring helm chart path/version in service repo.
Apr 3 2018, 6:42 PM · Patch-For-Review, Release-Engineering-Team (Kanban), Release Pipeline
dduvall moved T188935: modify service-pipeline to include helm install/helm test from Backlog to CI on the Release Pipeline board.
Apr 3 2018, 6:21 PM · Patch-For-Review, Release-Engineering-Team (Kanban), Release Pipeline
dduvall claimed T188935: modify service-pipeline to include helm install/helm test.
Apr 3 2018, 6:21 PM · Patch-For-Review, Release-Engineering-Team (Kanban), Release Pipeline
dduvall closed T188933: install kubectl on integration agents as Resolved.
Apr 3 2018, 6:21 PM · Release-Engineering-Team (Kanban), Release Pipeline
dduvall closed T188933: install kubectl on integration agents, a subtask of T183165: Verify functionality of the 'production' image in the context of an isolated k8s deployment, as Resolved.
Apr 3 2018, 6:21 PM · Release-Engineering-Team (Kanban), Release Pipeline
dduvall moved T188934: install helm on integration agents from Backlog to CI on the Release Pipeline board.
Apr 3 2018, 6:20 PM · Patch-For-Review, Release-Engineering-Team (Kanban), Release Pipeline
dduvall moved T188936: ensure minikube running on integration agents from Backlog to CI on the Release Pipeline board.
Apr 3 2018, 6:20 PM · Patch-For-Review, Release-Engineering-Team (Kanban), Release Pipeline
dduvall reassigned T188934: install helm on integration agents from dduvall to thcipriani.

Left open to ensure the right invocation of helm init in puppet.

Apr 3 2018, 6:20 PM · Patch-For-Review, Release-Engineering-Team (Kanban), Release Pipeline
dduvall reassigned T188936: ensure minikube running on integration agents from dduvall to thcipriani.
Apr 3 2018, 6:03 PM · Patch-For-Review, Release-Engineering-Team (Kanban), Release Pipeline
dduvall closed T191211: Permission denied upon `minikube start` as non-root user as Invalid.

After chatting with @thcipriani it's clear that minikube --vm-driver=none is not really meant to work when run as a non-root user. We'll continue on with this on labs instances only and limit our use to the test-only version of the pipeline job (w/o registry push).

Apr 3 2018, 5:21 PM · Release-Engineering-Team (Kanban), Release Pipeline
dduvall closed T191211: Permission denied upon `minikube start` as non-root user, a subtask of T188936: ensure minikube running on integration agents, as Invalid.
Apr 3 2018, 5:21 PM · Patch-For-Review, Release-Engineering-Team (Kanban), Release Pipeline

Apr 2 2018

dduvall triaged T191211: Permission denied upon `minikube start` as non-root user as High priority.
Apr 2 2018, 4:24 PM · Release-Engineering-Team (Kanban), Release Pipeline
dduvall added a subtask for T188936: ensure minikube running on integration agents: T191211: Permission denied upon `minikube start` as non-root user.
Apr 2 2018, 4:15 PM · Patch-For-Review, Release-Engineering-Team (Kanban), Release Pipeline
dduvall added a parent task for T191211: Permission denied upon `minikube start` as non-root user: T188936: ensure minikube running on integration agents.
Apr 2 2018, 4:15 PM · Release-Engineering-Team (Kanban), Release Pipeline
dduvall created T191211: Permission denied upon `minikube start` as non-root user.
Apr 2 2018, 4:14 PM · Release-Engineering-Team (Kanban), Release Pipeline