Archives
/
project-layout
mirror of https://github.com/golang-standards/project-layout
2
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

notes about the config files for the CI tools that are not flexible enough about their config files

Browse Source
pull/15/head
Kyle Quest 6 years ago
parent dfad3214cd
commit 5ab02c9d03
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File

2
README.md
Unescape Escape View File

@ -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`

2
build/README.md
Unescape Escape View File

@ -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:

Write Preview
Loading…
Cancel
Save