I have a Jenkins instance available over the internet. I have some jobs which need to be triggered manually (server start/server down). I found this cloudbees plugin which is supposed to work with on-prem Jenkins instance. However, when configuring the plugin it does not work.
Using the URL https://<jenkins_ur>/api/json on browser works, but cloudbess plugin complains about breadcrumb not found when trying to configure from Eclipse.
Related
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.
I have Jenkins Mutibranch pipeline. I want to integrate my Jira with one of multibranch project. I have installed the JIRA Trigger Plugin and configured Webhook in Jira. however, when I checked in my Jenkins job it does not show me the B***uild when an issue is updated in JIRA*** but it shows when I go to View Configuration in the particular branch. it allows me to select the Build when an issue is updated in JIRA but there is no option to save the changes. I know this might be a reason the option is view only. but how can I configure this?
Is anyone configured JIRA Trigger Plugin with Jenkins mutibranch project where using Jenkinsfile? and what is the correct way of integrating this?
Should I do some coding in the Jenkins file to get this done?
I have an project to upgrade my jenkins. So the problem is I use jenkins plugins called "Publish over ssh". As I read that plugin can publish our artifactory file to another server by ssh connection. But in the configuration it always run after our job finised. So every jobs that I run, always publish to server.
So, I want to ask, how can I pick which build history artifacts that I want to publish? and it can publish when I want to publish. And then I have an Idea to adding button in jenkins web interface, to trigger adding job configuration, build it, and publish it over SSH. But, I don't know how to modify jenkins web interface. My server use tomcat, that run java ".war" file.
So, do you all have suggestion for my problem, how to modify jenkins web interface, or how to pick certain build artifacts?
Thanks...
I want to trigger my Jenkins Job when a particular folder is modified in WAS server.Is there any plugin available ? I tried with 'FSTrigger' plugin but it is working only for local machine folder changes but not for server side changes. I am getting following message in FSTrigger floder log.
Trying to monitor the folder 'https:\server_name\folder_path'
The directory 'https:\server_name\folder_path' doesn't exist.
Kindly help me on this.!!
Regarding this answer:
How to set FSTrigger's folder path in Hudson CI integration tool?
I think you can only monitor a local URL, like:
/var/www/html/test/test1/config
To solve your problem, one solution is to connect your WAS server to your Jenkins master as a Jenkins slave.
And next, create a Jenkins job using the FSTrigger plugin and launch it on your WAS slave.
I have Jenkins as the CI server. I have an automated testing tool setup on another machine. I installed Jenkins on the other machine also. Now I want one instance of Jenkins to trigger the project build on the other instance of Jenkins. Is that possible?
You can do this by pinging a build URL. i.e.
http://server-url:{port}/job/{job_name}/build
Easiest is to use the Parameterized Remote Trigger Plugin. Calling the URL directly can be tricky if your build has parameters and / or your Jenkins instance is secured.