Week 2
June 3 - June 7
During the second week, I made some significant progress on the project, including:
-
A working #1 Deliverable. When the user clicks on the
Pause Job
button, Flamenco sends the job topause-requested
status, and depending on the specific situation, either waits foractive
jobs to complete, fails the entire job, or sets the job status topaused
. See the following demo:
-
Had a weekly meeting and specifically talked about interactive rebase, which I could use to flexibly build on top of existing codebase while being able to keep updating the existing codebase
-
Add test cases and make sure original test cases work with the introduction of a new job status
-
More minor edge cases considerations and created a design issue
In the following week, I have some personal stuff planned, but I will:
- Build on top of what I’ve accomplished and brainstorm ways to implement submitting jobs with
paused
status (maybe involve upgrading the job compiler? Addon? Custom job type? API changes?) - Review the first PR and write more test cases