Skip to content
Snippets Groups Projects
Select Git revision
  • merge_pipeline
  • devel default protected
  • mmenshikov-experimental-sa3
  • backward_compatibility
  • more_test
  • mmenshikov-experimental-sa
  • master protected
  • source_folder
  • 1.2 protected
  • 1.1 protected
  • 1.0 protected
  • 0.33.1 protected
  • 0.33 protected
  • 0.32 protected
  • 0.31 protected
  • 0.30 protected
  • 0.29 protected
  • 0.28 protected
  • 0.27 protected
  • 0.26 protected
  • 0.25 protected
21 results
Compare
Roman Azarenko's avatar
code-analysis: Factor out package versions into Docker build arguments,...
Roman Azarenko authored 
code-analysis: Factor out package versions into Docker build arguments, replace default-jre -> default-jre-headless

Package versions are now factored out as arguments, so that they can even be automatically updated from
iopsys/iopsyswrt by a pipeline.

default-jre has been replaced by default-jre-headless, since this image is designed to run in a container without UI,
so there's no need to pull in graphical dependencies, saving around 300 MB in compressed form:

	REPOSITORY                                                   TAG        IMAGE ID       CREATED          SIZE
	dev.iopsys.eu:5050/iopsys/gitlab-ci-pipeline/code-analysis   iop-8847   aaf075c8e753   23 minutes ago   2.25GB

	REPOSITORY             TAG       IMAGE ID       CREATED        SIZE
	iopsys/code-analysis   latest    ffaa1c3094dc   7 months ago   2.55GB
aaba21cd
History
Roman Azarenko's avatar aaba21cd
History
Name Last commit Last update
docker/code-analysis
public
.gitignore
.gitlab-ci.yml
README.md
static-code-analysis.yml
README.md

gitlab-ci-pipeline

Shared pipelines for CI. Different types of testing that is done in the CI pipeline:

  • Unit testing is defined as testing individual modules of an application in isolation (without any interaction with dependencies) to verify that the code is doing things right
  • Integration testing is defined as checking if different modules are working fine when combined together as a group
  • Functional testing is defined as testing a slice of functionality in the system (may interact with dependencies) to verify that the code is doing the right things

The tests mentioned above should not be hardware dependent, it should be possible to execute the tests in a single Docker container.