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.

Load configuration from object in S3

See original GitHub issue

It would be useful if CASC_JENKINS_CONFIG could point to an s3:// URL and load configuration from there. While you could use a signed S3 URL, the expiration date for such has a maximum of a week. It would be trivial to point to an S3 URL when using an instance or service role; in other cases, additional configuration for AWS credentials would be needed.

Issue Analytics

State:
Created 4 years ago
Reactions:1
Comments:8 (3 by maintainers)

Top GitHub Comments

2reactions

timjacommented, Mar 27, 2019

Might be good for this to be a separate plugin? Changes in here could be made if that doesn’t work very well currently

1reaction

kmcquadecommented, Apr 5, 2019

@jbouse you might want to check out https://github.com/odavid/my-bloody-jenkins#environment-variables. See his note on the environment variable JENKINS_ENV_CONFIG_YML_URL.

We just use that and assign an IAM role to the ECS task. Using my-bloody-jenkins, our Jenkins instances just grab the config.yml file at boot and polls for changes every 30 seconds 😃