Travis CI is taking a long time to compile the code about meilix HOT 20 CLOSED

Here are some findings: @niccokunzmann @meets2tarun @xeon-zolt @mariobehling

• Seems like Travis has better download speeds when caches are in the S3 bucket in the us-east region.
• The apt updater script can be made to run parallel.
• Travis does things faster if we put things we need in the .travis.yml file [Don't change build.sh as if we run apt-get install again from there since, packages are present apt will skip downloading and say that they are upto date] like this

 include:
    - os: linux
      addons:
        apt:
          sources:
            - ubuntu-toolchain-r-test
          packages:
            - packagename-version

This would reduce the build time.

from meilix.

It would make a small difference as the script won't take much time. But each second is valuable right?

from meilix.

@meets2tarun I get the logic now, but on the other hand, I have found some simple logical problems on to both branches which will be required. Opening issues for those.

I hope you to give a PR

On the way.

from meilix.

Yeah, it would be great to reduce the time. There are other CI in the market i.e; circleci, snap-ci, etc but travis is quite helpful and Github also recommends Travis. But if only time matterss, we can try a better one.

from meilix.

As I understood: building the metapackages is done when the iso image is built, ist that so? If it is so: Is there a way to split the process: Separate meta packages from building the image?

from meilix.

Yea you are right @niccokunzmann, we are also putting them into our apt source repository (gh-pages acts as an apt source repository)

from meilix.

We can't separate the process as far as I can see.

from meilix.

@Abhi2424shek I see that aptRepoUpdater.sh and build.sh are two different scripts.

from meilix.

But now to the analysis: which steps are taking which time and what is taking it so long?

from meilix.

Yep. But we can't split build.sh,h owever we can't be sure, I am investigating.... It would be best if you guys could also do the same :)

from meilix.

Distributed computing can be applied, but I don't think Travis is supports it.

from meilix.

@abishekvashok
Thanks, you remind me again to look at the parallel build and thanks for the finding too.
I'm referring you and this.

from meilix.

@abishekvashok I parallel the build but it still takes the same time?
https://travis-ci.org/fossasia/meilix/builds/246607082

from meilix.

Its not yet solved. The sources are still fetched from build.sh please be careful.

from meilix.

The sources are still fetched from build.sh please be careful.

Please elaborate

from meilix.

As i stated:

Travis does things faster if we put things we need in the .travis.yml file [Don't change build.sh as if we run apt-get install again from there since, packages are present apt will skip downloading and say that they are upto date] like this
include:
- os: linux
addons:
apt:
sources:
- ubuntu-toolchain-r-test
packages:
- packagename-version

from meilix.

any updates on this @meets2tarun

from meilix.

Since we have shifted the build to generator branch from the master branch and generator branch uses a different strategy to build the ISO.
But on the other hand master branch uses the same old method to build and same time also.
I have doubt in this approach, and I hope you to give a PR. @abishekvashok

from meilix.

@tabesin i didnt solve it as yet. A commit to the master branch takes in 24mins to complete

from meilix.

@abishekvashok
If you're working on the issue then kindly open the issue and file a PR.

from meilix.