[JIRA] [job-dsl-plugin] (JENKINS-32011) JOBDSL should allow dash ("-") in a job name
Title: Message Title
Daniel Kuffner commented on JENKINS-32011
Re: JOBDSL should allow dash ("-") in a job name
Ok, that is less painful Any reason why script names are so restrictive?
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-32011) JOBDSL should allow dash ("-") in a job name
Title: Message Title
Daniel Kuffner created an issue
Jenkins / JENKINS-32011
JOBDSL should allow dash ("-") in a job name
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
10/Dec/15 5:46 PM
Priority:
Minor
Reporter:
Daniel Kuffner
I found following deprecation message in:
Warning: script names may only contain letters, digits and underscores, but may not start with a digit; support for arbitrary names is deprecated
We use in all projects dash ("-") as separator between words. We also have fairly complex pipelines where teams rely on a given job name to pass down artifacts.
To not allow dash has a valid characters seems to me like a artificial limitation which forces, at least on us, an unnecessary burden to refactor build chains all over the place. Is there any objections to add dash to the list of valid job name character?
[JIRA] [job-dsl-plugin] (JENKINS-32011) JOBDSL should allow dash ("-") in a job name
Title: Message Title
Daniel Kuffner updated an issue
Jenkins / JENKINS-32011
JOBDSL should allow dash ("-") in a job name
Change By:
Daniel Kuffner
I found following deprecation message in:{code}Warning: script names may only contain letters, digits and underscores, but may not start with a digit; support for arbitrary names is deprecated{code}We use in all projects dash ("-") as separator between words. We also have fairly complex pipelines where teams rely on a given job name to pass down artifacts. To not allow dash has a valid characters character seems to me like a artificial limitation which forces, at least on us, an unnecessary burden to refactor build chains all over the place. Is there any objections to add dash to the list of valid job name character?
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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/d/optout.
[JIRA] [workflow-plugin] (JENKINS-30910) job input parameters should be exposed in sh task
Title: Message Title
Daniel Kuffner created an issue
Jenkins / JENKINS-30910
job input parameters should be exposed in sh task
Issue Type:
Improvement
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
12/Oct/15 8:22 PM
Priority:
Major
Reporter:
Daniel Kuffner
I noticed that job input parameters are not available inside of the sh task for example:
sh 'echo ${ARTIFACTS}'
I'm aware of that I can interpolate the variable but I have scripts which expects to have variables set.
// expects to have ARTIFACTS env available
sh('./some-python-script.py'))
Migration from my old hand patched pipeline to the new workflow would be easier if Job parameters and injected environment variables are available like in the regular script step (freestyle project)
[JIRA] [workflow-plugin] (JENKINS-29118) Workflow Job just gets canceled instead of queued
Title: Message Title
Daniel Kuffner updated an issue
Jenkins / JENKINS-29118
Workflow Job just gets canceled instead of queued
Change By:
Daniel Kuffner
Ihaveasimplejenkinssetup.Noslaves.Themasterprovidestwoexecutors.Ihavecreatedasimpleworkflowscript(echo-ingsomestuff)whichneedsuserinput.Icantriggertwoworkflowjobs.Firstworkflowstarts,secondisqueued.Inthisstateeverynextstartedworkflowjobwillbejustcanceled:{code}Canceledsince#16gothereRunning:EndofWorkflowSupersededby#16Finished:NOT_BUILT{code} Version:workflow1.8
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29118) Workflow Job just gets canceled instead of queued
Title: Message Title Daniel Kuffner created an issue Jenkins / JENKINS-29118 Workflow Job just gets canceled instead of queued Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 28/Jun/15 7:01 PM Priority: Minor Reporter: Daniel Kuffner I have a simple jenkins setup. No slaves. The master provides two executors. I have created a simple workflow script (echo-ing some stuff) which needs user input. I can trigger two workflow jobs. First workflow starts, second is queued. In this state every next started workflow job will be just canceled: Canceled since #16 got here Running: End of Workflow Superseded by #16 Finished: NOT_BUILT Add Comment
[JIRA] [job-dsl-plugin] (JENKINS-22708) JobDSL Plugin can produce never ending jobs (resource leak)
Daniel Kuffner
created JENKINS-22708
JobDSL Plugin can produce never ending jobs (resource leak)
Issue Type:
Bug
Assignee:
Justin Ryan
Components:
job-dsl-plugin
Created:
22/Apr/14 8:34 AM
Description:
It is possible to create a job which will never end by configuring a job like:
job {
name "Test"
configure { root -
// Please note I forgot to start with "root"
properties / 'hudson.plugins.disk__usage.DiskUsageProperty').@plugin="disk-usage@0.23"
}
}
I did obviously a mistake in the configuration block since I start with "properties" instead of "root". Neverless it would be good if in this case the job would just fail.
JobDSL Plugin Version 1.22
Project:
Jenkins
Priority:
Blocker
Reporter:
Daniel Kuffner
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/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-22708) JobDSL Plugin can produce never ending jobs (resource leak)
Daniel Kuffner
updated JENKINS-22708
JobDSL Plugin can produce never ending jobs (resource leak)
Change By:
Daniel Kuffner
(22/Apr/14 8:37 AM)
Description:
Itispossibletocreateajobwhichwillneverendbyconfiguringajoblike:{code}job{ nameTest configure{root- //PleasenoteIforgottostartwithroot
(
properties/
(
hudson.plugins.disk__usage.DiskUsageProperty).@plugin=disk-usage@0.23 }}{code}IdidobviouslyamistakeintheconfigurationblocksinceIstartwithpropertiesinsteadofroot.Neverlessitwouldbegoodifinthiscasethejobwouldjustfail.JobDSLPluginVersion1.22
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/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-22708) JobDSL Plugin can produce never ending jobs (resource leak)
Daniel Kuffner
updated JENKINS-22708
JobDSL Plugin can produce never ending jobs (resource leak)
Change By:
Daniel Kuffner
(22/Apr/14 8:36 AM)
Description:
Itispossibletocreateajobwhichwillneverendbyconfiguringajoblike:{code}job{ nameTest configure{root- //PleasenoteIforgottostartwithroot properties/
(
hudson.plugins.disk__usage.DiskUsageProperty).@plugin=disk-usage@0.23 }}{code}IdidobviouslyamistakeintheconfigurationblocksinceIstartwithpropertiesinsteadofroot.Neverlessitwouldbegoodifinthiscasethejobwouldjustfail.JobDSLPluginVersion1.22
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/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-22708) JobDSL Plugin can produce never ending jobs (resource leak)
Daniel Kuffner commented on JENKINS-22708 JobDSL Plugin can produce never ending jobs (resource leak) Just for clearifiaction, the JobDSL Plugin job hangs forever 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/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-22708) JobDSL Plugin can produce never ending jobs (resource leak)
Daniel Kuffner edited a comment on JENKINS-22708 JobDSL Plugin can produce never ending jobs (resource leak) Just for clarification, the JobDSL Plugin job hangs forever 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/d/optout.
[JIRA] (JENKINS-14272) allow defining custom path to gradlew (gradle wrapper) scipt
Daniel Kuffner commented on JENKINS-14272 allow defining custom path to gradlew (gradle wrapper) scipt I think a new textbox which allows to specify the gradle wrapper batch file parent would be the best solution. I would like to contribute a patch for that if there is no objection with this approach. 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-14272) allow defining custom path to gradlew (gradle wrapper) scipt
Daniel Kuffner commented on JENKINS-14272 allow defining custom path to gradlew (gradle wrapper) scipt Duplicate JENKINS-12769 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
