Older jenkins versions removed?

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

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

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

Re: git clone error

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

view Jenkins configuration

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

lastSuccessful / lastFailed - how to stop these being updated?

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

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

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

queue.xml is not persisted

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

LDAP Read Timeouts

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

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

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,

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:

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

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

Re: nodelabel plugin and groovy

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

Re: git clone error

I attached the logs - (I removed the repository url) Job with default timeout: Cloning the remote Git repository Cloning repository . .. > git init >

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

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

Send email with Expiration date from Jenkins

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. :)

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

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

Re: git clone error

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

Re: nodelabel plugin and groovy

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

Re: Workflow (pipeline) visual editor

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:

Re: nodelabel plugin and groovy

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.

RE: Jenkins P4 plugin problem

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

Re: Send email with Expiration date from Jenkins

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

Re: git clone error

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

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

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

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

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

Re: git clone error

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

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

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