Setting up a repository with Wercker is simple. We start by creating an app in the main profile screen. Once we click on that button, we are directed to a repository setup page.
Here we pick our service (GitHub or Bitbucket). When we select our service, the repos that are connected to our selected service will display below. Please note that for any repository selected that all of the appropriate permissions are needed. Any missing will be indicated by a yellow symbol with a question mark. That repository will be tagged, and it most likely will not have access to most of Wercker’s services.
Once we select the repo, the next step is configuring access. For most public projects, Wercker can checkout the code without an SSH key. If we are using submodules on a private repository, we can manually add the deploy key, or we can have Wercker add the key to the selected repository for us. (This is a good choice for private repositories without submodules.)
Our next screen is the app dashboard, which gives us access to features. (Look at the Wercker features overview for more information.) This is also where we set up our Wercker yml file for inclusion with our repository so that we can complete our initial build process. The yml file is available in Golang, Ruby, NodeJS, and Python, so there is a choice for almost all backend support.
Once that step is complete, then you are ready to use Wercker.