On Wed 2 Aug 2017 at 00:02, John Hovell wrote:
> From the docs:
>
>
> https://wiki.jenkins.io/display/JENKINS/Metrics+Plugin
>
>
> "The Healthcheck servlet runs the healthchecks defined against the Metrics
> API and returns the detailed status in JSON (or JSONP) format, while the
> high level sta
On Wed 2 Aug 2017 at 01:37, Ramanathan Muthaiah
wrote:
>
> https://go.cloudbees.com/docs/cloudbees-documentation/cje-user-guide/index.html#_controlling_what_is_built
>
> Documentation mentions that "By default, Jenkins will build any branches
> it finds in the “origin” repository (the actual repo
https://go.cloudbees.com/docs/cloudbees-documentation/cje-user-guide/index.html#_controlling_what_is_built
Documentation mentions that "By default, Jenkins will build any branches it
finds in the “origin” repository (the actual repository found in your
organization). Also, any pull requests that
On Tuesday, February 14, 2017 at 12:54:13 AM UTC+5:30, anton kropp wrote:
>
> Whenever someone submits a pull request from a forked repo to a job that
> is built with multi-branch github integration, jenkins never picks up the
> commits. PR's from branches work just fine though.
>
> Am I missing
I've read the "getting started with pipeline" pages
(https://jenkins.io/doc/book/pipeline/getting-started/).
I've spent literally hours looking for something really helpful, in one place,
for someone who wants to write CODE in the pipeline script.
I did just find https://jenkins.io/doc/book/pip
>From the docs:
https://wiki.jenkins.io/display/JENKINS/Metrics+Plugin
"The Healthcheck servlet runs the healthchecks defined against the Metrics
API and returns the detailed status in JSON (or JSONP) format, while the
high level status is reported by the HTTP status code.
These servlets a
I have an input step in a declarative pipeline and I want to add some logic
so that if the input step waits too long for someone to proceed, it will
send a reminder notification and loop, starting a new timeout.
What I have so far is this:
waitUntil {
timeout(time: 3, unit: 'MINUTES' )
Nice! is the plugin:
https://wiki.jenkins.io/display/JENKINS/NodeLabel+Parameter+Plugin
compatible with pipeline script (declarative or normal one)? if yes how do
we use it into those configuration?
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" gr
Periodic reminder:
https://javaadventure.blogspot.ie/2013/11/jenkins-maven-job-type-considered-evil.html
On 1 August 2017 at 00:41, tiendungitd wrote:
> I'm having problem with maven projects that are building on jenkins slave
> using docker container, it's taking too much time at "Parsing POM"
I'm having problem with maven projects that are building on jenkins slave
using docker container, it's taking too much time at "Parsing POM" step,
about 6mins+. If I build it manually or build it on jenkins master then it
take only 30s to finish. If using freestyle project to build, it take only
3m
Hi Team,
I was going through the link: http://hopsas.com/products/
informatica-powercenter-continuous-delivery-solution/
I am an Informatica developer and looking for some help to understand how
we can use Jenkins for CICD implementation in Informatica.
I need to know how we can establish a
Hi all!
I'm trying to set up a poc on semantic versioning with jenkins.
I see the semantic versioning plugin, however I don't find any materials
on the net, like a tutorial that shows me how to set up an example and
actually use it in practice.
Would anyone be able to give me a rough example of
Sam,
>As far as I know, this is not possible. I would very much like this
feature as well
It's doable with the Node Label Parameter plugin - you can choose "Label"
as a parameter when creating parameterized build.
On Mon, Jul 31, 2017 at 9:34 PM, Sam K wrote:
> As far as I know, this is not pos
13 matches
Mail list logo
