[JIRA] (JENKINS-59072) Cannot use shortcut under a folder
Title: Message Title Alessio Moscatello commented on JENKINS-59072 Re: Cannot use shortcut under a folder Hello, the problem seems to be how the plugins is using REST api link invoked MYSERVER/view/all/job/folderName/build?delay=0sec expected link MYSERVER/view/all/job/folderName/job/PipelineName/build?delay=0sec BR, Alessio Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201454.1566731992000.6151.1576141260229%40Atlassian.JIRA.
[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 Alessio Moscatello 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 Liam Newman your comment you are saing to set a JVM argument. I've added it to my Jenkins instance, and from the Jenkins script console I see that JAVA_OPTS variable is being populated like this: JAVA_OPTS=-Dorg.jenkinsci.plugins.pipeline.modeldefinition.parser.RuntimeASTTransformer.SCRIPT_SPLITTING_TRANSFORMATION=true This is sufficient to verify that the script splitting is enabled? Because I haven't seen any differences (my declarative pipeline is still failing). Another question you are talking about version 1.4 of which plugin? BR, Alessio Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174127.1473169024000.11260.1575385863755%40Atlassian.JIRA.
[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 Alessio Moscatello 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 Hello, I'm just fiddling with groovy shared libraries, it helped me reducing code size a bit, but now I'm pretty stuck since I cannot reduce it anymore, so each line I add is causing the issue...maybe I'm not using shared libraries in the correct way? Does anyone have some hints on this? BR, Alessio Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174127.1473169024000.11159.1565339826212%40Atlassian.JIRA.
[JIRA] (JENKINS-58814) Flag --no-repo-verify shall not be used by default when using "--repo-url" flag
Title: Message Title Alessio Moscatello created an issue Jenkins / JENKINS-58814 Flag --no-repo-verify shall not be used by default when using "--repo-url" flag Issue Type: Bug Assignee: Unassigned Components: repo-plugin Created: 2019-08-05 14:02 Environment: Jenkins ver. 2.167 repo-plugin version 1.10.7 Priority: Minor Reporter: Alessio Moscatello Repo plugin shall not use by default flag "-no-repo-verify" when using custom repo mirror "-repo-url", but an option should be added to control whether to perform this check or not. Use case: using internal mirror of upstream "gerrit repo" repository, so I can perform a build without accessing Internet For the moment the option "--no-repo-verify" is not working, but I don't need it since I'm just using a mirror of official repositories, so all the tags are signed with GPG. Add Comment
[JIRA] (JENKINS-58514) Repo plugin detect change when there is an error in repo sync
Title: Message Title Alessio Moscatello commented on JENKINS-58514 Re: Repo plugin detect change when there is an error in repo sync Probably is the same issue as JENKINS-37819 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200658.1563280071000.624.1564048200105%40Atlassian.JIRA.
[JIRA] (JENKINS-22299) Add a way to specify credentials
Title: Message Title Alessio Moscatello commented on JENKINS-22299 Re: Add a way to specify credentials Vote +1 also from me I really need this feature! BR Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.154080.139540600.11985.1563280200436%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58514) Repo plugin detect change when there is an error in repo sync
Title: Message Title Alessio Moscatello created an issue Jenkins / JENKINS-58514 Repo plugin detect change when there is an error in repo sync Issue Type: Bug Assignee: Unassigned Components: repo-plugin Created: 2019-07-16 12:27 Environment: Jenkins ver. 2.167 repo-plugin version 1.10.7 Priority: Minor Reporter: Alessio Moscatello Actual behaviour: When repo-plugin is configured to poll manifest and an error occurs during repo sync, the plugin reports that changes are found Expected behaviour: do not report any change, so the build is not launched notify that the polling is failing Here's polling log: ... [poll] Latest remote head revision on refs/heads/release/jk/v1 is: 4792dd5dd91515eb13e2eabb828dc734e766bb33 - already built by 2 [src] $ /usr/bin/repo/repo init -u MY_GIT_SERVER_ADDRESS -b releaes/v1 -m mymanifest.xml fatal: could not read Username for 'MY_BITBUCKET_ADDRESS:port': No such device or address fatal: could not read Username for 'MY_BITBUCKET_ADDRESS:port': No such device or address fatal: cannot obtain manifest MY_MANIFEST_REPO_ADDRESS Done. Took 1 min 13 sec Changes found
[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 Alessio Moscatello 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 Hello, this is causing troubles also on my company...I think that a solution could be moving bash commands to an external file or using groovy libraries, but during initial development phase of pipeline I usually put all the code in the a single file: it is not maintainable, but it is what I need to quickly develop and test new pipelines. I'll be really grateful to Jenkins developers if they can solve this issue BR, Alessio Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174127.1473169024000.8510.1562920921492%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52591) Job DSL does not track manual changes correctly
Title: Message Title Alessio Moscatello commented on JENKINS-52591 Re: Job DSL does not track manual changes correctly Hello, I'm experiencing a similar issue, but in a more complicated workflow: I have a DSL job that creates other jobs and these jobs are using separate repository to get the pipeline code to be executed: the DSL plugin always report that the job has been manually modified. Maybe the DSL plugin could be modified to compare current Job configuration to the one generated by the first run of the pipeline and not to the configuration generated by DSL plugin itself? BR, Alessio Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55813) Improve AD/LDAP attribute analysis for locked accounts
Title: Message Title Alessio Moscatello assigned an issue to Wadeck Follonier Jenkins / JENKINS-55813 Improve AD/LDAP attribute analysis for locked accounts Change By: Alessio Moscatello Assignee: Alessio Moscatello Wadeck Follonier Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55813) Improve AD/LDAP attribute analysis for locked accounts
Title: Message Title Alessio Moscatello assigned an issue to Alessio Moscatello Jenkins / JENKINS-55813 Improve AD/LDAP attribute analysis for locked accounts Change By: Alessio Moscatello Assignee: Wadeck Follonier Alessio Moscatello Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.
