I am working at a company who use the monorepo pattern to store their code. Each sub project has its own test and deploy job so every push to this repo will blindly test and deploy all the projects. In order to reduce build times I would like to only build the projects within which files have change…

This capacity does not exist at the moment. The previous discussion is found in [image] Issue: Exclude files from triggering a build opened by GittiHab on 2016-07-13 If you only edit the readme file you often forget to specify [ci-skip] in the commit message. It can't be s…

Ok no problem. Thanks BanzaiMan. A second scenario would be to try running a preliminary stage to execute the git diff which records the jobs to run on the environment. Can I set an environment variable on one stage and have it available in a later stage?

You can just make whatever checks you need ASAP – e.g. in before_install – and if they fail, exit the build early with travis_terminate <exit code>.

[image] native-api: You can just make whatever checks you need ASAP – e.g. in before_install – and if they fail, exit the build early with travis_terminate <exit code> . That doesnt help if the build should pass early if certain files are not modified and therefore do not need to be re-tested…

[image] jayvdb: That doesnt help if the build should pass early if certain files are not modified and therefore do not need to be re-tested. This sounds rather dangerous to do. Even if the particular file is unchanged, something else that affects it may have changed. In any case, such logic …

[image] native-api: This sounds rather dangerous to do. It may be dangerous sometimes, but the alternative may be to unable to run CI at all, if builds are queued. And it may never be dangerous in other cases, where a repo has clear separation of multiple components. At the moment I dont do…

[image] jayvdb: AppVeyor and GitLab CI both provide the functionality requested in this feature request, of path based selection of jobs. Bitrise CI also supports fast finishes of multiple job builds, albeit not quite as declarative as AppVeyor and GitLab. I havent significantly played with Circ…

Of course I can solve it, but I am not being paid to spec it or build it. The purpose of a feature request is to capture requirements, not the solution. However the way that AppVeyor and GitLab CI do it would be acceptable for many use cases, and is illustrative and simple enough to be almost a s…

I had a similar problem where I ended up early exiting if the current commit didn’t change files in the correct folders. This was for CircleCI but the logic would be the same. # 1. Get all the arguments of the script # https://unix.stackexchange.com/a/197794 PATHS_TO_SEARCH="$*" # 2. Make sure the…

How to skip jobs based on the files changed in a subdirectory?

Travis CI Discussions & Feedback Feature Requests

jayvdb July 19, 2019, 4:04am 4

This appears to be a dup of feature request Support for skipping builds via file filtering

Topic		Replies	Views
Skip builds when changing docs only? Travis CI Discussions & Feedback build-env	1	936	May 8, 2020
Ability to run jobs depending on what files are changed Feature Requests	1	1211	May 31, 2019
Support for skipping builds via file filtering Feature Requests	3	2783	August 24, 2022
Skip travis build if an unimportant file changed Travis CI Discussions & Feedback build-env , travis-build	3	949	November 13, 2020
Avoid running jobs if PR is documentation-related Travis CI Discussions & Feedback travis-build	2	774	July 16, 2020

How to skip jobs based on the files changed in a subdirectory?

Related topics