Bugzilla

Met with @walac @pmoore and @fubar earlier today to talk about next steps. I was worried that there wasn't a clear way of provisioning the generic-workers for Linux in order to build the pre-requirements for building flatpaks. But sounds like there is \o/ 

So next steps for me:
* reuse one of the existing generic-workers (e.g. https://github.com/taskcluster/generic-worker/tree/master/worker_types/gwci-linux) in order to create a flatpak workerType
* make sure I can deploy on my own so that I can be self-serve in deploying new changes
* adjust the https://github.com/taskcluster/generic-worker/blob/master/worker_types/gwci-linux/userdata to encompass whatever we used to build a successful Docker container - https://gist.github.com/MihaiTabara/8fc247e477683aa4e71d30a4b7f3a470&sa=D&ust=1569336116707000&usg=AOvVaw114FFeTddFJNSVFQfw8MbA
* once we have a good workerType, trigger staging releases in order to test the building of the flatpaks
* once that works, add task to ship-it to the Flathub

Talked to @tomprince earlier in the week. I initially thought we can get away with some docker-worker + TC secrets to push but we'll need to use a scriptworker. So that means we'll need to build something similar to https://github.com/mozilla-releng/pushsnapscript but more leightweight since we can use cli-ed commands. The task itself should only pass as arguments the `channel`.

Met with @walac @pmoore and @fubar earlier today to talk about next steps. I was worried that there wasn't a clear way of provisioning the generic-workers for Linux in order to build the pre-requirements for building flatpaks. But sounds like there is \o/ 

So next steps for me:
* reuse one of the existing generic-workers (e.g. https://github.com/taskcluster/generic-worker/tree/master/worker_types/gwci-linux) in order to create a flatpak workerType
* make sure I can deploy on my own so that I can be self-serve in deploying new changes
* adjust the https://github.com/taskcluster/generic-worker/blob/master/worker_types/gwci-linux/userdata to encompass whatever we used to build a successful Docker container - https://gist.github.com/MihaiTabara/8fc247e477683aa4e71d30a4b7f3a470&sa=D&ust=1569336116707000&usg=AOvVaw114FFeTddFJNSVFQfw8MbA
* once we have a good workerType, trigger staging releases in order to test the building of the flatpaks
* once that works, add task to ship-it to the Flathub

Talked to @tomprince earlier in the week. I initially thought we can get away with some docker-worker + TC secrets to push but we'll need to use a scriptworker. So that means we'll need to build something similar to https://github.com/mozilla-releng/pushsnapscript but more leightweight since we can use cli-ed commands. The task itself should only pass as arguments the `channel`.

Other useful resources:
* https://github.com/taskcluster/generic-worker#set-up-your-env
* https://github.com/taskcluster/mozilla-history/blob/master/AWSWorkerTypes/gwci-linux#L63
* https://tools.taskcluster.net/aws-provisioner/gwci-linux/view
* https://github.com/taskcluster/generic-worker/blob/master/worker_types/gwci-linux/userdata

Met with @walac @pmoore and @fubar earlier today to talk about next steps. I was worried that there wasn't a clear way of provisioning the generic-workers for Linux in order to build the pre-requirements for building flatpaks. But sounds like there is \o/ 

So next steps for me:
* reuse one of the existing generic-workers (e.g. https://github.com/taskcluster/generic-worker/tree/master/worker_types/gwci-linux) in order to create a flatpak workerType
* make sure I can deploy on my own so that I can be self-serve in deploying new changes
* adjust the https://github.com/taskcluster/generic-worker/blob/master/worker_types/gwci-linux/userdata to encompass whatever we used to build a successful Docker container - https://gist.github.com/MihaiTabara/8fc247e477683aa4e71d30a4b7f3a470
* once we have a good workerType, trigger staging releases in order to test the building of the flatpaks
* once that works, add task to ship-it to the Flathub

Talked to @tomprince earlier in the week. I initially thought we can get away with some docker-worker + TC secrets to push but we'll need to use a scriptworker. So that means we'll need to build something similar to https://github.com/mozilla-releng/pushsnapscript but more leightweight since we can use cli-ed commands. The task itself should only pass as arguments the `channel`.

Other useful resources:
* https://github.com/taskcluster/generic-worker#set-up-your-env
* https://github.com/taskcluster/mozilla-history/blob/master/AWSWorkerTypes/gwci-linux#L63
* https://tools.taskcluster.net/aws-provisioner/gwci-linux/view
* https://github.com/taskcluster/generic-worker/blob/master/worker_types/gwci-linux/userdata