mirror of
https://github.com/golang-standards/project-layout.git
synced 2026-11-11 23:07:50 +03:00
notes about the config files for the CI tools that are not flexible enough about their config files
This commit is contained in:
1 parent
dfad3214cd
commit
5ab02c9d03
2 files changed
+2
-2
No files matched your search
@@ -88,7 +88,7 @@ Packaging and Continous Integration.
|
||||
|
||||
Put your cloud (AMI), container (Docker), OS (deb, rpm, pkg) package configurations and scripts in the `/build/package` directory.
|
||||
|
||||
Put your CI (travis, circle, drone) configurations and scripts in the `/build/ci` directory.
|
||||
Put your CI (travis, circle, drone) configurations and scripts in the `/build/ci` directory. Note that some of the CI tools (e.g., Travis CI) are very picky about the location of their config files. Try putting the config files in the `/build/ci` directory linking them to the location where the CI tools expect them (when possible).
|
||||
|
||||
### `/deployments`
|
||||
|
||||
|
||||
+1
-1
@@ -4,7 +4,7 @@ Packaging and Continous Integration.
|
||||
|
||||
Put your cloud (AMI), container (Docker), OS (deb, rpm, pkg) package configurations and scripts in the `/build/package` directory.
|
||||
|
||||
Put your CI (travis, circle, drone) configurations and scripts in the `/build/ci` directory.
|
||||
Put your CI (travis, circle, drone) configurations and scripts in the `/build/ci` directory. Note that some of the CI tools (e.g., Travis CI) are very picky about the location of their config files. Try putting the config files in the `/build/ci` directory linking them to the location where the CI tools expect them (when possible).
|
||||
|
||||
Examples:
|
||||
|
||||
|
||||
Reference in new issue
Block a user