[JIRA] [ws-cleanup] (JENKINS-18446) Add ability to specify if the workspace should be wiped out via a job parameter
Florin Hillebrand created JENKINS-18446 Add ability to specify if the workspace should be wiped out via a job parameter Issue Type: Improvement Assignee: vjuranek Components: ws-cleanup Created: 21/Jun/13 2:43 PM Description: Sometimes we don't want to wipe out the workspace all the time when building. e.g. when we want to make cached builds, omit checkouts to unload the VCS server. It would be very helpful to specify a boolean parameter, which is read every build to check whether the user wants to wipe out the workspace or not. Project: Jenkins Priority: Major Reporter: Florin Hillebrand This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16352) Cron TimerTrigger with parameters
Florin Hillebrand created JENKINS-16352 Cron TimerTrigger with parameters Issue Type: Improvement Assignee: Unassigned Components: core Created: 15/Jan/13 5:12 PM Description: I was missing the possibility to pass a parameter to a crontab line, so that I can do different things on different days. e.g. We have a linux that is built every day except Saturdays (~1h) and on Sundays we run a clean build (~10h), where Saturday is reserved for other projects that run a clean build. The only way for me was to create a conditional build step. It blows up the job configuration and gets decoupled from the crontab: So when someone changes the crontab from Sunday to Saturday for clean builds, he will also have to change the day in the conditional build step. My proposal is to extend the crontab syntax by something like: MIN HOUR DOM MONTH DOW % PARAM1=VALUE1,PARAM2=VALUE2 This would than schedule a build with the given parameters. Would others be interested too? Project: Jenkins Labels: TimerTrigger, Parameter Priority: Minor Reporter: Florin Hillebrand This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16352) Add ability to specify parameters in the crontab
Florin Hillebrand updated JENKINS-16352 Add ability to specify parameters in the crontab Change By: Florin Hillebrand (15/Jan/13 5:17 PM) Summary: CronTimerTriggerwith Addabilitytospecify parameters inthecrontab This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15390) Custom workspace in matrix project doesn't expand environment variable
Florin Hillebrand
created JENKINS-15390
Custom workspace in matrix project doesnt expand environment variable
Issue Type:
Improvement
Affects Versions:
current
Assignee:
Unassigned
Components:
matrix
Created:
03/Oct/12 11:45 AM
Description:
I have a matrix job with a string parameter:
CUSTOM_WORKSPACE (no default value)
The matrix job has the custom workspace feature activated and is set to "${CUSTOM_WORKSPACE}". Directory for sub-builds is set to "."
console log says:
...
Building remotely on buildbot in workspace /home/jenkins/jenkins-root/${CUSTOM_WORKSPACE}
...
Project:
Jenkins
Priority:
Major
Reporter:
Florin Hillebrand
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14846) Multiple repositories failes checkout of custom branch
Florin Hillebrand
updated JENKINS-14846
Multiple repositories failes checkout of custom branch
Change By:
Florin Hillebrand
(24/Sep/12 6:54 AM)
Summary:
Environmentvariabledoesntgetexpanded
Multiplerepositoriesfailescheckoutofcustombranch
Labels:
git
multiple-scms
Description:
Stepstoreproduce:1.Setup
MultiSCMwitha
git
repository
checkoutwithtworepositories(withorwithoutrefspec)
2.Specify
${TEST_BRANCH}as
ajobstringparameterforthe
branch
specifier
3.
Definejobisparameterizedanddefine
Launch
the
stringparameterTEST_BRANCH
build
witha
valid
custom
branch
.
asparameter
Actualresults:Checksoutthelast
build
built
branchExpectedresults:Checkoutthebranchwhichwasspecifiedby
TEST_BRANCH
parameter
Component/s:
multiple-scms
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14846) Multiple repositories failes checkout of custom branch
Florin Hillebrand updated JENKINS-14846 Multiple repositories failes checkout of custom branch Change By: Florin Hillebrand (24/Sep/12 6:54 AM) Description: Stepstoreproduce:1.Setupgit checkout plugin withtworepositories(withorwithoutrefspec)2.Specifyajobstringparameterforthebranch3.LaunchthebuildwithacustombranchasparameterActualresults:ChecksoutthelastbuiltbranchExpectedresults:Checkoutthebranchwhichwasspecifiedbyparameter This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14846) Multiple repositories failes checkout of custom branch
Florin Hillebrand commented on JENKINS-14846 Multiple repositories failes checkout of custom branch A workaround for this is to specify a choose parameter containing the repositories, to have only one repository set up in git plugin. So a user can first select the repository where his branch is and then specify the branch. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14846) Multiple repositories failes checkout of custom branch
Florin Hillebrand assigned JENKINS-14846 to Kohsuke Kawaguchi Multiple repositories failes checkout of custom branch Change By: Florin Hillebrand (24/Sep/12 7:00 AM) Assignee: NicolasDeLoof KohsukeKawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14846) Multiple repositories failes checkout of custom branch
Florin Hillebrand updated JENKINS-14846 Multiple repositories failes checkout of custom branch Change By: Florin Hillebrand (24/Sep/12 7:01 AM) Environment: jenkins:1.477and1.472git:1.1.21and1.1.22 multi-scm:0.2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13509) PROPFILE handling of missing file isn't very nice
Florin Hillebrand commented on JENKINS-13509 PROPFILE handling of missing file isnt very nice Or create an empty file at that (/home/jenkins/.jenkins/jobs//version.properties) location, so that it can find a file, but not able to get a property out of it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14198) Ability to append a description to existing description for use with flexible publish
Florin Hillebrand
created JENKINS-14198
Ability to append a description to existing description for use with flexible publish
Issue Type:
Improvement
Affects Versions:
current
Assignee:
huybrechts
Attachments:
job-configuration.gif, result.gif
Components:
description-setter
Created:
24/Jun/12 10:12 AM
Description:
There is currently no way to create a multi line description based on multiple regex. The "Flexible publish" plugin gives me the possibility to call the description-setter plugin multiple times, but the last description-setter overwrites the result of the one before.
Therefore I added two checkboxes in the job configuration page for the plugin: One that says "Append description to existing description", which then calls build.getDescription() and prepends it to the current description.
The second checkbox "Append in a new line" is self explanatory and adds a "br /" between the existing description and the current description.
I've also added the helppages, but I'm not sure if this is the right way to specify a help file for an optionalBlock element:
f:optionalBlock ... help="${descriptor.getDescriptorFullUrl()}/help/setAppend"
but it actually works.
I would appreciate if you would merge my branch, because I think other people would need that feature as well.
Project:
Jenkins
Priority:
Major
Reporter:
Florin Hillebrand
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
