Scheduling

By making your WHT Project as a GIT Repository, you can seamlessly collaborate with your team mates, with modular control over your model files. Check out this link on making your project available as a git repository.

Prerequisites

  • You should have already created a git repository from your WHT project.

Follow these steps to configure WHT from the RudderStack web app

  1. Go to RudderStack web app at app.rudderstack.com.

  2. On the left side navigation bar, click on ‘Enhance’, then ‘WHT Project’.

../_images/WebApp-Menu.png

Fig. 2 Option Menu With “WHT Project”

  1. On top right, click on the button ‘Create a new project’. Enter the Project name and description.

../_images/WebApp-Create-Project.png

Fig. 3 Create New Project

  1. Next, enter the GIT Repo URL along with GIT Repo SSH key.

../_images/WebApp-Add.png

Fig. 4 Add GIT Repo Credentials

  1. You must now enter data warehouse credentials such as Profile, Account, Database, Warehouse, User, Password, Schema, Role, and Cloud.

../_images/WebApp-Add_3.png

Fig. 5 Adding Warehouse Credentials

  1. Now you can define the interval at which to automatically run the repo. Web app provides 3 scheduling options:

    Basic: If you want to run on set of interval.
    Cron: If you want to run every 15 minutes or every 1 hour, etc. Click here to know more.
    Manual: Select this you if want to manually trigger run.
../_images/WebApp-Cron.png

Fig. 6 Basic Scheduling

../_images/WebApp-Cron_2.png

Fig. 7 Cron Scheduling

  1. After creating project, you will see it in the list of project. Click on details. You will get option to manually trigger run or view all previous run.

../_images/WebApp-Project-List.png

Fig. 8 WHT project list

../_images/WebApp-Project-Details.png

Fig. 9 WHT project details

  1. Click on view runs to see a list of all previous runs.

../_images/WebApp-Run-Instance.png

Fig. 10 List of current and previous run instances of project

  1. If any error message is there then it’ll be displayed on screen when you click on link in the list.

  2. By selecting the Add button, you will obtain folder-wise artefacts and logging. If any errors occur, the cause will be listed in a file called log.txt. You will get both the most recent and older artefacts and logging along wih option for download.

../_images/WebApp-Artefacts.png

Fig. 11 Artefacts folders

../_images/WebApp-Artefacts-1.png

Fig. 12 List of artefacts