Update local-jobs.md #1107
Merged
Update local-jobs.md #1107
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Qualify working_directory for clarity and add limitation and workaround for env vars.
keybits
reviewed
Jun 2, 2017
jekyll/_cci2/local-jobs.md
Outdated
| @@ -87,12 +91,10 @@ Caching is not currently supported in local jobs. When you have either a `save_c | |||
|
|
|||
| ### Relative Path for working_directory | |||
|
|
|||
| Using a relative path for `working_directory` is not currently supported in local jobs. If a relative path is used in `working_directory`, then `circleci` returns an error and immediately exists. | |||
| The `working_directory:` key in your `.cirecleci.config.yml` file must not use a relative path for local jobs. If a relative path is used in `working_directory`, then `circleci` returns an error and immediately exists. To workaround this problem, change the value of the `working_directory:` key in your `.cirecleci.config.yml` file to use an absolute path. | |||
There was a problem hiding this comment.
Typo: exists should be exits
keybits
reviewed
Jun 2, 2017
jekyll/_cci2/local-jobs.md
Outdated
| @@ -77,6 +77,10 @@ The CLI tool automatically checks for updates and will prompt you if one is avai | |||
|
|
|||
| Although running jobs locally with `circleci` is very helpful, there are some limitations. | |||
|
|
|||
| ### Setting Environment Variables | |||
|
|
|||
| We don't yet have an ideal solution for setting environment variables, but there is a workaround. Define which variables you want to export in a file within your repository (don't commit it - just have it in the directory). Then set BASH_ENV to that filename in your `.cirecleci.config.yml` file. The file will be automatically sourced on each command as long as BASH_ENV is correct. | |||
There was a problem hiding this comment.
Suggest to be super clear this is for local builds:
"We don't yet have an ideal solution for setting environment variables on local builds, ..."
I've not had a chance to check, but if BASH_ENV is set in .circleci/config.yml what happens when that file doesn't exist on a non-local build?
incorporate Tom's changes
FelicianoTech
suggested changes
Jun 8, 2017
incorporate Ricardo fixes
FelicianoTech
approved these changes
Jun 8, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Qualify working_directory for clarity and add limitation and workaround for env vars.