We are currently contributing to this Jenkins plugin which allows querying InfluxDB to fail a build based on queries:
https://github.com/jenkinsci/influxdb-query-plugin
A version has been released and we updated Jenkins wiki:
https://wiki.jenkins.io/display/JENKINS/InfluxDB+Query+Plugin
But this documentation is not editable and we guess generated from code analysis or plugin help page:
https://jenkins.io/doc/pipeline/steps/influxdb-query/
So could someone explain what needs to be done to have this documentation updated or point me to the documentation explaining it ?
The documentation for the pipeline steps is updated via an automated job based on the released plugin.
Per answer provided by Daniel Beck:
https://github.com/jenkins-infra/pipeline-steps-doc-generator/blob/c810a08f50f34d688eb69ec2ebab96947440f71d/Jenkinsfile#L5
The job runs over the weekend.
reference : https://groups.google.com/forum/m/#!msg/jenkinsci-dev/Xo2kWiY2hoI/y-EU8x4QBQAJ
Related
Technical stuff that comes after migrating jenkins. Which are to be consider and how we will go through them?
I am browsing related to this issue but can't find any.
How does one go about finding the documentation on Jenkinsfile configuration options provided by Jenkins and the plugins that are installed?
For example, to set the "Do not allow concurrent builds" option, I have to set properties([disableConcurrentBuilds()]). I don't see documentation on that option anywhere except under the documentation on declarative syntax.
For plugins, I have the Github plugin installed but I don't know how to find what the option is to check "GitHub hook trigger for GITScm polling". I don't see documentation on the plugin page or github page.
Do I need to dig into the source to find these options? If so, what am I looking for in the source?
I found it under the Pipeline Syntax generator. There's a sample step for properties that allows you to check all the boxes and will generate the relevant code for you.
We have JIRA, BitBucket and Bamboo, all integrated running locally on a server.
I would like to have Bamboo build my software when I decide to release it in JIRA.
There is a document available at Atlassian that describes this:
https://confluence.atlassian.com/jirasoftwarecloud/running-a-bamboo-build-when-releasing-a-version-764478184.html
The problem is that my interface doesn't have the Build Variables as described in the documentation. This is crucial, because I want JIRA to pass the version number and Bamboo to use that as a variable for different tasks.
Here is a screenshot of the interface:
I realise that the docs are for JIRA cloud, but seeing that the same interface is available on the server edition, I would expect to be able to accomplish the same thing.
We use JIRA version 7.9.2 and Bamboo version 6.5.1
Does anyone know why the Build Variables might be missing, or how else to tackle passing variables from JIRA to Bamboo in a self-hosted situation?
I worked around this by using the "Dump variables to log" job to check what variables are available. As it turns out the JIRA version is available when a build is triggered through the JIRA "release" button.
The variable I could use is bamboo.jira.version.
This doesn't solve the actual problem of defining arbitrary variables in JIRA and passing them on to Bamboo, but it solves the problem in my use-case, as I was looking to pass the release version.
Update:
I have an offical answer form Atlassian regarding this question.
I was under the impression that the custom variables you want to pass are defined on the release screen in JIRA itself.
As it turns out, variables are defined on the plan or global level in Bamboo, and they can then be used/overridden on the release screen in JIRA.
It works now!
I'm investigating the Jenkins Workflow plugin, so far I think its brilliant.
Is their a way to visualize the pipeline that is defined by the workflow script, I've come across something that CloudBees say they have but I'm presuming that isn't freely available, does anyone know of any others?
Jenkins Workflow visualization is now open sourced by Cloudbees as promised - https://github.com/jenkinsci/pipeline-stage-view-plugin
I just stumbled over this statement in a blog post from the Jenkins/Hudson founder, at https://groups.google.com/forum/#!topic/jenkinsci-dev/vbXK7JJekFw:
To reinforce the message that workflow is the future, CloudBees is going to open-source our workflow stage view plugin that was previously a part of CloudBees Jenkins Enterprise.
So it sounds like it's not freely available, but may be in the near future.
I am currently trying to create a build pipeline. The buildflow plugin looks interesting, but I cannot find any information on whether manual steps are possible.
Does anyone know if this is possible?
Does not seem this is possible yet, but you can look at the build pipeline plugin which supports manual steps. This is an alternative plugin for implementing build pipelines that also includes nice visualizations.