[FEAT] run-many --tags=tag1,tag2 #2675
Comments
|
This issue has been automatically marked as stale because it hasn't had any recent activity. It will be closed in 14 days if no further activity occurs. |
|
Not sure what to do here. Should I keep this alive until it's implemented or rejected? |
|
Sorry. The issue was marked by mistake. I removed the label. |
|
To add on to this, another related feature that would be really nice is the ability to check if something is affected by tag. EG # print affected by tag, one line per service
SERVICES_TO_DEPLOY=$(nx print-affected --tags=services --target=build --select=tasks.target.project | awk 'gsub(/, /, "\n")')
# if there are more than one line output by
if [[ $(echo $SERVICES_TO_DEPLOY | wc -l) -gt 0 ]] echo "run deploy command for services" |
|
Yes, Yes, Yes, we need this!! We need to group multiple apps/libs to larger applications and it would be soo nice to be able to run them with a single tag! |
`nx run-many --target=deploy --tags=foo` runs the given target for all projects that have a tag `foo` configured in nx.json. Closes nrwl#2675.
`nx run-many --target=deploy --tags=foo` runs the given target for all projects that have a tag `foo` configured in nx.json. Closes nrwl#2675.
`nx run-many --target=deploy --tags=foo` runs the given target for all projects that have a tag `foo` configured in nx.json. Closes nrwl#2675.
`nx run-many --target=deploy --tags=foo` runs the given target for all projects that have a tag `foo` configured in nx.json. Closes nrwl#2675.
`nx run-many --target=deploy --tags=foo` runs the given target for all projects that have a tag `foo` configured in nx.json. Closes nrwl#2675.
`nx run-many --target=deploy --tags=foo` runs the given target for all projects that have a tag `foo` configured in nx.json. Closes nrwl#2675.
`nx run-many --target=deploy --tags=foo` runs the given target for all projects that have a tag `foo` configured in nx.json. Closes nrwl#2675.
`nx run-many --target=deploy --tags=foo` runs the given target for all projects that have a tag `foo` configured in nx.json. Closes nrwl#2675.
|
This issue has been automatically marked as stale because it hasn't had any recent activity. It will be closed in 14 days if no further activity occurs. |
|
Please keep it open stale bot |
`nx run-many --target=deploy --tags=foo` runs the given target for all projects that have a tag `foo` configured in nx.json. Closes nrwl#2675.
`nx run-many --target=deploy --tags=foo` runs the given target for all projects that have a tag `foo` configured in nx.json. Closes nrwl#2675.
|
Hi all, just dropping in to share my 0.02c, its seems like the |
|
this feature would be absolutely great!! |
|
+1 |
|
Still wondering why this haven't been implemented yet 😅 |
|
Agree, it will be quite useful for me also! Right now I have to list all projects as excluded in different tasks manually, grouping projects by tag will simplify this process a lot and make it much more scalable. |
|
We just came across the same requirement. We tag based on business domains on a higher level. In the pipeline related to the business domain I just want to lint all those projects and this would be very helpful |
|
That would be great indeed, nice to see there is a PR open for that! |
|
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context. |
Would be nice if we could use tags with the
nx run-manycommand.Example
> nx run-many --target=build --tags=core,demo-appThe text was updated successfully, but these errors were encountered: