Enable GitLab CI automated testing

Created on 9 May 2024, about 2 months ago
Updated 24 May 2024, about 1 month ago

Enable GitLab CI automated testing

📌 Task
Status

Needs work

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" → (Open) created by Liam Morland
  • Pipeline finished with Failed
    about 2 months ago
    Total: 187s
    #168764
  • Status changed to Needs review about 2 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
    about 1 month ago
    Total: 148s
    #175318
  • Pipeline finished with Failed
    about 1 month ago
    Total: 181s
    #175326
  • Pipeline finished with Failed
    about 1 month ago
    Total: 179s
    #175340
  • Pipeline finished with Failed
    about 1 month ago
    Total: 151s
    #175348
  • Pipeline finished with Failed
    about 1 month ago
    #180398
  • Pipeline finished with Success
    about 1 month ago
    #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
    about 1 month ago
    #180416
  • Status changed to Needs work about 1 month 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.

Production build 0.69.0 2024