Context variables randomly injected in the environment


We works on an open-source project with repository forks and pull request. As a collaborator, I have my own CirceCI account and I have no problem to run the CircleCI build tasks on each PR.

But we have troubles running the workflow on the main project CircleCI environnment : the workflow uses a context to inject parameters for orb aws-ecr and the Spin Up Environment view shows that the context variables are sometimes injected in the environnment, sometimes not. It causes task failures as it resolves context parameters as empty string :

$ #!/bin/bash -eo pipefail
aws configure set aws_access_key_id \
--profile default
usage: aws [options] <command> <subcommand> [<subcommand> ...] [parameters]
To see help text, you can run:

  aws help
  aws <command> help
  aws <command> <subcommand> help
aws: error: too few arguments
Exited with code 2

We have not found any correlation to explain this behavior. It fails far more usualy than it success.

Any ideas ?




Still have the problem : sometimes the vars from the context are injected, sometimes they don’t.

Any clues ?

@AlexandreBrach Can you post your config.yml and a link to your project on CircleCI?

Is the context restricted? If so, it’s normal that it would fail for some users but not for others.