Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Feature Request: New Environment Variable for "args"

See original GitHub issue

I’m not sure if there’s a reason this was not created in the first place, but we want to pass Conan args from environment variables for CI.

CONAN_ARGS=<project_name>:shared=True, boost:shared=True

We’re implementing this on our own, but would like to see it land in CPT.

We want this because it’s not suitable for us to create conan profiles which go into as much detail as defining the options for projects and their dependencies. I did try creating project-specific profiles in the project folder, which include() global profiles. It wasn’t terrible, but it added to the directory pollution problem, hides information from the person reading the Jenkinsfile, and becomes harder to maintain at scale. There are of course advantages to the project-specific-profiles, and maybe we end up going back to that. However, it still seems like a reasonable feature to request.

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:1
  • Comments:10 (10 by maintainers)

github_iconTop GitHub Comments

solvingjcommented, Oct 9, 2018

One of the most brilliant parts of CPT is the flexibility in where users can specify. In CI web portal, CI specific files, or (shared between CI). We have used all three for different things at different times. Environment variables in CI files are more declarative and much more clear than reading through conditionals when you want an option on only one CI. I want to only do things in when logic or options are shared across CI, or I need the power of python.

solvingjcommented, Oct 1, 2018

Oh, funny, it did exist and was removed. that explains why i kinda thought i remembered it 😃

Read more comments on GitHub >

github_iconTop Results From Across the Web

[Feature Request] Support specifying `--provider` parameters ...
Supports specifying the --provider parameter through environment variables. For example, when I want to delete a cluster, I can use commands like the ......
Read more >
Passing parameters to your programs as environment variables
Passing parameters to your programs as environment variables requires that you set the proper handling of environment variables in your programs.
Read more >
Set environment variable using command line arguments
Is it possible to pass values for environment variables using command line arguments? E.g. I'd like to set a version number which is...
Read more >
Variables reference - Visual Studio Code
Variables Reference. Visual Studio Code supports variable substitution in Debugging and Task configuration files as well as some select settings.
Read more >
Environments - Laravel Vapor
This command will add a new environment entry to your project's vapor.yml file ... When using this feature, the requested number of execution...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found