1. 05 Nov, 2017 1 commit
  2. 10 Aug, 2017 1 commit
  3. 31 Jul, 2017 1 commit
    • Ricardo Martincoski's avatar
      .gitlab-ci.yml: save rootfs as artifact for runtime tests · af6b5830
      Ricardo Martincoski authored
      
      
      Sometimes when a test fails in a gitlab pipeline the reason of the
      failure cannot be determined using only the logfile.
      
      Add the modified rootfs as an artifact of the job to improve
      troubleshooting. To accomplish this, always use -k option from the test
      infra, unconditionally add the resulting images to the artifacts, and
      let the runner do the cleanup for us.
      
      These artifacts can also be useful when a test fails locally but pass at
      gitlab runners.
      
      When the test does not generate a image, this message is displayed in
      the runner log:
      WARNING: test-output/*/images/*: no matching files
      
      Cc: Arnout Vandecappelle <arnout@mind.be>
      Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
      Signed-off-by: default avatarRicardo Martincoski <ricardo.martincoski@gmail.com>
      Signed-off-by: default avatarThomas Petazzoni <thomas.petazzoni@free-electrons.com>
      af6b5830
  4. 02 Jul, 2017 2 commits
  5. 01 Jul, 2017 3 commits
  6. 10 Mar, 2017 1 commit
  7. 05 Mar, 2017 1 commit
    • Arnout Vandecappelle's avatar
      Add gitlab-CI support · 4f863d77
      Arnout Vandecappelle authored
      The buildroot repository is now mirrored on
      https://gitlab.com/buildroot.org/buildroot so we can use Gitlab-CI to
      test Buildroot. Gitlab-CI is controlled by a .gitlab-ci.yml file
      that exists in the repository.
      
      For now, the only test is building all defconfigs (inspired on
      https://travis-ci.org/buildroot/buildroot-defconfig-testing/
      
      ). Since
      all the defconfigs have to be specified in the .gitlab-ci.yml file,
      we generate the file based on .gitlab-ci.yml.in. The generated
      .gitlab-ci.yml file has to be committed into the repository, though,
      otherwise Gitlab-CI doesn't see it. So there is also a test to verify
      that .gitlab-ci.yml is up-to-date.
      
      Building all the defconfigs takes a long time. Gitlab-CI will do that
      every time it pulls from git.buildroot.org, which is once per hour.
      That is way too often. Therefore, the defconfigs are not built on pull,
      but only on explicit trigger through the API or when a tag is added.
      Signed-off-by: default avatarArnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
      [Thomas:
       - fix typo not -> no
       - add LC_ALL=C when calling 'ls -1' to get a predictable order of the
         defconfigs
       - regenerate .gitlab-ci.yml.]
      Signed-off-by: default avatarThomas Petazzoni <thomas.petazzoni@free-electrons.com>
      4f863d77