Parcourir la source

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

chore/proposed-structure
Kyle Quest il y a 7 ans
Parent
révision
5ab02c9d03
2 fichiers modifiés avec 2 ajouts et 2 suppressions
  1. +1
    -1
      README.md
  2. +1
    -1
      build/README.md

+ 1
- 1
README.md Voir le fichier

@@ -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 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` ### `/deployments`




+ 1
- 1
build/README.md Voir le fichier

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




Chargement…
Annuler
Enregistrer