Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • irdest-corrupted irdest-corrupted
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 14
    • Issues 14
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 5
    • Merge requests 5
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • we
  • irdest-corruptedirdest-corrupted
  • Issues
  • #25
Closed
Open
Created Aug 12, 2021 by Ayush Shrivastava@s-ayush2903Developer

ci: Reports not being uploaded to CI on Job failure

Describe the bug

The main purpose of uploading lint reports to CI is only that devs are able to see all the errors on the browser itself without wasting any time. But this doesn't happen as the reports don't get uploaded to the CI. I believe the problem here is that we are first running lint and then customizing the artifacts dir heirarchy, so the reports do get written to a specific location but us customizing the artifacts dir heirarchy messes that up, because as soon as the job fails, it quickly passes on to the upload artifacts section of it, where it searches for the customized path of reports but since those customization commands never ran due to the job failure, it all becomes useless.

  • We'll have to figure out a way to maintain customized dir heirarchy in our artifacts archive and also upload the reports always.

  • See: https://git.irde.st/we/irdest/-/blob/develop/ci/pipeline-scripts/irdest-android-app-ci.yml#L15-21, as line#15 fails control passes to line#18 and lines between 'em get rendered useless :(

Component

CI

To Reproduce

Steps to reproduce the behavior: Commit the changes so that it violates lint rules and push it to any branch.

Expected behavior

Reports should always be uploaded no matter whether job fails or passes

Screenshots(If Applicable)

NA, but you can see the failing job here: https://git.irde.st/s-ayush2903/irdest/-/jobs/34213

Environment:

NA

Assignee
Assign to
Time tracking