Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Provide a granular way to depend on OS / Architecture #1315

Closed
gsoltis opened this issue May 31, 2022 · 2 comments
Closed

Provide a granular way to depend on OS / Architecture #1315

gsoltis opened this issue May 31, 2022 · 2 comments
Assignees
@anthonyshew
Labels
area: caching Issues reported about incorrect cache hits or misses area: ergonomics Issues and features impacting the developer experience of using turbo linear: turbo Issues to sync to Linear for Turborepo team needs: investigation The bug / idea needs more investigation

Comments

@gsoltis
Copy link
Contributor

gsoltis commented May 31, 2022 •
edited by padmaia
Loading

Describe the feature you'd like to request

Some tasks, particularly tests and builds for non-frontend, non-backend binaries, behave differently on different OSes and architectures. turbo should be able to be easily configured to not cache results across platforms / architectures

Describe the solution you'd like

Most likely something in turbo.json to apply either monorepo-wide or per-task.

Describe alternatives you've considered

Environment variables can be used, but require every person or process who interacts with turbo to have them set appropriately.

TURBO-2047
@gsoltis gsoltis mentioned this issue Jun 2, 2022
Closed
@mehulkar
Copy link
Contributor

Related: #4124

@mehulkar mehulkar added story area: ergonomics Issues and features impacting the developer experience of using turbo area: caching Issues reported about incorrect cache hits or misses needs: team input Filter for core team meetings labels Oct 20, 2023
@padmaia padmaia added the linear: turbo Issues to sync to Linear for Turborepo team label Jan 16, 2024
@anthonyshew anthonyshew mentioned this issue Jan 22, 2024
Merged
anthonyshew added a commit that referenced this issue Jan 26, 2024
@anthonyshew @NicholasLYang
Document handling of Node.js versions, OS, and arch. (#7072)
23f231f 
### Description

While we may consider OS and arch handling as a feature in the future,
we don't today. Here, we're documenting how to handle this advanced use
case as well as jotting down a proper way of handling Node.js versions.

Closes #4124 and
#1315

---------

Co-authored-by: Nicholas Yang <nicholas.yang@vercel.com>
@mehulkar mehulkar added needs: investigation The bug / idea needs more investigation and removed needs: team input Filter for core team meetings labels Jan 26, 2024
@anthonyshew
Copy link
Contributor

Documented in #7072

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@anthonyshew anthonyshew

Labels
area: caching Issues reported about incorrect cache hits or misses area: ergonomics Issues and features impacting the developer experience of using turbo linear: turbo Issues to sync to Linear for Turborepo team needs: investigation The bug / idea needs more investigation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@gsoltis @mehulkar @padmaia @anthonyshew