Closed Bug 1314601 Opened 9 years ago Closed 9 years ago

Please help transfer the nss-taskcluster bot to Mozilla's Heroku account

Categories

(mozilla.org :: Heroku: Administration, task)

Product:
mozilla.org
Component:
Heroku: Administration
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: ttaubert, Unassigned)

Details

The nss-taskcluster [1] bot in #nss currently runs from my Heroku account. I'd like to move this to Mozilla's Heroku account. Is it preferred to move the repository to the Mozilla org before we do that? Thanks! [1] https://github.com/ttaubert/nss-taskcluster
I could do both for you, if you'd like. What is your heroku account? Once you're a member you can request a transfer via the admin panel, under the settings tab. See: https://devcenter.heroku.com/articles/transferring-apps
Flags: needinfo?(ttaubert)
also, yo move the repo I'd need to be added as an admin (@lonnen on github)
Moved the repo to: https://github.com/mozilla/nss-taskcluster My heroku account email is tim@timtaubert.de.
Flags: needinfo?(ttaubert)
Hmmm. I thought I could add you as an admin afterwards, but looks like even I lost my admin access to the repo by moving it... darn. Can't connect it to Heroku anymore.
Hey Tim -- you moved it fine without me. I restored your admin access to that repo, no need to add me directly anymore now. I've also sent you an invite to the Heroku org. You should be able to transfer the app now.
Great, thank you! I just transferred the app to the Mozilla account, but I can't link it to the new GitHub repository for automatic deployment. I'm missing the necessary credentials probably? Heroku tells me "Something went wrong" when I try to connect it to GitHub.
That's curious. I went ahead and set up the initial connection. You should be able to configure it from there with respect to how it deploys, branches, waiting for CI, etc. Do you need anything else?
Nothing more, this seems to work. Thanks a lot for your help!
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.