-
-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Running Jobs on Dev Server
- If you are writing a Job yourself and want to test how would it work.
- If you are working on an issue related to a Job.
- If you are looking through the code of a Job and want to see what it does.
-
Migration one off jobs - These jobs are used for migrating from one schema version to other. If you are creating a new schema version for any model, make sure to run the migration job and check if the migration works as expected. One of the examples is
ExplorationMigrationJobManager
which is used for migration of explorations to the latest version. -
Feedback Continuous Computation one off jobs - These jobs are used for continuously computing feedback analytics and updating them. You can run these jobs when you are making changes to the feedback system and check if the analytics are computed and updated correctly.
-
Validation One off jobs - These jobs can be used to validate the exploration data. One such example is the
ExplorationContentValidationJobForCKEditor
which validates if the html is in correct format for ckeditor. You can run this job to find invalid html content in an exploration which does not fit the ckeditor schema. Any validation job can be used to find the cases which violate the required schema. -
Audit One off jobs - These jobs can be used to audit various properties related to a model. One such example is
HintsAuditOneOffJob
which is used to find number of hints used in each state of an exploration. These jobs can be run if you need to audit any property associated with any model.
1.) Start the dev server and log in as admin.
2.) Hover over the user avatar and select the Admin Page.
3.) Select the Jobs tab and start it from the list. Note that your job will run on the explorations that are present on the server, the job is being run on. Say, if you are running on local host to check how your job is performing you need to have some explorations created on the local server. You could also take a look at the activites tab, there we have some already available explorations. You could just click on reload
and that corresponding exploration will be made available on your server then (you could browse through your library and you'll see the particular exploration).
- go to
core/domain/
- Find the file related to the Job and see its documentation to know what it does.
Have an idea for how to improve the wiki? Please help make our documentation better by following our instructions for contributing to the wiki.
Core documentation
Developing Oppia
- FAQs
- How to get help
- Getting started with the project
- How the codebase is organized
- Making your first PR
- Debugging
- Testing
- Codebase policies and processes
- Guidelines for launching new features
- Guidelines for making an urgent fix (hotfix)
- Testing jobs and other features on production
- Guidelines for Developers with Write Access to oppia/oppia
- Release schedule and other information
- Revert and Regression Policy
- Privacy aware programming
- Code review:
- Project organization:
- QA Testing:
- Design docs:
- Team-Specific Guides
- LaCE/CD:
- Developer Workflow:
Developer Reference
- Oppiabot
- Git cheat sheet
- Frontend
- Backend
- Backend Type Annotations
- Writing state migrations
- Calculating statistics
- Storage models
- Coding for speed in GAE
- Adding a new page
- Adding static assets
- Wipeout Implementation
- Notes on NDB Datastore transactions
- How to handle merging of change lists for exploration properties
- Instructions for editing roles or actions
- Protocol buffers
- Webpack
- Third-party libraries
- Extension frameworks
- Oppia-ml Extension
- Mobile development
- Performance testing
- Build process
- Best practices for leading Oppia teams
- Past Events