artifact-manager-s3-plugin
job-dsl-gradle-example
artifact-manager-s3-plugin | job-dsl-gradle-example | |
---|---|---|
2 | 2 | |
61 | 439 | |
- | - | |
6.7 | 0.0 | |
2 days ago | about 2 years ago | |
Java | Groovy | |
- | 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.
artifact-manager-s3-plugin
-
Is there a way to use the Jenkins core 'archiveArtifact' with Artifactory?
I see. The only option I'm aware of is https://github.com/jenkinsci/artifact-manager-s3-plugin (S3 API compatible).
-
CMV: Jenkins shouldn't be anywhere near a robust, mature application environment
So, yep done all this and completely agree. I set this all up with Terraform, Docker, and JCasC. However with our 80 person org and around 30 active repos (all with multibranch pipelines) ,200-300 builds a day; I'm seeing reboot times in the 15-20 minutes range (which hurts.) Also, if you don't drain the Jenkins instance prior to replacement then the currently running jobs fail; causing more issues (need to automate this anyone got a script?). Other complaints, plugins break ALL THE TIME so we really have to do some QA before sending a new Jenkins container out to prod. The S3 Artifact plugin doesn't do multipart uploads which limits the maximum size and performance on stash/archiveArtifact (patch here https://github.com/jenkinsci/artifact-manager-s3-plugin/pull/141; could still use a patch to stream the zip/tarball creation). The downstream build feature is really powerful but the blue ocean ui is iffy on it (sometimes it shows downstream builds; sometimes not). The ec2 plugin works but I've never gotten the spot-fleet plugin to work properly (specifically interested in being able to choose alternately sized instances based on spot price and availability). If you use spot-instances with the ec2 plugin; there's no clear way to retry the build (would love a tutorial or script that accomplishes the steps needed on this. i.e. trapping the signal coming from the OS and turning it into an exception in the pipeline). Overall, it's nice once you get here; but it's a metric ton of work... and there's still a bunch of problems. Really wish there was something easier to maintain and grow with a cloud first approach (i.e. rolling upgrades, object store support, fleet support).
job-dsl-gradle-example
-
Jenkins as code, part 2: Setting up the Jenkins job
Yeah I've tried with the later approach days ago and make it work today, thanks to this helpful repo: https://github.com/sheehan/job-dsl-gradle-example :D
-
CMV: Jenkins shouldn't be anywhere near a robust, mature application environment
Have a look at https://github.com/sheehan/job-dsl-gradle-example it's a nice example that even allows you to test your job configuration.
What are some alternatives?
pipeline - A cloud-native Pipeline resource.
ods-jenkins-shared-library - Shared Jenkins library which all ODS projects & components use - provisioning, SonarQube code scanning, Nexus publishing, OpenShift template based deployments and repository orchestration
configuration-as-code-plugin - Jenkins Configuration as Code Plugin
aws-cf-templates - Free Templates for AWS CloudFormation
job-dsl-plugin - A Groovy DSL for Jenkins Jobs - Sweeeeet!
jenkins-script-console-scripts - A repository of one-off script console scripts for Jenkins.
jervis - Self service Jenkins job generation using Jenkins Job DSL plugin groovy scripts. Reads .jervis.yml and generates a job in Jenkins.
S3-Upload-JMeter-Groovy - Upload files to AWS S3 in JMeter using Groovy
Apollo - Genome annotation editor with a Java Server backend and a Javascript client that runs in a web browser as a JBrowse plugin.