action #57050

Turn off travis

Added by coolo 5 months ago. Updated 3 days ago.

Status:ResolvedStart date:30/09/2019
Priority:HighDue date:
Assignee:okurz% Done:

100%

Category:Organisational
Target version:Current Sprint
Difficulty:medium
Duration:

Description

Most obvious lack will be documentation generation, possibly more


Subtasks

action #57548: Move building and publishing of docs to CircleCIResolvedandriinikitin


Related issues

Related to openQA Project - action #53915: switch "travis_test" aka. "openqa_dev" container to a sup... Resolved 07/09/2019
Related to openQA Project - action #55478: Evaluate circleci for openQA Resolved 14/08/2019
Related to openQA Project - action #55364: Let's make codecov reports reliable New 12/08/2019
Related to openQA Project - action #60056: badge in https://github.com/os-autoinst/openQA/blob/maste... Resolved 19/11/2019
Related to openQA Project - action #57047: Mark .circleci/dependencies.txt as generated file Rejected 18/09/2019

History

#1 Updated by mkittler 5 months ago

Not sure about the coverage data. Likely the Circle CI job doesn't upload it to codecov yet.

#2 Updated by andriinikitin 5 months ago

  • Related to action #53915: switch "travis_test" aka. "openqa_dev" container to a supported base since Leap 42.3 is EOL added

#3 Updated by andriinikitin 5 months ago

At the moment circleci runs tests without codecov, so coverage must be implemented / tested as part of this ticket

#4 Updated by andriinikitin 5 months ago

#5 Updated by andriinikitin 5 months ago

  • Status changed from New to In Progress
  • Assignee set to andriinikitin

#6 Updated by okurz 5 months ago

  • Blocks action #57047: Mark .circleci/dependencies.txt as generated file added

#7 Updated by andriinikitin 5 months ago

Now I think dependencies.txt must be renamed to something like ci-setup.txt or testing-layout.txt or packages-used.txt
Because its role is to set up consistent testing environment, and current name may make impression that it is for managing dependencies.

#9 Updated by cdywan 4 months ago

  • Status changed from In Progress to Blocked

Blocked by #57548

#10 Updated by okurz 4 months ago

  • Related to action #55364: Let's make codecov reports reliable added

#11 Updated by okurz 3 months ago

  • Status changed from Blocked to Resolved

With also the docs generation done properly in circle CI we can either set this ticket to "Resolved" or we can keep it open to cover os-autoinst potentially. @andriinikitin I set it to "Resolved" now as we decided in the weekly QA tools meeting that os-autoinst is not important or urgent. Please feel welcome to reopen with a comment if you think differently.

#12 Updated by okurz 3 months ago

  • Status changed from Resolved to Workable

Ok, I was wrong. We are not really done, e.g. see

$ git grep -i travis
.gitignore:.openqa-travis
Makefile:ifeq ($(TRAVIS),true)
Makefile:       env | grep -E 'CHECKSTYLE|FULLSTACK|UITEST|GH|TRAVIS|CPAN|DEBUG|ZYPPER' > $(docker_env_file)
README.asciidoc::travis-ci: image:https://api.travis-ci.org/os-autoinst/openQA.svg?branch=master[link=https://travis-ci.org/os-autoinst/openQA]
README.asciidoc:{codecov} {travis-ci}
cpanfile:feature 'coverage', 'coverage for travis' => sub {
docs/Contributing.asciidoc:* Every commit is checked by https://travis-ci.org/travis[Travis CI] as soon as
docs/Contributing.asciidoc:  which is made using +docker/travis_test/Dockerfile+ within the openQA repository.
docs/Contributing.asciidoc:tests are executed in the same environment as on the Travis CI. This allows to reproduce issues
docs/Contributing.asciidoc:and based on the `Dockerfile` within the `docker/travis_tests` sub directory of the openQA repository.
docs/Contributing.asciidoc:Logs are redirected to a logfile when running tests within Travis. The output can therefore not be asserted using +Test::Output+. This
script/generate-documentation:            echo "" >> last.commit # somehow travis does not like \n
script/run-tests-within-container:if test -n "$TRAVIS"; then
t/ui/21-admin-needles.t:    # the following should work, but apparently doesn't - at least when executing tests in Travis:

#13 Updated by okurz 3 months ago

  • Related to action #60056: badge in https://github.com/os-autoinst/openQA/blob/master/README.asciidoc references travis CI, should be circle CI added

#14 Updated by okurz 3 months ago

  • Blocks deleted (action #57047: Mark .circleci/dependencies.txt as generated file)

#15 Updated by okurz 3 months ago

  • Related to action #57047: Mark .circleci/dependencies.txt as generated file added

#16 Updated by okurz 3 months ago

  • Status changed from Workable to In Progress
  • Assignee changed from andriinikitin to okurz

#17 Updated by okurz 3 months ago

  • Status changed from In Progress to Feedback

merged but still not there yet: https://github.com/os-autoinst/openQA/pull/2579

#18 Updated by okurz about 1 month ago

  • Status changed from Feedback to Workable
  • Assignee deleted (okurz)

Also merged. But there are still references to travis in the github repo.

#19 Updated by okurz about 1 month ago

  • Status changed from Workable to In Progress
  • Assignee set to okurz

Actually I still have https://github.com/os-autoinst/openQA/pull/2587 open and just updated the branch. Waiting for circle CI test results.

It's hard. Fails in https://app.circleci.com/jobs/github/os-autoinst/openQA/12157 and I did not yet understand why. Did I miss another reference? Will apply https://github.com/os-autoinst/openQA/pull/2698 first. This should really be trivial.

#20 Updated by okurz about 1 month ago

  • Status changed from In Progress to Feedback

#21 Updated by cdywan 21 days ago

gh#2698 got merged

#22 Updated by okurz 20 days ago

rebased https://github.com/os-autoinst/openQA/pull/2587/files . I assume circle CI also sets the environment variable "CI" which then goes into "run-tests-within-container". I guess the right approach would be to delete that part in the Makefile as well as anything related to "run-tests-wihin-container" unless we find another use case for these. But we should really bring circle CI tests a bit closer again to what developers would do for manual testing.

#23 Updated by okurz 3 days ago

  • Status changed from Feedback to Resolved

This is as much as we can do. There is unfortunately more duplication introduced by andriinikitin than we had in before. We should try to solve that in #53546

Also available in: Atom PDF