Re: Removing old jobs from Jenkins

Do you know where can I find some documentation for this ? What packages should i import? Thanks, Alex On Sep 18, 2014 11:37 PM, "Eric Pyle" wrote: > Something like this. For safety, I've written this to print out the list > of builds it would delete. Uncomment the delete() line to actually de

Re: Removing old jobs from Jenkins

Do you know where can I find some documentation for this ? What packages should i import? Is it based on java ? Thanks, Alex On Sep 18, 2014 11:37 PM, "Eric Pyle" wrote: > Something like this. For safety, I've written this to print out the list > of builds it would delete. Uncomment the delete(

Re: Shelving old builds

There's the Jenkins Shelve plugin for that, it adds an entry to the menu on the job's page. On Sep 19, 2014 5:46 PM, "alex131290" wrote: > Is there any way the shelve old builds through the Jenkins UI using some > command ? > I found something using the jenkins CLI, but i don't know where to writ

Set build result

Hello everyone. Can't find a way to set build result via HTTP API intead of `java -jar jenkins-cli.jar set-build-result ...`. Is this possible? Thnx -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop rec

Shelving old builds

Is there any way the shelve old builds through the Jenkins UI using some command ? I found something using the jenkins CLI, but i don't know where to write this command in Jenkins i didn't find something that won't delete the builds i need something that will be able to shelve them into a tar file.

Re: calendar parameters in jenkins

up. Any idea ? -- View this message in context: http://jenkins-ci.361315.n4.nabble.com/calendar-parameters-in-jenkins-tp4719502p4719708.html Sent from the Jenkins users mailing list archive at Nabble.com. -- You received this message because you are subscribed to the Google Groups "Jenkins U

[SOLVED] Re: "Processing failed due to a bug in the code"

Problem solved. After updating to the current version (Jenkins + Plugins) everything worked fine. Am Donnerstag, 18. September 2014 14:13:02 UTC+2 schrieb hagen@gmail.com: > > Hello, > > I get the following error since some days from our Jenkins. Any idea what > the problem could be? > > [.

Force SFTP on Exec command in "Send build artifacts over SSH"

Hi List, I'm trying to set up a Job to deploy an website to a hosted server where I only have SFTP access. Uploading the directories and files using "Send build artifacts over SSH" already works. After the upload I would like to create some symlinks in this newly uploaded directory. I added the

Re: Issue with RegEx for project roles in Matrix Authorization Strategy Plugin

If you want to allow that MIB can appear anywhere else other that immmediately after GUIDE_ you can change the regex for : (.*)GUIDE_(?!MIB)((?!P4).)*$ Richard Lavoie > On 2014-09-19, at 06:52, Richard Lavoie wrote: > > As a few people already mentioned you need to anchor your pattern. Otherw

Re: Issue with RegEx for project roles in Matrix Authorization Strategy Plugin

As a few people already mentioned you need to anchor your pattern. Otherwise, .* might match what you want to exclude and attempt the match after it, resulting in an unwanted result. What your regx is doing in words is this: (.*) match anywhere GUIDE_ : normal text match (?!MIB) : immediately n

Re: Issue with RegEx for project roles in Matrix Authorization Strategy Plugin

On 09/19/14 11:44, Jan Seidel wrote: Yay, got it. A set of projects rules. each one containing a positve match and then combine the rule works well. One odd thing I learned is, that you don't need wildcards if your match has a trailing string. e.g. *MB**_GUIDE**_Pxxx_P4**_DELIVERY* wil

Re: Issue with RegEx for project roles in Matrix Authorization Strategy Plugin

On 09/19/14 11:27, Jan Seidel wrote: True (.*) is very greedy, but (?!P4) is a but not P4 and I would expect it to work. It isn't as I just figured out in a test run with a completely different RegEx to skim for other jobs :/ I don't know what kind of regex the Matrix supports, but "X(?!Y)"

Re: Issue with RegEx for project roles in Matrix Authorization Strategy Plugin

Yay, got it. A set of projects rules. each one containing a positve match and then combine the rule works well. One odd thing I learned is, that you don't need wildcards if your match has a trailing string. e.g. *MB**_GUIDE**_Pxxx_P4**_DELIVERY* will also be found when you work with *(.*)G

Re: Issue with RegEx for project roles in Matrix Authorization Strategy Plugin

True (.*) is very greedy, but (?!P4) is a but not P4 and I would expect it to work. It isn't as I just figured out in a test run with a completely different RegEx to skim for other jobs :/ I got to tweak it and create a set of project rules and then combine them for each user depending on what

Re: Expanding Parameters when triggering Jobs

Yeah, that's what I was hoping to avoid. Simply choosing "Use Current Parameters", and have it auto-magically include the evaluated value ... which is not feasible, so I'm trying to do something it's not meant to do. Hence, thread closed ;) On 19 September 2014 02:13, Jan Seidel wrote: > >

Re: Expanding Parameters when triggering Jobs

Ah, I got your point :) use the "Predefined parameters" opton. Then the variables will expand. See picture attached Am Dienstag, 16. September 2014 03:21:03 UTC+2 schrieb Brantone: > > Perhap

Re: Jenkins 1.580 and Windows slave connect

Fixed: was due to a mistake with the use of a reverse proxy. I needed to put the right URL in the jenkins configuration. -- 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

TAP plugin skip test

Hi, I can't seem to be able to generate a tap that marks a test as skip. Does anyone have an example of TAP test file that marks a test as skipped? Thanks, Paulo Matos -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from thi

Re: Issue with RegEx for project roles in Matrix Authorization Strategy Plugin

Hi, I did of course not read the subject. Shame on me. The answer below is for regex in general, not sure how applicable it is to the Matrix Authorization Strategy Plugin (not using it). BR Gunnar On 09/19/14 09:57, Gunnar Strand wrote: Hi Jan, On 09/19/14 09:38, Jan Seidel wrote: Hi all,

Re: Issue with RegEx for project roles in Matrix Authorization Strategy Plugin

Hi Jan, On 09/19/14 09:38, Jan Seidel wrote: Hi all, I have a weird issue with a regular expression. Hopefully you can help me out here. I have a RegEx like *(.*)GUIDE_(?!MIB)(.*)(?!P4)* It should, as far as I can tell, list all jobs containing GUIDE but exclude GUIDE jobs with a MIB in the m

Re: Expanding Parameters when triggering Jobs

"${WORKSPACE}" was a poor example ... how about "${SOME_RANDOM_FOLDER}" .. the point was, when param goes to get passed, it doesn't evaluate any nested parameters, just passes it straight text. On 19 September 2014 00:46, Jan Seidel wrote: > ${WORKSPACE} is dynamic. > Job A and job B have their

How to set "Environment variables" in "Global properties" of global Jenkins configuration programmatically?

Hi! I have some environment variables as List of key-value pairs within the "Global properties" section of the global Jenkins configuration. I wonder if it is possible to change such a environment variables programmatically, for example by means of a Groovy script? Regards, mr -- You received

Re: Expanding Parameters when triggering Jobs

${WORKSPACE} is dynamic. Job A and job B have their own defined workspace and will use different values. If you want job B to use the same you could pass the value as parameter like: ALT_WORKSPACE=${WORKSPACE} Am Dienstag, 16. September 2014 03:21:03 UTC+2 schrieb Brantone: > > Perhaps just no

Issue with RegEx for project roles in Matrix Authorization Strategy Plugin

Hi all, I have a weird issue with a regular expression. Hopefully you can help me out here. I have a RegEx like *(.*)GUIDE_(?!MIB)(.*)(?!P4)* It should, as far as I can tell, list all jobs containing GUIDE but exclude GUIDE jobs with a MIB in the middle or P4 at the end of the project name, rig