You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This project is part of our comprehensive ["SweetOps"](https://cpco.io/sweetops) approach towards DevOps.
64
-
[<imgalign="right"title="Share via Email"src="https://docs.cloudposse.com/images/ionicons/ios-email-outline-2.0.1-16x16-999999.svg"/>][share_email]
65
-
[<imgalign="right"title="Share on Google+"src="https://docs.cloudposse.com/images/ionicons/social-googleplus-outline-2.0.1-16x16-999999.svg" />][share_googleplus]
66
-
[<imgalign="right"title="Share on Facebook"src="https://docs.cloudposse.com/images/ionicons/social-facebook-outline-2.0.1-16x16-999999.svg" />][share_facebook]
67
-
[<imgalign="right"title="Share on Reddit"src="https://docs.cloudposse.com/images/ionicons/social-reddit-outline-2.0.1-16x16-999999.svg" />][share_reddit]
68
-
[<imgalign="right"title="Share on LinkedIn"src="https://docs.cloudposse.com/images/ionicons/social-linkedin-outline-2.0.1-16x16-999999.svg" />][share_linkedin]
69
-
[<imgalign="right"title="Share on Twitter"src="https://docs.cloudposse.com/images/ionicons/social-twitter-outline-2.0.1-16x16-999999.svg" />][share_twitter]
70
-
71
-
72
-
[][terraform_modules]
Security scanning is graciously provided by Bridgecrew. Bridgecrew is the leading fully hosted, cloud-native solution providing continuous Terraform security and compliance.
|[](https://www.bridgecrew.cloud/link/badge?vcs=github&fullRepo=cloudposse%2Fterraform-aws-jenkins&benchmark=CIS+KUBERNETES+V1.5)| Center for Internet Security, KUBERNETES Compliance |
99
-
|[](https://www.bridgecrew.cloud/link/badge?vcs=github&fullRepo=cloudposse%2Fterraform-aws-jenkins&benchmark=CIS+AWS+V1.2)| Center for Internet Security, AWS Compliance |
100
-
|[](https://www.bridgecrew.cloud/link/badge?vcs=github&fullRepo=cloudposse%2Fterraform-aws-jenkins&benchmark=CIS+AZURE+V1.1)| Center for Internet Security, AZURE Compliance |
101
-
|[](https://www.bridgecrew.cloud/link/badge?vcs=github&fullRepo=cloudposse%2Fterraform-aws-jenkins&benchmark=PCI-DSS+V3.2)| Payment Card Industry Data Security Standards Compliance |
102
-
|[](https://www.bridgecrew.cloud/link/badge?vcs=github&fullRepo=cloudposse%2Fterraform-aws-jenkins&benchmark=NIST-800-53)| National Institute of Standards and Technology Compliance |
103
-
|[](https://www.bridgecrew.cloud/link/badge?vcs=github&fullRepo=cloudposse%2Fterraform-aws-jenkins&benchmark=ISO27001)| Information Security Management System, ISO/IEC 27001 Compliance |
104
-
|[](https://www.bridgecrew.cloud/link/badge?vcs=github&fullRepo=cloudposse%2Fterraform-aws-jenkins&benchmark=SOC2)| Service Organization Control 2 Compliance |
105
-
|[](https://www.bridgecrew.cloud/link/badge?vcs=github&fullRepo=cloudposse%2Fterraform-aws-jenkins&benchmark=CIS+GCP+V1.1)| Center for Internet Security, GCP Compliance |
106
-
|[](https://www.bridgecrew.cloud/link/badge?vcs=github&fullRepo=cloudposse%2Fterraform-aws-jenkins&benchmark=HIPAA)| Health Insurance Portability and Accountability Compliance |
107
-
108
-
109
82
110
83
## Usage
111
84
112
85
113
-
**IMPORTANT:** We do not pin modules to versions in our examples because of the
114
-
difficulty of keeping the versions in the documentation in sync with the latest released versions.
115
-
We highly recommend that in your code you pin the version to the exact version you are
116
-
using so that your infrastructure remains stable, and update versions in a
117
-
systematic way so that they do not catch you by surprise.
118
86
119
-
Also, because of a bug in the Terraform registry ([hashicorp/terraform#21417](https://github.com/hashicorp/terraform/issues/21417)),
120
-
the registry shows many of our inputs as required when in fact they are optional.
121
-
The table below correctly indicates which inputs are required.
87
+
> **Important**
88
+
> We do not pin modules to versions in our examples because of the
89
+
> difficulty of keeping the versions in the documentation in sync with the latest released versions.
90
+
> We highly recommend that in your code you pin the version to the exact version you are
91
+
> using so that your infrastructure remains stable, and update versions in a
92
+
> systematic way so that they do not catch you by surprise.
93
+
122
94
123
95
124
96
For a complete example, see [examples/complete](examples/complete).
@@ -370,15 +342,6 @@ Available targets:
370
342
<!-- markdownlint-restore -->
371
343
372
344
373
-
374
-
## Share the Love
375
-
376
-
Like this project? Please give it a ★ on [our GitHub](https://github.com/cloudposse/terraform-aws-jenkins)! (it helps us **a lot**)
377
-
378
-
Are you using this project or any of our other projects? Consider [leaving a testimonial][testimonial]. =)
379
-
380
-
381
-
382
345
## Related Projects
383
346
384
347
Check out these related projects.
@@ -391,81 +354,70 @@ Check out these related projects.
391
354
-[terraform-aws-cicd](https://github.com/cloudposse/terraform-aws-cicd) - Terraform Module for CI/CD with AWS Code Pipeline and Code Build
392
355
-[terraform-aws-codebuild](https://github.com/cloudposse/terraform-aws-codebuild) - Terraform Module to easily leverage AWS CodeBuild for Continuous Integration
393
356
394
-
## Help
357
+
## ✨ Contributing
395
358
396
-
**Got a question?** We got answers.
359
+
This project is under active development, and we encourage contributions from our community.
360
+
Many thanks to our outstanding contributors:
397
361
398
-
File a GitHub [issue](https://github.com/cloudposse/terraform-aws-jenkins/issues), send us an [email][email] or join our [Slack Community][slack].
Please use the [issue tracker](https://github.com/cloudposse/terraform-aws-jenkins/issues) to report any bugs or file feature requests.
403
369
370
+
### 💻 Developing
404
371
405
-
We are a [**DevOps Accelerator**][commercial_support]. We'll help you build your cloud infrastructure from the ground up so you can own it. Then we'll show you how to operate it and stick around for as long as you need us.
If you are interested in being a contributor and want to get involved in developing this project or [help out](https://cpco.io/help-out) with our other projects, we would love to hear from you! Shoot us an [email][email].
408
373
409
-
Work directly with our team of DevOps experts via email, slack, and video conferencing.
374
+
In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.
410
375
411
-
We deliver 10x the value for a fraction of the cost of a full-time engineer. Our track record is not even funny. If you want things done right and you need it done FAST, then we're your best bet.
376
+
1.**Fork** the repo on GitHub
377
+
2.**Clone** the project to your own machine
378
+
3.**Commit** changes to your own branch
379
+
4.**Push** your work back up to your fork
380
+
5. Submit a **Pull Request** so that we can review your changes
412
381
413
-
-**Reference Architecture.** You'll get everything you need from the ground up built using 100% infrastructure as code.
414
-
-**Release Engineering.** You'll have end-to-end CI/CD with unlimited staging environments.
415
-
-**Site Reliability Engineering.** You'll have total visibility into your apps and microservices.
416
-
-**Security Baseline.** You'll have built-in governance with accountability and audit logs for all changes.
417
-
-**GitOps.** You'll be able to operate your infrastructure via Pull Requests.
418
-
-**Training.** You'll receive hands-on training so your team can operate what we build.
419
-
-**Questions.** You'll have a direct line of communication between our teams via a Shared Slack channel.
420
-
-**Troubleshooting.** You'll get help to triage when things aren't working.
421
-
-**Code Reviews.** You'll receive constructive feedback on Pull Requests.
422
-
-**Bug Fixes.** We'll rapidly work with you to fix any bugs in our projects.
382
+
**NOTE:** Be sure to merge the latest changes from "upstream" before making a pull request!
423
383
424
-
## Slack Community
384
+
### 🌎 Slack Community
425
385
426
386
Join our [Open Source Community][slack] on Slack. It's **FREE** for everyone! Our "SweetOps" community is where you get to talk with others who share a similar vision for how to rollout and manage infrastructure. This is the best place to talk shop, ask questions, solicit feedback, and work together as a community to build totally *sweet* infrastructure.
427
387
428
-
## Discourse Forums
429
-
430
-
Participate in our [Discourse Forums][discourse]. Here you'll find answers to commonly asked questions. Most questions will be related to the enormous number of projects we support on our GitHub. Come here to collaborate on answers, find solutions, and get ideas about the products and services we value. It only takes a minute to get started! Just sign in with SSO using your GitHub account.
431
-
432
-
## Newsletter
388
+
### 📰 Newsletter
433
389
434
390
Sign up for [our newsletter][newsletter] that covers everything on our technology radar. Receive updates on what we're up to on GitHub as well as awesome new projects we discover.
Please use the [issue tracker](https://github.com/cloudposse/terraform-aws-jenkins/issues) to report any bugs or file feature requests.
447
-
448
-
### Developing
449
-
450
-
If you are interested in being a contributor and want to get involved in developing this project or [help out](https://cpco.io/help-out) with our other projects, we would love to hear from you! Shoot us an [email][email].
451
-
452
-
In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.
453
-
454
-
1.**Fork** the repo on GitHub
455
-
2.**Clone** the project to your own machine
456
-
3.**Commit** changes to your own branch
457
-
4.**Push** your work back up to your fork
458
-
5. Submit a **Pull Request** so that we can review your changes
459
-
460
-
**NOTE:** Be sure to merge the latest changes from "upstream" before making a pull request!
398
+
This project is maintained and funded by [Cloud Posse, LLC][website].
We are a [**DevOps Accelerator**][commercial_support]. We'll help you build your cloud infrastructure from the ground up so you can own it. Then we'll show you how to operate it and stick around for as long as you need us.
Work directly with our team of DevOps experts via email, slack, and video conferencing.
466
406
407
+
We deliver 10x the value for a fraction of the cost of a full-time engineer. Our track record is not even funny. If you want things done right and you need it done FAST, then we're your best bet.
467
408
409
+
-**Reference Architecture.** You'll get everything you need from the ground up built using 100% infrastructure as code.
410
+
-**Release Engineering.** You'll have end-to-end CI/CD with unlimited staging environments.
411
+
-**Site Reliability Engineering.** You'll have total visibility into your apps and microservices.
412
+
-**Security Baseline.** You'll have built-in governance with accountability and audit logs for all changes.
413
+
-**GitOps.** You'll be able to operate your infrastructure via Pull Requests.
414
+
-**Training.** You'll receive hands-on training so your team can operate what we build.
415
+
-**Questions.** You'll have a direct line of communication between our teams via a Shared Slack channel.
416
+
-**Troubleshooting.** You'll get help to triage when things aren't working.
417
+
-**Code Reviews.** You'll receive constructive feedback on Pull Requests.
418
+
-**Bug Fixes.** We'll rapidly work with you to fix any bugs in our projects.
@@ -491,58 +443,11 @@ specific language governing permissions and limitations
491
443
under the License.
492
444
```
493
445
494
-
495
-
496
-
497
-
498
-
499
-
500
-
501
-
502
446
## Trademarks
503
447
504
448
All other trademarks referenced herein are the property of their respective owners.
505
-
506
-
## About
507
-
508
-
This project is maintained and funded by [Cloud Posse, LLC][website]. Like it? Please let us know by [leaving a testimonial][testimonial]!
509
-
510
-
[![Cloud Posse][logo]][website]
511
-
512
-
We're a [DevOps Professional Services][hire] company based in Los Angeles, CA. We ❤️ [Open Source Software][we_love_open_source].
513
-
514
-
We offer [paid support][commercial_support] on all of our projects.
515
-
516
-
Check out [our other projects][github], [follow us on twitter][twitter], [apply for a job][jobs], or [hire us][hire] to help with your cloud strategy and implementation.
0 commit comments