Enable GitLab CI automated testing

Created on 9 May 2024, 12 months ago
Updated 31 July 2024, 9 months ago

Enable GitLab CI automated testing

📌 Task
Status

Fixed

Version

2.0

Component

Miscellaneous

Created by

🇨🇦Canada Liam Morland Ontario, CA 🇨🇦

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @Liam Morland
  • Merge request !35Resolve #3446269 "Enable gitlab ci" → (Merged) created by Liam Morland
  • Pipeline finished with Failed
    12 months ago
    Total: 187s
    #168764
  • Status changed to Needs review 12 months ago
  • 🇨🇦Canada Liam Morland Ontario, CA 🇨🇦
  • 🇦🇺Australia VladimirAus Brisbane, Australia

    VladimirAus changed the visibility of the branch 2.0.x to hidden.

  • Pipeline finished with Failed
    11 months ago
    Total: 148s
    #175318
  • Pipeline finished with Failed
    11 months ago
    Total: 181s
    #175326
  • Pipeline finished with Failed
    11 months ago
    Total: 179s
    #175340
  • Pipeline finished with Failed
    11 months ago
    Total: 151s
    #175348
  • Pipeline finished with Failed
    11 months ago
    Total: 279s
    #180398
  • Pipeline finished with Success
    11 months ago
    Total: 164s
    #180410
  • 🇨🇦Canada Liam Morland Ontario, CA 🇨🇦

    I have rebased, disabled a test, and used just the default template for .gitlab-ci.yml. These changes allow the tests to pass.

    Since there are currently no automated tests being run, it would be great to get this committed so at least most of the tests are running. The disabled test can be re-enabled later once it is fixed. As well, the stricter coding standards tests can be enabled once they pass.

  • Pipeline finished with Success
    11 months ago
    Total: 244s
    #180416
  • Status changed to Needs work 11 months ago
  • 🇦🇺Australia VladimirAus Brisbane, Australia

    Test should fail if they don't pass especially for phpcs.

  • 🇨🇦Canada Liam Morland Ontario, CA 🇨🇦

    A good way to start is to get tests running based on the default template. This will help prevent regressions because any new pull requests will have tests run on them. This allows adopting the practice of not merging pull requests unless the tests pass.

    Then work on getting phpcs, etc. to pass without any warnings. Once each passes without warnings, the warnings can be upgraded to an error.

    I don't have any more time to work on getting phpcs, etc. to pass.

  • Status changed to Needs review 9 months ago
  • 🇦🇺Australia VladimirAus Brisbane, Australia
  • Status changed to RTBC 9 months ago
  • 🇦🇺Australia jannakha Brisbane!

    hurray for CI!
    it fails - so next tasks to make it green!

  • Pipeline finished with Skipped
    9 months ago
    #226715
  • Status changed to Fixed 9 months ago
  • 🇦🇺Australia VladimirAus Brisbane, Australia

    Thank you! 🍻

  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024