Re: pipeline global library no longer works on latest builds on Windows

[Baptiste Mathus]

Hi,
Are you sure it's not just the Git URL? Does really your Jenkins instance
run on *your* machine? (127.0.0.1)
Cheers
Le 1 juin 2016 5:36 AM,  a écrit :

> Hi,
>Jenkins pipeline global library no longer works for me on Windows which
> unfortunately my employer choose to use.  I simply can't access the
> workflowLibs.git through the http URL (
> http://127.0.0.1:8080/workflowLibs.git/ in my case).  It give me the Not
> Found error message even after I already disable the security feature in
> order to create the empty git repository first.
>I had successfully setup pipeline global library before using Jenkins
> 1.x but then I was busy with something else until now when suddenly nothing
> works.  I forgot which version of Jenkins 1.x I used before so I tried the
> LTS version and Jenkins 2.6 and 2.7.
>Please let me know which option I should follow.  I already tried to
> manually create the git repository under workflow-libs but it doesn't
> work.  SSH mechanism doesn't work on Windows for the initial repository
> either.
>
> Thanks
>
> --
> 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/084c46b1-f3d5-4caa-a335-a46ad290de5e%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/CANWgJS71_U5k_n1v9oejLdvWdH%3DmpOs3hfGKt%3DiKOo3D68qNkQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: deployment of multiple git branches

[Tomáš Bohuněk]

Thank you a lot guys. My question was - what do you use for this type of 
deployment - build from each feature branch.

On Tuesday, May 31, 2016 at 1:04:30 PM UTC+2, Tomáš Bohuněk wrote:
>
> What do you recommend for deployment of multiple git repository (one 
> project with few feature branches). Final artifact is JAR with bundled 
> Tomcat application server. I usually run this JAR in Docker container. What 
> do you prefer?
>

-- 
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/6afa3353-2f58-4c6b-9e42-62c5db210ec9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

pipeline global library no longer works on latest builds on Windows

[tomwilson001 . us]

Hi,
   Jenkins pipeline global library no longer works for me on Windows which 
unfortunately my employer choose to use.  I simply can't access the 
workflowLibs.git through the http URL 
(http://127.0.0.1:8080/workflowLibs.git/ in my case).  It give me the Not 
Found error message even after I already disable the security feature in 
order to create the empty git repository first.
   I had successfully setup pipeline global library before using Jenkins 
1.x but then I was busy with something else until now when suddenly nothing 
works.  I forgot which version of Jenkins 1.x I used before so I tried the 
LTS version and Jenkins 2.6 and 2.7.
   Please let me know which option I should follow.  I already tried to 
manually create the git repository under workflow-libs but it doesn't work. 
 SSH mechanism doesn't work on Windows for the initial repository either.

Thanks

-- 
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/084c46b1-f3d5-4caa-a335-a46ad290de5e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Remove build triggers section

[Daniel Beck]

> On 31.05.2016, at 17:59, Victor Martinez  
> wrote:
> 
> Jenkins.instances?.items

`items` will not get items in folders, so is very configuration dependent.

`allItems` OTOH will get also get e.g. Matrix configurations.

`getAllItems(TopLevelItem.class)` is probably the best approach.

-- 
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/A5CA0CF7-4B39-4049-B87A-2E899F689B75%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Parse CSV data in jenkins job ?

[Daniel Beck]

> On 31.05.2016, at 23:25, Beau Henderson  wrote:
> 
> I would like to set up a job that parses the data in a CSV/XLS/XML file. Is 
> there a way to upload / pass along a file when initiating a job run ?

This job is parameterized -> File parameter

-- 
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/D1691A92-22F6-4C7B-B400-59AE0CDD2ACB%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Parse CSV data in jenkins job ?

[Beau Henderson]

I would like to set up a job that parses the data in a CSV/XLS/XML file. Is 
there a way to upload / pass along a file when initiating a job run ?

-- 
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/861db9dc-e297-41dc-9004-2bc1f31cafc7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline stop/resume gates

[Baptiste Mathus]

You can choose whatever suits your need. You are basically gonna catch your
calls to steps A & B, and in the catch clause, are going to use some
business logic to decide to make it fail, and just continue with a simple
if condition.

When you're ready, just write those, and ask for review here if you don't
manage to do what you want. It'll be probably easier to help you anyway
(and you'll have got a better grasp of it)

2016-05-31 21:50 GMT+02:00 Brian Jones :

> Thanks for the "outside the node" tip.
>
> Case 1, subsequent job steps are performed where case 3 they are not. So
> default of running job if no further further human input is given is to
> just do A,B.
>
> On Tuesday, May 31, 2016 at 11:44:06 AM UTC-7, Baptiste Mathus wrote:
>>
>> Well, either you didn't give enough info, or seems quite straightforward.
>> The human interaction is the input step. Make sure to use it outside a
>> node { } to not occupy an agent while waiting for user input.
>> I don't see the actual difference you mean between your 1st and 3rd case.
>>
>> 2016-05-31 20:02 GMT+02:00 Brian Jones :
>>
>>> I want to have a pipeline where segments of the pipeline are only
>>> executed upon a human decision, possibly hours or days after the job is
>>> started. What is the recommended way to do this using the pipeline plugin?
>>>
>>> pipeline:
>>>
>>> Decide to continue case:
>>> build step A - build step B - < human decision, decide to continue> -
>>> build step C
>>>
>>> Decide not to continue:
>>> build step A - build step B - < human decision, decide to stop> - no
>>> further action
>>>
>>> Ignore job after AB completed:
>>> build step A - build step B - < no further human action with job > - no
>>> further action
>>>
>>>
>>> --
>>> 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/2268a2c6-5a0b-4bf1-a949-0a3204caa80b%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/1ac10094-9fef-4461-a74f-09ff06317111%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/CANWgJS7DSPjaDGA4a7BsFW2oe1EGfQ-cVEXWrJYR%3DZ2StqF-ow%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline stop/resume gates

[Brian Jones]

Thanks for the "outside the node" tip. 

Case 1, subsequent job steps are performed where case 3 they are not. So 
default of running job if no further further human input is given is to 
just do A,B.

On Tuesday, May 31, 2016 at 11:44:06 AM UTC-7, Baptiste Mathus wrote:
>
> Well, either you didn't give enough info, or seems quite straightforward.
> The human interaction is the input step. Make sure to use it outside a 
> node { } to not occupy an agent while waiting for user input.
> I don't see the actual difference you mean between your 1st and 3rd case.
>
> 2016-05-31 20:02 GMT+02:00 Brian Jones >:
>
>> I want to have a pipeline where segments of the pipeline are only 
>> executed upon a human decision, possibly hours or days after the job is 
>> started. What is the recommended way to do this using the pipeline plugin?
>>
>> pipeline: 
>>
>> Decide to continue case:
>> build step A - build step B - < human decision, decide to continue> - 
>> build step C
>>
>> Decide not to continue:
>> build step A - build step B - < human decision, decide to stop> - no 
>> further action
>>
>> Ignore job after AB completed:
>> build step A - build step B - < no further human action with job > - no 
>> further action
>>
>>
>> -- 
>> 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/2268a2c6-5a0b-4bf1-a949-0a3204caa80b%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/1ac10094-9fef-4461-a74f-09ff06317111%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline stop/resume gates

[Baptiste Mathus]

Well, either you didn't give enough info, or seems quite straightforward.
The human interaction is the input step. Make sure to use it outside a node
{ } to not occupy an agent while waiting for user input.
I don't see the actual difference you mean between your 1st and 3rd case.

2016-05-31 20:02 GMT+02:00 Brian Jones :

> I want to have a pipeline where segments of the pipeline are only executed
> upon a human decision, possibly hours or days after the job is
> started. What is the recommended way to do this using the pipeline plugin?
>
> pipeline:
>
> Decide to continue case:
> build step A - build step B - < human decision, decide to continue> -
> build step C
>
> Decide not to continue:
> build step A - build step B - < human decision, decide to stop> - no
> further action
>
> Ignore job after AB completed:
> build step A - build step B - < no further human action with job > - no
> further action
>
>
> --
> 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/2268a2c6-5a0b-4bf1-a949-0a3204caa80b%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/CANWgJS4%3D%3DpnwynhXMuhzCg2i6Mz19VXSWTYrZ1GHb99oAaNHtw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: deployment of multiple git branches

[Mark Waite]

You might consider fingerprinting the artifacts then you can use the
Jenkins fingerprint lookup to steer what created that artifact

On Tue, May 31, 2016, 12:07 PM Thomas Zoratto 
wrote:

> Tomáš was talking about Docker so let’s take it for example. You could
> build a new Docker image for each one of your branches and tag it with the
> branch name, build number or whatever you prefer.
>
> Regarding Nexus or Maven specifically you could use a plugin such as the
> Maven build number plugin for that purpose.
>
> It’s just my opinion based on little experience, there are probably better
> methods (or workflows that don’t raise this question) out there.
>
> But honestly, I think this isn’t directly related to Jenkins.
>
> Good luck !
>
> Le 31 mai 2016 à 18:59, Philipp Meier  a écrit :
>
> Hi,
>
> The interesting question for me is how to handle and identify the
> different artifacts which are built by the several branches. I. e. in Maven
> you specify a version 1.0.0-snapshot and this is then used to build the
> Jar. When you're going to deploy this on a machine or a repository (i. e.
> Nexus) you won't be able to identify from which branch it was built. How do
> you handle this?
>
> Best, Philipp
>
> On Tuesday, 31 May 2016 18:16:34 UTC+2, Thomas Zoratto wrote:
>>
>> Hello,
>>
>> You can achieve this with a Jenkinsfile per branch in your repository.
>> Then create a new multibranch pipeline job in Jenkins pointing to your
>> repository and you're done. See
>> https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Multibranch+Plugin
>>
>> Thomas
>>
>> Le 31 mai 2016 à 14:00, Tomáš Bohuněk  a écrit :
>>
>> I would like to deploy and run each jar file for each feature branch.
>>
>> Project is written in Java and JavaScript. Jar file is built by maven. I
>> need to deploy somehow to one machine each of jar built from each feature
>> branch.
>>
>>
>> On Tuesday, May 31, 2016 at 1:55:21 PM UTC+2, Mark Waite wrote:
>>>
>>> I think you'll need to provide more details about the problem you're
>>> trying to solve, and the languages you're using to solve it.  For example,
>>> since you mentioned that you're deploying to tomcat, are you writing in
>>> Java or some other JRE supported language (like Scala)?
>>>
>>> Are you building your jar with maven, gradle, ant, or some other build
>>> tool?
>>>
>>> Mark Waite
>>>
>>> On Tue, May 31, 2016 at 5:46 AM Tomáš Bohuněk  wrote:
>>>
 Sorry for mistake. You are right. I have one single git repository (one
 project) with a few feature branches.


 On Tuesday, May 31, 2016 at 1:44:19 PM UTC+2, Mark Waite wrote:

> Could you explain further what you mean by "multiple git repository
> (one project with few feature branches)"?
>
> The phrase "multiple git repository" seems to be in conflict with the
> phrase "one project".  I typically place a project in a single git
> repository with a few feature branches as necessary.  Can you describe 
> more
> about why you need multiple git repositories?
>
> Thanks,
> Mark Waite
>
> On Tue, May 31, 2016 at 5:04 AM Tomáš Bohuněk 
> wrote:
>
 What do you recommend for deployment of multiple git repository (one
>> project with few feature branches). Final artifact is JAR with bundled
>> Tomcat application server. I usually run this JAR in Docker container. 
>> What
>> do you prefer?
>>
>> --
>> 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/911cbd52-c307-486d-b0bd-339ea40b8200%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-use...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-users/a5cf009f-289a-4945-ac5c-00fb6f52568e%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-use...@googlegroups.com.
>> To view this discussion on the web visit
>> https

Re: AWS Elastic Beanstalk deploy fails after 2.7 and plugin upgrade

[Aldrin Leal]

Register on github.com/inenieux/awseb-deployment-plugin/issues

Thank you

--
-- Aldrin Leal,  / http://about.me/aldrinleal

On Tue, May 31, 2016 at 1:21 PM, Steve Abbitt  wrote:

> I just updated Jenkins to 2.7 from 2.6 along with about 10 plugins. After
> the upgrades, one of my jobs that deploys to Elastic Beanstalk using the
> 'AWSEB Deployment Plugin' is failing with the following errors below. This
> job had been working fine for almost a year. I also noticed that the same
> erros are popping up when I try to verify my AWS credentials through the
> plugin config dialog (and yes, the credentials are active). Anyone have any
> ideas?
>
> AWSEB Deployment Plugin Version 0.3.8
> FATAL: Deployment Failure
> java.io.IOException: Deployment Failure
>   at 
> br.com.ingenieux.jenkins.plugins.awsebdeployment.AWSEBDeploymentBuilder.perform(AWSEBDeploymentBuilder.java:171)
>   at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)
>   at hudson.model.Build$BuildExecution.build(Build.java:205)
>   at hudson.model.Build$BuildExecution.doRun(Build.java:162)
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
>   at hudson.model.Run.execute(Run.java:1741)
>   at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
>   at hudson.model.ResourceController.execute(ResourceController.java:98)
>   at hudson.model.Executor.run(Executor.java:410)
> Caused by: java.util.concurrent.ExecutionException: 
> java.lang.reflect.InvocationTargetException
>   at java.util.concurrent.FutureTask.report(FutureTask.java:122)
>   at java.util.concurrent.FutureTask.get(FutureTask.java:192)
>   at hudson.remoting.LocalChannel$2.get(LocalChannel.java:77)
>   at 
> br.com.ingenieux.jenkins.plugins.awsebdeployment.DeployerRunner.perform(DeployerRunner.java:66)
>   at 
> br.com.ingenieux.jenkins.plugins.awsebdeployment.AWSEBDeploymentBuilder.perform(AWSEBDeploymentBuilder.java:167)
>   ... 9 more
> Caused by: java.lang.reflect.InvocationTargetException
>   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>   at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>   at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
>   at 
> org.apache.commons.lang.reflect.ConstructorUtils.invokeConstructor(ConstructorUtils.java:162)
>   at 
> br.com.ingenieux.jenkins.plugins.awsebdeployment.AWSClientFactory.getService(AWSClientFactory.java:138)
>   at 
> br.com.ingenieux.jenkins.plugins.awsebdeployment.cmd.DeployerCommand$InitAWS.perform(DeployerCommand.java:145)
>   at 
> br.com.ingenieux.jenkins.plugins.awsebdeployment.cmd.DeployerChain.perform(DeployerChain.java:54)
>   at 
> br.com.ingenieux.jenkins.plugins.awsebdeployment.SlaveDeployerCallable.call(SlaveDeployerCallable.java:42)
>   at 
> br.com.ingenieux.jenkins.plugins.awsebdeployment.SlaveDeployerCallable.call(SlaveDeployerCallable.java:27)
>   at hudson.remoting.LocalChannel$1.call(LocalChannel.java:52)
>   at 
> jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NoClassDefFoundError: 
> org/apache/http/conn/ssl/SSLSocketFactory
>   at 
> com.amazonaws.AmazonWebServiceClient.(AmazonWebServiceClient.java:136)
>   at 
> com.amazonaws.services.s3.AmazonS3Client.(AmazonS3Client.java:481)
>   at 
> com.amazonaws.services.s3.AmazonS3Client.(AmazonS3Client.java:461)
>   at 
> com.amazonaws.services.s3.AmazonS3Client.(AmazonS3Client.java:443)
>   ... 16 more
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.http.conn.ssl.SSLSocketFactory
>   at 
> jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1376)
>   at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1326)
>   at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1079)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>   ... 20 more
> Finished: FAILURE
>
>
> --
> 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/de1aad09-604c-4d6b-a5d2-ef8510e5bb3a%40googlegroups.com
> 

AWS Elastic Beanstalk deploy fails after 2.7 and plugin upgrade

[Steve Abbitt]

I just updated Jenkins to 2.7 from 2.6 along with about 10 plugins. After 
the upgrades, one of my jobs that deploys to Elastic Beanstalk using the 
'AWSEB Deployment Plugin' is failing with the following errors below. This 
job had been working fine for almost a year. I also noticed that the same 
erros are popping up when I try to verify my AWS credentials through the 
plugin config dialog (and yes, the credentials are active). Anyone have any 
ideas? 

AWSEB Deployment Plugin Version 0.3.8
FATAL: Deployment Failure
java.io.IOException: Deployment Failure
at 
br.com.ingenieux.jenkins.plugins.awsebdeployment.AWSEBDeploymentBuilder.perform(AWSEBDeploymentBuilder.java:171)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)
at hudson.model.Build$BuildExecution.build(Build.java:205)
at hudson.model.Build$BuildExecution.doRun(Build.java:162)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
at hudson.model.Run.execute(Run.java:1741)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)
Caused by: java.util.concurrent.ExecutionException: 
java.lang.reflect.InvocationTargetException
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:192)
at hudson.remoting.LocalChannel$2.get(LocalChannel.java:77)
at 
br.com.ingenieux.jenkins.plugins.awsebdeployment.DeployerRunner.perform(DeployerRunner.java:66)
at 
br.com.ingenieux.jenkins.plugins.awsebdeployment.AWSEBDeploymentBuilder.perform(AWSEBDeploymentBuilder.java:167)
... 9 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at 
org.apache.commons.lang.reflect.ConstructorUtils.invokeConstructor(ConstructorUtils.java:162)
at 
br.com.ingenieux.jenkins.plugins.awsebdeployment.AWSClientFactory.getService(AWSClientFactory.java:138)
at 
br.com.ingenieux.jenkins.plugins.awsebdeployment.cmd.DeployerCommand$InitAWS.perform(DeployerCommand.java:145)
at 
br.com.ingenieux.jenkins.plugins.awsebdeployment.cmd.DeployerChain.perform(DeployerChain.java:54)
at 
br.com.ingenieux.jenkins.plugins.awsebdeployment.SlaveDeployerCallable.call(SlaveDeployerCallable.java:42)
at 
br.com.ingenieux.jenkins.plugins.awsebdeployment.SlaveDeployerCallable.call(SlaveDeployerCallable.java:27)
at hudson.remoting.LocalChannel$1.call(LocalChannel.java:52)
at 
jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NoClassDefFoundError: 
org/apache/http/conn/ssl/SSLSocketFactory
at 
com.amazonaws.AmazonWebServiceClient.(AmazonWebServiceClient.java:136)
at 
com.amazonaws.services.s3.AmazonS3Client.(AmazonS3Client.java:481)
at 
com.amazonaws.services.s3.AmazonS3Client.(AmazonS3Client.java:461)
at 
com.amazonaws.services.s3.AmazonS3Client.(AmazonS3Client.java:443)
... 16 more
Caused by: java.lang.ClassNotFoundException: 
org.apache.http.conn.ssl.SSLSocketFactory
at 
jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1376)
at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1326)
at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1079)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 20 more
Finished: FAILURE


-- 
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/de1aad09-604c-4d6b-a5d2-ef8510e5bb3a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: deployment of multiple git branches

[Thomas Zoratto]

Tomáš was talking about Docker so let’s take it for example. You could build a 
new Docker image for each one of your branches and tag it with the branch name, 
build number or whatever you prefer.

Regarding Nexus or Maven specifically you could use a plugin such as the Maven 
build number plugin for that purpose.

It’s just my opinion based on little experience, there are probably better 
methods (or workflows that don’t raise this question) out there.

But honestly, I think this isn’t directly related to Jenkins.

Good luck !

> Le 31 mai 2016 à 18:59, Philipp Meier  a écrit :
> 
> Hi,
> 
> The interesting question for me is how to handle and identify the different 
> artifacts which are built by the several branches. I. e. in Maven you specify 
> a version 1.0.0-snapshot and this is then used to build the Jar. When you're 
> going to deploy this on a machine or a repository (i. e. Nexus) you won't be 
> able to identify from which branch it was built. How do you handle this?
> 
> Best, Philipp
> 
> On Tuesday, 31 May 2016 18:16:34 UTC+2, Thomas Zoratto wrote:
> Hello,
> 
> You can achieve this with a Jenkinsfile per branch in your repository. Then 
> create a new multibranch pipeline job in Jenkins pointing to your repository 
> and you're done. See 
> https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Multibranch+Plugin 
> 
> 
> Thomas
> 
> Le 31 mai 2016 à 14:00, Tomáš Bohuněk > a 
> écrit :
> 
>> I would like to deploy and run each jar file for each feature branch. 
>> 
>> Project is written in Java and JavaScript. Jar file is built by maven. I 
>> need to deploy somehow to one machine each of jar built from each feature 
>> branch.
>> 
>> 
>> On Tuesday, May 31, 2016 at 1:55:21 PM UTC+2, Mark Waite wrote:
>> I think you'll need to provide more details about the problem you're trying 
>> to solve, and the languages you're using to solve it.  For example, since 
>> you mentioned that you're deploying to tomcat, are you writing in Java or 
>> some other JRE supported language (like Scala)?
>> 
>> Are you building your jar with maven, gradle, ant, or some other build tool?
>> 
>> Mark Waite
>> 
>> On Tue, May 31, 2016 at 5:46 AM Tomáš Bohuněk > wrote:
>> Sorry for mistake. You are right. I have one single git repository (one 
>> project) with a few feature branches.
>> 
>> 
>> On Tuesday, May 31, 2016 at 1:44:19 PM UTC+2, Mark Waite wrote:
>> Could you explain further what you mean by "multiple git repository (one 
>> project with few feature branches)"?
>> 
>> The phrase "multiple git repository" seems to be in conflict with the phrase 
>> "one project".  I typically place a project in a single git repository with 
>> a few feature branches as necessary.  Can you describe more about why you 
>> need multiple git repositories?
>> 
>> Thanks,
>> Mark Waite
>> 
>> On Tue, May 31, 2016 at 5:04 AM Tomáš Bohuněk > wrote:
>> What do you recommend for deployment of multiple git repository (one project 
>> with few feature branches). Final artifact is JAR with bundled Tomcat 
>> application server. I usually run this JAR in Docker container. What do you 
>> prefer?
>> 
>> -- 
>> 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/911cbd52-c307-486d-b0bd-339ea40b8200%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-use...@googlegroups.com <>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/a5cf009f-289a-4945-ac5c-00fb6f52568e%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-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/ef93b121-e7e9-4591-aa2a-e31f57c49b32%40googlegroups.com
>>  
>> 

Pipeline stop/resume gates

[Brian Jones]

I want to have a pipeline where segments of the pipeline are only executed 
upon a human decision, possibly hours or days after the job is 
started. What is the recommended way to do this using the pipeline plugin?

pipeline: 

Decide to continue case:
build step A - build step B - < human decision, decide to continue> - build 
step C

Decide not to continue:
build step A - build step B - < human decision, decide to stop> - no 
further action

Ignore job after AB completed:
build step A - build step B - < no further human action with job > - no 
further action


-- 
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/2268a2c6-5a0b-4bf1-a949-0a3204caa80b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: deployment of multiple git branches

[Philipp Meier]

Hi,

The interesting question for me is how to handle and identify the different 
artifacts which are built by the several branches. I. e. in Maven you 
specify a version 1.0.0-snapshot and this is then used to build the Jar. 
When you're going to deploy this on a machine or a repository (i. e. Nexus) 
you won't be able to identify from which branch it was built. How do you 
handle this?

Best, Philipp

On Tuesday, 31 May 2016 18:16:34 UTC+2, Thomas Zoratto wrote:
>
> Hello,
>
> You can achieve this with a Jenkinsfile per branch in your repository. 
> Then create a new multibranch pipeline job in Jenkins pointing to your 
> repository and you're done. See 
> https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Multibranch+Plugin
>
> Thomas
>
> Le 31 mai 2016 à 14:00, Tomáš Bohuněk > a 
> écrit :
>
> I would like to deploy and run each jar file for each feature branch. 
>
> Project is written in Java and JavaScript. Jar file is built by maven. I 
> need to deploy somehow to one machine each of jar built from each feature 
> branch.
>
>
> On Tuesday, May 31, 2016 at 1:55:21 PM UTC+2, Mark Waite wrote:
>>
>> I think you'll need to provide more details about the problem you're 
>> trying to solve, and the languages you're using to solve it.  For example, 
>> since you mentioned that you're deploying to tomcat, are you writing in 
>> Java or some other JRE supported language (like Scala)?
>>
>> Are you building your jar with maven, gradle, ant, or some other build 
>> tool?
>>
>> Mark Waite
>>
>> On Tue, May 31, 2016 at 5:46 AM Tomáš Bohuněk  wrote:
>>
>>> Sorry for mistake. You are right. I have one single git repository (one 
>>> project) with a few feature branches.
>>>
>>>
>>> On Tuesday, May 31, 2016 at 1:44:19 PM UTC+2, Mark Waite wrote:
>>>
 Could you explain further what you mean by "multiple git repository 
 (one project with few feature branches)"?

 The phrase "multiple git repository" seems to be in conflict with the 
 phrase "one project".  I typically place a project in a single git 
 repository with a few feature branches as necessary.  Can you describe 
 more 
 about why you need multiple git repositories?

 Thanks,
 Mark Waite

 On Tue, May 31, 2016 at 5:04 AM Tomáš Bohuněk  
 wrote:

>>> What do you recommend for deployment of multiple git repository (one 
> project with few feature branches). Final artifact is JAR with bundled 
> Tomcat application server. I usually run this JAR in Docker container. 
> What 
> do you prefer?
>
> -- 
> 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/911cbd52-c307-486d-b0bd-339ea40b8200%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-use...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-users/a5cf009f-289a-4945-ac5c-00fb6f52568e%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-use...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/ef93b121-e7e9-4591-aa2a-e31f57c49b32%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/a9af9134-fdfa-4bbc-aa1a-788417f71e1c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Remove build triggers section

[Davi Diório Mendes]

This looks like solves my problem!

Thanks for response

2016-05-31 12:59 GMT-03:00 Victor Martinez :

> Hi,
>
> You can easily iterate through jenkins groovy api and use the method
> http://javadoc.jenkins-ci.org/hudson/model/AbstractProject.html#removeTrigger(hudson.triggers.TriggerDescriptor)
> in addition to
> http://javadoc.jenkins-ci.org/hudson/model/AbstractProject.html#getTriggers()
>
>
>  Something line
>
> Jenkins.instances?.items.findAll { it.getTrigers () }.each{
>
>   //iterate through each trigger and remove it
>
> }
>
> I haven't tested it out, but something like that it should work
>
> Cheers
>
> --
> 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/l-4c3SghZxs/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/30d947e7-9e3f-4677-bfaa-2f7bc33579dc%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
*Davi Diório Mendes*
Eng. de Computação - Turma de 2011
Universidade de São Paulo - EESC/ICMC

-- 
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/CA%2B7fAA6z73AZPJ5m6ifBKC0SNXDSBFq-wr0gTqr5A6ESAc2tEw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: deployment of multiple git branches

[Zoratto Thomas]

Hello,

You can achieve this with a Jenkinsfile per branch in your repository. Then 
create a new multibranch pipeline job in Jenkins pointing to your repository 
and you're done. See 
https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Multibranch+Plugin

Thomas

> Le 31 mai 2016 à 14:00, Tomáš Bohuněk  a écrit :
> 
> I would like to deploy and run each jar file for each feature branch. 
> 
> Project is written in Java and JavaScript. Jar file is built by maven. I need 
> to deploy somehow to one machine each of jar built from each feature branch.
> 
> 
>> On Tuesday, May 31, 2016 at 1:55:21 PM UTC+2, Mark Waite wrote:
>> I think you'll need to provide more details about the problem you're trying 
>> to solve, and the languages you're using to solve it.  For example, since 
>> you mentioned that you're deploying to tomcat, are you writing in Java or 
>> some other JRE supported language (like Scala)?
>> 
>> Are you building your jar with maven, gradle, ant, or some other build tool?
>> 
>> Mark Waite
>> 
>>> On Tue, May 31, 2016 at 5:46 AM Tomáš Bohuněk  wrote:
>>> Sorry for mistake. You are right. I have one single git repository (one 
>>> project) with a few feature branches.
>>> 
>>> 
 On Tuesday, May 31, 2016 at 1:44:19 PM UTC+2, Mark Waite wrote:
>>> 
 Could you explain further what you mean by "multiple git repository (one 
 project with few feature branches)"?
 
 The phrase "multiple git repository" seems to be in conflict with the 
 phrase "one project".  I typically place a project in a single git 
 repository with a few feature branches as necessary.  Can you describe 
 more about why you need multiple git repositories?
 
 Thanks,
 Mark Waite
 
>>> 
> On Tue, May 31, 2016 at 5:04 AM Tomáš Bohuněk  wrote:
>>> 
> What do you recommend for deployment of multiple git repository (one 
> project with few feature branches). Final artifact is JAR with bundled 
> Tomcat application server. I usually run this JAR in Docker container. 
> What do you prefer?
> -- 
> 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/911cbd52-c307-486d-b0bd-339ea40b8200%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-use...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-users/a5cf009f-289a-4945-ac5c-00fb6f52568e%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/ef93b121-e7e9-4591-aa2a-e31f57c49b32%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/8E6462C2-EC15-4164-B5CD-B04D50276E3D%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Multibranch Pipeline / Git question -- Use same information as used to retrieve Jenkinsfile

[Greg Smith]

Thank you -- This is exactly what I was looking for.  Now that I have it, 
and was able to search the docs for it, I don't know how I missed it

Thanks,
Greg


On Tuesday, May 31, 2016 at 11:54:25 AM UTC-4, Antonio Muñiz wrote:
>
> You can use `checkout scm` which will clone the repository at the same 
> revision than the previously fetched Jenkinsfile.
>
> -- 
> Antonio Muñiz
> Software Engineer
> CloudBees, Inc.
>

-- 
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/98fb0c47-3637-471c-b7ed-d8c947f07776%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Remove build triggers section

[Victor Martinez]

Hi,

You can easily iterate through jenkins groovy api and use the method 
http://javadoc.jenkins-ci.org/hudson/model/AbstractProject.html#removeTrigger(hudson.triggers.TriggerDescriptor)
 in addition to 
http://javadoc.jenkins-ci.org/hudson/model/AbstractProject.html#getTriggers()


 Something line

Jenkins.instances?.items.findAll { it.getTrigers () }.each{

  //iterate through each trigger and remove it 

}

I haven't tested it out, but something like that it should work

Cheers

-- 
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/30d947e7-9e3f-4677-bfaa-2f7bc33579dc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Multibranch Pipeline / Git question -- Use same information as used to retrieve Jenkinsfile

[Antonio Muñiz]

You can use `checkout scm` which will clone the repository at the same
revision than the previously fetched Jenkinsfile.

On Tue, May 31, 2016 at 5:00 PM, Greg Smith  wrote:

>
> Hello,
>
> I have a question that is probably obvious, but I couldn't seem to find it
> anywhere.  Apologies for my newbie question:
>
> If I have a multibranch Pipeline job, does my Jenkinsfile need to do the
> git extract?  Or should that be assumed as part of the retrieval of the
> Jenkinsfile?
>
> For example, lets say I have project "MyProject", with branch "master",
> with a Jenkins file like this:
>
> node() {
>stage 'Checkout'
>// git -- Do I need to do the git checkout here??
>git credentialsId: '1ab8712b-28f4-498e-af0f-433b409675ea', url:
> 'g...@github.com:smithgcovert/MyProject.git'
>
>   // build stuff
> }
>
> Now I branch master to "newtestbranch" -- it has the same Jenkinsfile at
> the top.
>
> 1)  Do I even need the git extract step?  It would seem to be implied by
> the fact that the Jenkins file was found in that branch... but it seems i
> do from the testing I've done
> 2)  How can I pass the url and branch into the git step, so that I do not
> put a path to the repo in the file that is checked in?
>
> IE, I want the repo URL, and the branch being built, and the credentials
> used to do the extract to all be defined by the same url, branch, creds
> that were used to retrieve the Jenkinsfile.  It seems wrong to have any
> url, branch or credential information in the Jenkinsfile -- is there a way
> to say "extract the same as used to retrieve the Jenkinsfile"?
>
> Thanks,
> Greg
>
> --
> 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/549e1e95-d6f2-4c40-83b4-b731fdbf2ba6%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Antonio Muñiz
Software Engineer
CloudBees, Inc.

-- 
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/CAJc7kzQLySkhg_EV8KQBmJACDLBxFu3hff6iyBzBP7tLcn%2BT6w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Multibranch Pipeline / Git question -- Use same information as used to retrieve Jenkinsfile

[Greg Smith]

Hello,

I have a question that is probably obvious, but I couldn't seem to find it 
anywhere.  Apologies for my newbie question:

If I have a multibranch Pipeline job, does my Jenkinsfile need to do the 
git extract?  Or should that be assumed as part of the retrieval of the 
Jenkinsfile?

For example, lets say I have project "MyProject", with branch "master", 
with a Jenkins file like this:

node() {
   stage 'Checkout'
   // git -- Do I need to do the git checkout here??
   git credentialsId: '1ab8712b-28f4-498e-af0f-433b409675ea', url: 
'g...@github.com:smithgcovert/MyProject.git'

  // build stuff
}

Now I branch master to "newtestbranch" -- it has the same Jenkinsfile at 
the top.

1)  Do I even need the git extract step?  It would seem to be implied by 
the fact that the Jenkins file was found in that branch... but it seems i 
do from the testing I've done
2)  How can I pass the url and branch into the git step, so that I do not 
put a path to the repo in the file that is checked in?  

IE, I want the repo URL, and the branch being built, and the credentials 
used to do the extract to all be defined by the same url, branch, creds 
that were used to retrieve the Jenkinsfile.  It seems wrong to have any 
url, branch or credential information in the Jenkinsfile -- is there a way 
to say "extract the same as used to retrieve the Jenkinsfile"?

Thanks,
Greg

-- 
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/549e1e95-d6f2-4c40-83b4-b731fdbf2ba6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Publisher plugins crash in workflow pipeline

[Nicholas Brown]

See https://issues.jenkins-ci.org/browse/JENKINS-35234 
and https://issues.jenkins-ci.org/browse/JENKINS-35096

On Tuesday, 31 May 2016 14:05:01 UTC+1, Nicholas Brown wrote:
>
> Your correct:
>
> Neither of them implement this interface:
>
> https://github.com/jenkinsci/sloccount-plugin/blob/master/src/main/java/hudson/plugins/sloccount/SloccountPublisher.java#L30
>
> https://github.com/jenkinsci/cobertura-plugin/blob/master/src/main/java/hudson/plugins/cobertura/CoberturaPublisher.java#L53
>
> while for example the xunit plugin does:
>
> https://github.com/jenkinsci/xunit-plugin/blob/master/src/main/java/org/jenkinsci/plugins/xunit/XUnitPublisher.java#L63
>
> I found the following issue tracking this for cobertua:
> https://github.com/jenkinsci/cobertura-plugin/issues/50
>
> Neither is listed on the compatibility page.
>
> On Tuesday, 31 May 2016 12:12:46 UTC+1, Daniel Beck wrote:
>>
>> Check the snippet generator if those types appear there for the 'General 
>> Step'. If they don't, they cannot be used that way, as they're not 
>> implementing the required API (SimpleBuildStep in this case). 
>>
>> Also, 
>> https://github.com/jenkinsci/pipeline-plugin/blob/master/COMPATIBILITY.md 
>>
>>
>> > On 26.05.2016, at 19:46, Nicholas Brown  wrote: 
>> > 
>> > I'm trying to get to grips with defining a workflow pipeline. I tried 
>> adding a step with: 
>> > 
>> > step([$class: 'hudson.plugins.sloccount.SloccountPublisher', pattern: '
>> sloccount.sc', encoding: 'UTF-8', commentIsCode: false, 
>> numBuildsInGraph: 0, ignoreBuildFailure: false]) 
>> > 
>> > but it fails with this error: 
>> > 
>> > java.lang.IllegalArgumentException: argument type mismatch 
>> > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
>> Method) 
>> > at 
>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
>>  
>>
>> > at 
>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>>  
>>
>> > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) 
>> > at 
>> org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:193)
>>  
>>
>> > at 
>> org.jenkinsci.plugins.workflow.steps.StepDescriptor.newInstance(StepDescriptor.java:104)
>>  
>>
>> > at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:134) 
>> > at 
>> org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:113)
>>  
>>
>> > at groovy.lang.GroovyObject$invokeMethod.call(Unknown Source) 
>> > 
>> > The following step, using a similar publisher plugin also fails with a 
>> similar cryptic error: 
>> > 
>> > step([$class: 'hudson.plugins.cobertura.CoberturaPublisher', 
>> coberturaReportFile: 'coverage.xml']) 
>> > 
>> > Can anyone suggest what's wrong? Should it be possible to use these 
>> publisher plugins from a pipeline in this way? 
>> > 
>> > Cheers, 
>> > Nick 
>> > 
>> > 
>> > -- 
>> > 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/a8ae6cec-cdb1-480f-b67d-ca2ef85fab46%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/909e990d-b3a9-4924-9c28-47bfc2d64e10%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Remove build triggers section

[Davi Diório Mendes]

Hi everyone,

I am working with gearman serving multiples jenkins master.
The team's architect asked me a way remove build triggers section of 
jenkins projects, in order to let a gearman client trigger the jobs.

I searched a lot and found nothing. Does someone know a plugin to this, or 
knows if it is programatically possible by a groovy script or even a new 
plugin?

BR.

-- 
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/c90ed9dc-a385-43d8-b4f4-1cdc64770ba2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Publisher plugins crash in workflow pipeline

[Nicholas Brown]

I've also raised https://issues.jenkins-ci.org/browse/JENKINS-32524

On Tuesday, 31 May 2016 14:05:01 UTC+1, Nicholas Brown wrote:
>
> Your correct:
>
> Neither of them implement this interface:
>
> https://github.com/jenkinsci/sloccount-plugin/blob/master/src/main/java/hudson/plugins/sloccount/SloccountPublisher.java#L30
>
> https://github.com/jenkinsci/cobertura-plugin/blob/master/src/main/java/hudson/plugins/cobertura/CoberturaPublisher.java#L53
>
> while for example the xunit plugin does:
>
> https://github.com/jenkinsci/xunit-plugin/blob/master/src/main/java/org/jenkinsci/plugins/xunit/XUnitPublisher.java#L63
>
> I found the following issue tracking this for cobertua:
> https://github.com/jenkinsci/cobertura-plugin/issues/50
>
> Neither is listed on the compatibility page.
>
> On Tuesday, 31 May 2016 12:12:46 UTC+1, Daniel Beck wrote:
>>
>> Check the snippet generator if those types appear there for the 'General 
>> Step'. If they don't, they cannot be used that way, as they're not 
>> implementing the required API (SimpleBuildStep in this case). 
>>
>> Also, 
>> https://github.com/jenkinsci/pipeline-plugin/blob/master/COMPATIBILITY.md 
>>
>>
>> > On 26.05.2016, at 19:46, Nicholas Brown  wrote: 
>> > 
>> > I'm trying to get to grips with defining a workflow pipeline. I tried 
>> adding a step with: 
>> > 
>> > step([$class: 'hudson.plugins.sloccount.SloccountPublisher', pattern: '
>> sloccount.sc', encoding: 'UTF-8', commentIsCode: false, 
>> numBuildsInGraph: 0, ignoreBuildFailure: false]) 
>> > 
>> > but it fails with this error: 
>> > 
>> > java.lang.IllegalArgumentException: argument type mismatch 
>> > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
>> Method) 
>> > at 
>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
>>  
>>
>> > at 
>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>>  
>>
>> > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) 
>> > at 
>> org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:193)
>>  
>>
>> > at 
>> org.jenkinsci.plugins.workflow.steps.StepDescriptor.newInstance(StepDescriptor.java:104)
>>  
>>
>> > at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:134) 
>> > at 
>> org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:113)
>>  
>>
>> > at groovy.lang.GroovyObject$invokeMethod.call(Unknown Source) 
>> > 
>> > The following step, using a similar publisher plugin also fails with a 
>> similar cryptic error: 
>> > 
>> > step([$class: 'hudson.plugins.cobertura.CoberturaPublisher', 
>> coberturaReportFile: 'coverage.xml']) 
>> > 
>> > Can anyone suggest what's wrong? Should it be possible to use these 
>> publisher plugins from a pipeline in this way? 
>> > 
>> > Cheers, 
>> > Nick 
>> > 
>> > 
>> > -- 
>> > 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/a8ae6cec-cdb1-480f-b67d-ca2ef85fab46%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/f4f1fa8b-80dc-49d0-98ca-067553cc7f50%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Publisher plugins crash in workflow pipeline

[Nicholas Brown]

Your correct:

Neither of them implement this interface:
https://github.com/jenkinsci/sloccount-plugin/blob/master/src/main/java/hudson/plugins/sloccount/SloccountPublisher.java#L30
https://github.com/jenkinsci/cobertura-plugin/blob/master/src/main/java/hudson/plugins/cobertura/CoberturaPublisher.java#L53

while for example the xunit plugin does:
https://github.com/jenkinsci/xunit-plugin/blob/master/src/main/java/org/jenkinsci/plugins/xunit/XUnitPublisher.java#L63

I found the following issue tracking this for cobertua:
https://github.com/jenkinsci/cobertura-plugin/issues/50

Neither is listed on the compatibility page.

On Tuesday, 31 May 2016 12:12:46 UTC+1, Daniel Beck wrote:
>
> Check the snippet generator if those types appear there for the 'General 
> Step'. If they don't, they cannot be used that way, as they're not 
> implementing the required API (SimpleBuildStep in this case). 
>
> Also, 
> https://github.com/jenkinsci/pipeline-plugin/blob/master/COMPATIBILITY.md 
>
>
> > On 26.05.2016, at 19:46, Nicholas Brown > 
> wrote: 
> > 
> > I'm trying to get to grips with defining a workflow pipeline. I tried 
> adding a step with: 
> > 
> > step([$class: 'hudson.plugins.sloccount.SloccountPublisher', pattern: '
> sloccount.sc', encoding: 'UTF-8', commentIsCode: false, numBuildsInGraph: 
> 0, ignoreBuildFailure: false]) 
> > 
> > but it fails with this error: 
> > 
> > java.lang.IllegalArgumentException: argument type mismatch 
> > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) 
> > at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
>  
>
> > at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>  
>
> > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) 
> > at 
> org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:193)
>  
>
> > at 
> org.jenkinsci.plugins.workflow.steps.StepDescriptor.newInstance(StepDescriptor.java:104)
>  
>
> > at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:134) 
> > at 
> org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:113) 
>
> > at groovy.lang.GroovyObject$invokeMethod.call(Unknown Source) 
> > 
> > The following step, using a similar publisher plugin also fails with a 
> similar cryptic error: 
> > 
> > step([$class: 'hudson.plugins.cobertura.CoberturaPublisher', 
> coberturaReportFile: 'coverage.xml']) 
> > 
> > Can anyone suggest what's wrong? Should it be possible to use these 
> publisher plugins from a pipeline in this way? 
> > 
> > Cheers, 
> > Nick 
> > 
> > 
> > -- 
> > 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/a8ae6cec-cdb1-480f-b67d-ca2ef85fab46%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/35adb457-f018-48b3-b16a-7aa65cfa77f8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: deployment of multiple git branches

[Tomáš Bohuněk]

I would like to deploy and run each jar file for each feature branch. 

Project is written in Java and JavaScript. Jar file is built by maven. I 
need to deploy somehow to one machine each of jar built from each feature 
branch.


On Tuesday, May 31, 2016 at 1:55:21 PM UTC+2, Mark Waite wrote:
>
> I think you'll need to provide more details about the problem you're 
> trying to solve, and the languages you're using to solve it.  For example, 
> since you mentioned that you're deploying to tomcat, are you writing in 
> Java or some other JRE supported language (like Scala)?
>
> Are you building your jar with maven, gradle, ant, or some other build 
> tool?
>
> Mark Waite
>
> On Tue, May 31, 2016 at 5:46 AM Tomáš Bohuněk  > wrote:
>
>> Sorry for mistake. You are right. I have one single git repository (one 
>> project) with a few feature branches.
>>
>>
>> On Tuesday, May 31, 2016 at 1:44:19 PM UTC+2, Mark Waite wrote:
>>
>>> Could you explain further what you mean by "multiple git repository 
>>> (one project with few feature branches)"?
>>>
>>> The phrase "multiple git repository" seems to be in conflict with the 
>>> phrase "one project".  I typically place a project in a single git 
>>> repository with a few feature branches as necessary.  Can you describe more 
>>> about why you need multiple git repositories?
>>>
>>> Thanks,
>>> Mark Waite
>>>
>>> On Tue, May 31, 2016 at 5:04 AM Tomáš Bohuněk  wrote:
>>>
>> What do you recommend for deployment of multiple git repository (one 
 project with few feature branches). Final artifact is JAR with bundled 
 Tomcat application server. I usually run this JAR in Docker container. 
 What 
 do you prefer?

 -- 
 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/911cbd52-c307-486d-b0bd-339ea40b8200%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-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/a5cf009f-289a-4945-ac5c-00fb6f52568e%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/ef93b121-e7e9-4591-aa2a-e31f57c49b32%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: deployment of multiple git branches

[Mark Waite]

I think you'll need to provide more details about the problem you're trying
to solve, and the languages you're using to solve it.  For example, since
you mentioned that you're deploying to tomcat, are you writing in Java or
some other JRE supported language (like Scala)?

Are you building your jar with maven, gradle, ant, or some other build tool?

Mark Waite

On Tue, May 31, 2016 at 5:46 AM Tomáš Bohuněk  wrote:

> Sorry for mistake. You are right. I have one single git repository (one
> project) with a few feature branches.
>
>
> On Tuesday, May 31, 2016 at 1:44:19 PM UTC+2, Mark Waite wrote:
>
>> Could you explain further what you mean by "multiple git repository (one
>> project with few feature branches)"?
>>
>> The phrase "multiple git repository" seems to be in conflict with the
>> phrase "one project".  I typically place a project in a single git
>> repository with a few feature branches as necessary.  Can you describe more
>> about why you need multiple git repositories?
>>
>> Thanks,
>> Mark Waite
>>
>> On Tue, May 31, 2016 at 5:04 AM Tomáš Bohuněk  wrote:
>>
> What do you recommend for deployment of multiple git repository (one
>>> project with few feature branches). Final artifact is JAR with bundled
>>> Tomcat application server. I usually run this JAR in Docker container. What
>>> do you prefer?
>>>
>>> --
>>> 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/911cbd52-c307-486d-b0bd-339ea40b8200%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/a5cf009f-289a-4945-ac5c-00fb6f52568e%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/CAO49JtHTzrs%2BGt24qAHUM%3D681NgzYJSmLhf-6Um1HA%3Dn6kYzjw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: deployment of multiple git branches

[Tomáš Bohuněk]

Sorry for mistake. You are right. I have one single git repository (one 
project) with a few feature branches.

On Tuesday, May 31, 2016 at 1:44:19 PM UTC+2, Mark Waite wrote:
>
> Could you explain further what you mean by "multiple git repository (one 
> project with few feature branches)"?
>
> The phrase "multiple git repository" seems to be in conflict with the 
> phrase "one project".  I typically place a project in a single git 
> repository with a few feature branches as necessary.  Can you describe more 
> about why you need multiple git repositories?
>
> Thanks,
> Mark Waite
>
> On Tue, May 31, 2016 at 5:04 AM Tomáš Bohuněk  > wrote:
>
>> What do you recommend for deployment of multiple git repository (one 
>> project with few feature branches). Final artifact is JAR with bundled 
>> Tomcat application server. I usually run this JAR in Docker container. What 
>> do you prefer?
>>
>> -- 
>> 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/911cbd52-c307-486d-b0bd-339ea40b8200%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/a5cf009f-289a-4945-ac5c-00fb6f52568e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: deployment of multiple git branches

[Mark Waite]

Could you explain further what you mean by "multiple git repository (one
project with few feature branches)"?

The phrase "multiple git repository" seems to be in conflict with the
phrase "one project".  I typically place a project in a single git
repository with a few feature branches as necessary.  Can you describe more
about why you need multiple git repositories?

Thanks,
Mark Waite

On Tue, May 31, 2016 at 5:04 AM Tomáš Bohuněk  wrote:

> What do you recommend for deployment of multiple git repository (one
> project with few feature branches). Final artifact is JAR with bundled
> Tomcat application server. I usually run this JAR in Docker container. What
> do you prefer?
>
> --
> 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/911cbd52-c307-486d-b0bd-339ea40b8200%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/CAO49JtFdU9%2Btn5xMka2_GHuW8MY5R6r3RUH-0-4%2Bdy4M2g2aBw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Violations cause a java.lang.IllegalStateException: cannot change build result while in COMPLETED

[Amedee Van Gasse]

I also have this error in Jenkins 2.7

On Tuesday, October 14, 2014 at 7:05:57 PM UTC+2, llaumgui wrote:
>
> Hi,
>
> with Jenkins 1.584 and Violations plugin 0.7.11, when I build my project 
> on Jenkins, I have a successfull build, but a IllegalStateException caused 
> by Violations plugins cause a fail:
> INFO: 
> 
> INFO: EXECUTION SUCCESS
> INFO: 
> 
> Total time: 25.044s
> Final Memory: 17M/621M
> INFO: 
> 
> ERROR: Processing failed due to a bug in the code. Please report this to 
> jenkinsci-users@googlegroups.com
> java.lang.IllegalStateException: cannot change build result while in 
> COMPLETED
> at hudson.model.Run.setResult(Run.java:453)
> at hudson.plugins.violations.ViolationsReport.setBuildResult(
> ViolationsReport.java:542)
> at hudson.plugins.violations.hudson.maven.ViolationsMavenReporter.end(
> ViolationsMavenReporter.java:100)
> at hudson.maven.AbstractMavenBuilder.end(AbstractMavenBuilder.java:103
> )
> at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun
> (MavenModuleSetBuild.java:846)
> at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild
> .java:533)
> at hudson.model.Run.execute(Run.java:1754)
> at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529)
> at hudson.model.ResourceController.execute(ResourceController.java:89)
> at hudson.model.Executor.run(Executor.java:240)
> project=hudson.maven.MavenModuleSet@20ef6b76[blabla.services.core]
> project.getModules()=[hudson.maven.MavenModule@3ae75e2d[blabla.services.
> core/com.blabla.blabla:services.core][blabla.services.core/com.blabla.
> blabla:services.core][relativePath:]]
> project.getRootModule()=hudson.maven.MavenModule@3ae75e2d[blabla.services.
> core/com.blabla.blabla:services.core][blabla.services.core/com.blabla.
> blabla:services.core][relativePath:]
> FATAL: cannot change build result while in COMPLETED
> java.lang.IllegalStateException: cannot change build result while in 
> COMPLETED
> at hudson.model.Run.setResult(Run.java:453)
> at hudson.plugins.violations.ViolationsReport.setBuildResult(
> ViolationsReport.java:542)
> at hudson.plugins.violations.hudson.maven.ViolationsMavenReporter.end(
> ViolationsMavenReporter.java:100)
> at hudson.maven.AbstractMavenBuilder.end(AbstractMavenBuilder.java:103
> )
> at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun
> (MavenModuleSetBuild.java:846)
> at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild
> .java:533)
> at hudson.model.Run.execute(Run.java:1754)
> at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529)
> at hudson.model.ResourceController.execute(ResourceController.java:89)
> at hudson.model.Executor.run(Executor.java:240)
>
> Have you some idea ?
>
> Thx.
>

-- 
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/41078e45-eab9-40f5-a96b-e3fd67fa128d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline Global Library vars file naming convention

[Sverre Moe]

Well if it is a bug. I was not entirely sure as I have just begun using 
Pipeline.
I will create a bug report of this problem.

tirsdag 31. mai 2016 12.55.59 UTC+2 skrev Daniel Beck følgende:
>
>
> > On 31.05.2016, at 12:01, Sverre Moe > 
> wrote: 
> > 
> > This naming does not work: 
> > vars/packageInformation.groovy 
> > 
> > I get the following exception when calling a function 
> packageInformation.init() 
> > java.lang.NullPointerException: Cannot invoke method init() on null 
> object 
> > 
> > This works 
> > vars/packageinformation.groovy 
> > 
>
> Bug reports should go into JIRA: 
> https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue 
>
>

-- 
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/15440b57-4f2f-4594-99a1-c06a765ab36d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Stable version of Jenkins and the Robot Framework Plugin?

[Daniel Beck]

> On 27.05.2016, at 17:54, developer.go...@gmail.com wrote:
> 
> 1.651.2 LTS and 1.6.4, the report and log files cannot be opened from within 
> Jenkins. Does anyone know of a stable release that in the 1.6X series or the 
> 2.X series that works with the current robot framework plugin?

Probably caused by: 
https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-12-09

See 
https://wiki.jenkins-ci.org/display/JENKINS/Configuring+Content+Security+Policy 
for workarounds.

-- 
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/5DD4EC2D-22E4-4BD2-8A95-A25335E05F53%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: How can i store ne information and/or file in the build folder ?

[Daniel Beck]

> On 27.05.2016, at 16:11, Lionel Hubeau  wrote:
> 
>  For your information, the created files are not part of the deployable 
> artifacts but are only files containing some informations about the build 
> wich were excuted.
>  How can i do this task ? 

You can still archive them as build artifacts.

-- 
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/7682CACD-3C0F-4C81-93E9-3429FA5BA6BC%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Publisher plugins crash in workflow pipeline

[Daniel Beck]

Check the snippet generator if those types appear there for the 'General Step'. 
If they don't, they cannot be used that way, as they're not implementing the 
required API (SimpleBuildStep in this case).

Also, https://github.com/jenkinsci/pipeline-plugin/blob/master/COMPATIBILITY.md


> On 26.05.2016, at 19:46, Nicholas Brown  wrote:
> 
> I'm trying to get to grips with defining a workflow pipeline. I tried adding 
> a step with:
> 
> step([$class: 'hudson.plugins.sloccount.SloccountPublisher', pattern: 
> 'sloccount.sc', encoding: 'UTF-8', commentIsCode: false, numBuildsInGraph: 0, 
> ignoreBuildFailure: false])
> 
> but it fails with this error:
> 
> java.lang.IllegalArgumentException: argument type mismatch 
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) 
> at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
>  
> at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>  
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526) 
> at 
> org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:193)
> at 
> org.jenkinsci.plugins.workflow.steps.StepDescriptor.newInstance(StepDescriptor.java:104)
> at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:134)
> at 
> org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:113)
> at groovy.lang.GroovyObject$invokeMethod.call(Unknown Source)
> 
> The following step, using a similar publisher plugin also fails with a 
> similar cryptic error:
> 
> step([$class: 'hudson.plugins.cobertura.CoberturaPublisher', 
> coberturaReportFile: 'coverage.xml'])
> 
> Can anyone suggest what's wrong? Should it be possible to use these publisher 
> plugins from a pipeline in this way?
> 
> Cheers,
> Nick
> 
> 
> -- 
> 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/a8ae6cec-cdb1-480f-b67d-ca2ef85fab46%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/10425E74-6EE2-489A-B1C1-5C152C474955%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Running a pipeline job on all the nodes with the same label

[Daniel Beck]

> On 26.05.2016, at 15:44, Michael Pereira  wrote:
> 
> With a few modifications it should do the job, but it is still a lot of code. 
> I'm dreaming about things like:
> node(label='slave', run_on_all_matching_nodes=true) {
> // some block
> }
> Is this even possible?

Pipeline global lib should allow you to define a function that does this, for 
reuse in all your build scripts.

https://github.com/jenkinsci/workflow-cps-global-lib-plugin#pipeline-global-library

-- 
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/5260CF07-FAE6-44E2-8F30-FE5C7746CCB7%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: maven projects become slow after a couple of months

[Daniel Beck]

Is there a workspace-private local Maven repository? Maybe repository 
operations (up to date check?) take long…

I think for Maven jobs, you should be able to see internal state (current 
threads' stacks?) in the Jenkins UI.

> On 30.05.2016, at 10:14, Jorg Heymans  wrote:
> 
> Interestingly, executing offline with -o makes the problem disappear. But 
> this is obviously not a solution for me..
> 
> Jorg
> 
> On Monday, May 30, 2016 at 9:52:04 AM UTC+2, Jorg Heymans wrote:
> Sadly there is no additional debug output being emitted during the 'scanning 
> for projects' phase, with -X set.
> 
> 00:00:10.329 
> [DEBUG] Reading user settings from C:\.m2\settings.xml
> 
> 00:00:10.378 
> [INFO] Scanning for projects...
> 
> 00:00:56.941 
> [INFO]
>  
> 
> 00:00:56.950 [INFO] 
> 
> 
> 
> Also tried increasing heap and perm size, does not change anything. Is there 
> an easy way to attach a profiler during a maven build ? 
> 
> Jorg
> 
> On Sunday, May 29, 2016 at 12:12:36 PM UTC+2, Jorg Heymans wrote:
> Good point! Trying this and will report back ...
> 
> -- 
> 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/77bdb41c-a14d-412b-94ac-6ebb005e918b%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/731C3786-B74A-4E84-93DA-2268DC0002D6%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Maven projects ending with

[Daniel Beck]

> On 30.05.2016, at 10:06, chnik...@gmail.com wrote:
> 
> Please advice since this is blocking our production.

Could this be caused by the security update, and you're relying on an 
undeclared build parameter here?

https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-05-11

-- 
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/C8F15F3E-37FF-488B-AB04-5DF0067426A8%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Exporting evironment variables from Groovy script doesn't work

[Daniel Beck]

> On 30.05.2016, at 10:18, chnik...@gmail.com wrote:
> 
> We are currently using Jenkins version 2.7.
> After upgrading from 1.647, we have the problem that environment variables 
> created in a Groovy script are not exported and visible in a following shell 
> script.
> The projects are Maven-based.

https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-05-11

-- 
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/1F1E3B6F-9F3A-470C-A88E-E735DCBB0FD8%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

deployment of multiple git branches

[Tomáš Bohuněk]

What do you recommend for deployment of multiple git repository (one 
project with few feature branches). Final artifact is JAR with bundled 
Tomcat application server. I usually run this JAR in Docker container. What 
do you prefer?

-- 
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/911cbd52-c307-486d-b0bd-339ea40b8200%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Global Tool Configuration crash in Jenkins 2.6 latest global tool config

[Daniel Beck]

> On 30.05.2016, at 20:20, Warren Postma  wrote:
> 
> Appears to be fixed in 2.7.

Looks like a Slack Plugin issue, probably 
https://github.com/jenkinsci/slack-plugin/issues/191

-- 
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/CBBC888C-E2FE-47B2-B042-F48202A1F8A3%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Proxy and certificate

[Daniel Beck]

> On 26.05.2016, at 16:46, sebastienjfoss...@free.fr wrote:
> 
> The "Test URL" was "http://jenkins-ci.org/"; ; there is no problem for 
> accessing this URL in brower with same proxy configuration.

Could be Oracle Java not accepting letsencrypt certificates, while all modern 
browsers do.

-- 
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/59255956-67D9-4C53-9FE8-7439EAC89DEB%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline Global Library vars file naming convention

[Daniel Beck]

> On 31.05.2016, at 12:01, Sverre Moe  wrote:
> 
> This naming does not work:
> vars/packageInformation.groovy
> 
> I get the following exception when calling a function 
> packageInformation.init()
> java.lang.NullPointerException: Cannot invoke method init() on null object
> 
> This works
> vars/packageinformation.groovy
> 

Bug reports should go into JIRA:
https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue

-- 
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/FEAE3639-EF7F-4517-97C1-FFBC2C0837DB%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins 2.7 - How to list all files in a directory

[Daniel Beck]

> On 30.05.2016, at 19:43, Kristian  wrote:
> 
> for f in $(ls *.c); do

Also, this is wrong. `for f in *.c` does the same thing, but has fewer bugs 
(spaces in file names etc.)

-- 
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/3125D878-F22E-4DDC-9AE8-0E5AF7D0DED8%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Pipeline Global Library vars file naming convention

[Sverre Moe]

This naming does not work:
vars/packageInformation.groovy

I get the following exception when calling a function 
packageInformation.init()
java.lang.NullPointerException: Cannot invoke method init() on null object

This works
vars/packageinformation.groovy

According to the instructions/tutorial on GitHub 
 the files 
should be camelCased.
The vars directory hosts scripts that define global variables accessible 
from Pipeline scripts. The basename of each*.groovy file should be a Groovy 
(~ Java) identifier, conventionally camelCased.


-- 
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/c67e6a2a-a52e-4a16-8453-aa84ede0e386%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins 2.7 - How to list all files in a directory

[Daniel Beck]

> On 30.05.2016, at 19:43, Kristian  wrote:
> 
> Is this a bug? Are there any workarounds?

Looks like there are no such files and then the shell does not glob. Look for 
'nullglob' in `man bash`.

-- 
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/1B35079C-3745-42F6-982A-82463B9D1C4E%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

j_acegi_security_check is not accessible

[Jarno Hämäläinen]

Dear Jenkins users

I installed latest Jenkins of the Ubuntu 16.04 machine as instructed 
in https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+on+Ubuntu
I got it running (sudo service jenkins start) and I'm able to open it by 
browsing http://:8080

The problem I'm facing is that when I configure Global Security to use Jenkins’ 
own user database and I try to add users, I found out that if I'm trying to 
log in the browsers 
requests http://:8080/j_acegi_security_check that does not 
respond at all.
E.g. Chrome says 'This site can’t be reached'

Any ideas what is wrong?

The Jenkins version is 1.651.2

-- Jarno

-- 
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/b44bfd7b-a5e5-455b-acdf-9c71f39ed3b1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Unable to anonymously clone a Jenkins scriptler repository

[Daniel Beck]

> On 26.05.2016, at 00:00, Mark Eggers  wrote:
> 
> So I'm missing something in my upgrade from 1.656 to 2.x?
> 

Wild guess -- your security configuration changed between releases, now 
anonymous doesn't have the relevant permissions anymore.

-- 
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/788C9CF4-9545-477B-BE81-8DDBC223AA13%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Error after upgrade: Prime size must be multiple of 64

[Peter Marcoen]

I have created the following 
ticket: https://issues.jenkins-ci.org/browse/JENKINS-35231

Op dinsdag 31 mei 2016 10:03:20 UTC+2 schreef Peter Marcoen:
>
> After some more research I found out that the Jenkins upgrade from 2.1 to 
> 2.7 was not the cause of the problem.
> The cause is the upgrade of the Publish Over SSH 
>  plugin 
> from 1.13 to 1.14.
>
> Op maandag 30 mei 2016 10:17:25 UTC+2 schreef Peter Marcoen:
>>
>> When updating from v2.1 to v2.7, I all of a sudden get the following 
>> error when using "Send build artifacts over SSH":
>>
>> ERROR: Exception when publishing, exception message [Failed to connect 
>> session for config [*my-server-name*]. Message [Session.connect: 
>> java.security.InvalidAlgorithmParameterException: Prime size must be 
>> multiple of 64, and can only range from 512 to 1024 (inclusive)]]
>>
>> I have configured this SSH server with user root, remote directory '/' and 
>> password authentication without a key.
>>
>> When I google this error I only get responses regarding the programming of 
>> SSH clients, no mention of a misconfiguration of some kind.
>>
>>
>> Does anyone know if this is a bug? And if so, if there is a work around?
>>
>>

-- 
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/7bbb1b8b-04c9-442e-ba58-5c520ac3d85d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Error after upgrade: Prime size must be multiple of 64

[Peter Marcoen]

After some more research I found out that the Jenkins upgrade from 2.1 to 
2.7 was not the cause of the problem.
The cause is the upgrade of the Publish Over SSH 
 plugin 
from 1.13 to 1.14.

Op maandag 30 mei 2016 10:17:25 UTC+2 schreef Peter Marcoen:
>
> When updating from v2.1 to v2.7, I all of a sudden get the following error 
> when using "Send build artifacts over SSH":
>
> ERROR: Exception when publishing, exception message [Failed to connect 
> session for config [*my-server-name*]. Message [Session.connect: 
> java.security.InvalidAlgorithmParameterException: Prime size must be multiple 
> of 64, and can only range from 512 to 1024 (inclusive)]]
>
> I have configured this SSH server with user root, remote directory '/' and 
> password authentication without a key.
>
> When I google this error I only get responses regarding the programming of 
> SSH clients, no mention of a misconfiguration of some kind.
>
>
> Does anyone know if this is a bug? And if so, if there is a work around?
>
>

-- 
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/0b9a9d1f-b64e-4574-8ff8-79e7098e4a7e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Multi-Branch project with svn externals

[Lars Meynberg]

I've created a BUG now: https://issues.jenkins-ci.org/browse/JENKINS-35227

Am Montag, 2. Mai 2016 16:11:51 UTC+2 schrieb Lars Meynberg:
>
> We have setup a multi-branch project with a Jenkinsfile. The detection is 
> working fine but we're using external links for some stuff and everytime 
> when the projects start it fails with an authentication error:
>
> org.tmatesoft.svn.core.SVNCancelException 
> :
>  svn: E200015: authentication cancelled
>
>
> In the single pipeline script it works because we have setup 
> ignoreExternals like this:
>  checkout scm: [$class: "SubversionSCM", locations: [[remote: '*',
> clean: true, local: '.', ignoreExternalsOption: 
> false]]]
>
>
> but as the Jenkinsfile has only checkout sum I'm not able to add this 
> setup to it. Or needs this to be setup in the config of the multi-branch 
> project? But there is only the option for the remote url and nothing else.
>
> So I'm grateful for any tipps to solve the authentication problems (All 
> found issue we're solved by bugfixes in the past and seems not related) or 
> to add the ignoreExternalsOption to the multi-branch project.
>
> Kind regards Lars
>

-- 
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/1c3c69e5-c689-4f87-9adc-ff67f3bac827%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.