You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have read the article https://www.pantsbuild.org/docs/using-pants-in-ci but I would find it very helpful if anyone could share an example repo of how they have achieved integrating pants successfully with Jenkins CI. Specifically I am looking for examples in a monorepo where one Jenkinsfile at the root of the project folder is handling the CI pipeline for every project in the monorepo. I believe this is where Pants would shine because it is able to detect the files which contain any changes and only run the lint/tests on those projects instead of running the CI pipeline on all the projects in the monorepo. Any help on understanding this further is appreciated.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have read the article https://www.pantsbuild.org/docs/using-pants-in-ci but I would find it very helpful if anyone could share an example repo of how they have achieved integrating pants successfully with Jenkins CI. Specifically I am looking for examples in a monorepo where one Jenkinsfile at the root of the project folder is handling the CI pipeline for every project in the monorepo. I believe this is where Pants would shine because it is able to detect the files which contain any changes and only run the lint/tests on those projects instead of running the CI pipeline on all the projects in the monorepo. Any help on understanding this further is appreciated.
Beta Was this translation helpful? Give feedback.
All reactions