Install GitHub Apps https://github.com/apps/action-button Sign In and find your repository https://github-action-button.web.app/repos Create a button Copy and Paste the button markdown to your README
Full Answer
Salesforce Continuous Integration
The basic idea for continuous integration is to ensure that any changes you or your team make to the code base are tested. This can be done by setting up a workflow that will run a validation deployment on a pre-authorized salesforce org (a developer org would work fine).
Workflow Setup
The basic idea for continuous integration is to ensure that any changes you or your team make to the code base are tested. This can be done by setting up a workflow that will run a validation deployment on a pre-authorized salesforce org (a developer org would work fine).
Github Actions
Github Actions, which became available to the public on November 19th, 2020, provides an easy mechanism to automate workflows. Such as CI/CD, testing, and deploying directly from Github (where developers live already).
Continuous Integration Lifecycle
Now that we’ve discussed a few of our specific lifecycle events that trigger GitHub Actions, let’s take a step back and look at the full continuous integration lifecycle.
What Is A Workflow?
- When you talk about GitHub Actions, you talk about workflows. Workflows are configurable processes where you specify your jobs to run. This might sound difficult at first, but believe me, it’s not. Jobs are written in a YAML file, which runs when a workflow runs. We’ll go through som…
Sample Workflow
- For reference, I have created a gistwhere you can get the source code for this workflow. Let’s take a look at what this workflow is made of.
Name
- The name of the workflow or job will be used for identification in the build logs, where you can view the workflow and jobs’ statuses. If you omit the name of the workflow, GitHub uses the path to that workflow from the root of the repository.
on
- This is a requiredfield that indicates the event or events that trigger the workflow. You can pass a string, a list of strings, or a map. In the above example, we specify that the workflow should run on push and pull requests. To see a list of all the events that can trigger a workflow, visit Events that trigger workflows.
Jobs
- Each workflow is made up of one or more jobs, which are the pieces giving life to your functionality. By default, each job runs parallel, but you can make them run sequentially. A virtual environment must be specified for these jobs to run.You can do this by using the ‘runs-on’ keyword. This is a required field.
Conclusion
- We can see that in our case, on every push and pull request to the master branch, our workflow will authorize an org, run all the test classes, and deploy our changed code to that org if everything works out. This saves developers time and effort since all these things would otherwise need to be done manually. Plus, GitHub Actions provides your project with a version control system. Thi…