setting up jenkins installation for an open-edx workflow
100 views
Skip to first unread message
Michael Bravo
Jul 23, 2015, 8:07:55 AM7/23/15
to Open edX operations
Hi,
I'm helping with setting up CI infrastructure for a team of open-edx developers in Moscow. So far, I have had nice success with the jenkins roles in the playbooks, however there are some things I'd like to ask about to save time figuring those out (aside from job configs and other things we need to get up and running, I wrote to Jesse Zoldak an email about that).
When provisioning a jenkins worker, there's a github_oauth_token variable that needs to be specified. It is used in ways like this (in jenkins_worker/tasks/test.yml):
# The role is run with a github oauth token passed in
# as github_oauth_token var value.
# This test confirms that the key being used will work
- name: ensure github token works
shell:
"github_post_status.py edx edx-platform
dddac0b5dddf00c0950daf324e603e4935994954 success
https://jenkins.testeng.edx.org/ \"Tests Passed\" \"CI Test Results\""
could you explain what this token should be giving access to? where do I generate it, if, say, we have an organization myorg and an edx-platform repo in it (url would look like https://github.com/myorg/edx-platform)
Also, just for general understanding, if we have limited loads, how okay would it be to combine jenkins master and worker on a single machine?
Many thanks in advance for your informative replies!
I'm helping with setting up CI infrastructure for a team of open-edx developers in Moscow. So far, I have had nice success with the jenkins roles in the playbooks, however there are some things I'd like to ask about to save time figuring those out (aside from job configs and other things we need to get up and running, I wrote to Jesse Zoldak an email about that).
When provisioning a jenkins worker, there's a github_oauth_token variable that needs to be specified. It is used in ways like this (in jenkins_worker/tasks/test.yml):
# The role is run with a github oauth token passed in
# as github_oauth_token var value.
# This test confirms that the key being used will work
- name: ensure github token works
shell:
"github_post_status.py edx edx-platform
dddac0b5dddf00c0950daf324e603e4935994954 success
https://jenkins.testeng.edx.org/ \"Tests Passed\" \"CI Test Results\""
could you explain what this token should be giving access to? where do I generate it, if, say, we have an organization myorg and an edx-platform repo in it (url would look like https://github.com/myorg/edx-platform)
Also, just for general understanding, if we have limited loads, how okay would it be to combine jenkins master and worker on a single machine?
Many thanks in advance for your informative replies!
Jesse Zoldak
Jul 30, 2015, 4:10:47 PM7/30/15
to Open edX operations, mike....@gmail.com
Although it is incomplete, I have put together a guide on how we have set up a Jenkins system for running the tests for the edx-platform repo:
If other people have more questions (or answers!), please feel free to ask in comments there, edit the page to improve, etc.
-- JZ
Reply all
Reply to author
Forward
0 new messages