EC2 website & project proposal init
This commit is contained in:
1 parent
8af93058df
commit
916ee92f90
17 files changed
+340
-14
No files matched your search
@@ -0,0 +1,19 @@
|
||||
\chapter{Project Proposal}
|
||||
\ChapterLabel{ProjectProposal}
|
||||
\index{GitHub Actions}\index{Jenkins}
|
||||
|
||||
\section{Proposed Tool: GitHub Actions}
|
||||
We propose researching GitHub Actions and comparing it with Jenkins, which
|
||||
will be introduced in class. GitHub Actions interests us because our group
|
||||
already uses GitHub to maintain source code and documentation. We want to
|
||||
understand how repository workflows can automate the build, testing, and
|
||||
deployment of our Dockerized website to AWS.
|
||||
|
||||
Our comparison will consider setup effort, workflow configuration, and
|
||||
visibility into build and deployment results. A future demonstration could
|
||||
provide a manually triggered workflow that builds and deploys the application.
|
||||
For this proposal, no installation or implementation of the comparison tool
|
||||
is claimed. The current proof of concept is the manually deployed EC2 website.
|
||||
|
||||
% Draft selection based on the earlier discussion: both authors should confirm
|
||||
% GitHub Actions versus Jenkins before submitting this chapter.
|
||||
Reference in new issue
Block a user