Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setup task worker for new git-push mode #27

Open
6 tasks done
pmac opened this issue Apr 9, 2020 · 3 comments
Open
6 tasks done

Setup task worker for new git-push mode #27

pmac opened this issue Apr 9, 2020 · 3 comments

Comments

@pmac
Copy link
Member

pmac commented Apr 9, 2020

Now that mozilla/nucleus#166 has merged we need to setup the worker pod for this to work. We'll need to:

  • Create a deployment for the worker
  • Create a repo for the dev instance to use: https://github.com/mozmeao/nucleus-dev-data
  • Set GITHUB_OUTPUT_REPO with above
  • Configure the Github user token GITHUB_ACCESS_TOKEN
  • Configure the REDIS_URL for the web and worker
  • Set GITHUB_PUSH_ENABLE to True

/cc @duallain

@pmac
Copy link
Member Author

pmac commented Apr 9, 2020

Should also setup a separate repo for nucleus-dev to work with. I'll get on that. Or do you think that just separate branches for dev to use would be sufficient? I think I'd feel better with a different repo.

@duallain
Copy link
Contributor

duallain commented Apr 9, 2020

Different repo makes sense to me. Unless there's some path you want to follow (push to dev branch -> if X person/automation thinks it looks good -> go to prod) inside the repo.

@pmac
Copy link
Member Author

pmac commented Apr 9, 2020

We'll be doing that, but I mean for the dev instance of nucleus to use. A separate repo does seem best per nucleus instance

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants