Closed
Bug 1515139
Opened 6 years ago
Closed 6 years ago
Deployment process for Heroku services from monorepo
Categories
(Taskcluster :: Services, enhancement)
Taskcluster
Services
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dustin, Unassigned)
References
Details
No description provided.
Reporter | ||
Comment 1•6 years ago
|
||
https://github.com/heroku/heroku-buildpack-multi-procfile seems to work great:
* Set PROCFILE config to services/<service>/Procfile
* Run heroku buildpacks:add -a <app> https://github.com/taskcluster/heroku-buildpack-multi-procfile
* Disconnect from the existing Github repo
* Reconnect to org=taskcluster repo=taskcluster-temporary-monorepo
* Click “Deploy” from the master branch
The use of taskcluster-temporary-monorepo is to work around a Heroku bug, where a search for "taskcluster" only returns a few results. Hopefully that will be fixed soon, and we can just deploy from taskcluster/taskcluster.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•6 years ago
|
Component: Platform and Services → Services
You need to log in
before you can comment on or make changes to this bug.
Description
•