Adding a New Application

You create an application in Wercker from a repository in your Git provider (GitHub, Bitbucket, or GitLab).

You add new applications to Wercker using a simple wizard. The wizard takes you through a couple of guided steps to get the best setup from the start.

Note: On 1st April 2019 this wizard was changed for applications that use Bitbucket. See Changes to Bitbucket support.

To add a new application: 1. Click Add application from the Add (+) menu. Add Application Menu 2. In Step 1 of the wizard, choose the following and then click Next: - Choose the owner of the new application. You can either specify your own user account, or choose from a list of organizations where you’re a member of the organization’s Owners team. - If you select an organization, note that by default your Git provider credentials will be used for API operations. If you want a different user’s credentials to be used, you can go back and change that later (by selecting an alternative user from the API user list on the Options page). - Choose the Git provider containing the repository from which the application will be created. Add Application Wizard Step 1 3. In Step 2 of the wizard, choose the repository from which the application will be created, and then click Next.

Symbols indicate whether a repository is private, or is a fork of another repository.

If a repository you're expecting to see is not shown in the list, check that Wercker has access to the repository in the Git provider. Even if a repository is shown in the list, note that your Wercker account might not have the appropriate permissions on that repository. A warning symbol appears beside repositories for which your Wercker account doesn't have sufficient permissions.

If an application has already been created from the repository you selected, you cannot create another application based on the same repository. Instead, you're given the option to join the existing application as a collaborator. Note the following:

  - When you join an existing application, you get `Build + view deploys` access rights to the application.
  - You're not allowed to join an existing application that's already owned by an organization. In that case, all collaborator management is done by members of the organization's Owners team.

If you choose to join the existing application, you're done and you can skip the remaining steps below.
  1. In Step 3 of the wizard, choose whether Wercker will use an SSH key to access the repository when checking out the code to run a build, and then click Next.

    Add Application Wizard Step 3

    For public repositories, it’s recommended that Wercker doesn’t use a public SSH key. Instead, select the Make my app public option in Step 4 of the wizard (or set the application’s Privacy property to Public on the application’s Options page).

    For private repositories, you have to add a public SSH key as a deploy key to your repository.

  2. In Step 4 of the wizard, review the details of the application that you’re about to add, and specify whether to grant public access to the application.

    Add Application Wizard Step 4

    Note that even if you grant public access to the application, you’ll only ever see your builds.

  3. Click Create to add the application to Wercker.

    Having created the new application, you’re immediately given the chance to build it right away on the Runs tab.

    Add Application Wizard Nicely Done

  4. If you want to build the application:

    • If the repository doesn’t already contain a wercker.yml file, follow the on-screen instructions to create one and push it to the repository. You can create a wercker.yml file in Golang, Ruby, NodeJS, and Python, so there is a choice for almost all backend support. Pushing the wercker.yml file will trigger the first build of the application.
    • If the repository already contains a wercker.yml file, click the trigger a build now link to manually trigger a build.

    The Runs tab shows the progress of the build.