E08: Continuous integration for your project

Providing the GitHub Action workflow definition

If your project does not contain a .github/workflows directory with a ci.yml file, you should copy the meteor-application-template-production workflows directory with its ci.yml file.

Providing a badge on your CI status in your documentation

The meteor-application-template-production readme.md page contains a badge with the status of its GitHub Action to build and test the system. Here it is:

You must provide a badge in your project’s github.io site that indicates your project’s build status. To do this:

First, edit the first line of your project’s ci.yml file to rename the workflow to your project’s name.

Second, copy the following code into your github.io site:

![ci-badge](https://github.com/ics-software-engineering/meteor-application-template-production/workflows/ci-meteor-application-template-production/badge.svg)

Third, edit this line of code:

• Change “ics-software-engineering” to your project’s organization name.
• Change “meteor-application-template-production” to your project’s application repo name.
• Change “ci-meteor-application-template-production” to your project’s workflow name.

Now this badge should display the most recent results of your project’s build.

Submission Instructions

Continuous integration should be implemented by the time and date indicated on the Schedule page. In Laulima submit a screenshot of the CI badge for your project.