Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • abuild abuild
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 58
    • Issues 58
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 32
    • Merge requests 32
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • alpinealpine
  • abuildabuild
  • Merge requests
  • !96

abuild.conf: don't export CARGO_BUILD_JOBS

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed omni requested to merge omni/abuild:unset-cargo-build-jobs into master May 13, 2021
  • Overview 2
  • Commits 1
  • Pipelines 0
  • Changes 1

cargo build.jobs should default to number of logical CPUs anyway and setting it like this had at least gitlab CI pipelines get stuck at or right after crate downloads.

Found in aports!20973 (closed)

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: unset-cargo-build-jobs