Fix the Heroku deploy payload

[Lothiraldan]

The payload structure was modified by #46. Also adds some logs so we can
better understand what is happening

[Lothiraldan]

This PR has been validated locally

[La0]

Could you validate in a Taskcluster task manually created, so we can see the full execution. Please link the task here. Thanks !

[Lothiraldan]

I'm not sure how to do it but I will try

[marco-c]

What if we add a test push in the .taskcluster.yml of task-boot?

[Lothiraldan]

It needs to find the dependencies to get the artifacts, I'm not sure how we could "override" the TASK_ID to point to another task.

[Lothiraldan]

I have create a Docker image with the code if this branch: lothiraldan/task-boot:fix-heroku-deploy, I'm trying to rerun / retrigger https://tools.taskcluster.net/groups/LxTuw6rUTs-B2PPzIEBtyA/tasks/eG9eMHmMT1W2dJlLPrbO9g/details with the custom image

[Lothiraldan]

Done https://tools.taskcluster.net/groups/fzCU8ZX0QdyyQl3JK3Mrzg/tasks/fzCU8ZX0QdyyQl3JK3Mrzg/runs/0/logs/public%2Flogs%2Flive.log

[La0]

@Lothiraldan You can use docker image available as Taskcluster artifact in new taskcluster tasks (instead of building and pushing on a test repo).

In the task definition:

  "image": {
    "path": "public/path/to/image.tar",
    "taskId": "TASK_ID",
    "type": "task-image"
  },

Here you could use task id TtZTB3_ESHqXdrRHcp1New (from the last build)

[marco-c]

We could have a build task in .taskcluster.yml that creates a basic image (like hello-world) and then a task that pushes it to Heroku. I'll file an issue.

[Lothiraldan]

We could have a build task in .taskcluster.yml that creates a basic image (like hello-world) and then a task that pushes it to Heroku. I'll file an issue.

I've manually created a task for validation using the docker image I built locally: https://tools.taskcluster.net/groups/fzCU8ZX0QdyyQl3JK3Mrzg/tasks/fzCU8ZX0QdyyQl3JK3Mrzg/runs/0/logs/public%2Flogs%2Flive.log. Do we want more before merging this PR?

@marco-c are you speaking about having an automated test that would be run on each commit?

[marco-c]

@marco-c are you speaking about having an automated test that would be run on each commit?

Yep, I've added it to the list of integration tests we should write in #44.