public-mirrors
/
composer
mirror of https://github.com/composer/composer
1
0
Fork 0
Code

Merge pull request #3869 from SchulteMarkus/patch-1 

Explaining how to deal with cyclic dependency problems within Jenkins-bu...
pull/3789/merge
Jordi Boggiano 2015-04-15 02:05:50 +01:00
parent 1b3ca77bd5 bcc387b297
commit 39c912005b
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/articles/troubleshooting.md
View File

@ -58,6 +58,11 @@ This is a list of common pitfalls on using Composer, and how to avoid them.
Use: `before_script: COMPOSER_ROOT_VERSION=dev-master composer install` to export Use: `before_script: COMPOSER_ROOT_VERSION=dev-master composer install` to export
the variable for the call to composer. the variable for the call to composer.
## Package not found in a Jenkins-build
1. Check the ["Package not found"](#package-not-found) item above.
2. Reason for failing is similar to the problem which can occur on travis-ci.org: The git-clone / checkout within Jenkins leaves the branch in a "detached HEAD"-state. As a result, composer is not able to identify the version of the current checked out branch and may not be able to resolve a cyclic dependency. To solve this problem, you can use the "Additional Behaviours" -> "Check out to specific local branch" in your Git-settings for your Jenkins-job, where your "local branch" shall be the same branch as you are checking out. Using this, the checkout will not be in detached state any more and cyclic dependency is recognized correctly.
## Need to override a package version ## Need to override a package version
Let say your project depends on package A which in turn depends on a specific Let say your project depends on package A which in turn depends on a specific