[JIRA] (JENKINS-60707) option to configure Default Checkout
Title: Message Title Viachaslau Kabak created an issue Jenkins / JENKINS-60707 option to configure Default Checkout Issue Type: Improvement Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2020-01-09 07:58 Priority: Major Reporter: Viachaslau Kabak In pipelines we need to add some options to modify default checkout: Path of the reference repo to use during clone: to use baregit repo path Sparse checkout path these options are available for checkout in default and in pipeline step. It would be nice to have them in Declarative pipeline in options for pipeline. Add Comment
[JIRA] (JENKINS-54647) Plugin is not working in downstream jobs
Title: Message Title Viachaslau Kabak created an issue Jenkins / JENKINS-54647 Plugin is not working in downstream jobs Issue Type: Improvement Assignee: Bruno P. Kinoshita Components: active-choices-plugin Created: 2018-11-15 13:57 Environment: Jenkins 2.138.2 Active-choices 2.1 Priority: Major Reporter: Viachaslau Kabak Parameter failed when it is located in downstream job it uses Fallback Script groovy and set description to null Add Comment
[JIRA] (JENKINS-53517) Add fucntionality to parse only stage (part of log)
Title: Message Title Viachaslau Kabak created an issue Jenkins / JENKINS-53517 Add fucntionality to parse only stage (part of log) Issue Type: Improvement Assignee: Manuel Recena Soto Components: log-parser-plugin Created: 2018-09-12 08:07 Environment: Jenkins 2.121.3 Priority: Major Reporter: Viachaslau Kabak Could you please implement functionality to parse only stage log Add Comment
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Viachaslau Kabak commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script +1 it is a real headache about 800-900 lines of code could you please enforce fixing this issue? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-51263) try-catch is not working in declarative pipeline
Title: Message Title
Viachaslau Kabak updated an issue
Jenkins / JENKINS-51263
try-catch is not working in declarative pipeline
Change By:
Viachaslau Kabak
{code:java}pipeline { stages { stage("Test") { script { for (i in list){ try { echo "Any code with error" } catch(err) { echo "Error" } } } } } } {code} So the try-catch is not working in script section of declarative pipeline. It throws an exception and pipeline fails
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
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-51263) try-catch is not working in declarative pipeline
Title: Message Title
Viachaslau Kabak updated an issue
Jenkins / JENKINS-51263
try-catch is not working in declarative pipeline
Change By:
Viachaslau Kabak
{code:java} pipeline \ { stages \ { stage("Test") \ { script \ { try \ { echo "Any code with error" } catch(err) \ { echo "Error" } } } } } {code } So the try-catch is not working in script section of declarative pipeline. It throws an exception and pipeline fails
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
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-51263) try-catch is not working in declarative pipeline
Title: Message Title
Viachaslau Kabak created an issue
Jenkins / JENKINS-51263
try-catch is not working in declarative pipeline
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2018-05-11 12:36
Environment:
Jenkins 2.107.2
Priority:
Minor
Reporter:
Viachaslau Kabak
pipeline { stages { stage("Test") { script { try { echo "Any code with error" } catch(err) { echo "Error" } } } } } So the try-catch is not working in script section of declarative pipeline. It throws an exception and pipeline fails
Add Comment
[JIRA] (JENKINS-25829) Proxy configuration does not work
Title: Message Title Viachaslau Kabak commented on JENKINS-25829 Re: Proxy configuration does not work Have no chance to test for now, sorry Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49261) Mulitbranch pipeline failed to find JenkinsFile in a subfolder
Title: Message Title Viachaslau Kabak commented on JENKINS-49261 Re: Mulitbranch pipeline failed to find JenkinsFile in a subfolder having the same issue Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-40184) Credentials parameters are not passed to jobs stored in pipeline parallel
Title: Message Title Viachaslau Kabak closed an issue as Fixed Found that after jenkins or pipeline plugin update issue has disappeared. Jenkins / JENKINS-40184 Credentials parameters are not passed to jobs stored in pipeline parallel Change By: Viachaslau Kabak Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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
[JIRA] (JENKINS-40184) Credentials parameters are not passed to jobs stored in pipeline parallel
Title: Message Title Viachaslau Kabak updated an issue Jenkins / JENKINS-40184 Credentials parameters are not passed to jobs stored in pipeline parallel Change By: Viachaslau Kabak Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40857) Add option to pass all parameters and/or environment variables to trigered job
Title: Message Title Viachaslau Kabak created an issue Jenkins / JENKINS-40857 Add option to pass all parameters and/or environment variables to trigered job Issue Type: Improvement Assignee: Unassigned Components: pipeline Created: 2017/Jan/06 7:58 AM Labels: pipeline Priority: Minor Reporter: Viachaslau Kabak It would be nice to have possibility to have an option to trigger any job from pipeline with all parameters and/or environment variables (like in multijob plugin). Add Comment
[JIRA] (JENKINS-39727) Any way to control builds from PR comments?
Title: Message Title Viachaslau Kabak commented on JENKINS-39727 Re: Any way to control builds from PR comments? also please take a look on Github Integration plugin and take please the features from it now using it (it is compatible with pipelines) but the future is for GH organization and multibranch plugins Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39838) CHANGE_ variables are missing
Title: Message Title Viachaslau Kabak commented on JENKINS-39838 Re: CHANGE_ variables are missing Could you please also add following variables: Source_branch Repository_owner (organization) repository_name sha (commit_sha) the last one is very important Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40184) Credentials parameters are not passed to jobs stored in pipeline parallel
Title: Message Title Viachaslau Kabak commented on JENKINS-40184 Re: Credentials parameters are not passed to jobs stored in pipeline parallel All other parameters are passed successfully (string and boolean types) the issue is only with credentials Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40184) Credentials parameters are not passed to jobs stored in pipeline parallel
Title: Message Title
Viachaslau Kabak created an issue
Jenkins / JENKINS-40184
Credentials parameters are not passed to jobs stored in pipeline parallel
Issue Type:
Bug
Assignee:
Stephen Connolly
Components:
credentials-plugin
Created:
2016/Dec/02 9:38 AM
Environment:
Jenkins 2.19.3 Centos7 Oracle Java 1.8.0_60
Labels:
pipeline
Priority:
Major
Reporter:
Viachaslau Kabak
parallel ( "stream1": { build job: "job1", parameters: [[$class: 'CredentialsParameterValue', description: 'credentials for git storage', name: 'GIT_CREDENTIALS', value: "$ {GIT_CREDENTIALS}"]] } "stream2": { build job: "job2", parameters: [[$class: 'CredentialsParameterValue', description: 'credentials for git storage', name: 'GIT_CREDENTIALS', value: "${GIT_CREDENTIALS} "]] } ) This is the script example. Both job1 and job2 have GIT_CREDENTIALS parameter with Credentials type. job1 gets right GIT_CREDENTIALS from pipeline. job2 have a message in the parameter field " Not available to current user "
[JIRA] (JENKINS-25508) Git plugin doesn't parse changelog (false "First time build")
Title: Message Title Viachaslau Kabak commented on JENKINS-25508 Re: Git plugin doesn't parse changelog (false "First time build") facing the same issue jenkins1.651.3 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-28335) Step to run Git commands w/ credentials & tool (was: GitPublisher support)
Title: Message Title Viachaslau Kabak commented on JENKINS-28335 Re: Step to run Git commands w/ credentials & tool (was: GitPublisher support) Hello, need the pipeline functioning ASAP could you please provide such feature? thanks Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-31939) The top value is better to be chosen by default of to have such option
Title: Message Title Viachaslau Kabak commented on JENKINS-31939 Re: The top value is better to be chosen by default of to have such option thanks) will wait for 0.6.2 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-31939) The top value is better to be chosen by default of to have such option
Title: Message Title Viachaslau Kabak commented on JENKINS-31939 Re: The top value is better to be chosen by default of to have such option I have added my screenshots with plugin version and with 2 types of job run: 1) by timer 2) manually Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-31939) The top value is better to be chosen by default of to have such option
Title: Message Title Viachaslau Kabak updated an issue Jenkins / JENKINS-31939 The top value is better to be chosen by default of to have such option Change By: Viachaslau Kabak Attachment: by timer.PNG Attachment: by timer_console.PNG Attachment: manually.PNG Attachment: plugin version.PNG Attachment: plugin_config.PNG Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this
[JIRA] (JENKINS-31939) The top value is better to be chosen by default of to have such option
Title: Message Title Viachaslau Kabak commented on JENKINS-31939 Re: The top value is better to be chosen by default of to have such option what jenkins version are you using? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-31939) The top value is better to be chosen by default of to have such option
Title: Message Title Viachaslau Kabak commented on JENKINS-31939 Re: The top value is better to be chosen by default of to have such option hi, seems that yes but it does not work by schedule, only by manual job start( Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-31939) The top value is better to be chosen by default of to have such option
Title: Message Title Viachaslau Kabak commented on JENKINS-31939 Re: The top value is better to be chosen by default of to have such option Hi I meant not plugin parameter but jenkins parameter if I use plugin and set name as GIT_TAG and start job by schedule - there is no this parameter in job parameters list Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-31939) The top value is better to be chosen by default of to have such option
Title: Message Title Viachaslau Kabak commented on JENKINS-31939 Re: The top value is better to be chosen by default of to have such option Hi, it works on manual job start. The top value is selected. but if job started by schedule - it does not show the parameter in parameters jenkins version is 1.651.3 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-31939) The top value is better to be chosen by default of to have such option
Title: Message Title Viachaslau Kabak reopened an issue Jenkins / JENKINS-31939 The top value is better to be chosen by default of to have such option Change By: Viachaslau Kabak Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] [git-parameter-plugin] (JENKINS-31939) The top value is better to be chosed by default of to have such option
Title: Message Title Viachaslau Kabak reopened an issue tested it get the most top right value if job is started manually but gets wrong value if started by timer and GIT parameter has a filter set it ignores filter and gets top value Jenkins / JENKINS-31939 The top value is better to be chosed by default of to have such option Change By: Viachaslau Kabak Resolution: Fixed Status: Resolved Reopened 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] [active-choices-plugin] (JENKINS-32405) Groovy script failed to run if build started by timer
Title: Message Title Viachaslau Kabak created an issue Jenkins / JENKINS-32405 Groovy script failed to run if build started by timer Issue Type: Bug Assignee: Bruno P. Kinoshita Attachments: issueAttachment.png Components: active-choices-plugin Created: 12/Jan/16 8:14 AM Priority: Critical Reporter: Viachaslau Kabak Add groovy script to fill the list. If run build manually - script run successfully and list is filling well. But if job runs by timer - fallback script runs. Using Active Choices Reactive Parameter with 2 Referenced Parameters. Add Comment
[JIRA] [active-choices-plugin] (JENKINS-32405) Groovy script failed to run if build started by timer
Title: Message Title Viachaslau Kabak commented on JENKINS-32405 Re: Groovy script failed to run if build started by timer thanks 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] [git-parameter-plugin] (JENKINS-31939) The top value is better to be chosed by default of to have such option
Title: Message Title Viachaslau Kabak created an issue Jenkins / JENKINS-31939 The top value is better to be chosed by default of to have such option Issue Type: Improvement Assignee: Niklaus Giger Components: git-parameter-plugin Created: 07/Dec/15 1:36 PM Priority: Major Reporter: Viachaslau Kabak It would be good to have an option or setting the most top of results to be chosen by default. Add Comment This message was sent by Atlassian JIRA
[JIRA] [multijob-plugin] (JENKINS-25817) Improve multijob plugin to restart tasks from failed subjob
Viachaslau Kabak created JENKINS-25817 Improve multijob plugin to restart tasks from failed subjob Issue Type: Improvement Assignee: Unassigned Components: multijob-plugin Created: 28/Nov/14 7:33 AM Description: If one sub-job fails we need to restart this job manually and then start next sub-jobs manually too. Or start multijob again. I suggest to improve multijob flexibility: to start multijob from any of sub-jobs: it starts chosen sub-job and next subjobs. It will help to save time if some job fails and we need to continue building after some fixes. Project: Jenkins Priority: Major Reporter: Viachaslau Kabak 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-multijob-plugin] (JENKINS-24540) MultiJob does not ask parameters values if Phase jobs are parameterized
Viachaslau Kabak commented on JENKINS-24540 MultiJob does not ask parameters values if Phase jobs are parameterized can you explain in details? 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.
