Re: is there any load test options in jenkins?

[Mark Waite]

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' 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 receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/592ce4d9-2b6f-4c0c-9b99-9e8156c155df%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtH0mtn1Uw60t4jVBTab8cwWVecafhWTQdWL01so6E%3DHKA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

is there any load test options in jenkins?

[Mark Miller]

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 receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/592ce4d9-2b6f-4c0c-9b99-9e8156c155df%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Disabling shallow clone using the GitHub organisation

[Damien Coraboeuf]

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.
>
> 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 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 "git checkout -b branch_name" in your build step.
>>
>> Mark Waite
>>
>> On Sat, Feb 18, 2017 at 11:10 AM Damien Coraboeuf  
>> wrote:
>>
>>> 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 shows that we are 
>>> using either a shallow clone or a detached head. I need the target branch 
>>> to be checked out as a local branch.
>>>
>>> Best regards,
>>> Damien.
>>>
>>>
>>> On Sat, Feb 18, 2017 at 7:06 PM, Mark Waite  
>>> wrote:
>>>
 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 Folder configuration for Jenkins git plugin 
 and Jenkins git client plugin development changes from my forks at 
 https://github.com/MarkEWaite/git-client-plugin.  If I clone that 
 repository with a shallow clone, there are unit tests which fail because 
 the tests rely on a full local history of the repository.

 Are you performing a "checkout scm" (or similar) in your Jenkinsfile so 
 that each job has its own working copy of the repository?  If so, are you 
 enabling shallow clone in that checkout?  If not, then you need to change 
 to use "checkout scm" in each Jenkinsfile.

 Mark Waite

 On Sat, Feb 18, 2017 at 10:57 AM Damien Coraboeuf <
 damien.c...@gmail.com> wrote:

> Hi,
>
> In order to compute versions correctly (using 
> https://github.com/nemerosa/versioning), I need my projects not to be 
> checked out using a shallow clone option.
>
> The Organization plug-in (
> https://wiki.jenkins-ci.org/display/JENKINS/GitHub+Organization+Folder+Plugin)
>  
> does not seem to allow to disable this option. Or is it something we can 
> change using the Pipeline Model Definition plug-in syntax?
>
> Thanks,
> Damien.
>
> -- 
> You received this message because you are subscribed to the Google 
> Groups "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send 
> an email to jenkinsci-use...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/69ac8ef3-010a-4a6f-8874-10a4b632dd6d%40googlegroups.com
>  
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
 -- 
 You received this message because you are subscribed to a topic in the 
 Google Groups "Jenkins Users" group.
 To unsubscribe from this topic, visit 
 https://groups.google.com/d/topic/jenkinsci-users/TIK6DERVZqQ/unsubscribe
 .
 To unsubscribe from this group and all its topics, send an email to 
 jenkinsci-use...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtF7Hd1XVatjf5q4caTV6KLmrWTrnK7J7OfjAk9fPcM8yA%40mail.gmail.com
  
 
 .
>>>
>>>
 For more options, visit https://groups.google.com/d/optout.

>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Jenkins Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to jenkinsci-use...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-users/CAMbUmAEfvgh-nG-Ss49k6Nf69D0f%2Bgbk%2B9UJPyYYe8GY5hMhkw%40mail.gmail.com
>>>  
>>> 

Re: Disabling shallow clone using the GitHub organisation

[Damien Coraboeuf]

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 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 "git checkout -b branch_name" in your build step.
>
> Mark Waite
>
> On Sat, Feb 18, 2017 at 11:10 AM Damien Coraboeuf  > wrote:
>
>> 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 shows that we are 
>> using either a shallow clone or a detached head. I need the target branch 
>> to be checked out as a local branch.
>>
>> Best regards,
>> Damien.
>>
>>
>> On Sat, Feb 18, 2017 at 7:06 PM, Mark Waite > > wrote:
>>
>>> 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 Folder configuration for Jenkins git plugin 
>>> and Jenkins git client plugin development changes from my forks at 
>>> https://github.com/MarkEWaite/git-client-plugin.  If I clone that 
>>> repository with a shallow clone, there are unit tests which fail because 
>>> the tests rely on a full local history of the repository.
>>>
>>> Are you performing a "checkout scm" (or similar) in your Jenkinsfile so 
>>> that each job has its own working copy of the repository?  If so, are you 
>>> enabling shallow clone in that checkout?  If not, then you need to change 
>>> to use "checkout scm" in each Jenkinsfile.
>>>
>>> Mark Waite
>>>
>>> On Sat, Feb 18, 2017 at 10:57 AM Damien Coraboeuf >> > wrote:
>>>
 Hi,

 In order to compute versions correctly (using 
 https://github.com/nemerosa/versioning), I need my projects not to be 
 checked out using a shallow clone option.

 The Organization plug-in (
 https://wiki.jenkins-ci.org/display/JENKINS/GitHub+Organization+Folder+Plugin)
  
 does not seem to allow to disable this option. Or is it something we can 
 change using the Pipeline Model Definition plug-in syntax?

 Thanks,
 Damien.

 -- 
 You received this message because you are subscribed to the Google 
 Groups "Jenkins Users" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to jenkinsci-use...@googlegroups.com .
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-users/69ac8ef3-010a-4a6f-8874-10a4b632dd6d%40googlegroups.com
  
 
 .
 For more options, visit https://groups.google.com/d/optout.

>>> -- 
>>> You received this message because you are subscribed to a topic in the 
>>> Google Groups "Jenkins Users" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/jenkinsci-users/TIK6DERVZqQ/unsubscribe
>>> .
>>> To unsubscribe from this group and all its topics, send an email to 
>>> jenkinsci-use...@googlegroups.com .
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtF7Hd1XVatjf5q4caTV6KLmrWTrnK7J7OfjAk9fPcM8yA%40mail.gmail.com
>>>  
>>> 
>>> .
>>
>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/CAMbUmAEfvgh-nG-Ss49k6Nf69D0f%2Bgbk%2B9UJPyYYe8GY5hMhkw%40mail.gmail.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this 

Re: Disabling shallow clone using the GitHub organisation

[Mark Waite]

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 "git checkout -b branch_name" in your build step.

Mark Waite

On Sat, Feb 18, 2017 at 11:10 AM Damien Coraboeuf <
damien.corabo...@gmail.com> wrote:

> 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 shows that we are
> using either a shallow clone or a detached head. I need the target branch
> to be checked out as a local branch.
>
> Best regards,
> Damien.
>
>
> On Sat, Feb 18, 2017 at 7:06 PM, Mark Waite 
> wrote:
>
> 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 Folder configuration for Jenkins git plugin
> and Jenkins git client plugin development changes from my forks at
> https://github.com/MarkEWaite/git-client-plugin.  If I clone that
> repository with a shallow clone, there are unit tests which fail because
> the tests rely on a full local history of the repository.
>
> Are you performing a "checkout scm" (or similar) in your Jenkinsfile so
> that each job has its own working copy of the repository?  If so, are you
> enabling shallow clone in that checkout?  If not, then you need to change
> to use "checkout scm" in each Jenkinsfile.
>
> Mark Waite
>
> On Sat, Feb 18, 2017 at 10:57 AM Damien Coraboeuf <
> damien.corabo...@gmail.com> wrote:
>
> Hi,
>
> In order to compute versions correctly (using
> https://github.com/nemerosa/versioning), I need my projects not to be
> checked out using a shallow clone option.
>
> The Organization plug-in (
> https://wiki.jenkins-ci.org/display/JENKINS/GitHub+Organization+Folder+Plugin)
> does not seem to allow to disable this option. Or is it something we can
> change using the Pipeline Model Definition plug-in syntax?
>
> Thanks,
> Damien.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/69ac8ef3-010a-4a6f-8874-10a4b632dd6d%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-users/TIK6DERVZqQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtF7Hd1XVatjf5q4caTV6KLmrWTrnK7J7OfjAk9fPcM8yA%40mail.gmail.com
> 
> .
>
>
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CAMbUmAEfvgh-nG-Ss49k6Nf69D0f%2Bgbk%2B9UJPyYYe8GY5hMhkw%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtGXv0j7KUWPuXfkFZVPnhfHX%3Dq3Lcz5ckpNrxntKcWuYQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Disabling shallow clone using the GitHub organisation

[Damien Coraboeuf]

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 shows that we are using
either a shallow clone or a detached head. I need the target branch to be
checked out as a local branch.

Best regards,
Damien.


On Sat, Feb 18, 2017 at 7:06 PM, Mark Waite 
wrote:

> 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 Folder configuration for Jenkins git plugin
> and Jenkins git client plugin development changes from my forks at
> https://github.com/MarkEWaite/git-client-plugin.  If I clone that
> repository with a shallow clone, there are unit tests which fail because
> the tests rely on a full local history of the repository.
>
> Are you performing a "checkout scm" (or similar) in your Jenkinsfile so
> that each job has its own working copy of the repository?  If so, are you
> enabling shallow clone in that checkout?  If not, then you need to change
> to use "checkout scm" in each Jenkinsfile.
>
> Mark Waite
>
> On Sat, Feb 18, 2017 at 10:57 AM Damien Coraboeuf <
> damien.corabo...@gmail.com> wrote:
>
>> Hi,
>>
>> In order to compute versions correctly (using https://github.com/
>> nemerosa/versioning), I need my projects not to be checked out using a
>> shallow clone option.
>>
>> The Organization plug-in (https://wiki.jenkins-ci.org/
>> display/JENKINS/GitHub+Organization+Folder+Plugin) does not seem to
>> allow to disable this option. Or is it something we can change using the
>> Pipeline Model Definition plug-in syntax?
>>
>> Thanks,
>> Damien.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/
>> msgid/jenkinsci-users/69ac8ef3-010a-4a6f-8874-
>> 10a4b632dd6d%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/jenkinsci-users/TIK6DERVZqQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/CAO49JtF7Hd1XVatjf5q4caTV6KLmr
> WTrnK7J7OfjAk9fPcM8yA%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAMbUmAEfvgh-nG-Ss49k6Nf69D0f%2Bgbk%2B9UJPyYYe8GY5hMhkw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Disabling shallow clone using the GitHub organisation

[Mark Waite]

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 Folder configuration for Jenkins git plugin and
Jenkins git client plugin development changes from my forks at
https://github.com/MarkEWaite/git-client-plugin.  If I clone that
repository with a shallow clone, there are unit tests which fail because
the tests rely on a full local history of the repository.

Are you performing a "checkout scm" (or similar) in your Jenkinsfile so
that each job has its own working copy of the repository?  If so, are you
enabling shallow clone in that checkout?  If not, then you need to change
to use "checkout scm" in each Jenkinsfile.

Mark Waite

On Sat, Feb 18, 2017 at 10:57 AM Damien Coraboeuf <
damien.corabo...@gmail.com> wrote:

> Hi,
>
> In order to compute versions correctly (using
> https://github.com/nemerosa/versioning), I need my projects not to be
> checked out using a shallow clone option.
>
> The Organization plug-in (
> https://wiki.jenkins-ci.org/display/JENKINS/GitHub+Organization+Folder+Plugin)
> does not seem to allow to disable this option. Or is it something we can
> change using the Pipeline Model Definition plug-in syntax?
>
> Thanks,
> Damien.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/69ac8ef3-010a-4a6f-8874-10a4b632dd6d%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtF7Hd1XVatjf5q4caTV6KLmrWTrnK7J7OfjAk9fPcM8yA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins configuration from script

[Damien Coraboeuf]

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, tools, plugin configurations, etc.). 
That's some work to do, but on the other hand, it is only code and you can 
test it automatically before going in production.

On Friday, 17 February 2017 00:44:03 UTC+1, Andrew Hammond wrote:
>
> I'm doing something similar. My current "solution" is as follows:
>
> 1) Jenkins master is run in a docker container. The dockerfile includes a 
>
> RUN /usr/local/bin/install-plugins.sh your plugins listed here
>
> Currently I have only the following plugins:
> blueocean (I know it's beta, but it make jenkins actually usable, so...)
> digitalocean-plugin (master is in DO, and build agents are spun up there 
> on demand)
> docker-build-step (we want to create docker images and push them to 
> dockerhub...)
> github-oauth (we have an organization on gh: use that to determine who 
> people are)
> github-branch-source (automatically scan repos in that organization and 
> detect Jenkinsfiles)
>
> 2) Absolutely minimal configuration in the Jenkins master. That means all 
> builds are driven by the Jenkinsfile in the repo with the code.
>
> I'm trying to get scm-sync-configuration plugin working now, but I'm 
> realizing that maybe it's not even worth trying. I think I'll just go with 
> snapshotting the filesystem.
>
> A
>
>
> On Thursday, November 3, 2016 at 3:42:29 AM UTC-7, Tomasz Szandała wrote:
>>
>> Greetings All,
>> I am working on new Jenkins usage model for my Team.
>> My idea is to:
>> 1. Create new cloud instance
>> 2. Configure it and install Jenkins using Ansible
>> 3. Configure Jenkins using some kind of script
>> 4. Create and configure few projcts - I have them in DSL scripts 
>> currently.
>>
>> My problem is point nr 3.:
>> I need to:
>> a. Configure LDAP
>> b. Add nodes
>> c. Install needed plugins.
>>
>> So far I've found script to add nodes, but don't know how to use it from 
>> command line...
>>
>> Anyone knows where to look for guides about my problem?
>>
>> Thank You in advance,
>> Tomek
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/afa96bee-0eb0-4f61-a25d-4e411a3cdd80%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins LTS and Docker 1.13

[Damien Coraboeuf]

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 with docker 1.12 
> because of this issue 
> https://github.com/maxfields2000/dockerjenkins_tutorial/issues/20
> Has anyway here tested jenkins LTS with the Docker 1.13? 
>
> Is there a way to get around the issue with another docker plugin?
>
>
> Can help if you start giving the plugins and LTS version you're referring 
> to.
>
>
> On my setup we would to experiment with docker swarm mode which is a 1.12+ 
> feature.
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-use...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/dda0da4c-04f5-4042-9f14-92494e23ef3f%40googlegroups.com
>  
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/fc6a8f40-6857-4975-a708-0b6277c1490b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Build project inside docker

[Damien Coraboeuf]

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 usr/local/src/freeswitch-1.4.26?

Best regards,
Damien.

On Saturday, 18 February 2017 11:26:17 UTC+1, Ruchir Brahmbhatt wrote:
>
> 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 
> docker.image('bettervoice/freeswitch-container:1.6.9').inside {
> sh 'cd usr/local/src/freeswitch-1.4.26'
>
> sh './rebootstrap'
>
> sh './configure' sh 'make' } } }
>
>
> But I get error as below.
>
> [st-cawsup-awpbx-voip_master-ZVTVQJCM4MJ75YVFR46JVXULPIMRLC6U3ILUY4WLDZ7ISHOVOE6A]
>  Running shell script
> + usr/local/src/freeswitch-1.4.26/rebootstrap
> /var/lib/jenkins/workspace/st-cawsup-awpbx-voip_master-ZVTVQJCM4MJ75YVFR46JVXULPIMRLC6U3ILUY4WLDZ7ISHOVOE6A@tmp/durable-776c465c/script.sh:
>  2: 
> /var/lib/jenkins/workspace/st-cawsup-awpbx-voip_master-ZVTVQJCM4MJ75YVFR46JVXULPIMRLC6U3ILUY4WLDZ7ISHOVOE6A@tmp/durable-776c465c/script.sh:
>  usr/local/src/freeswitch-1.4.26/rebootstrap: not found
>
>
> Any hints on what is wrong with the file?
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/732ba5c5-41d2-41e5-ba15-451d44d998e8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Execute shell script on remote host using ssh - Jenkinsfile

[jequals5]

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 subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/8e3f2e46-f8bc-4ead-b622-dedb4d449237%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Wojciech Jamrozik]

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 build,
tests and bundle packages, while Octopus takes the whole responsibility of
deployment, where Octopus is focused and particularly good at"

Jenkins is an overall automation and CI tool, Octopus is focused on
deployment automation (and over the years not only .NET).

To illustrate the question and ask Jenkins/Jenkins+Octopus users for a
second opinion: I've been challenged with requirement:
- client wants to have a on-demand test environment in AWS that has to be
instantiated automatically whenever new releases of business software are
ready.
- the infrastructure consists of multiple VMs provisioned by choice of
DevOps with Terraform/Puppet and some other tools
- the business applications consist of both .NET and non-dot-net
applications - all can be automated in deployment.

The two approaches we have discussed are:
1. Jenkins job fires terraform, puppet, etc. to build up the
infrastructure, and then triggers Octopus via API to release only the
business applications. This approach was proposed based on the opinion that
Octopus is not for orchestration and mainly for .NET applications. DevOps
don't use it to orchestrate the infrastructure, use the right tools for the
right job.
2. OR Jenkins is for build, test, and package the applications, where the
set of infrastructure (terraform/puppet) scripts are just one of them. All
are deployed from Octopus, infrastructure first, applications second. Clear
distinction of responsibility, despite the opinion that Octopus is doing
something it wasn't designed for.

What is your opinion? Why we use Jenkins+Octopus and how would we use this
pair in a dynamic cloud scenario like above which is becoming more and more
popular.

BR
Wojtek/Dojo

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAAn6uHSPBUJoR45Ju6O2fwmtArcmq8GvA0htBoQJnJ9Y8XN4DQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Build project inside docker

[Ruchir Brahmbhatt]

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 
docker.image('bettervoice/freeswitch-container:1.6.9').inside {
sh 'cd usr/local/src/freeswitch-1.4.26'

sh './rebootstrap'

sh './configure' sh 'make' } } }


But I get error as below.

[st-cawsup-awpbx-voip_master-ZVTVQJCM4MJ75YVFR46JVXULPIMRLC6U3ILUY4WLDZ7ISHOVOE6A]
 Running shell script
+ usr/local/src/freeswitch-1.4.26/rebootstrap
/var/lib/jenkins/workspace/st-cawsup-awpbx-voip_master-ZVTVQJCM4MJ75YVFR46JVXULPIMRLC6U3ILUY4WLDZ7ISHOVOE6A@tmp/durable-776c465c/script.sh:
 2: 
/var/lib/jenkins/workspace/st-cawsup-awpbx-voip_master-ZVTVQJCM4MJ75YVFR46JVXULPIMRLC6U3ILUY4WLDZ7ISHOVOE6A@tmp/durable-776c465c/script.sh:
 usr/local/src/freeswitch-1.4.26/rebootstrap: not found


Any hints on what is wrong with the file?

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/fbaf0dbb-20e8-4413-b157-a56161167fb9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[esharish]

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 plugin and did not work.

-Harish


-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/2082dcae-d23b-4f5b-82b7-cbf72de67cbd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.