How to do Code Promotion in Artifactory - jenkins

I am relatively new to Artifactory. We are using gardle artifactory plugin to publish the artifacts & also we are using Jenkins CI to automate builds.
In Artifactory Snapshot we have urls like (dev, stg, perf, prodfix) version & filename(abc-dev.jar).
1.) After dev build, I have to promote abc-dev.jar to stg URL(abc-stg.jar).similarly for rest of environment.
Kindly advise how we can achieve this.

In Jenkins, there's a Pipeline DSL that you can use to promote your builds. See the documentation here:
https://wiki.jenkins-ci.org/display/JENKINS/Artifactory+-+Working+With+the+Pipeline+Jenkins+Plugin

Related

Jenkins Build CI/CD deployment from SVN repository

Basically I am trying to implement an automated Jenkins pipeline. which will automatically build and test my codes from SVN repository. The pipeline has to be set such that, it riggers a test and build each time a code is committed to the SVN repository. All the servers are on premises. I am trying to implement a Jenkins Build and CI/CD pipeline concept with SVN as my Source code repository. This is my requirement.
I am new to SVN and on premises servers. My expertise are in with Git and Github, Terraform and AWS Cloud platform. So I must say I am lost with this one.
I have ben doing some research and mostly found things on Github and Cloud platforms with Jenkins. Which is exactly opposite what I want.
How do I go about this? Is there any good, clear concise documentation I could use? or video? or tutorials?

trigger a Jenkins from bamboo

My requirement:
My build pipeline is in Bamboo and Test integration pipeline is implemented in Jenkins. So once CI pipeline is completed in Bamboo, there should be a trigger from Bamboo to Jenkins job.
I'm aware this can be done via API call to Jenkins, however I also saw that there is some kind of plugin in Bamboo which can integrate with Jenkins.
I could not find the name of that plugin anywhere, can someone of you help me is providing the plugin name ?
Please do let me know for more question.
You might be referring to the following plugin: https://marketplace.atlassian.com/apps/1211284/webhook-to-jenkins-for-bitbucket. However, this plugin is for Bitbucket and not Bamboo. As far as I'm aware, there is no Jenkins specific plugin for Bamboo.
There is however a generic webhooks plugin for Bamboo: https://marketplace.atlassian.com/apps/1220844/webhooks-for-bamboo, which can be configured to trigger Jenkins at the end of a build.

Jenkins Build Trigger "Enable Artifactory trigger" is not working with JFrog

We are using JFrog as artifactory and Jenkins is our CI/CD tool. I have created a Jenkins which should run upon an artifact gets published to jfrog artifactory. But seems to be the plugin is not working as expected. When i googled, found the below URL and as per URL its applicable only for JFrog Pro-version. https://www.jfrog.com/jira/browse/HAP-1138
My question is, this option applicable only for JFrog pro-version or am i missing something here.
Thanks,
Srikanth.
The Artifactory Trigger feature in Jenkins, allowing to trigger Jenkins jobs following changes in pre-configired paths in Artifactory, requires at least an Artifactory Pro license.

How to promote non maven artifacts in Nexus?

I have a non maven project whose binaries get deployed to Nexus.
I used gradle's maven plugin to create the artifacts and publish it to Nexus
Now, the trouble is how do I promote this artifacts to release in Nexus? I tried looking up the M2 release plugin for jenkins but it looks for the pom file in my source code.
There are a number of Gradle examples including usage with the Nexus staging suite in the Nexus book examples and eval guide.

Puppet Plugin for Jenkins

How to integrate Jenkins with Puppet?
As of now i am integrating Jenkins with Puppet. But We dont know which puppet plugin will support for jenkins. Can you please help on us.
It depends on what you want to achieve. If you simply want to deploy the manifests, there is no need for a puppet plugin. You could use the Publish over SSH plugin or something that let you push your code to the puppet master.
To actually execute puppet commands a generic job configuration would be fine.
If you are looking for a full chain of source control, tests and deployment for your manifests, you should take a look at Gerrit and how to integrate it with Jenkins using the Gerrit Trigger plugin

Resources