Speed Up our Docker Travis CI builds #714
Comments
|
|
I |
|
I want to claim this issue. |
|
@Sj1218305 Yes it is, please reach out on Discord to share your plan of action on this issue. |
|
@Sj1218305 please work against branch |
|
Hey @Sj1218305 :) |
|
@Glide7 , I am working on this. Actually , I am new to Docker so I need some more time. I will surely reach out if any kind of help is required. |
|
Awesome, thanks for the update! |
|
@Sj1218305 also, feel free to join the #mainteners channel on our discord! https://appwrite.io/discord |
|
Hey @Sj1218305 - how are things going? Do you need assistance from us? |
|
hi, I would like to take it.
|
|
@hack3r-0m moving to Github actions is not part of this issue scope. The team is currently using Travis CI for ~60 repos and we need to have a wider plan for this kind of migration, which unfortunately is not a priority right now. |
|
@eldadfux once 0.7.x is ready and pushed to docker, let say new PRs get merged into 0.7.x branch then how is old image updated on docker hub, there must be something step in .travis.yml file to merge new code into existing Docker image? As far as caching Travis CI, docs recommend not to cache images, so the only thing to cache is |
|
@hack3r-0m sorry for the late reply. Not sure about the Docker part, can you verify its already installed in |
|
@hack3r-0m yes, mind submitting a PR removing Docker so we can make sure tests are still green? |
|
sure, i will try to do it ASAP |
|
@eldadfux |
We want to use caching to speed up Appwrite's Travis CI build process, and we can use the community help here.
Currently our build process time is around ~10 minutes which is OK, but as faster it can be less time maintainers needs to wait for confirmation that there changes are running as expected.
This change should be focused on our Travis CI YAML file. Any suggestions for improving the code base should be handled on an independent issue.
The text was updated successfully, but these errors were encountered: