Update workflow

[kibettheophilus]

• Removed the job for cancelling previous workflows, this is not needed as a job or using external action since GitHub provides a way to cancel out of the box. Read more on Concurrency.
• Removed the trigger for on push to main since this felt like a double run which consumes the minutes twice(with the assumption that all code changes will be made via a pull request).
• Update the flow and dependency between jobs, only build can be done after all the other jobs are successful. This will make it easy to track all the failures in a single run. In the previous impl, if androidTest and test had failures, you first had to fix test then wait for the second run to be able to catch failures in the androidTest.
  • This also reduces the time the workflow takes to run because the child jobs run in parallel, it only took 3mins while the previous impl took 4mins+, check on compare on actions

Evidence kwa kalatas

1. Cancelled workflow when a new one was triggered

2. Re-organization of the jobs

I am open for discussion 😄

[MamboBryan]

@kibettheophilus I thought creating a waterfall of actions would be better than running all 3 independently and then running build later. My thought was : if the app doesn't pass linting don't even run testing, let it pass the previous phase so that it can proceed to the next phase.
CC : @tamzi @janewaitara thoughts

[kibettheophilus]

@kibettheophilus I thought creating a waterfall of actions would be better than running all 3 independently and then running build later. My thought was : if the app doesn't pass linting don't even run testing, let it pass the previous phase so that it can proceed to the next phase. CC : @tamzi @janewaitara thoughts

@MamboBryan I see your POV.

[MamboBryan]

Way forward on this @kibettheophilus ?

[kibettheophilus]

Way forward on this @kibettheophilus ?

I was waiting to hear from @tamzi @janewaitara about their opinions, but I can just close it.