Skip to content

Project 3B: Pipeline Implementation

Deliverables

Final Deliverables – 65 points – due Monday, November 2, 2026, 11:59PM

Individual Pipeline Integration (45 pts)

Now that your team has a CI/CD Pipeline Design Document, each person will individually implement the check they committed to owning and merge it into the team's real pipeline.

  1. Create a separate branch in the team's repository (named appropriately for the check you're adding) to integrate it into your project's GitHub Actions workflow(s).

  2. Create a pull request to the main branch from that branch. The PR should include:

  3. Concrete evidence that you have successfully installed the check, through trackable file changes demonstrating that extra files/packages were installed.

  4. Artifacts that demonstrate that you have successfully run the check on your repository. Acceptable artifacts include output files generated by the check, a text file containing the terminal/Action-log output, or a link to a successful GitHub Actions run. Screenshots are also acceptable as additional evidence.
  5. A short comment noting anything that changed versus your design doc plan — e.g. configuration you had to tune, false positives you hit once it ran for real, or scope you narrowed to get it passing.

Grading Note

We will not be grading the quality or quantity of any code changes in these branches/PRs beyond the check itself — just the evidence that you have successfully installed, run, and merged it.

By the deadline, you will each individually submit to Gradescope:

  • A link to the PR that demonstrates that you have successfully installed, run, and merged your check, including artifacts that act as appropriate evidence as outlined above.

Final Working Pipeline (Group) (20 pts)

Once every teammate's check has been merged, your team's pipeline should run all of them alongside the deploy workflow from Checkpoint 1. To be considered successfully integrated, each check must:

  • Be merged into your main branch
  • Have been run at least once in the Git flow cycle (i.e. either during the pull request, merge, or commit stage)
  • Pass when run on your codebase. This is indicated by having a green checkmark.

This configuration must have been justified in your design document under the Integration section.

Ensuring Passing Checks

In order to ensure your checks pass successfully, you may have to make additional changes to your repository, such as fixing reported issues or tweaking check configuration. These changes should be documented and addressed in your design document.

Failing CI builds

Continually failing builds show you have not completely integrated the pipeline into your workflow.

On Gradescope, submit a link to your repository and a link to one successful run of the full pipeline (all checks + deploy) on your codebase.

Extra Credit: Feature Review (6 pts)

Now that you and your classmates have deployed your applications in 3A, you will be able to test out each other’s features and provide constructive feedback on your experience and how to improve them! Take this as an opportunity to learn about what your classmates have been working on for the past few weeks.

Note that this is an individual task.

For extra credit, you will conduct reviews of features developed by other teams. Pick three teams' deployments from the public spreadsheet to review--1 from your own section (morning of afternoon) and 2 from the other section.

For each team, you will submit a review of their feature(s) on that team's sheet. You will need to test the feature(s) as described in their UserGuide.md file and provide feedback on the following:

  1. How was the experience of using the feature(s), would this be something you think would help enable better communication between faculty and students and why?
  2. How do you think the feature can be improved? and/or What do you think the feature did well in?
  3. Did you discover any bugs using the feature(s)?

To qualify for extra credit, you will have to submit your reviews:

  • on Gradescope
  • in the appropriate sheets for the groups you want to review in the public spreadsheet. There should be one sheet per team, and you should add your review to the sheets for the teams you are reviewing.

Grading

To receive full credit for the final deadline, we expect:

  • A link to your successfully run CD GitHub action that deploys the website while following proper GitHub practices in handling deployment secrets
  • A link to your individual PR demonstrating that you successfully installed, ran, and merged your check, with evidence and a note on what changed versus the design doc plan
  • A link to a successful run of the full GitHub Actions pipeline (all teammates' checks + deploy) on your team's main branch

To receive full credit for the extra credit, we expect:

  • Your review of three different teams' features on Gradescope and on the public spreadsheet, addressing the three questions described.