Draft: Split build and test

At some point it might be interesting to split build jobs from testing jobs, specially when testing starts to be costly (e.g. a simulation) and you do not want either to wait until build + test is finished, or even you do not want to run tests (i.e. simulations) for every commit.

This MR is not really intended to be merged, just as a point for discussion.

assigned to @jon.azpiazu

@inigo.moreno I have been playing with this idea of splitting building vs testing jobs. What do you think?

Looks interesting. Why do you push and pull an image to the registry? You are not using it afterwards. This is only using the ccache from the previous build so that the build is quicker, no?

That is actually a typo, good that you realized it. The idea is that testing should reuse the image, so no need to reinstall dependencies or recompile the whole thing. The ccache can probably be omitted.

Target and upstream repositories will still be built, even in dependencies are in the base image, so I guess ccache should accually help, no?

added 1 commit

• ee6930c7 - Fix using previous image in test job

Compare with previous version

By the way, I am using this repo for testing this template, feel free to propose a more interesting example (e.g. a repo based on C++).

Maybe the testing examples repo could be used?

One thing I'd consider here is not to make this the default behavior. That is, I'd make not testing require explicit opt-in.

If running tests is made opt-in instead, people who do write tests but don't think about this may end up not actually exercising their tests.

added 1 commit

• 050f7d92 - Fix docker image tag to avoid overlapping between distros

Compare with previous version

added 90 commits

• 050f7d92...4cf11148 - 85 commits from branch master
• 6a604da4 - Quick example trying to split build and test jobs
• bb607712 - Fix typo
• b199f08e - Add caching
• e8d1bc09 - Fix using previous image in test job
• f155c217 - Fix docker image tag to avoid overlapping between distros

Compare with previous version

added 1 commit

• f90f60be - Fix intermediate docker image tag

Compare with previous version

Waking up this MR in https://git.code.tecnalia.com/tecnalia_robotics/converging/converging_noether_demo/-/tree/tmp/ci-template-build-and-test?ref_type=heads

This should be adapted to work with the auto-rules, right? Or are you planning on adding it as an optional yaml to include?

Probably yes, right now I am just trying to make it work and decide if it is worth pursuing, and then we can think on the logic.

added 1 commit

• 99b62da0 - Fix add dind to job

Compare with previous version

added 1 commit

• 189dbaf2 - Set jobs as hidden

Compare with previous version

added 1 commit

• 80a77994 - Add docker tag

Compare with previous version

added 1 commit

• 6259c0d9 - Adding rule as I do not see my job

Compare with previous version

added 1 commit

• 96fa99f0 - Delete rules from notest job, as there was no rule in test job and i could see it

Compare with previous version

added 1 commit

• c5199f68 - Test stage was not recognized

Compare with previous version

added 1 commit

• 3b901760 - Change to pre stage

Compare with previous version

added 1 commit

• 6e904f56 - Back to build stage

Compare with previous version

added 1 commit

• 661bdf39 - Add lfs hooks to new jobs

Compare with previous version