ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #travis
The cache feature in Travis CI allows for the persistence of specific directories, such as node_modules or .maven , across multiple build cycles to optimize execution time. While this reduces installation overhead, it introduces a potential discrepancy between a clean local environment and the remote CI runner. When dependencies are updated in a lock-file bu
When a pull request originates from a fork, Travis CI must decide which .travis.yml to run, whether to expose secure environment variables, and how to report the resulting status back to GitHub. The .travis.yml is taken from the head branch of the pull request, which allows a malicious fork to alter build steps while secrets remain hidden. However, the exact
Context Travis CI enforces a documented maximum of 200 jobs per build matrix expansion and a repository-level concurrency limit (default 5 for public repositories on travis-ci.org). When multiple matrix builds from the same repository enter the queue concurrently, the scheduling order of their jobs across the shared concurrency slots is not specified in the
When using the travis_retry helper to handle transient failures, the goal is to retry a failing shell command without causing duplicate side effects from non‑idempotent operations such as database writes, file appends, or external API calls. The helper retries the entire process but does not wrap the command in a transaction, roll back partial changes, or pr
Cache Persistence and Dependency Rotation Travis CI provides a cache key in the .travis.yml configuration to persist directories across builds, which is typically used for node_modules or vendor folders to optimize execution time. When dependencies are updated frequently, relying on a static cache key can lead to stale artifacts being injected into new build
Travis CI utilizes the matrix key in .travis.yml to execute parallel job variations. While these jobs are defined in a specific order within the configuration file, the scheduler prioritizes resource utilization, which often results in non-deterministic start times and execution sequences across different builds. This behavior introduces uncertainty when bui
A Travis CI build with a deploy section in .travis.yml runs the deploy stage only after script succeeds, and the on keys ( branch , tags , condition ) decide whether that stage executes at all. The goal is to diagnose builds where deployment never runs and to tell a condition-based skip apart from a provider failure. The uncertainty is how those keys are mat
When using Travis CI's deploy stage to drive a zero‑downtime migration, the build exits as soon as the deploy command returns, even if the target platform (for example Kubernetes) is still performing a rolling update. This behavior is documented: Travis CI does not wait for asynchronous provider operations to complete. The 50‑minute job timeout and 10,000‑li
Secure Variable Access in External PRs Travis CI restricts the injection of secure environment variables to builds triggered by pushes to the repository or pull requests originating from internal branches. This security measure prevents credential leakage when external contributors submit code via forks. For projects requiring integration testing during the
github
kubernetes