Re: Disabling shallow clone using the GitHub organisation

Small precision: better using "git checkout -B ${BRANCH_NAME}" in case the workspace is not discarded On Saturday, 18 February 2017 19:26:58 UTC+1, Damien Coraboeuf wrote: > > Using "git checkout -b ${BRANCH_NAME}" as a first shell step before the > actual build is a very elegant trick. > >

is there any load test options in jenkins?

JMeter would be a natural choice. The jenkins 'Performance Plugin' will parse and perform error threshold calculations and fail the build accordingly. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop

Re: is there any load test options in jenkins?

BlazeMeter also provides a performance test plugin for Jenkins. Mark Waite (I work for CA Technologies, and BlazeMeter is part of CA Technologies) On Sat, Feb 18, 2017 at 9:00 PM Mark Miller wrote: > JMeter would be a natural choice. The jenkins 'Performance Plugin'

How to use variable thresholds instead of constants in build status thresholds in job configuration?

Instead of hard coding the build status thresholds into Jenkins configuration, I want to use variable thresholds that either are read from a file or supplied as input parameters to job. Does anyone know if there is a way to do this? I tried using injected variables as thresholds in warnings

Build project inside docker

Hi, I'm trying to build a project inside docker container so that all dependencies required for project are available and doesn't require installation in jenkins system. Below is my Jenkinsfile. node{stage ('Build'){ checkout scm

Jenkins with Octopus - Why and what for we even use both

No doubt there are numerous tutorials and plugins that support this "marriage", but when we ask the question "why?", what is the answer? Jenkins is has a very wide range of applications after all, it can do deployments by itself. I would say that usually the reason for users is: "Jenkins will

Re: Disabling shallow clone using the GitHub organisation

Using "git checkout -b ${BRANCH_NAME}" as a first shell step before the actual build is a very elegant trick. Thanks Mark! Best regards, Damien. On Saturday, 18 February 2017 19:14:12 UTC+1, Mark Waite wrote: > > The git plugin defaults to performing a checkout with a detached head at > the

Re: Build project inside docker

The `cd` in the first shell step will change the directory only in the first shell step. You should group shell steps together: sh '''\ cd usr/local/src/freeswitch-1.4.26 ./rebootstrap ./configure make ''' Additionally, should not you use cd /usr/local/src/freeswitch-1.4.26 and not cd

Re: Jenkins LTS and Docker 1.13

I've used Jenkins LTS 2.32.2 with Docker 1.13.1 without any issue. What is exactly your issue? On Friday, 17 February 2017 08:55:01 UTC+1, Baptiste Mathus wrote: > > > > Le 9 févr. 2017 4:38 PM, "Omeka" a > écrit : > > Previously the current LTS of jenkins would not work

Re: Disabling shallow clone using the GitHub organisation

What are you observing that makes you think that shallow clone is always enabled? The git plugin and all my work with GitHub Organization Folders indicates that shallow clone is disabled by default for all git plugin usage, including GitHub Organization Folders. I run a GitHub Organization

Re: Disabling shallow clone using the GitHub organisation

The git plugin defaults to performing a checkout with a detached head at the SHA1 hash to be built. There is a plugin option "LocalBranch" which can assign the name of the local branch to be created at that SHA1. If that's not available from the declarative pipeline, you may be able to perform a

Execute shell script on remote host using ssh - Jenkinsfile

Hello all. First time poster, long time stalker. I am trying to find an example of executing a shell script on a remote host using ssh. There is the plugin for this but I want to convert that action in to a Jenkinsfile. Any help is appreciated. -- You received this message because you are

Re: Jenkins configuration from script

At my client (big scale), the Jenkins master is provisioned using Groovy script files in the /var/lib/jenkins/init.groovy.d directory. Any script in this directory is run at Jenkins startup. It is then just a matter of calling the Jenkins Java API to provision everything you need (credentials,

Re: Disabling shallow clone using the GitHub organisation

Hi Mark, I'm also using the Pipeline Model Definition plug-in, and I think this is the culprit in this story. Using the model definition, I do not see any way to specify the "checkout scm" (as I would do in a "regular" pipeline definition). I'm using a versioning Gradle plugin and its output