Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
CI_Source CI_Source
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Labels
    • Labels
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Metrics
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • Support
  • CI_SourceCI_Source
  • Merge requests
  • !29

Merged
Created Dec 14, 2022 by Ben Avison@bavisonDeveloper

List information about the build environment used in softload jobs

  • Overview 0
  • Commits 1
  • Pipelines 4
  • Changes 1

List information about the build environment used in softload jobs

Softload jobs (and deployment jobs, and when they're re-enabled, ROM jobs) in submodule pipelines save time by using the build trees which are regenerated overnight by each superproject pipeline. The build trees are packaged as a zip file, and contain the whole RiscOS directory, but not other top-level files such as .gitlab-ci.yml, nor the .git directory, in order to save space.

It is desirable to be able to access the version numbers of the components from this build tree in the submodule job log. This is expected to be helpful in debugging build issues, but would also form a record of what constituted "top of tree" at the time of the build: whilst this might be obvious at the time that the job runs, it could well be less so when looking back at the job log days, weeks or even longer afterwards.

However, since the build zip file doesn't contain git information, this isn't directly accessible from the submodule pipeline. Instead, generate a listing of version information (using the same git describe command as is used when generating prodcommit logs) during the superproject pipeline, and print a link to it during the submodule job (with the actual URLs involved being conveyed by a file called BuildInfo which is inserted into the zip file).

Take the opportunity to also dump information about the use of CrossCompilationSupport branches, to assist with diagnosing issues related thereto.

Edited Dec 16, 2022 by Ben Avison
Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Source branch: manifest