RE: Build not triggered when change is pushed to bitbucket

[Vladimir Zak]

Hello,

I use the mask plugin and standard mercurial plugin for bitbucket. Polling is 
working without any problem. I do not use webhook, it is not necessary.

But maybe your problem could be in proxy if you are behind it. If yes, I would 
suggest to add proxy to the connection of hg.

Here is my setting for connecting to bitbucket.

I hope it will help you.

Vladimir





From: slide.o@gmail.com
Date: Thu, 21 Jan 2016 16:07:21 +
Subject: Re: Build not triggered when change is pushed to bitbucket
To: jenkinsci-users@googlegroups.com

Perhaps it would help if you gave some more information about your 
configuration, things you have tried, exact error messages, etc. Your request 
is somewhat lacking in that regard.

On Thu, Jan 21, 2016, 08:44 Rohit Sharma  wrote:
Hello Everyone,
I am using the jenkins version 1.625.3. And i am facing issues in integrating 
jenkins with bitbucket. What all i need to do is to trigger a job when a change 
is pushed to bitbucket. But unfortunately its not working and I am continuously 
getting the 500 error response code on webhook configured on bitbucket.Please 
help me out in this.
ThanksRohit




-- 

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/9f9a6a3d-c504-45c4-8239-79d129ee3e6a%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/CAPiUgVei-upXz0sX_93WRZj9C-bUPW%2BV8KF%2BST_KSciaDe8z0Q%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.
  

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

Re: git-plugin test cases running 5+ minutes

[Mark Waite]

Those are the tests as they currently exist in the git plugin.  I generally
find that the git plugin tests need 15-20 minutes to run on an SSD equipped
Linux machine.  Windows machines with an SSD generally need 20-30 minutes
to run all the tests.

I've generally accepted slower development in hopes of releasing fewer bugs
with new versions of the plugin.

I tend to execute single tests or single test classes from my IDE, and find
the response time reasonable in that case.

Of course, if you can find a way to assess the same conditions with faster
tests, I'd love to have faster tests.

Mark Waite

On Thu, Jan 21, 2016 at 8:01 PM Michael Giroux  wrote:

> I'm attempting to build git-plugin and find that the test cases are taking
> a very long time.  Several of the tests are running 270+ seconds.
>
> Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 270.683
> sec - in hudson.plugins.git.CliGitSCMTriggerRemotePollTest
>
> Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 272.201
> sec - in hudson.plugins.git.CliGitSCMTriggerLocalPollTest
>
> Tests run: 55, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 264.263
> sec - in hudson.plugins.git.GitSCMTest
>
> Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 244.154
> sec - in hudson.plugins.git.JGitSCMTriggerLocalPollTest
>
> Tests run: 20, Failures: 9, Errors: 0, Skipped: 0, Time elapsed: 224.619
> sec <<< FAILURE! - in hudson.plugins.git.JGitSCMTriggerRemotePollTest
>
>
> Should I be configuring something on my local system to allow the tests to
> run faster?
>
> --
> 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/3fb841fb-f48b-4345-8a90-ef195632d905%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/CAO49JtFLABUFG5xCnZdfGveCC1VAPxg8QLNvDq8aiYQq%3D8gnUQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

git-plugin test cases running 5+ minutes

[Michael Giroux]

I'm attempting to build git-plugin and find that the test cases are taking 
a very long time.  Several of the tests are running 270+ seconds.

Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 270.683 
sec - in hudson.plugins.git.CliGitSCMTriggerRemotePollTest

Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 272.201 
sec - in hudson.plugins.git.CliGitSCMTriggerLocalPollTest

Tests run: 55, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 264.263 
sec - in hudson.plugins.git.GitSCMTest

Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 244.154 
sec - in hudson.plugins.git.JGitSCMTriggerLocalPollTest

Tests run: 20, Failures: 9, Errors: 0, Skipped: 0, Time elapsed: 224.619 
sec <<< FAILURE! - in hudson.plugins.git.JGitSCMTriggerRemotePollTest


Should I be configuring something on my local system to allow the tests to 
run faster?

-- 
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/3fb841fb-f48b-4345-8a90-ef195632d905%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

AWS ECS Plugin

[Brandon Wagner]

I'm trying to use the Jenkins AWS EC2 Container Service (ECS) plugin to 
deploy Jenkins Slave Containers for builds. I have an ECS cluster setup, 
and I have it configured in my Jenkins Configuration. Everything appears to 
be good until I try to build a job, restricting to the ecs cloud label I 
setup, and it just comes back with "(pending—
Jenkins-Container-Cloud-456...164 
is
 
offline)" .  

Does anyone know how to fix this, or have suggestions on debugging steps? 

-- 
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/f9bf24d9-a9e3-46f6-8fba-041b3344bdc7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [workflow plugin] use case question

[Craig Rodrigues]

Hi,

Node Label Parameter Plugin version 1.7.1 and higher has my fix and now
works with Workflow.

--
Craig

On Thursday, January 21, 2016, Eric Pyle  wrote:

> I think you would need the NodeLabel Parameter Plugin. And as Craig
> Rodrigues recently posted, that plugin is not yet compatible with Workflow,
> although he has proposed a fix:
>

-- 
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/CAG%3DrPVdXe%3DyUKO3YKdnJ0Y0LqpHyFOwZiWr8yPsnWtQy5tBSmA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: LDAP Read Timeouts

[Ashish Yadav]

Any idea what could be causing these 3 different LDAP errors?

Error 1: org.acegisecurity.ldap.LdapDataAccessException: LdapCallback;LDAP 
response read timed out, timeout used:6ms.; nested exception is 
javax.naming.NamingException: LDAP response read timed out, timeout 
used:6ms.; remaining name ‘'
Error 2: org.acegisecurity.ldap.LdapDataAccessException: Failed to obtain 
InitialDirContext due to unexpected exception; nested exception is 
javax.naming.NamingException: LDAP response read timed out, timeout 
used:3ms.
Error 3: org.acegisecurity.ldap.LdapDataAccessException: LdapCallback;null; 
nested exception is javax.naming.PartialResultException [Root exception is 
javax.naming.NamingException: LDAP response read timed out, timeout 
used:6ms. [Root exception is com.sun.jndi.ldap.LdapReferralException: 
Continuation Reference; remaining name '']; remaining name ‘’]


From: Ashish Yadav mailto:ashish.ya...@firemon.com>>
Reply-To: 
"jenkinsci-users@googlegroups.com" 
mailto:jenkinsci-users@googlegroups.com>>
Date: Wednesday, January 20, 2016 at 3:45 PM
To: "jenkinsci-users@googlegroups.com" 
mailto:jenkinsci-users@googlegroups.com>>
Subject: Re: LDAP Read Timeouts

Additional info…

Case 1: org.acegisecurity.ldap.LdapDataAccessException: LdapCallback;LDAP 
response read timed out, timeout used:6ms.; nested exception is 
javax.naming.NamingException: LDAP response read timed out, timeout 
used:6ms.; remaining name ‘'
Case 2: org.acegisecurity.ldap.LdapDataAccessException: Failed to obtain 
InitialDirContext due to unexpected exception; nested exception is 
javax.naming.NamingException: LDAP response read timed out, timeout 
used:3ms.
Case 3: org.acegisecurity.ldap.LdapDataAccessException: LdapCallback;null; 
nested exception is javax.naming.PartialResultException [Root exception is 
javax.naming.NamingException: LDAP response read timed out, timeout 
used:6ms. [Root exception is com.sun.jndi.ldap.LdapReferralException: 
Continuation Reference; remaining name '']; remaining name ‘']


Looks like 3 different errors/conditions.




Failed to search LDAP for username=ABCD
org.acegisecurity.ldap.LdapDataAccessException: LdapCallback;LDAP response read 
timed out, timeout used:6ms.; nested exception is 
javax.naming.NamingException: LDAP response read timed out, timeout 
used:6ms.; remaining name ''
at 
org.acegisecurity.ldap.LdapTemplate$LdapExceptionTranslator.translate(LdapTemplate.java:295)
at org.acegisecurity.ldap.LdapTemplate.execute(LdapTemplate.java:128)
at 
org.acegisecurity.ldap.LdapTemplate.searchForSingleEntry(LdapTemplate.java:246)
at 
org.acegisecurity.ldap.search.FilterBasedLdapUserSearch.searchForUser(FilterBasedLdapUserSearch.java:119)
at 
hudson.security.LDAPSecurityRealm$LDAPUserDetailsService.loadUserByUsername(LDAPSecurityRealm.java:839)
at 
hudson.security.LDAPSecurityRealm$LDAPUserDetailsService.loadUserByUsername(LDAPSecurityRealm.java:790)
at 
jenkins.security.ImpersonatingUserDetailsService.loadUserByUsername(ImpersonatingUserDetailsService.java:32)
at 
org.acegisecurity.ui.rememberme.TokenBasedRememberMeServices.loadUserDetails(TokenBasedRememberMeServices.java:308)
at 
org.acegisecurity.ui.rememberme.TokenBasedRememberMeServices.autoLogin(TokenBasedRememberMeServices.java:218)
at 
hudson.security.TokenBasedRememberMeServices2.autoLogin(TokenBasedRememberMeServices2.java:128)
at 
org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:104)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
at 
hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:168)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at 
org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at 
hudson.util.CharacterEncodingFilter.doFilter(Charact

WARNING: Caught exception evaluating: h.getRelativeLinkTo(job)

[SamL]

Hello Folks getting the following warning each time I open a job 
configuration:

Core 1.6.25.1
OS: Ubuntu 14.04


WARNING: Caught exception evaluating: h.getRelativeLinkTo(job) in 
/view/M2/job/WAPI_GenerateBranchInfo/configure. Reason: 
java.lang.NullPointerException
java.lang.NullPointerException
at hudson.Functions.getRelativeLinkTo(Functions.java:1054)
at sun.reflect.GeneratedMethodAccessor131.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258)
at 
org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104)
at 
org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)
at 
org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)
at 
org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51)
at 
org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)
.
.
.
.



Does anyone know what causes this issue?
Is there a work around?

Thanks in advanced

-- 
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/27862060-e72b-4e75-b076-c6e1fd509818%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [workflow plugin] use case question

[Eric Pyle]

I think you would need the NodeLabel Parameter Plugin. And as Craig 
Rodrigues recently posted, that plugin is not yet compatible with 
Workflow, although he has proposed a fix:


==
*Re: [workflow-plugin] Example using NodeLabel Parameter plugin?*

It turns out that the NodeLabel Parameter plugin doesn't work with the 
workflow plugin:

https://issues.jenkins-ci.org/browse/JENKINS-32209

I submitted this fix:

https://github.com/jenkinsci/nodelabelparameter-plugin/pull/10

--
Craig
===

On 1/21/2016 11:53 AM, Patrick Bruneton wrote:

No because I would have to restrict the jobs on a particular slaves.
I have many windows slaves.
If job 'build' gets executed on windows-slave-1 I want the 'test' to 
be executed on the same slave (and be executed immediately)


Le jeudi 21 janvier 2016 17:21:33 UTC+1, Brian Ray a écrit :

Can you just set the *Restrict where this project can be run*
checkbox in conjunction with the *Label Expression* param on the
two subjobs?

On Thursday, January 21, 2016 at 2:16:39 AM UTC-8, Patrick
Bruneton wrote:

Hi all,

I am trying to implement a use case with the workflow plugin.
I have two jobs, say build & test, that I want to run inside a
pipeline. Sounds easy.
But I have a constraint:I want the two jobs to executed on the
same slave.
So I tried something like this:

|
node('windows'){
   stage name:'Build',concurrency:1
   build 'build'
   stage name:'Test',concurrency:1
   build 'test'
}
|


But 'build' and 'test' are executed in their own slave, which
is not the one allocated by 'node'. That seems logical.
Is there a way to force the builds to run a node?

I understand I could(/should) write the job logic directly in
the pipeline, e.g.

|
node('windows'){
   stage name:'Build',concurrency:1
// build stage details
   stage name: 'Test', concurrency: 1
   // test stage details
}
|

However, I am not sure I can do this, because my jobs exist
already, and use plugins that do not seem to be supported by
workflow (e.g. xUnit, Extended Email)

Any thought?

Thanks,
Patrick

--
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/413e8e29-f03c-406d-b1d1-7a8cc7964ee7%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/56A1310F.8010609%40cd-adapco.com.
For more options, visit https://groups.google.com/d/optout.

Re: [workflow plugin] stage concurrency

[R. Tyler Croy]

(replies inline)

On Thu, 21 Jan 2016, Patrick Bruneton wrote:

> Hi all,
> 
> I tried a very simple workflow with a stage running a job, and concurrency 
> set to 2:
> 
> node('windows') {
>stage name: 'Build', concurrency: 2
>build 'build'
> }
> 
> 
> I have allowed the job 'build' to have multiple runs in parallel (works 
> fine if I trigger the jobs manually multiple times).
> However, if I trigger my workflow multiple times, executions of the job 
> 'build' are serialized where I expect to have two runs in parallel.


First things first, I'm assuming there are at least two nodes in the cluster
with the 'windows' label right?


That said, it's probably better to put the stage *ahead* of the node
allocation, that way you won't end up allocating 10 nodes but only executing
the build two at a time.


Past that, I'm not sure what might not be working


> Did I miss something? Or is it a know issue?
> 
> Thanks for your help,
> Patrick
> 
> -- 
> 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/477f5cf8-3b54-4ddc-8ff4-4630f2825ff4%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.


- R. Tyler Croy

--
 Code: 
  Chatter: 

  % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
--

-- 
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/20160121175531.GV2753%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Digital signature

Re: [theme] New Jenkins Material Design Theme

[Slide]

I really like this theme, nice work!

On Thu, Jan 21, 2016 at 10:17 AM Afonso F  wrote:

> Hi guys,
>
> I created a Jenkins theme based on Google Material Design. It changes the
> layout and icons using SVG ones. Take a look!
>
> http://afonsof.com/jenkins-material-theme/
>
>
> 
> 
> 
>
>
>
>
>
> --
> 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/e1a3564b-cd21-4acc-b74b-645cddfd1902%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/CAPiUgVcCLNubvcptFsVXNaJp92ar9bWv_5%2BUCd_BWEbd3szk3A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[theme] New Jenkins Material Design Theme

[Afonso F]

Hi guys,

I created a Jenkins theme based on Google Material Design. It changes the 
layout and icons using SVG ones. Take a look!

http://afonsof.com/jenkins-material-theme/


 

 






-- 
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/e1a3564b-cd21-4acc-b74b-645cddfd1902%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [workflow plugin] use case question

[Patrick Bruneton]

No because I would have to restrict the jobs on a particular slaves.
I have many windows slaves.
If job 'build' gets executed on windows-slave-1 I want the 'test' to be 
executed on the same slave (and be executed immediately)

Le jeudi 21 janvier 2016 17:21:33 UTC+1, Brian Ray a écrit :
>
> Can you just set the *Restrict where this project can be run* checkbox in 
> conjunction with the *Label Expression* param on the two subjobs?
>
> On Thursday, January 21, 2016 at 2:16:39 AM UTC-8, Patrick Bruneton wrote:
>>
>> Hi all,
>>
>> I am trying to implement a use case with the workflow plugin.
>> I have two jobs, say build & test, that I want to run inside a pipeline. 
>> Sounds easy.
>> But I have a constraint:I want the two jobs to executed on the same slave.
>> So I tried something like this:
>>
>> node('windows') {
>>stage name: 'Build', concurrency: 1
>>build 'build'
>>stage name: 'Test', concurrency: 1
>>build 'test'
>> }
>>
>>
>> But 'build' and 'test' are executed in their own slave, which is not the 
>> one allocated by 'node'. That seems logical.
>> Is there a way to force the builds to run a node?
>>
>> I understand I could(/should) write the job logic directly in the 
>> pipeline, e.g.
>>
>> node('windows') {
>>stage name: 'Build', concurrency: 1
>>// build stage details
>>stage name: 'Test', concurrency: 1
>>// test stage details
>> }
>>
>> However, I am not sure I can do this, because my jobs exist already, and 
>> use plugins that do not seem to be supported by workflow (e.g. xUnit, 
>> Extended Email)
>>
>> Any thought?
>>
>> Thanks,
>> Patrick
>>
>

-- 
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/413e8e29-f03c-406d-b1d1-7a8cc7964ee7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to configure Maven Installation via Groovy

[Антон Юшков]

Useful for me:
import jenkins.model.*

a=Jenkins.instance.getExtensionList(hudson.tasks.Maven.DescriptorImpl.class
)[0];
b=(a.installations as List);
b.add(new hudson.tasks.Maven.MavenInstallation("MAVEN", "/usr/local/maven", 
[]));
a.installations=b
a.save()



On Friday, January 9, 2015 at 2:08:17 AM UTC+4, Kenneth Baltrinic wrote:
>
> I am trying to build a chef recipe to deploy/manage our Jenkins instances. 
>  Things are going reasonably well but the ops-code Jenkin cookbook only 
> provides some basic configuration recipes. It does give you a resource by 
> which to run groovy scripts though and with that and the help of a few 
> blogs I have gotten some basic stuff set up.  However, now now I am trying 
> to do something quite simple in the UI but am stumped about how to do this 
> with a groovy script: Set up a Maven installation that installs a specific 
> version automatically.
>
> Here is what I think I have figured out so far:
>
>
> *import jenkins.model.**
>
> *def inst = Jenkins.getInstance()*
> *def desc = inst.getDescriptor('hudson.tasks.Maven')*
> *def installs = desc.getInstallations()*
>
> installs in this case seems to have the list of existing installs, but I 
> cannot figure out how to programatically add an install to it, for instance 
> I would like to add an installation that is named 'mvn-3-0-5' that 
> automatically installs maven v 3.0.5.
>
> Any idea on how I can do this?  Any help will be much appreciated.  Thanks.
>
> --Ken
>
>

-- 
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/6b4218ec-2008-490b-9b45-c1f283879219%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins Upgrade Installation Constraints and Risks

[Nia Hunter]

Good morning, I have two basic questions. I am not sure if this is the 
correct group for these questions, if not please let me know where to pose 
these questions.

We are using Jenkins as a stand-alone application on our UNIX server.

1. Other than Java 7 and above, are there any System Requirements or 
Environmental constraints associated with upgrading from a much older 
version of Jenkins to the latest? For example, we are using Version 1.423 
and would like to go to at least Version 1.638, but preferably the latest. 
Is there a patch required when doing an upgrade from such an old version?

2. Are there any general risks associated with upgrading from an older 
version to a newer version?

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/8afcd1af-840f-4d05-b72e-afcc8a57600f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [workflow plugin] use case question

[Brian Ray]

Can you just set the *Restrict where this project can be run* checkbox in 
conjunction with the *Label Expression* param on the two subjobs?

On Thursday, January 21, 2016 at 2:16:39 AM UTC-8, Patrick Bruneton wrote:
>
> Hi all,
>
> I am trying to implement a use case with the workflow plugin.
> I have two jobs, say build & test, that I want to run inside a pipeline. 
> Sounds easy.
> But I have a constraint:I want the two jobs to executed on the same slave.
> So I tried something like this:
>
> node('windows') {
>stage name: 'Build', concurrency: 1
>build 'build'
>stage name: 'Test', concurrency: 1
>build 'test'
> }
>
>
> But 'build' and 'test' are executed in their own slave, which is not the 
> one allocated by 'node'. That seems logical.
> Is there a way to force the builds to run a node?
>
> I understand I could(/should) write the job logic directly in the 
> pipeline, e.g.
>
> node('windows') {
>stage name: 'Build', concurrency: 1
>// build stage details
>stage name: 'Test', concurrency: 1
>// test stage details
> }
>
> However, I am not sure I can do this, because my jobs exist already, and 
> use plugins that do not seem to be supported by workflow (e.g. xUnit, 
> Extended Email)
>
> Any thought?
>
> Thanks,
> Patrick
>

-- 
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/ecced7f3-ac77-4698-8837-2fb609822094%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Version Number Plugin does not work when job is running more then once

[Andrew Novinger]

I have a Jenkins job that is using the Version Number Plugin to change the 
build label in Jenkins to show the environment name and job number.

This job is not throttle so it can run many times concurrently for 
different environments.

The issue I am having is the first environment that is run, the label gets 
update and is correct, the next job that is running while the first job is 
running.  We get a null pointer exception thrown (see below), and the 
Jenkins label does not change.  

ERROR: java.lang.NullPointerExceptionjava.lang.NullPointerException 
  
at 
org.jvnet.hudson.tools.versionnumber.VersionNumberBuilder.incBuild(VersionNumberBuilder.java:262)
 

at 
org.jvnet.hudson.tools.versionnumber.VersionNumberBuilder.setUp(VersionNumberBuilder.java:540)
 

at hudson.model.Build$BuildExecution.doRun(Build.java:156) 

at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) 

at hudson.model.Run.execute(Run.java:1738) 

at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 

at hudson.model.ResourceController.execute(ResourceController.java:98) 

at hudson.model.Executor.run(Executor.java:410) 


Any ideas on how to make this plugin work on a job that can run concurrently?


-- 
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/41c4eebd-8df9-4af9-8ca3-67e042db0f7a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Build not triggered when change is pushed to bitbucket

[Slide]

Perhaps it would help if you gave some more information about your
configuration, things you have tried, exact error messages, etc. Your
request is somewhat lacking in that regard.

On Thu, Jan 21, 2016, 08:44 Rohit Sharma 
wrote:

> Hello Everyone,
>
> I am using the jenkins version 1.625.3. And i am facing issues in
> integrating jenkins with bitbucket. What all i need to do is to trigger a
> job when a change is pushed to bitbucket. But unfortunately its not working
> and I am continuously getting the 500 error response code on webhook
> configured on bitbucket.
> Please help me out in this.
>
> Thanks
> Rohit
>
> --
> 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/9f9a6a3d-c504-45c4-8239-79d129ee3e6a%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/CAPiUgVei-upXz0sX_93WRZj9C-bUPW%2BV8KF%2BST_KSciaDe8z0Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Build not triggered when change is pushed to bitbucket

[Rohit Sharma]

Hello Everyone,

I am using the jenkins version 1.625.3. And i am facing issues in 
integrating jenkins with bitbucket. What all i need to do is to trigger a 
job when a change is pushed to bitbucket. But unfortunately its not working 
and I am continuously getting the 500 error response code on webhook 
configured on bitbucket.
Please help me out in this.

Thanks
Rohit

-- 
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/9f9a6a3d-c504-45c4-8239-79d129ee3e6a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins CI server with Unity / TFS VSO - First time user

[mragon]

Hi,

I am trying to configure Jenkins as a CI server using Unity and TFS Visual 
Studio Online. This is my first time of trying to configure anything like 
this and was wondering if anyone could point me in the right direction? 
>From my attempts to far I don't seem to be able to authenticate with TFS 
VSO and get the following error...

"FATAL: com.microsoft.tfs.core.exceptions.TECoreException: Invalid 
authority" - I have added alternative logon credentials to my Visual Studio 
account.

I have installed Jenkins on a Server 2012 R2 machine and installed the 
Unity, TFS and MS Build plugins.

Thanks,

Mark



-- 
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/0aad4969-30bb-4b51-ba47-9a3b81449553%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Exception when I try to trigger buildflow job from workflow job

[EK]

Hi , 


I am facing the following error , we recently moved to workflow and when we 
try to run\trigger old build flow jobs from workflow jobs we get exception:

Stacktrace of exception is as below , appreciate if anyone can help\advice on 
this and how we can overcome the issue ? 


Best Regards

EK


FATAL: Cannot cast object 'MyWorkFlowJobName #3' with class 
'org.jenkinsci.plugins.workflow.job.WorkflowRun' to class 
'hudson.model.AbstractBuild'org.codehaus.groovy.runtime.typehandling.GroovyCastException
 
:
 Cannot cast object 'MyWorkFlowJobName #3' with class 
'org.jenkinsci.plugins.workflow.job.WorkflowRun' to class 
'hudson.model.AbstractBuild'
at 
org.codehaus.groovy.runtime.typehandling.DefaultTypeTransformation.castToType(DefaultTypeTransformation.java:360)
 

at 
org.codehaus.groovy.runtime.ScriptBytecodeAdapter.castToType(ScriptBytecodeAdapter.java:599)
 

at 
com.cloudbees.plugins.flow.FlowDSL$_executeFlowScript_closure1.doCall(FlowDSL.groovy:55)
 

at sun.reflect.GeneratedMethodAccessor1187.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at 
org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)
at 
org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:272)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:903)
at groovy.lang.Closure.call(Closure.java:415)
at groovy.lang.Closure.call(Closure.java:428)
at 
org.codehaus.groovy.runtime.DefaultGroovyMethods.each(DefaultGroovyMethods.java:1379)
at 
org.codehaus.groovy.runtime.DefaultGroovyMethods.each(DefaultGroovyMethods.java:1351)
at org.codehaus.groovy.runtime.DefaultGroovyMethods$each.call(Unknown 
Source)
at 
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
at org.codehaus.groovy.runtime.DefaultGroovyMethods$each.call(Unknown 
Source)
at 
com.cloudbees.groovy.cps.CpsDefaultGroovyMethods.each(CpsDefaultGroovyMethods.groovy:26)
at sun.reflect.GeneratedMethodAccessor941.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at 
org.codehaus.groovy.runtime.metaclass.ReflectionMetaMethod.invoke(ReflectionMetaMethod.java:51)
at 
org.codehaus.groovy.runtime.metaclass.NewInstanceMetaMethod.invoke(NewInstanceMetaMethod.java:54)
at 
org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoMetaMethodSiteNoUnwrapNoCoerce.invoke(PojoMetaMethodSite.java:271)
at 
org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMetaMethodSite.java:53)
at 
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116)
at 
com.cloudbees.plugins.flow.FlowDSL.executeFlowScript(FlowDSL.groovy:52)
at 
com.cloudbees.plugins.flow.FlowRun$FlyweightTaskRunnerImpl.run(FlowRun.java:219)
at hudson.model.Run.execute(Run.java:1738)
at com.cloudbees.plugins.flow.FlowRun.run(FlowRun.java:155)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)

-- 
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/c8322a8f-c743-4d51-9047-8a472942c5ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

"somecommand".execute()

[Niksan]

When running a process on a slave using execute system groovy, what's the 
correct way to syncronise so a wait() can be performed on the process?

def proc = "dir".execute()
synchronized (proc) { 
   proc.consumeProcessOutput(out, out)
   proc.wait();
}

this just waits forever and not synchronising causes and exception.

-- 
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/64e99f96-a409-42db-940d-5bca578378a6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Send email with Expiration date from Jenkins

[Sinai Rijkov]

Hi. Thank you. 
added just one line to Pre-send Script and it worked for me: 

import jenkins.*;
import hudson.model.*;
import jenkins.model.*;

*msg.setHeader('Expiry-Date', 'Fri, 22 Jan 2016 18:00:00 +0200');*

*...*


On Wednesday, January 20, 2016 at 2:44:32 PM UTC+2, slide wrote:
>
> The easiest way to do this would be to use a presend script and add the 
> header there on the msg object, which is an instance of MimeMessage. You 
> can look at the docs for that and the presend script feature in email-ext 
> to determine what you need to do.
>
> On Wed, Jan 20, 2016, 02:30 Sinai Rijkov > 
> wrote:
>
>> Hi,
>>  I need to use Expiration date,when I'm sending email from plugin.
>>
>>
>>
>> I've found ,that i can use some plugin,where we can edit headers - 
>> *Email-ext 
>> plugin*
>> How I can use Email-ext plugin for Jenkins and add custom header, like 
>> Expiration date? 
>>
>> But any moresuggestions will be welcome. :)
>>
>>
>>
>>
>> Example: 
>>
>> Expiry-Date:  header. 
>>  
>> sendmail from CentOS: 
>>
>>
>> echo -e "Content-Type: text/plain\r\nExpiry-Date: Fri, 20 Jan 2010 
>> 18:00:00 +0200 From: jen...@mycompany.com \r\
>> nSubject: Test\r\n\r\nTest with expiration for tomorrow 20 Jan 2016" | 
>> sendmail -f sen...@gmail.com   desti...@gmail.com 
>> 
>>
>>
>> So at Outlook you can see like this: 
>>
>>
>>
>> [image: Inline image 1]
>>
>> -- 
>> 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/213adcaa-4c61-4bee-8b5b-906eb65682ae%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/29b87e08-361f-4bc9-8ef4-1b0b1c604020%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[workflow plugin] use case question

[Patrick Bruneton]

Hi all,

I am trying to implement a use case with the workflow plugin.
I have two jobs, say build & test, that I want to run inside a pipeline. 
Sounds easy.
But I have a constraint:I want the two jobs to executed on the same slave.
So I tried something like this:

node('windows') {
   stage name: 'Build', concurrency: 1
   build 'build'
   stage name: 'Test', concurrency: 1
   build 'test'
}


But 'build' and 'test' are executed in their own slave, which is not the 
one allocated by 'node'. That seems logical.
Is there a way to force the builds to run a node?

I understand I could(/should) write the job logic directly in the pipeline, 
e.g.

node('windows') {
   stage name: 'Build', concurrency: 1
   // build stage details
   stage name: 'Test', concurrency: 1
   // test stage details
}

However, I am not sure I can do this, because my jobs exist already, and 
use plugins that do not seem to be supported by workflow (e.g. xUnit, 
Extended Email)

Any thought?

Thanks,
Patrick

-- 
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/098bab82-0336-468f-8aa5-415b6e457a57%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[workflow plugin] stage concurrency

[Patrick Bruneton]

Hi all,

I tried a very simple workflow with a stage running a job, and concurrency 
set to 2:

node('windows') {
   stage name: 'Build', concurrency: 2
   build 'build'
}


I have allowed the job 'build' to have multiple runs in parallel (works 
fine if I trigger the jobs manually multiple times).
However, if I trigger my workflow multiple times, executions of the job 
'build' are serialized where I expect to have two runs in parallel.

Did I miss something? Or is it a know issue?

Thanks for your help,
Patrick

-- 
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/477f5cf8-3b54-4ddc-8ff4-4630f2825ff4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.