Older jenkins versions removed?

[Eero Arvonen]

Was there some sort of a christmas clean-up of older Jenkins-versions? I 
need to install an old version of Jenkins, 1.517 specifically, for red hat 
but everything older than 1.597 seems to have been removed even if it's 
listed right here: http://pkg.jenkins-ci.org/redhat/

Can anyone tell me where I could find the rpm I need?

Best regards,
Eero Arvonen

-- 
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/43624679-9e84-43ac-b491-dfc3c5174ce7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Configuring Specflow scenarios tags running in CI (Jenkins)

[Victor Martinez]

Hi Ana,

 Do you use any build scripts? If so, as long as that logic is part of the 
script itself you can easily run those commands in Jenkins. Other than 
that, I don't see any other way of doing it.

Cheers

On Thursday, 14 January 2016 08:58:10 UTC, Ana Sousa wrote:
>
> Hi all, 
>
> I have a lot of specflow feature files in my .Net code with loads of 
> scenarios for each feature file. 
> I'm putting some tags in the scenarios in order to categorize my tests and 
> only run sub-sets of the tests. My tags are as simple as @smoke 
> @integration @regression @critical.
>
> I was wondering if someone knows a way to configure CI (jenkins) in order 
> to run only the "smoke" or "critical" or "integration" tags.
>
> Thank you for your help.
>
> Best regards,
> Ana
>

-- 
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/dc51aa0d-ed89-43c9-b319-7c57921fe784%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: git clone error

[Klaus Schniedergers]

If you're dealing with a flaky origin repository, the "SCM checkout retry
count" configuration comes in very handy.
It's in the main Jenkins configuration screen.

On Wed, Jan 20, 2016 at 5:56 AM, Mark Waite 
wrote:

> If it is a large repository, and if you don't mind keeping an extra copy
> on your slave, you might consider using the "reference repository" option.
> That allows you to place a bare copy of the git repository on your slave
> and reference its contents rather than copying them over the network.  It
> saves network time and can save disc space if you have multiple jobs
> cloning the same original repository.
>
> Mark Waite
>
> On Wed, Jan 20, 2016 at 6:28 AM Victor Martinez <
> victormartinezru...@gmail.com> wrote:
>
>> Timeout issue as you can see
>>
>> *09:40:08* ERROR: Timeout after 20 minutes
>>
>>
>>
>> You can set that value as you probably did  it since the default timeout
>> is 10 minutes. Probably some networking latency issue in your system so you
>> can bypass it with a longer timeout.
>>
>> Cheers
>>
>> On Wednesday, 20 January 2016 08:44:31 UTC, GS_L wrote:
>>>
>>> I attached the logs - (I removed the repository url)
>>>
>>>
>>> Job with default timeout:
>>>
>>> Cloning the remote Git repository
>>> Cloning repository . ..
>>>  > git init 
>>> /var/lib/jenkins/jobs/NightlyBuild-3.4/workspace/dir_clis/build_cli_centos_final/cloudify-cli
>>>  # timeout=10
>>> Fetching upstream changes from . 
>>> ..
>>>  > git --version # timeout=10
>>>  > git -c core.askpass=true fetch --tags --progress . 
>>> .. 
>>> +refs/heads/*:refs/remotes/origin/*
>>> ERROR: Timeout after 10 minutesERROR 
>>> : Error cloning remote 
>>> repo 'origin'hudson.plugins.git.GitException 
>>> :
>>>  Command "git -c core.askpass=true fetch --tags --progress . 
>>> .. 
>>> +refs/heads/*:refs/remotes/origin/*" returned status code 143:
>>> stdout:
>>> stderr: remote: Counting objects: 8354, done.
>>> remote: Compressing objects:   2% (1/38)
>>> remote: Compressing objects:   5% (2/38)
>>> remote: Compressing objects:   7% (3/38)
>>> remote: Compressing objects:  10% (4/38)
>>>
>>>
>>> Job with 20 minutes timeout:
>>>
>>> *9:20:08* Cloning the remote Git repository
>>>
>>> *09:20:08* Cloning repository ...*09:20:08*  > git init 
>>> /var/lib/jenkins/jobs/dir_admin/jobs/sync_xap-openspaces/workspace/xap # 
>>> timeout=10*09:20:08* Fetching upstream changes from ...*09:20:08*  > git 
>>> --version # timeout=10*09:20:08*  > git -c core.askpass=true fetch --tags 
>>> --progress ... +refs/heads/*:refs/remotes/origin/* # timeout=20*09:40:08* 
>>> ERROR: Timeout after 20 minutes*09:40:08* ERROR 
>>> : Error cloning remote 
>>> repo 'origin'*09:40:08* hudson.plugins.git.GitException 
>>> :
>>>  Command "git -c core.askpass=true fetch --tags --progress ... 
>>> +refs/heads/*:refs/remotes/origin/*" returned status code 143:*09:40:08* 
>>> stdout: *09:40:08* stderr: remote: Counting objects: 1192544, done. 
>>> [K*09:40:08* remote: Compressing objects:   0% (1/337)[K
>>> remote: Compressing objects:   1% (4/337)[K
>>> remote: Compressing objects:   2% (7/337)[K
>>> remote: Compressing objects:   3% (11/337)[K
>>> remote: Compressing objects:   4% (14/337)[K
>>> remote: Compressing objects:   5% (17/337)[K
>>>
>>> remote: Compressing objects:   6% (21/337)[K
>>>
>>>
>>> On Wednesday, January 20, 2016 at 10:18:29 AM UTC+2, Victor Martinez
>>> wrote:

 Correct me if I'm wrong but those log details are not enough, can you
 attach your full console log? Probably there is something else after that
 error in the stacktrace error output. It might be related to some timeout
 issues...

 Cheers

 On Tuesday, 19 January 2016 14:17:34 UTC, GS_L wrote:
>
> I'm using jenkins 1.631 on ubuntu 14.04, slaves installed also on
> ubuntu 14.04.
> I added git path to PATH env variable.
> git plugins:
> Git client plugin 1.19.1
> Git plugin 2.4.1
> GitHub API Plugin 1.71
> GitHub plugin 1.14.2
>
> Sometimes I get the following error: "ERROR: Error cloning remote repo
> 'origin'"
> hudson.plugins.git.GitException: Command "git -c core.askpass=true
> fetch --tags --progress ... +refs/heads/*:refs/remotes/origin/*" returned
> status code 143:
> It's happen on master and slaves as well.
>
> Most of the builds success but everyday some of the builds fail on
> this error.
> I looked over the posts with the same problem 

view Jenkins configuration

[Eric Naitove]

Is there a way to retrieve all the system configuration via api or groovy. 
 Such as all Maven definitions, Ant definitions, JDK's 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/19ca7736-5667-4019-9575-872db8852eec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

lastSuccessful / lastFailed - how to stop these being updated?

[Niksan]

As the subject says, in concurrent builds, as the linking is non atomic, 
depending how many jobs you have running you get exceptions because 
multiple instances try to do the same operation.

As with some if not most concurrent jobs, a last successful / failed makes 
no sense, so is there anyway to disable this per job?

-- 
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/1f938dbc-e5b8-481f-a591-3a00936b9d5b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Configuring Specflow scenarios tags running in CI (Jenkins)

[André Carmo]

Hi Ana,

Sure it is possible, but it will depend on the test runner you are using 
with Specflow(NUnit, MSTest, Specflow+ Runner, ConsoleUnitTestRunner, and 
so on). Check your App.config file, and search for the "unitTestProvider" 
key.

Then you will need to configure your Jenkins job to call the test runner 
using the correct parameters. For example, if you are using NUnit you can 
use something like this, you can use a batch command:
nunit-console myassembly.dll */include:Smoke*

It would be easier to help if you could tell us what do you have right now. 
Do you already have your Jenkins job configured? Can you run all your tests 
in Jenkins? 

Regards,
André

quinta-feira, 14 de Janeiro de 2016 às 08:58:10 UTC, Ana Sousa escreveu:
>
> Hi all, 
>
> I have a lot of specflow feature files in my .Net code with loads of 
> scenarios for each feature file. 
> I'm putting some tags in the scenarios in order to categorize my tests and 
> only run sub-sets of the tests. My tags are as simple as @smoke 
> @integration @regression @critical.
>
> I was wondering if someone knows a way to configure CI (jenkins) in order 
> to run only the "smoke" or "critical" or "integration" tags.
>
> Thank you for your help.
>
> Best regards,
> Ana
>

-- 
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/1287eb32-f8ce-4ed3-a8ef-20d537a72465%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

queue.xml is not persisted

[André Carmo]

Hi.

I just upgraded to Jenkins 1.644 and the queue.xml file is not persisted. 
This causes me to lose all queue items after a restart (using 
/safeRestart). I was using v.1637 it this happened too. Even after a fresh 
install on another machine the problem exists. I already checked log files 
for any relevant information but I can't find any. I also checked 
permissions and everything seems to be ok. Is there any configuration I 
need to make? I don't see anyone complaining about this.

I was able to reproduce this problem using Windows 7 and Windows Server 
2012.

Thank you very much

-- 
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/a4ec454f-11c1-4378-b3ae-6c4c810c2d8a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

LDAP Read Timeouts

[Ashish Yadav]

I am running Jenkins version 1.609.3 with LDAP plugin version 1.11

Lately, I have been seeing these errors in the logs.


Jan 20, 2016 1:57:27 PM WARNING 
hudson.security.LDAPSecurityRealm$LDAPUserDetailsService loadUserByUsername

Failed to search LDAP for username=ABCD
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 '']
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(CharacterEncodingFilter.java:81)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at 
org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474)
at 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499)
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
at 
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533)
at 
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)
at 
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086)
at 
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428)
at 
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)
at 
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020)
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
at org.eclipse.jetty.server.Server.handle(Server.java:370)
at 
org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489)
at 
org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:949)
at 
org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1011)
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:644)
at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235)
at 

Why doesn't Jenkins authenticate with a key provided on the cli?

[Wayne Werner]

I have Jenkins setup with the Bitbucket OAuth plugin for security.

I'm using SaltStack to setup Jenkins 
, which uses the 
Jenkins CLI jar to interface with Jenkins. Obviously when Jenkins has zero 
security this works jst fine.

However, when I turn on the BitBucket OAuth security, it no longer works.

That SaltStack formula is handy enough to share the command line it uses 
and I can give it a try myself:

$ java -jar /var/cache/jenkins/jenkins-cli.jar -s http://127.0.0.1:8080 
-i /var/lib/jenkins/.ssh/id_rsa reload-configuration
Authentication failed. No private key accepted.

cue sad trombone .

I've added the output of `ssh-keygen -y /var/lib/jenkins.ssh/id_rsa` to my 
user credentials in the Jenkins management screen, but as you can see... 
that doesn't seem to help.

So why doesn't Jenkins authenticate my key, and more importantly, how can I 
get that working?

-- 
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/f6a5f358-3395-4d8a-ae22-c4066e1c643b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: LDAP Read Timeouts

[Ashish Yadav]

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(CharacterEncodingFilter.java:81)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at 
org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474)
at 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499)
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
at 
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533)
at 
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)
at 
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086)
at 
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428)
at 
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)
at 
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020)
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
at 

Re: Git Plugin: updated password now cannot connect to repo

[Jim Klo]

An update... still haven't figured this out entirely but now I'm pretty 
confident there is at least 1 Jenkins bug.

I figured out a way to capture the temporary credentials file.  When I 
looked at this, there were a couple of things that struck me.

1) it contained multiple credentials, both old and new.
2) when changing passwords using Safari 9 browser on a Mac, the credential 
file contained random garbage; i.e. it contained the field help text for 
the password field instead of the password.
3) the password credentials file does not appear to completely URL encode 
the password; characters '{' and '}' were not encoded.

Now if I don't select a credential, and correctly url encode the username & 
password in the SCM Repository URL field... it "works" albeit not exactly 
secure.

Any thoughts on how to fix? Mind you that this all works fine using the 
same entered credentials for SVN and only a problem with GIT.  Also the odd 
thing is that old password contained both '{' and '}' and it worked fine 
for the last year.


On Thursday, January 14, 2016 at 5:11:59 PM UTC-8, Jim Klo wrote:
>
> Hi, 
>
> Over the last few days my password used for Jenkins' Git Plugin expired, 
> of which I promptly updated in Jenkins.
>
> Unfortunately, even with the correct password (which uses the same special 
> characters as the previous password) it won't authenticate, and there 
> doesn't seem to be any other error that what I captured in the attached 
> screen grab.
> The same credentials work with Jenkins SVN Plugin, noting that our SCM 
> uses LDAP.  I can switch to another user's credentials and it work fine, 
> but I cannot seem to get the original login to work.
>
> Not sure what I'm doing wrong.  Is this a bug?  Is there a workaround?  It 
> seems like to me like Git might caching credentials globally, but not sure.
>

-- 
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/f4a11331-c055-4c4d-947e-c8347bbd14c1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: nodelabel plugin and groovy

[Niksan]

The matrix job differs in its workspace layout so doesn't play ball, a square 
peg for a round hole.

-- 
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/3d5511c2-972f-45ed-8d01-1dee13051c38%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: git clone error

[GS_L]

I attached the logs - (I removed the repository url)


Job with default timeout:

Cloning the remote Git repository
Cloning repository . ..
 > git init 
 > /var/lib/jenkins/jobs/NightlyBuild-3.4/workspace/dir_clis/build_cli_centos_final/cloudify-cli
 >  # timeout=10
Fetching upstream changes from . 
..
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress . 
 > .. 
 > +refs/heads/*:refs/remotes/origin/*
ERROR: Timeout after 10 minutesERROR 
: Error cloning remote 
repo 'origin'hudson.plugins.git.GitException 
:
 Command "git -c core.askpass=true fetch --tags --progress . 
.. 
+refs/heads/*:refs/remotes/origin/*" returned status code 143:
stdout: 
stderr: remote: Counting objects: 8354, done.
remote: Compressing objects:   2% (1/38)   
remote: Compressing objects:   5% (2/38)   
remote: Compressing objects:   7% (3/38)   
remote: Compressing objects:  10% (4/38) 


Job with 20 minutes timeout:

*9:20:08* Cloning the remote Git repository

*09:20:08* Cloning repository ...*09:20:08*  > git init 
/var/lib/jenkins/jobs/dir_admin/jobs/sync_xap-openspaces/workspace/xap # 
timeout=10*09:20:08* Fetching upstream changes from ...*09:20:08*  > git 
--version # timeout=10*09:20:08*  > git -c core.askpass=true fetch --tags 
--progress ... +refs/heads/*:refs/remotes/origin/* # timeout=20*09:40:08* 
ERROR: Timeout after 20 minutes*09:40:08* ERROR 
: Error cloning remote 
repo 'origin'*09:40:08* hudson.plugins.git.GitException 
:
 Command "git -c core.askpass=true fetch --tags --progress ... 
+refs/heads/*:refs/remotes/origin/*" returned status code 143:*09:40:08* 
stdout: *09:40:08* stderr: remote: Counting objects: 1192544, done. 
[K*09:40:08* remote: Compressing objects:   0% (1/337)[K
remote: Compressing objects:   1% (4/337)[K
remote: Compressing objects:   2% (7/337)[K
remote: Compressing objects:   3% (11/337)[K
remote: Compressing objects:   4% (14/337)[K
remote: Compressing objects:   5% (17/337)[K

remote: Compressing objects:   6% (21/337)[K  


On Wednesday, January 20, 2016 at 10:18:29 AM UTC+2, Victor Martinez wrote:
>
> Correct me if I'm wrong but those log details are not enough, can you 
> attach your full console log? Probably there is something else after that 
> error in the stacktrace error output. It might be related to some timeout 
> issues...
>
> Cheers
>
> On Tuesday, 19 January 2016 14:17:34 UTC, GS_L wrote:
>>
>> I'm using jenkins 1.631 on ubuntu 14.04, slaves installed also on ubuntu 
>> 14.04.
>> I added git path to PATH env variable.
>> git plugins:
>> Git client plugin 1.19.1
>> Git plugin 2.4.1
>> GitHub API Plugin 1.71
>> GitHub plugin 1.14.2
>>
>> Sometimes I get the following error: "ERROR: Error cloning remote repo 
>> 'origin'"
>> hudson.plugins.git.GitException: Command "git -c core.askpass=true fetch 
>> --tags --progress ... +refs/heads/*:refs/remotes/origin/*" returned status 
>> code 143:
>> It's happen on master and slaves as well.
>>
>> Most of the builds success but everyday some of the builds fail on this 
>> error.
>> I looked over the posts with the same problem but I haven't found a 
>> solution.
>>
>> Please your advice.
>>
>

-- 
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/8920e1a0-38d1-4b8f-a429-99d97cde01e7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

RE: Run job on ALL cloud (i.e. Docker) slaves including a given label

[Vladimir Zak]

Hi,
I set it to our local cloud service a year ago. I would start the images in one 
job and then I use the "3rdparty_all" job to run the things there.
But with Docker I am not much familiar because we are "windows company".
I hope this could help.
Best regards,
Vladimir




Date: Wed, 20 Jan 2016 00:42:06 -0800
From: jule...@googlemail.com
To: jenkinsci-users@googlegroups.com
Subject: Re: Run job on ALL cloud (i.e. Docker) slaves including a given label

Hi Vladimir,
thank you very much for your detailed explanation. I just set up my Jenkins 
according to your screenshots.The problem I am having is, that the Node label 
parameter factory (when given something like docker&) seems to not be 
able to recognize the node labels of unstarted Docker images.I would like to 
have the needed images to be automatically started (and stopped once they are 
finished). I think unstarted images do not even have a real Nodename that can 
be passed as a parameter.
Do you use this setup with Docker or other clouds?
Thanks,Julianus

Am Dienstag, 19. Januar 2016 18:17:59 UTC+1 schrieb zakyn:









Hello,

I just set it without any problem.

You need one job which will trigger the job(s) on all slaves on all nodes with 
given label(s).

3rdparty_all job triggeres 3rdparty job on all nodes which fit "3rdparty" 
labels.

See attachments. I hope it is clear.

Best regards,

Vladimir






Date: Tue, 19 Jan 2016 08:13:43 -0800
From: jul...@googlemail.com
To: jenkins...@googlegroups.com
Subject: Run job on ALL cloud (i.e. Docker) slaves including a given label

Hello everybody,
currently I am desperately looking for a way to create a Jenkins job that, when 
launched, will be executed concurrentlyon ALL slaves matching a label (or 
better a set of labels).Usually (but not exclusively) my slaves will be cloud 
based. That means they should be fired up automatically with the Docker plugin 
of Jenkins.
I tried some different configurations (e.g. Elastic Axis Plugin, Matrix plugin 
[and its label_expressions], Restricting job to certain slaves in its 
configuration) but either it does not work at all or Jenkins will only fire up 
the job on one slave (that matches the label) only.
The method I am looking for should work on labels because I do not want to 
click all the slaves that should be used for a certain job everytime my 
configuration changes (i.e. via a slaves axis).Has anyone found a way of doing 
what I envision?

Your help is highly appreciated.Regards,Julianus




-- 

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/9dfd9ba5-052b-4f23-9a05-fe2ab3ce17c7%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/2650806c-1d4e-47ca-97c5-16b9eec2be59%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/DUB122-W2524D5708BEF0BA2E867D0ACC20%40phx.gbl.
For more options, visit https://groups.google.com/d/optout.

Send email with Expiration date from Jenkins

[Sinai Rijkov]

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: jenk...@mycompany.com \r\
nSubject: Test\r\n\r\nTest with expiration for tomorrow 20 Jan 2016" | 
sendmail -f sen...@gmail.com  destinat...@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-users+unsubscr...@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.

Re: Run job on ALL cloud (i.e. Docker) slaves including a given label

[Julianus Pfeuffer]

Hi Vladimir,

thank you very much for your detailed explanation. I just set up my Jenkins 
according to your screenshots.
The problem I am having is, that the Node label parameter factory (when 
given something like docker&) seems to not be able to recognize 
the node labels of unstarted Docker images.
I would like to have the needed images to be automatically started (and 
stopped once they are finished). I think unstarted images do not even have 
a real Nodename that can be passed as a parameter.

Do you use this setup with Docker or other clouds?

Thanks,
Julianus

Am Dienstag, 19. Januar 2016 18:17:59 UTC+1 schrieb zakyn:
>
>
> Hello,
>
> I just set it without any problem.
>
> You need one job which will trigger the job(s) on all slaves on all nodes 
> with given label(s).
>
> 3rdparty_all job triggeres 3rdparty job on all nodes which fit "3rdparty" 
> labels.
>
> See attachments. I hope it is clear.
>
> Best regards,
>
> Vladimir
>
>
>
>
>
>
> --
> Date: Tue, 19 Jan 2016 08:13:43 -0800
> From: jul...@googlemail.com 
> To: jenkins...@googlegroups.com 
> Subject: Run job on ALL cloud (i.e. Docker) slaves including a given label
>
> Hello everybody,
>
> currently I am desperately looking for a way to create a Jenkins job that, 
> when launched, will be executed concurrently
> on ALL slaves matching a label (or better a set of labels).
> Usually (but not exclusively) my slaves will be cloud based. That means 
> they should be fired up automatically with the Docker plugin of Jenkins.
>
> I tried some different configurations (e.g. Elastic Axis Plugin, Matrix 
> plugin [and its label_expressions], Restricting job to certain slaves in 
> its configuration) but either it does not work at all or Jenkins will only 
> fire up the job on one slave (that matches the label) only.
>
> The method I am looking for should work on labels because I do not want to 
> click all the slaves that should be used for a certain job everytime my 
> configuration changes (i.e. via a slaves axis).
> Has anyone found a way of doing what I envision?
>
> Your help is highly appreciated.
> Regards,
> Julianus
>
> -- 
> 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/9dfd9ba5-052b-4f23-9a05-fe2ab3ce17c7%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/2650806c-1d4e-47ca-97c5-16b9eec2be59%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins P4 plugin problem

[Kenneth Nielsen]

Hi gurus

I am trying to introduce Jenkins at my workplace. We use Perforce as 
version control.
I have installed the p4 plugin. 

My job currently only tries to get the files, and it fails: It appears that 
I cannot login to the version control.
I cannot find where to put the server name for the plugin, that could be 
the problem.
Does anyone have a setup for that Works with the p4 plugin.
And do you have any tips?
thanks


log from build:
8x8x8x8x8x8x
Started by user *anonymous* 
Building in workspace C:\Projects\jenkins
FATAL: null
*java.lang.NullPointerException * 
 
at 
*org.jenkinsci.plugins.p4.client.ConnectionConfig.(ConnectionConfig.java:18)*
 

at 
*org.jenkinsci.plugins.p4.client.ConnectionHelper.(ConnectionHelper.java:71)*
 

at 
*org.jenkinsci.plugins.p4.client.ClientHelper.(ClientHelper.java:67)* 

at 
*org.jenkinsci.plugins.p4.tasks.AbstractTask.getConnection(AbstractTask.java:166)*
 

at 
*org.jenkinsci.plugins.p4.tasks.AbstractTask.setWorkspace(AbstractTask.java:66)*
 

at *org.jenkinsci.plugins.p4.PerforceScm.checkout(PerforceScm.java:262)* 

at *hudson.scm.SCM.checkout(SCM.java:485)* 

at *hudson.model.AbstractProject.checkout(AbstractProject.java:1276)* 

at 
*hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607)*
 

at *jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)* 

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

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)* 

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/31f242dc-9ca2-456a-acad-02bdef77bc27%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: git clone error

[Victor Martinez]

Correct me if I'm wrong but those log details are not enough, can you 
attach your full console log? Probably there is something else after that 
error in the stacktrace error output. It might be related to some timeout 
issues...

Cheers

On Tuesday, 19 January 2016 14:17:34 UTC, GS_L wrote:
>
> I'm using jenkins 1.631 on ubuntu 14.04, slaves installed also on ubuntu 
> 14.04.
> I added git path to PATH env variable.
> git plugins:
> Git client plugin 1.19.1
> Git plugin 2.4.1
> GitHub API Plugin 1.71
> GitHub plugin 1.14.2
>
> Sometimes I get the following error: "ERROR: Error cloning remote repo 
> 'origin'"
> hudson.plugins.git.GitException: Command "git -c core.askpass=true fetch 
> --tags --progress ... +refs/heads/*:refs/remotes/origin/*" returned status 
> code 143:
> It's happen on master and slaves as well.
>
> Most of the builds success but everyday some of the builds fail on this 
> error.
> I looked over the posts with the same problem but I haven't found a 
> solution.
>
> Please your advice.
>

-- 
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/7668eb2d-bae9-4bd7-a7c2-3efc0968bd16%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: nodelabel plugin and groovy

[Victor Martinez]

Hi,

 Have you tried to use the matrix project type? you can run same steps in 
different slaves/labels at the same time.

Cheers

On Tuesday, 19 January 2016 17:35:09 UTC, Niksan wrote:
>
> I'm trying to control where jobs are run from a groovy script, it's an 
> edge case that I have to run on all nodes in a label rather than what's 
> free.  I was hoping I could use the nodelabel plugin to do this.
>
> On my slave job I have a label parameter, named and defaults to my label 
> that a lot of slaves are hooked up to (Distributed_build), I run as run on 
> all nodes matching the label, ignore offline nodes and run regardless of 
> result.
>
> I put a machine in there that's part of the label cluster to see if I 
> could force to a node (Machine_1) so I could visually see the jobs queued 
> for that node rather than using a free node part of the label cluster, but 
> it seems to run all builds on the label cluster regardless. Am I doing 
> something wrong or just assuming incorrectly how the plugin works?
>
>
> In my source job I have the following groovy script.
>
> def nodes = [
>   "Distributed_build",
>   "Distributed_build",
>   "Distributed_build",
>   "Distributed_build",
>   "Distributed_build",
>   "Machine_1",
>   "Machine_1",
>   "Machine_1",
>   "Machine_1"
> ];
>
> def targetJobName = "SuperDuper Job"  
> def jobToTrigger = Jenkins.instance.getItem( targetJobName )  
>
> def i=1
> nodes.each {
>   node ->
> if(jobToTrigger!=null) {
>   def futureJob = jobToTrigger.scheduleBuild( 2, new 
> Cause.UpstreamCause( build ), new ParametersAction( [
> new StringParameterValue( 'Distribution_Label', node ), 
> new StringParameterValue( 'Build_Command_Line', i.toString() ) 
>   ] ) )
>   println(futureJob)
> }
> println(node)
> i++
> }
>
>

-- 
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/45d21b0d-2456-44bb-b35a-a401592a7313%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Workflow (pipeline) visual editor

[Julien GARCIA GONZALEZ]

Awesome! I will love to try it asap on our platform !

Le mercredi 13 janvier 2016 23:35:25 UTC+1, Michael Neale a écrit :
>
> That's great. The workflow generated isn't ideal yet, so that is something 
> to be done. 
>
> On Wednesday, January 13, 2016 at 9:13:42 PM UTC+11, Craig Rodrigues wrote:
>>
>> On Tue, Jan 12, 2016 at 6:12 PM, Michael Neale  
>> wrote:
>>
>>>
>>> In fact Keith Zantow has a react-js version of this editor, which shows 
>>> both the script below with live changes, and is right in the config page: 
>>> https://github.com/kzantow/react-pipeline-editor-plugin 
>>>
>>>
>> I played with that plugin here: 
>> https://twitter.com/rodrigc6/status/687215217646907392
>>
>> Very nice!  The ability to see a graphical view of the workflow and the 
>> code at the same time is very useful.
>>
>> --
>> Craig 
>>
>

-- 
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/f3f35a74-7b64-4233-b7f7-0c31fe8437b5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: nodelabel plugin and groovy

[Niksan]

Parameters matter, the fix is obvious in hindsight. 

new StringParameterValue( 'Distribution_Label', node ), 

should be

new LabelParameterValue( 'Distribution_Label', node ), 

Happy days \o/

-- 
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/d539e743-a456-4a3e-a301-96d8e6960643%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

RE: Jenkins P4 plugin problem

[Ginga, Dick]

Hi Kenneth, we use Jenkins and Perforce. there are actually 2 plugins for 
Perforce. we use this one:

https://wiki.jenkins-ci.org/display/JENKINS/Perforce+Plugin

version 1.3.25

with this plugin, you specify the p4port in each job when you select Perforce 
as the SCM

[cid:image001.png@01D15353.5CD774B0]

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Kenneth Nielsen
Sent: Wednesday, January 20, 2016 4:07 AM
To: Jenkins Users
Subject: Jenkins P4 plugin problem

Hi gurus

I am trying to introduce Jenkins at my workplace. We use Perforce as version 
control.
I have installed the p4 plugin.

My job currently only tries to get the files, and it fails: It appears that I 
cannot login to the version control.
I cannot find where to put the server name for the plugin, that could be the 
problem.
Does anyone have a setup for that Works with the p4 plugin.
And do you have any tips?
thanks


log from build:
8x8x8x8x8x8x
Started by user anonymous
Building in workspace C:\Projects\jenkins
FATAL: null
java.lang.NullPointerException 
 
at 
org.jenkinsci.plugins.p4.client.ConnectionConfig.(ConnectionConfig.java:18)
at 
org.jenkinsci.plugins.p4.client.ConnectionHelper.(ConnectionHelper.java:71)
at 
org.jenkinsci.plugins.p4.client.ClientHelper.(ClientHelper.java:67)
at 
org.jenkinsci.plugins.p4.tasks.AbstractTask.getConnection(AbstractTask.java:166)
at 
org.jenkinsci.plugins.p4.tasks.AbstractTask.setWorkspace(AbstractTask.java:66)
at 
org.jenkinsci.plugins.p4.PerforceScm.checkout(PerforceScm.java:262)
at 
hudson.scm.SCM.checkout(SCM.java:485)
at 
hudson.model.AbstractProject.checkout(AbstractProject.java:1276)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607)
at 
jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
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)
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/31f242dc-9ca2-456a-acad-02bdef77bc27%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/6C6EE445A6F6CE4E8A0FFB51B071A4E2D86B3818%40AMERMBX02.PERKINELMER.NET.
For more options, visit https://groups.google.com/d/optout.

Re: Send email with Expiration date from Jenkins

[Slide]

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: jenk...@mycompany.com \r\
> nSubject: Test\r\n\r\nTest with expiration for tomorrow 20 Jan 2016" |
> sendmail -f sen...@gmail.com  destinat...@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-users+unsubscr...@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/CAPiUgVegdpRtMoEeH%2B0xqvaahUnsXenqu0HKPYnbQBPPdTb33Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: git clone error

[Victor Martinez]

Timeout issue as you can see

*09:40:08* ERROR: Timeout after 20 minutes



You can set that value as you probably did  it since the default timeout is 
10 minutes. Probably some networking latency issue in your system so you 
can bypass it with a longer timeout.

Cheers

On Wednesday, 20 January 2016 08:44:31 UTC, GS_L wrote:
>
> I attached the logs - (I removed the repository url)
>
>
> Job with default timeout:
>
> Cloning the remote Git repository
> Cloning repository . ..
>  > git init 
> /var/lib/jenkins/jobs/NightlyBuild-3.4/workspace/dir_clis/build_cli_centos_final/cloudify-cli
>  # timeout=10
> Fetching upstream changes from . 
> ..
>  > git --version # timeout=10
>  > git -c core.askpass=true fetch --tags --progress . 
> .. 
> +refs/heads/*:refs/remotes/origin/*
> ERROR: Timeout after 10 minutesERROR 
> : Error cloning remote 
> repo 'origin'hudson.plugins.git.GitException 
> :
>  Command "git -c core.askpass=true fetch --tags --progress . 
> .. 
> +refs/heads/*:refs/remotes/origin/*" returned status code 143:
> stdout: 
> stderr: remote: Counting objects: 8354, done.
> remote: Compressing objects:   2% (1/38)   
> remote: Compressing objects:   5% (2/38)   
> remote: Compressing objects:   7% (3/38)   
> remote: Compressing objects:  10% (4/38) 
>
>
> Job with 20 minutes timeout:
>
> *9:20:08* Cloning the remote Git repository
>
> *09:20:08* Cloning repository ...*09:20:08*  > git init 
> /var/lib/jenkins/jobs/dir_admin/jobs/sync_xap-openspaces/workspace/xap # 
> timeout=10*09:20:08* Fetching upstream changes from ...*09:20:08*  > git 
> --version # timeout=10*09:20:08*  > git -c core.askpass=true fetch --tags 
> --progress ... +refs/heads/*:refs/remotes/origin/* # timeout=20*09:40:08* 
> ERROR: Timeout after 20 minutes*09:40:08* ERROR 
> : Error cloning remote 
> repo 'origin'*09:40:08* hudson.plugins.git.GitException 
> :
>  Command "git -c core.askpass=true fetch --tags --progress ... 
> +refs/heads/*:refs/remotes/origin/*" returned status code 143:*09:40:08* 
> stdout: *09:40:08* stderr: remote: Counting objects: 1192544, done. 
> [K*09:40:08* remote: Compressing objects:   0% (1/337)[K
> remote: Compressing objects:   1% (4/337)[K
> remote: Compressing objects:   2% (7/337)[K
> remote: Compressing objects:   3% (11/337)[K
> remote: Compressing objects:   4% (14/337)[K
> remote: Compressing objects:   5% (17/337)[K
>
> remote: Compressing objects:   6% (21/337)[K  
>
>
> On Wednesday, January 20, 2016 at 10:18:29 AM UTC+2, Victor Martinez wrote:
>>
>> Correct me if I'm wrong but those log details are not enough, can you 
>> attach your full console log? Probably there is something else after that 
>> error in the stacktrace error output. It might be related to some timeout 
>> issues...
>>
>> Cheers
>>
>> On Tuesday, 19 January 2016 14:17:34 UTC, GS_L wrote:
>>>
>>> I'm using jenkins 1.631 on ubuntu 14.04, slaves installed also on ubuntu 
>>> 14.04.
>>> I added git path to PATH env variable.
>>> git plugins:
>>> Git client plugin 1.19.1
>>> Git plugin 2.4.1
>>> GitHub API Plugin 1.71
>>> GitHub plugin 1.14.2
>>>
>>> Sometimes I get the following error: "ERROR: Error cloning remote repo 
>>> 'origin'"
>>> hudson.plugins.git.GitException: Command "git -c core.askpass=true fetch 
>>> --tags --progress ... +refs/heads/*:refs/remotes/origin/*" returned status 
>>> code 143:
>>> It's happen on master and slaves as well.
>>>
>>> Most of the builds success but everyday some of the builds fail on this 
>>> error.
>>> I looked over the posts with the same problem but I haven't found a 
>>> solution.
>>>
>>> Please your advice.
>>>
>>

-- 
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/87e5dd63-b984-4e61-a6ce-f00ed5185b53%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Is there a way to fail the build after it's finished?

[Victor Martinez]

Probably you could run the build promotion and some adhoc system groovy 
script to change the status. But using that approach might be dangerous as 
you will use some internal api and will require some knowledge otherwise 
you might break its reliability and consistency.

What if you add an extra step like deploying the war file in a docker 
container/vagrant box and run some smoke tests and if it works then do your 
2. task? 

Then your task pipeline woud be>

   1. One just builds project and saves artifacts (war files).
   2. Deploy war in an isolated container/box and do some test validations
   3. Second copies artifacts of last successful build and deploys them.

Cheers

On Friday, 15 January 2016 12:54:07 UTC, maciej wrote:
>
> That doesn't work. There doesn't seem to be a simple way to promote all 
> sucessfull build automatically (i.e. make them OK by default) and then 
> revoke promotion status (effectively marking it is failed).
>
> So still looking for a way to fail the build on demand (manually).
>
> Eric Pyle (2016-01-13 15:16):
>
> Seems like this could be handled by build promotion? 
>
> On 1/13/2016 8:50 AM, Maciej Jaros wrote:
>
> Hi.
>
> I want to fail one of the builds to be able to mark it as something that 
> should not be deployed.
>
> My setup is that I have two task:
>
>1. One just builds project and saves artifacts (war files). 
>2. Second copies artifacts of last successful build and deploys them.
>
> Occasionally some build passes automatic tests, but then fails after 
> deployment. If I can mark the build as failed, then re-deployment would use 
> older, but working version.
>
> Regards,
> Nux.
> -- 
> 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/56965633.6030301%40mol.com.pl
> .
> 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/6836804e-f6a6-4f9a-a414-f9c3035269a0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to get the list of user views by the api

[Victor Martinez]

You can raise a Jira ticket and ask about that feature since it might not 
be developed yet. and if you somehow need that feature in place as long as 
you raise a jira ticket it would be easy to track it.

Cheers

On Thursday, 14 January 2016 12:56:39 UTC, Yohann Perraud wrote:
>
> Thanks.
>
> I don't understand why this *user* informations are not actually exposed 
> on the /*user* api.
>
> So, I create a new UserProperty called UserViewsProperty (source code in 
> attachment) and integrate it in a plugin.
> This solution required me to create an empty config.jelly for the 
> /user/configure page. My skills on Jenkins core being insufficient, I 
> haven't really understood why.
> When I call the user api, I 've got now a new property called "userViews"
>
> In any case, it works but I'm interested in any comments or another type 
> of solution.
>
> Le mercredi 13 janvier 2016 16:09:35 UTC+1, Daniel Beck a écrit :
>>
>> These are not exposed via the API. The MyViewsProperty is one of the 
>> empty {} in 'property'. 
>>
>> On 13.01.2016, at 15:52, Yohann Perraud  wrote: 
>>
>> > Hi, 
>> > 
>> > Is there a way to retrieve the list of view for a user via the Rest API 
>> ? 
>> > 
>> > I tried /user//my-views/api/json, /user/picadmin/api/json 
>> with differents depth but it never return his views. 
>> > I googled it and I 've found nothing. 
>> > 
>> > Thanks in advance. 
>> > 
>> > Yohann. 
>> > 
>> >   
>> > 
>> > -- 
>> > 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/85cb952a-8012-4ce3-aeb5-e9dd2873dc9b%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/cf555722-04bb-45ca-873d-57353d5a2d99%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: git clone error

[Mark Waite]

If it is a large repository, and if you don't mind keeping an extra copy on
your slave, you might consider using the "reference repository" option.
That allows you to place a bare copy of the git repository on your slave
and reference its contents rather than copying them over the network.  It
saves network time and can save disc space if you have multiple jobs
cloning the same original repository.

Mark Waite

On Wed, Jan 20, 2016 at 6:28 AM Victor Martinez <
victormartinezru...@gmail.com> wrote:

> Timeout issue as you can see
>
> *09:40:08* ERROR: Timeout after 20 minutes
>
>
>
> You can set that value as you probably did  it since the default timeout
> is 10 minutes. Probably some networking latency issue in your system so you
> can bypass it with a longer timeout.
>
> Cheers
>
> On Wednesday, 20 January 2016 08:44:31 UTC, GS_L wrote:
>>
>> I attached the logs - (I removed the repository url)
>>
>>
>> Job with default timeout:
>>
>> Cloning the remote Git repository
>> Cloning repository . ..
>>  > git init 
>> /var/lib/jenkins/jobs/NightlyBuild-3.4/workspace/dir_clis/build_cli_centos_final/cloudify-cli
>>  # timeout=10
>> Fetching upstream changes from . 
>> ..
>>  > git --version # timeout=10
>>  > git -c core.askpass=true fetch --tags --progress . 
>> .. 
>> +refs/heads/*:refs/remotes/origin/*
>> ERROR: Timeout after 10 minutesERROR 
>> : Error cloning remote 
>> repo 'origin'hudson.plugins.git.GitException 
>> :
>>  Command "git -c core.askpass=true fetch --tags --progress . 
>> .. 
>> +refs/heads/*:refs/remotes/origin/*" returned status code 143:
>> stdout:
>> stderr: remote: Counting objects: 8354, done.
>> remote: Compressing objects:   2% (1/38)
>> remote: Compressing objects:   5% (2/38)
>> remote: Compressing objects:   7% (3/38)
>> remote: Compressing objects:  10% (4/38)
>>
>>
>> Job with 20 minutes timeout:
>>
>> *9:20:08* Cloning the remote Git repository
>>
>> *09:20:08* Cloning repository ...*09:20:08*  > git init 
>> /var/lib/jenkins/jobs/dir_admin/jobs/sync_xap-openspaces/workspace/xap # 
>> timeout=10*09:20:08* Fetching upstream changes from ...*09:20:08*  > git 
>> --version # timeout=10*09:20:08*  > git -c core.askpass=true fetch --tags 
>> --progress ... +refs/heads/*:refs/remotes/origin/* # timeout=20*09:40:08* 
>> ERROR: Timeout after 20 minutes*09:40:08* ERROR 
>> : Error cloning remote 
>> repo 'origin'*09:40:08* hudson.plugins.git.GitException 
>> :
>>  Command "git -c core.askpass=true fetch --tags --progress ... 
>> +refs/heads/*:refs/remotes/origin/*" returned status code 143:*09:40:08* 
>> stdout: *09:40:08* stderr: remote: Counting objects: 1192544, done. 
>> [K*09:40:08* remote: Compressing objects:   0% (1/337)[K
>> remote: Compressing objects:   1% (4/337)[K
>> remote: Compressing objects:   2% (7/337)[K
>> remote: Compressing objects:   3% (11/337)[K
>> remote: Compressing objects:   4% (14/337)[K
>> remote: Compressing objects:   5% (17/337)[K
>>
>> remote: Compressing objects:   6% (21/337)[K
>>
>>
>> On Wednesday, January 20, 2016 at 10:18:29 AM UTC+2, Victor Martinez
>> wrote:
>>>
>>> Correct me if I'm wrong but those log details are not enough, can you
>>> attach your full console log? Probably there is something else after that
>>> error in the stacktrace error output. It might be related to some timeout
>>> issues...
>>>
>>> Cheers
>>>
>>> On Tuesday, 19 January 2016 14:17:34 UTC, GS_L wrote:

 I'm using jenkins 1.631 on ubuntu 14.04, slaves installed also on
 ubuntu 14.04.
 I added git path to PATH env variable.
 git plugins:
 Git client plugin 1.19.1
 Git plugin 2.4.1
 GitHub API Plugin 1.71
 GitHub plugin 1.14.2

 Sometimes I get the following error: "ERROR: Error cloning remote repo
 'origin'"
 hudson.plugins.git.GitException: Command "git -c core.askpass=true
 fetch --tags --progress ... +refs/heads/*:refs/remotes/origin/*" returned
 status code 143:
 It's happen on master and slaves as well.

 Most of the builds success but everyday some of the builds fail on this
 error.
 I looked over the posts with the same problem but I haven't found a
 solution.

 Please your advice.

>>> --
> 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
> 

Re: change the build status to NOT_BUILT if a file exists in post build

[Victor Martinez]

Hi,

If I understood correctly you would like to build your branch and have a 
post build action to change the build status only if the file exists, 
didn't  you? If it's a postbuild action a skip action in the jenkins job 
doesn't make sense. Can you elaborate it a bit more? 

Cheers


On Tuesday, 12 January 2016 22:33:41 UTC, Chanukhya Bachina wrote:
>
> I create a file in workspace for a specific type of branch during my 
> compilation. If the file exists I want the change the built status to 
> NOT_BUILT and skip the job.
>
> How can I do it through post build groovy script.
>

-- 
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/6bf07272-e81f-49a5-8df5-37bacdbfa8d5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.