What are the different pills in the deploy logs and what do they mean?

General Q&A
1

What are the different pills in the deploy logs and what do they mean?

2

There are three pills that could display in the deploy logs:

  1. Backend
  2. Update service
  3. CloudCode

When deploying your app, the deploy service reviews the deploy logs and compares the changes with the last successful deploy to determine what needs deployed. If there are changes related to the Backend, Update service, or CloudCode then the relevant pill will be displayed in the deploy log in OXIDE.

So what changes count as Backend, Update service, or CloudCode changes?

  1. Backend refers to data model changes
  2. Update service refers to views changes
  3. CloudCode refers to changes made in CloudCode

Please note that there are a few different ways you can deploy your code in OXIDE:

  1. To complete a full deploy
    a. Ctrl + s
    b. OXIDE action: Deploy to testing
    c. OXIDE action: Deploy app
  2. To deploy CloudCode only
    a. OXIDE action: Test Task
    b. This will not kick-off a full deploy regardless of if there are other code changes. Test Task will only deploy CloudCode, and will deploy CloudCode regardless of if there are any changes to your CloudCode codebase present. For example, if you have undeployed changes in your views, and then you do a CloudCode “Test Task” then there will be a green Deploy log, but it will only include a CloudCode pill and only the CloudCode changes would have been deployed. The changes in your view would remain undeployed.