terraform-provider-jenkins
helm-charts
terraform-provider-jenkins | helm-charts | |
---|---|---|
1 | 7 | |
76 | 544 | |
- | 2.0% | |
7.4 | 9.0 | |
13 days ago | 2 days ago | |
Go | Mustache | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
terraform-provider-jenkins
-
Battle-tested way to configure a Jenkins server on AWS using IaC/CaC?
Personally I manage and create my jobs manually in jenkins, but terraform does have a Jenkins provider https://github.com/taiidani/terraform-provider-jenkins to allow you to create your jobs via IAC (Infrastructure as Code) if you want to be 100% IAC. This has been a very successful solution for out team. I must give a disclaimer though, while we have jobs to build & deploy all of our apps from src, we generally rely on CircleCi for it. We keep the jenkins build jobs up to date and only use them when CircleCi is down (Which has been much less the last year). In addition to that we (the devops team) use jenkins to run all of our repetitive tasks like a fancy cron service. Things such as reset dev databases, backup or github repo to a second location, run password rotations, recycle services etc.
helm-charts
-
Why is argocd complaining about my ApplicationSet saying: error parsing value as string <nil>
I have no clue of what is wrong. The applicationset yaml looks like (somewhat cut-down): apiVersion: argoproj.io/v1alpha1 kind: ApplicationSet metadata: name: myjenkins namespace: argocd spec: generators: - list: elements: - namespace: "development" ingressHostName: "myjenkins-dev.scs.domain" limitsMemory: "12Gi" template: metadata: name: myjenkins spec: destination: namespace: '{{namespace}}' server: https://kubernetes.default.svc project: default syncPolicy: {} sources: - chart: jenkins repoURL: https://github.com/jenkinsci/helm-charts/tree/main/charts targetRevision: 4.3.9 helm: releaseName: myjenkins parameters: - name: extraLabels value: slice1 - name: controller.resources.limits.cpu value: '8' - name: controller.resources.limits.memory value: '{{limitsMemory}}' valueFiles: - $values/deployments/jenkins/global/common.values - $values/deployments/jenkins/global/shared-libs.values - $values/deployments/jenkins/global/job-dsl-seed.values - $values/deployments/jenkins/global/ssh-credentials.values - $values/deployments/jenkins/global/kubernetes-cloud.values - repoURL: 'ssh://[email protected]:29418/kubernetes' targetRevision: master ref: values
-
Jenkins CASC and Jenkins Community helm chart issues
Here is what I'm deploying.. I have a very small GKE cluster up and running right now with terraform. I'm on a budget, so I'm trying to containerize as many of the services we need for development as possible. I am using this Jenkins helm chart for deployment: https://github.com/jenkinsci/helm-charts/blob/main/charts/jenkins/README.md
- Deploying Jenkins on Google Cloud
-
Jenkins on Kubernetes - Can't Use PodTemplates Defined In Clouds
I've updated my post with the error logs and some descriptions. The "Additional Agents" thing is part of the Helm chart. The Adding Pod Templates Using additionalAgents section of the Helm Chart's README gives an example of how to declare them. I initially tried using a direct copy of the example in the README (adapted to use with the Ansible module) but that displayed roughly the same behaviour
-
Should we be using Jenkins for our Kubernetes CI/CD pipeline needs in 2021?
https://github.com/jenkinsci/helm-charts/tree/main/charts/jenkins Using offical chart
- Battle-tested way to configure a Jenkins server on AWS using IaC/CaC?
What are some alternatives?
reform - helpful terraform wrapper for templates, secrets and easy organization
actions-runner-controller - Kubernetes controller for GitHub Actions self-hosted runners
terraform-aws-jenkins - Terraform module to build Docker image with Jenkins, save it to an ECR repo, and deploy to Elastic Beanstalk running Docker stack
kubernetes-operator - Kubernetes native Jenkins Operator
terraform-provider-factorio - The Terraform Provider for Factorio
charts - ⚠️(OBSOLETE) Curated applications for Kubernetes
opta - The next generation of Infrastructure-as-Code. Work with high-level constructs instead of getting lost in low-level cloud configuration.
terraform-provider-solana - Data source provider for Terraform that interacts with the Solana networks
kubernetes-plugin - Jenkins plugin to run dynamic agents in a Kubernetes/Docker environment
terraform-provider-stripe - A Terraform Provider for Stripe
synapse