[JIRA] (JENKINS-61600) Stop using shaded snakeyaml from configuration-as-code plugin
Title: Message Title Emilio Escobar created an issue Jenkins / JENKINS-61600 Stop using shaded snakeyaml from configuration-as-code plugin Issue Type: Task Assignee: Stefan Wolf Components: gradle-plugin Created: 2020-03-20 11:56 Priority: Minor Reporter: Emilio Escobar Please consider using https://github.com/jenkinsci/snakeyaml-api-plugin instead of configuration-as-code snakeyaml module when code base version https://github.com/jenkinsci/gradle-plugin/blob/master/build.gradle#L27 is 2.204 or greater, Add Comment
[JIRA] (JENKINS-61453) Allow Jenkins.MANAGE user to access "Prepare for Shutdown"
Title: Message Title Emilio Escobar updated JENKINS-61453 Jenkins / JENKINS-61453 Allow Jenkins.MANAGE user to access "Prepare for Shutdown" Change By: Emilio Escobar Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205132.1584012795000.9044.1584550860163%40Atlassian.JIRA.
[JIRA] (JENKINS-61453) Allow Jenkins.MANAGE user to access "Prepare for Shutdown"
Title: Message Title Emilio Escobar started work on JENKINS-61453 Change By: Emilio Escobar Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205132.1584012795000.6590.1584089280160%40Atlassian.JIRA.
[JIRA] (JENKINS-61453) Allow Jenkins.MANAGE user to access "Prepare for Shutdown"
Title: Message Title Emilio Escobar created an issue Jenkins / JENKINS-61453 Allow Jenkins.MANAGE user to access "Prepare for Shutdown" Issue Type: New Feature Assignee: Emilio Escobar Components: core Created: 2020-03-12 11:33 Priority: Minor Reporter: Emilio Escobar Jenkins.MANAGE permission is required for Prepare for Shutdown action. More details at JENKINS-60266 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-60982) Gitlab oauth doesn't return groupdetails and userdetails
Title: Message Title
Emilio Escobar created an issue
Jenkins / JENKINS-60982
Gitlab oauth doesn't return groupdetails and userdetails
Issue Type:
Bug
Assignee:
Mohamed El Habib
Components:
gitlab-oauth-plugin
Created:
2020-02-05 16:26
Priority:
Major
Reporter:
Emilio Escobar
With GitLabSecurityRealm configured,
Jenkins.get().getSecurityRealm().loadUserByUsername("emilio");
throws
org.acegisecurity.userdetails.UsernameNotFoundException: user(emilio) is also an organization
at org.jenkinsci.plugins.GitLabSecurityRealm.loadUserByUsername(GitLabSecurityRealm.java:529)
at org.acegisecurity.userdetails.UserDetailsService$loadUserByUsername.call(Unknown Source)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
Trying to load groups details, the plugin always returns one even if doesn't match with the requested
Jenkins.get().getSecurityRealm().loadGroupByGroupname("non-existing-group");
https://github.com/jenkinsci/gitlab-oauth-plugin/blob/master/src/main/java/org/jenkinsci/plugins/GitLabSecurityRealm.java#L577
[JIRA] (JENKINS-60805) NoSuchMethodError c.c.j.plugins.advisor.AdvisorGlobalConfiguration.getComponents => c.c.j.support.SupportPlugin.getComponents
Title: Message Title Emilio Escobar commented on JENKINS-60805 Re: NoSuchMethodError c.c.j.plugins.advisor.AdvisorGlobalConfiguration.getComponents => c.c.j.support.SupportPlugin.getComponents Arnaud Héritier I have assigned to you. It seems that advisor code has to be adapted to the new support core api. 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.204135.1579238976000.993.1579256520170%40Atlassian.JIRA.
[JIRA] (JENKINS-60805) NoSuchMethodError c.c.j.plugins.advisor.AdvisorGlobalConfiguration.getComponents => c.c.j.support.SupportPlugin.getComponents
Title: Message Title Emilio Escobar assigned an issue to Arnaud Héritier Jenkins / JENKINS-60805 NoSuchMethodError c.c.j.plugins.advisor.AdvisorGlobalConfiguration.getComponents => c.c.j.support.SupportPlugin.getComponents Change By: Emilio Escobar Assignee: Emilio Escobar Arnaud Héritier 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.204135.1579238976000.990.1579256400319%40Atlassian.JIRA.
[JIRA] (JENKINS-60493) Configure System page save redirect broken when Job Import is installed
Title: Message Title Emilio Escobar resolved as Fixed Jenkins / JENKINS-60493 Configure System page save redirect broken when Job Import is installed Change By: Emilio Escobar Status: In Progress Resolved Resolution: Fixed Released As: job-import-plugin:3.4 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.203582.1576452931000.8161.1576492140456%40Atlassian.JIRA.
[JIRA] (JENKINS-60493) Configure System page save redirect broken when Job Import is installed
Title: Message Title Emilio Escobar assigned an issue to Emilio Escobar Jenkins / JENKINS-60493 Configure System page save redirect broken when Job Import is installed Change By: Emilio Escobar Assignee: Emilio Escobar 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.203582.1576452931000.8076.1576486321528%40Atlassian.JIRA.
[JIRA] (JENKINS-60493) Configure System page save redirect broken when Job Import is installed
Title: Message Title Emilio Escobar started work on JENKINS-60493 Change By: Emilio Escobar Status: Open In Progress 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.203582.1576452931000.8078.1576486321708%40Atlassian.JIRA.
[JIRA] (JENKINS-60327) Tests are failing in windows using jenkins-test-harness-2.56
Title: Message Title Emilio Escobar commented on JENKINS-60327 Re: Tests are failing in windows using jenkins-test-harness-2.56 yes, the change that let us know the bug exists has been introduced in the jenkins-test-harness 2.56 version 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.203335.1575022375000.9347.1575030240121%40Atlassian.JIRA.
[JIRA] (JENKINS-60327) Tests are failing in windows using jenkins-test-harness-2.56
Title: Message Title Emilio Escobar created an issue Jenkins / JENKINS-60327 Tests are failing in windows using jenkins-test-harness-2.56 Issue Type: Bug Assignee: Unassigned Components: support-core-plugin Created: 2019-11-29 10:12 Priority: Critical Reporter: Emilio Escobar Because of https://github.com/jenkinsci/jenkins-test-harness/commit/a07387a5d21b273cfc55305ecc2b193111d47bc0#diff-1d6816bd6f9430280c5d8b7853286b1d tests are failing in windows because of open files. Add Comment This
[JIRA] (JENKINS-60196) Support Core has some tests failing on Windows (but not on CI)
Title: Message Title Emilio Escobar assigned an issue to Unassigned Jenkins / JENKINS-60196 Support Core has some tests failing on Windows (but not on CI) Change By: Emilio Escobar Assignee: Emilio Escobar 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.203166.1574073044000.9287.1575022380333%40Atlassian.JIRA.
[JIRA] (JENKINS-58278) Add ReconfigurableDescribable support.
Title: Message Title Emilio Escobar created an issue Jenkins / JENKINS-58278 Add ReconfigurableDescribable support. Issue Type: Improvement Assignee: Ewelina Wilkosz Components: configuration-as-code-plugin Created: 2019-07-01 08:48 Priority: Major Reporter: Emilio Escobar ReconfigurableDescribable is not yet supported. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57657) SYSTEM user could be used to track changes during initialization process.
Title: Message Title Emilio Escobar created an issue Jenkins / JENKINS-57657 SYSTEM user could be used to track changes during initialization process. Issue Type: Improvement Assignee: Emilio Escobar Components: jobconfighistory-plugin Created: 2019-05-24 10:09 Priority: Minor Reporter: Emilio Escobar Until InitLevel is not COMPLETED, unknown/anonymous user is used for tracking changes in configuration files as is defined at https://github.com/jenkinsci/jobConfigHistory-plugin/blob/master/src/main/java/hudson/plugins/jobConfigHistory/JobConfigHistorySaveableListener.java#L88-L93 SYSTEM user looks like a better option (as the changes are done by the system at that point). Add Comment
[JIRA] (JENKINS-51426) make autobundle generation period configurable from UI
Title: Message Title Emilio Escobar commented on JENKINS-51426 Re: make autobundle generation period configurable from UI Hello Mateusz Janczuk I have tested with 2.164.1 and support-core 2.56. It is working as expected. You can disable the background bundle generation using the system property -Dcom.cloudbees.jenkins.support.SupportPlugin.AUTO_BUNDLE_PERIOD_HOURS=0 with no issues 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.190779.1526652933000.5301.1558350120284%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57426) Make pipeline-model-extensions dependency optional
Title: Message Title Emilio Escobar updated JENKINS-57426 Jenkins / JENKINS-57426 Make pipeline-model-extensions dependency optional Change By: Emilio Escobar Status: In Review Resolved Resolution: Fixed Released As: 1.27 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.199238.1557742883000.483.1557846540223%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57426) Make pipeline-model-extensions dependency optional
Title: Message Title Emilio Escobar updated JENKINS-57426 Jenkins / JENKINS-57426 Make pipeline-model-extensions dependency optional Change By: Emilio Escobar Status: In Progress Review 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.199238.1557742883000.1112.1557745320105%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57426) Make pipeline-model-extensions dependency optional
Title: Message Title Emilio Escobar commented on JENKINS-57426 Re: Make pipeline-model-extensions dependency optional PR sent https://github.com/jenkinsci/aws-credentials-plugin/pull/54 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.199238.1557742883000.1107.1557745020083%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57426) Make pipeline-model-extensions dependency optional
Title: Message Title Emilio Escobar started work on JENKINS-57426 Change By: Emilio Escobar Status: Open In Progress 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.199238.1557742883000.1059.1557742980577%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57426) Make pipeline-model-extensions dependency optional
Title: Message Title Emilio Escobar created an issue Jenkins / JENKINS-57426 Make pipeline-model-extensions dependency optional Issue Type: Improvement Assignee: Emilio Escobar Components: aws-credentials-plugin Created: 2019-05-13 10:21 Priority: Minor Reporter: Emilio Escobar Pipeline: Declarative Extension Points API might not be considered as a required dependency for AWS Credentials. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-38084) Add support to mark jobs as disabled on import
Title: Message Title Emilio Escobar assigned an issue to Emilio Escobar Jenkins / JENKINS-38084 Add support to mark jobs as disabled on import Change By: Emilio Escobar Assignee: Owen Wood Emilio Escobar 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-38124) Although FromUserRecordLDAPGroupMembershipStrategy is configured, Jenkins still populates authorities by using group search (with the default pattern)
Title: Message Title Emilio Escobar stopped work on JENKINS-38124 Change By: Emilio Escobar Status: In Progress Open 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-54920) Refactor AboutJenkins class
Title: Message Title Emilio Escobar updated an issue Jenkins / JENKINS-54920 Refactor AboutJenkins class Change By: Emilio Escobar Issue Type: Bug Improvement 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-55689) Not able to connect to jenkins master from windows slave
Title: Message Title Emilio Escobar closed an issue as Not A Defect Jenkins / JENKINS-55689 Not able to connect to jenkins master from windows slave Change By: Emilio Escobar Status: Open Closed Resolution: Not A Defect 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-55689) Not able to connect to jenkins master from windows slave
Title: Message Title Emilio Escobar commented on JENKINS-55689 Re: Not able to connect to jenkins master from windows slave hello Mohit, probably adding the tunnel with ":41172" might be enough. Anyway, this is not a windows-slaves-plugin issue but a question to ask at Jenkins users mailing list. 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-51095) after successfully importing job in destination folder, the success-prompt offers an invalid URL to visit
Title: Message Title Emilio Escobar assigned an issue to Emilio Escobar Jenkins / JENKINS-51095 after successfully importing job in destination folder, the success-prompt offers an invalid URL to visit Change By: Emilio Escobar Assignee: Emilio Escobar 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-10964) Allow to pick the Jenkins instance from which jobs have to be imported from a drop-down list
Title: Message Title Emilio Escobar started work on JENKINS-10964 Change By: Emilio Escobar Status: Open In Progress 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-10964) Allow to pick the Jenkins instance from which jobs have to be imported from a drop-down list
Title: Message Title Emilio Escobar stopped work on JENKINS-10964 Change By: Emilio Escobar Status: In Progress Open 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-10964) Allow to pick the Jenkins instance from which jobs have to be imported from a drop-down list
Title: Message Title Emilio Escobar assigned an issue to Emilio Escobar Jenkins / JENKINS-10964 Allow to pick the Jenkins instance from which jobs have to be imported from a drop-down list Change By: Emilio Escobar Assignee: Daniel Petisme Emilio Escobar 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-51426) make autobundle generation period configurable from UI
Title: Message Title Emilio Escobar commented on JENKINS-51426 Re: make autobundle generation period configurable from UI It will be probably available for changing it from Script Console running this line: com.cloudbees.jenkins.support.SupportPlugin.AUTO_BUNDLE_PERIOD_HOURS=0; 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-51426) support core makes systems with performance problems worse
Title: Message Title Emilio Escobar updated an issue Jenkins / JENKINS-51426 support core makes systems with performance problems worse Change By: Emilio Escobar Issue Type: Bug Improvement 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-51426) support core makes systems with performance problems worse
Title: Message Title Emilio Escobar updated an issue Jenkins / JENKINS-51426 support core makes systems with performance problems worse Change By: Emilio Escobar Priority: Major Minor 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-51426) make autobundle generation period configurable from UI
Title: Message Title Emilio Escobar updated an issue Jenkins / JENKINS-51426 make autobundle generation period configurable from UI Change By: Emilio Escobar Summary: support core makes systems with performance problems worse make autobundle generation period configurable from UI 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-51426) support core makes systems with performance problems worse
Title: Message Title Emilio Escobar commented on JENKINS-51426 Re: support core makes systems with performance problems worse Hello Christian Höltje and Oleg Nenashev, Automatic bundle generation can be disabled by adding this system property: -Dcom.cloudbees.jenkins.support.SupportPlugin.AUTO_BUNDLE_PERIOD_HOURS=0 You can also change the period. For example, instead of 1 hour, you can use 12 with: -Dcom.cloudbees.jenkins.support.SupportPlugin.AUTO_BUNDLE_PERIOD_HOURS=12 Regards 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-50174) pipeline job status page cannot be rendered properly if a build hits JENKINS-50171
Title: Message Title Emilio Escobar updated an issue Jenkins / JENKINS-50174 pipeline job status page cannot be rendered properly if a build hits JENKINS-50171 Change By: Emilio Escobar Attachment: status-page-page.log Attachment: status-page-error.log 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-27035) Request/response statistics
Title: Message Title Emilio Escobar commented on JENKINS-27035 Re: Request/response statistics Released in support-core:2.46 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-50174) pipeline job status page cannot be rendered properly if a build hits JENKINS-50171
Title: Message Title Emilio Escobar created an issue Jenkins / JENKINS-50174 pipeline job status page cannot be rendered properly if a build hits JENKINS-50171 Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2018-03-14 15:49 Priority: Major Reporter: Emilio Escobar If after facing JENKINS-50171 , you remove jenkins-home/org.jenkinsci.plugins.workflow.flow.FlowExecutionList.xml but not the build, the pipeline job status page won't be rendered properly. Add Comment This
[JIRA] (JENKINS-50172) load step doesn't generate unique name for classes
Title: Message Title Emilio Escobar created an issue Jenkins / JENKINS-50172 load step doesn't generate unique name for classes Issue Type: Improvement Assignee: Unassigned Attachments: JenkinsEnvironment.groovy, Utility.groovy Components: pipeline Created: 2018-03-14 15:43 Priority: Major Reporter: Emilio Escobar using load step for loading these two groovy generate same class name: org/foo/devops/org_foo_devops causing further LinkageError if the build is resumed Add Comment
[JIRA] (JENKINS-50171) LinkageError loader attempted duplicate class definition for name causes Jenkins to doesn't start
Title: Message Title
Emilio Escobar created an issue
Jenkins / JENKINS-50171
LinkageError loader attempted duplicate class definition for name causes Jenkins to doesn't start
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
JenkinsEnvironment.groovy, startup-error.log, startup-page.log, Utility.groovy
Components:
pipeline
Created:
2018-03-14 15:39
Priority:
Critical
Reporter:
Emilio Escobar
Using load step to load two different groovy files without an explicit class but the same package declaration, causes Jenkins to fail during startup process if the build should be resumed. For example, create a dummy pipeline like
def util
def config
def util2
node('master') {
sh 'cp -r /tmp/test/src .'
config = load 'src/org/foo/devops/JenkinsEnvironment.groovy'
util = load 'src/org/foo/devops/Utility.groovy'
config.loadProdConfiguration()
}
util.isValueExist("")
echo "kill me while I'm sleeping"
sleep 20
node('master') {
util2 = load 'src/org/foo/devops/Utility.groovy'
util = load 'src/org/foo/devops/Utility.groovy'
}
And copy the two attached files at /tmp/test/src/org/foo/devops/ (Files can be retrieved as you prefer) Build the job and restart jenkins while is building. Then you won't be able to access Jenkins.
[JIRA] (JENKINS-49678) Pipeline lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file
Title: Message Title Emilio Escobar updated an issue Jenkins / JENKINS-49678 Pipeline lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file Change By: Emilio Escobar Summary: Pipleine Pipeline lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file 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-49196) java.io.IOException: Premature EOF when shutdown CLI command is used
Title: Message Title Emilio Escobar commented on JENKINS-49196 Re: java.io.IOException: Premature EOF when shutdown CLI command is used Thanks Madhava Kulkarni but is a direct connection, not related to a proxy at all. Jenkins is running on 127.0.0.1:8080 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-50010) Config page for excluding components when bundle is generated in background
Title: Message Title Emilio Escobar commented on JENKINS-50010 Re: Config page for excluding components when bundle is generated in background DISABLE parameter doesn't look like the best way to disable a concrete component. 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-50010) Config page for excluding components when bundle is generated in background
Title: Message Title Emilio Escobar created an issue Jenkins / JENKINS-50010 Config page for excluding components when bundle is generated in background Issue Type: Improvement Assignee: Unassigned Components: support-core-plugin Created: 2018-03-08 10:41 Priority: Major Reporter: Emilio Escobar All components are included when the bundle is generated in background so make sense to have a configuration page (administrators) in order to select which should be included. Add Comment This
[JIRA] (JENKINS-50008) Heap Histogram (all instances by default)
Title: Message Title Emilio Escobar updated an issue Jenkins / JENKINS-50008 Heap Histogram (all instances by default) Change By: Emilio Escobar As -live instances histogram requires a fullgc, the histogram will produce all by default (which doesn't require a fullgc). You could easily configure it by using the system property -Dcom.cloudbees.jenkins.support.impl. HeapUsageHistogram.FULLGC=true (permanent) or by running from Script Console com.cloudbees.jenkins.support.impl. HeapUsageHistogram.FULLGC=true (temporal) if you want to grab live instances.The histogram component could be easily disabled by using the system property -Dcom.cloudbees.jenkins.support.impl. HeapUsageHistogram.DISABLE=true (permanent) or by running from Script Console com.cloudbees.jenkins.support.impl. HeapUsageHistogram.DISABLE=true (temporal). 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
[JIRA] (JENKINS-50008) Heap Histogram (all instances by default)
Title: Message Title Emilio Escobar updated JENKINS-50008 Jenkins / JENKINS-50008 Heap Histogram (all instances by default) Change By: Emilio Escobar Status: In Progress Review 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-50008) Heap Histogram (all instances by default)
Title: Message Title Emilio Escobar started work on JENKINS-50008 Change By: Emilio Escobar Status: Open In Progress 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-50008) Heap Histogram (all instances by default)
Title: Message Title Emilio Escobar created an issue Jenkins / JENKINS-50008 Heap Histogram (all instances by default) Issue Type: Improvement Assignee: Emilio Escobar Components: support-core-plugin Created: 2018-03-08 09:41 Priority: Major Reporter: Emilio Escobar As -live instances histogram requires a fullgc, the histogram will produce all by default (which doesn't require a fullgc). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49931) Heap Histogram Collection Destabilizes Masters
Title: Message Title Emilio Escobar commented on JENKINS-49931 Re: Heap Histogram Collection Destabilizes Masters new https://github.com/jenkinsci/support-core-plugin/pull/135 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-49931) Heap Histogram Collection Destabilizes Masters
Title: Message Title Emilio Escobar updated JENKINS-49931 Jenkins / JENKINS-49931 Heap Histogram Collection Destabilizes Masters Change By: Emilio Escobar Status: In Progress Review 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-49931) Heap Histogram Collection Destabilizes Masters
Title: Message Title Emilio Escobar commented on JENKINS-49931 Re: Heap Histogram Collection Destabilizes Masters https://github.com/jenkinsci/support-core-plugin/pull/134 already available for review! 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-49931) Heap Histogram Collection Destabilizes Masters
Title: Message Title Emilio Escobar started work on JENKINS-49931 Change By: Emilio Escobar Status: Open In Progress 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-36543) Boolean input parameter ignores default value of false
Title: Message Title Emilio Escobar assigned an issue to Sam Van Oort Jenkins / JENKINS-36543 Boolean input parameter ignores default value of false Change By: Emilio Escobar Assignee: Rupin R Nath Sam Van Oort 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-42831) Enable StartTls is always TRUE in the UI
Title: Message Title Emilio Escobar stopped work on JENKINS-42831 Change By: Emilio Escobar Status: In Progress Open 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-42831) Enable StartTls is always TRUE in the UI
Title: Message Title Emilio Escobar started work on JENKINS-42831 Change By: Emilio Escobar Status: Open In Progress 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-42831) Enable StartTls is always TRUE in the UI
Title: Message Title Emilio Escobar updated JENKINS-42831 Jenkins / JENKINS-42831 Enable StartTls is always TRUE in the UI Change By: Emilio Escobar Status: In Progress Review 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-42831) Enable StartTls is always TRUE in the UI
Title: Message Title Emilio Escobar created an issue Jenkins / JENKINS-42831 Enable StartTls is always TRUE in the UI Issue Type: Bug Assignee: Emilio Escobar Components: active-directory-plugin Created: 2017/Mar/16 10:55 AM Environment: active-directory-plugin 2.2 Priority: Critical Reporter: Emilio Escobar Enable StartTls new option is always TRUE in the UI, even if you try to uncheck it. But, it is properly persisted on disk Add Comment
[JIRA] (JENKINS-42831) Enable StartTls is always TRUE in the UI
Title: Message Title Emilio Escobar started work on JENKINS-42831 Change By: Emilio Escobar Status: Open In Progress 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-42749) Polling configuration is not updated until next successful build
Title: Message Title Emilio Escobar commented on JENKINS-42749 Re: Polling configuration is not updated until next successful build Patrick Wolf git related (git, github and bitbucket) Configure an SCM with the extension AuthorInChangelog and use an ephemeral node (docker?). The polling will be performed reusing the workspace. As the node has been removed, the polling will fail. Then, try to remove the AuthorInChangelog from the SCM but the polling will still fail because will try to reuse the workspace. It will happen until you rebuild the job successfully 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-42749) Polling configuration is not updated until next successful build
Title: Message Title Emilio Escobar updated an issue Jenkins / JENKINS-42749 Polling configuration is not updated until next successful build Change By: Emilio Escobar Polling configuration is not updated until next successful build. Thus if a polling is failing because is trying to reuse a workspace for polling (in an ephemeral node), any configuration change won't be effective until successful manual trigger.A pipeline will try to reuse the workspace if has configured the branch like */releases/*, or is using an extension like 'AuthorInChangelog' 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-42749) Polling configuration is not updated until next successful build
Title: Message Title Emilio Escobar updated an issue Jenkins / JENKINS-42749 Polling configuration is not updated until next successful build Change By: Emilio Escobar Polling configuration is not updated until next successful build. Thus if a polling is failing because is trying to reuse a workspace for polling (in an ephemeral node), any configuration change won't be effective until successful manual trigger.A pipeline will try to reuse the workspace if has configured the branch like ' */releases/* ' , or is using an extension like 'AuthorInChangelog' 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-42749) Polling configuration is not updated until next successful build
Title: Message Title Emilio Escobar created an issue Jenkins / JENKINS-42749 Polling configuration is not updated until next successful build Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2017/Mar/14 10:43 AM Priority: Minor Reporter: Emilio Escobar Polling configuration is not updated until next successful build. Thus if a polling is failing because is trying to reuse a workspace for polling (in an ephemeral node), any configuration change won't be effective until successful manual trigger. A pipeline will try to reuse the workspace if has configured the branch like '/releases/', or is using an extension like 'AuthorInChangelog' Add Comment
[JIRA] (JENKINS-38418) Failed to load persisted workflow state (remote-loader)
Title: Message Title Emilio Escobar started work on JENKINS-38418 Change By: Emilio Escobar Status: Open In Progress 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-37856) LDAP Authentication Overall/Read Permissions Missing
Title: Message Title Emilio Escobar commented on JENKINS-37856 Re: LDAP Authentication Overall/Read Permissions Missing Hey Zack White , are you using LDAP or Active Directory plugin? 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-39643) Implement the IdStrategy extension point provided in JENKINS-22247
Title: Message Title Emilio Escobar closed an issue as Incomplete Jenkins / JENKINS-39643 Implement the IdStrategy extension point provided in JENKINS-22247 Change By: Emilio Escobar Status: Resolved Closed Assignee: Kohsuke Kawaguchi Emilio Escobar 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-41251) User loses authenticated group (authority) membership
Title: Message Title Emilio Escobar commented on JENKINS-41251 Re: User loses authenticated group (authority) membership It could happen if the group membership strategy is FromUser 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-38124) Although FromUserRecordLDAPGroupMembershipStrategy is configured, Jenkins still populates authorities by using group search (with the default pattern)
Title: Message Title Emilio Escobar updated an issue Jenkins / JENKINS-38124 Although FromUserRecordLDAPGroupMembershipStrategy is configured, Jenkins still populates authorities by using group search (with the default pattern) Change By: Emilio Escobar Priority: Minor 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-38124) Although FromUserRecordLDAPGroupMembershipStrategy is configured, Jenkins still populates authorities by using group search (with the default pattern)
Title: Message Title Emilio Escobar started work on JENKINS-38124 Change By: Emilio Escobar Status: Open In Progress 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-38124) Although FromUserRecordLDAPGroupMembershipStrategy is configured, Jenkins still populates authorities by using group search (with the default pattern)
Title: Message Title Emilio Escobar edited a comment on JENKINS-38124 Re: Although FromUserRecordLDAPGroupMembershipStrategy is configured, Jenkins still populates authorities by using group search (with the default pattern) I'd like to add more context and explanations about how is working currently for justifying that PR ( pending link https://github.com/jenkinsci/ldap-plugin/pull/11 ) .A very simple LDAP configuration where user has different groupmembership configured at group and user side: !01-ldap-ajones-user.png|thumbnail! !02-ldap-brodate-group.png|thumbnail! !03-ldap-gambit-group.png|thumbnail! LDAP is configured at Jenkins, using group membership - Parse user attribute for list of groups !04-jenkins-security-ldap-fromuser.png|thumbnail! And two groups at matrix, brodate has administer permission and gambit just read. !05-jenkins-security-matrixroles.png|thumbnail! After login, ajones has manager access !06-jenkins-ajones-manager-BAD.png|thumbnail! !07-jenkins-ajones-groups.png|thumbnail! !08-jenkins-ajones-whoAmI-BAD.png|thumbnail! 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-38124) Although FromUserRecordLDAPGroupMembershipStrategy is configured, Jenkins still populates authorities by using group search (with the default pattern)
Title: Message Title Emilio Escobar commented on JENKINS-38124 Re: Although FromUserRecordLDAPGroupMembershipStrategy is configured, Jenkins still populates authorities by using group search (with the default pattern) I'd like to add more context and explanations about how is working currently for justifying that PR (pending link) . A very simple LDAP configuration where user has different groupmembership configured at group and user side: LDAP is configured at Jenkins, using group membership - Parse user attribute for list of groupsAnd two groups at matrix, brodate has administer permission and gambit just read.After login, ajones has manager access 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-38124) Although FromUserRecordLDAPGroupMembershipStrategy is configured, Jenkins still populates authorities by using group search (with the default pattern)
Title: Message Title Emilio Escobar updated an issue Jenkins / JENKINS-38124 Although FromUserRecordLDAPGroupMembershipStrategy is configured, Jenkins still populates authorities by using group search (with the default pattern) Change By: Emilio Escobar Attachment: 07-jenkins-ajones-groups.png 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-38124) Although FromUserRecordLDAPGroupMembershipStrategy is configured, Jenkins still populates authorities by using group search (with the default pattern)
Title: Message Title Emilio Escobar updated an issue Jenkins / JENKINS-38124 Although FromUserRecordLDAPGroupMembershipStrategy is configured, Jenkins still populates authorities by using group search (with the default pattern) Change By: Emilio Escobar Attachment: 08-jenkins-ajones-whoAmI-BAD.png 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-38124) Although FromUserRecordLDAPGroupMembershipStrategy is configured, Jenkins still populates authorities by using group search (with the default pattern)
Title: Message Title Emilio Escobar updated an issue Jenkins / JENKINS-38124 Although FromUserRecordLDAPGroupMembershipStrategy is configured, Jenkins still populates authorities by using group search (with the default pattern) Change By: Emilio Escobar Attachment: 05-jenkins-security-matrixroles.png 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-38124) Although FromUserRecordLDAPGroupMembershipStrategy is configured, Jenkins still populates authorities by using group search (with the default pattern)
Title: Message Title Emilio Escobar updated an issue Jenkins / JENKINS-38124 Although FromUserRecordLDAPGroupMembershipStrategy is configured, Jenkins still populates authorities by using group search (with the default pattern) Change By: Emilio Escobar Attachment: 06-jenkins-ajones-manager-BAD.png 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-38124) Although FromUserRecordLDAPGroupMembershipStrategy is configured, Jenkins still populates authorities by using group search (with the default pattern)
Title: Message Title Emilio Escobar updated an issue Jenkins / JENKINS-38124 Although FromUserRecordLDAPGroupMembershipStrategy is configured, Jenkins still populates authorities by using group search (with the default pattern) Change By: Emilio Escobar Attachment: 04-jenkins-security-ldap-fromuser.png 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-38124) Although FromUserRecordLDAPGroupMembershipStrategy is configured, Jenkins still populates authorities by using group search (with the default pattern)
Title: Message Title Emilio Escobar updated an issue Jenkins / JENKINS-38124 Although FromUserRecordLDAPGroupMembershipStrategy is configured, Jenkins still populates authorities by using group search (with the default pattern) Change By: Emilio Escobar Attachment: 03-ldap-gambit-group.png 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-38124) Although FromUserRecordLDAPGroupMembershipStrategy is configured, Jenkins still populates authorities by using group search (with the default pattern)
Title: Message Title Emilio Escobar updated an issue Jenkins / JENKINS-38124 Although FromUserRecordLDAPGroupMembershipStrategy is configured, Jenkins still populates authorities by using group search (with the default pattern) Change By: Emilio Escobar Attachment: 02-ldap-brodate-group.png 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-38124) Although FromUserRecordLDAPGroupMembershipStrategy is configured, Jenkins still populates authorities by using group search (with the default pattern)
Title: Message Title Emilio Escobar updated an issue Jenkins / JENKINS-38124 Although FromUserRecordLDAPGroupMembershipStrategy is configured, Jenkins still populates authorities by using group search (with the default pattern) Change By: Emilio Escobar Attachment: 01-ldap-ajones-user.png 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-38124) Although FromUserRecordLDAPGroupMembershipStrategy is configured, Jenkins still populates authorities by using group search (with the default pattern)
Title: Message Title Emilio Escobar assigned an issue to Emilio Escobar Jenkins / JENKINS-38124 Although FromUserRecordLDAPGroupMembershipStrategy is configured, Jenkins still populates authorities by using group search (with the default pattern) Change By: Emilio Escobar Assignee: Kohsuke Kawaguchi Emilio Escobar 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-41214) bitbucket branch source plugin notifies wrong repository
Title: Message Title Emilio Escobar commented on JENKINS-41214 Re: bitbucket branch source plugin notifies wrong repository Every build is notified at the repository storing the script, but not the one storing the projects. 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-41214) bitbucket branch source plugin notifies wrong repository
Title: Message Title Emilio Escobar created an issue Jenkins / JENKINS-41214 bitbucket branch source plugin notifies wrong repository Issue Type: Bug Assignee: Antonio Muñiz Components: bitbucket-branch-source-plugin Created: 2017/Jan/19 12:02 PM Environment: Jenkins 1.65.x bitbucket-branch-source-plugin 1.8 Priority: Major Reporter: Emilio Escobar All build notifications goes to the wrong repository in Bitbucket Team/Project when you use: Project Recognizers -> Custom script [cusotm Marker file; Pipeline definition: script from scm: git] Both bitbucket server configured at repository sources and git server scm repository are the same but script from scm is located in other repository than the sources. Add Comment
[JIRA] (JENKINS-40193) Upgrade plugin parent pom
Title: Message Title Emilio Escobar started work on JENKINS-40193 Change By: Emilio Escobar Status: Open In Progress 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-40193) Upgrade plugin parent pom
Title: Message Title Emilio Escobar created an issue Jenkins / JENKINS-40193 Upgrade plugin parent pom Issue Type: Task Assignee: Unassigned Components: mttr-plugin Created: 2016/Dec/02 3:38 PM Priority: Major Reporter: Emilio Escobar Upgrade the parent pom Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40193) Upgrade plugin parent pom
Title: Message Title Emilio Escobar assigned an issue to Emilio Escobar Jenkins / JENKINS-40193 Upgrade plugin parent pom Change By: Emilio Escobar Assignee: Emilio Escobar 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-40162) "durationMillis" is always 0 at wfapi/describe json
Title: Message Title
Emilio Escobar created an issue
Jenkins / JENKINS-40162
"durationMillis" is always 0 at wfapi/describe json
Issue Type:
Bug
Assignee:
Sam Van Oort
Components:
pipeline-stage-view-plugin
Created:
2016/Dec/01 5:22 PM
Priority:
Major
Reporter:
Emilio Escobar
"durationMillis" is always 0 when I use http://master1.localhost.local:8080/job/pipeline/1/wfapi/ Pipeline script
echo 'hello guys'
stage 'one'
node {
sh 'sleep 5'
}
stage 'two'
node {
sh 'sleep 5'
}
stage 'three'
echo 'we are going to crash'
//throw new Exception("crash!!!")
sleep 2
Two builds, the first one fails and the second goes well. http://master1.localhost.local:8080/job/pipeline/1/wfapi/
Unable to find source-code formatter for language: json. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml
[JIRA] (JENKINS-35983) Add support to job import jobs in folders
Title: Message Title Emilio Escobar resolved as Fixed PR merged Jenkins / JENKINS-35983 Add support to job import jobs in folders Change By: Emilio Escobar Status: In Progress Resolved 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37065) Sync jobs between two jenkins dashboards using job import plugin API & Linux command line
Title: Message Title Emilio Escobar resolved as Not A Defect Please Vivek Yadav take a look at https://wiki.jenkins-ci.org/display/JENKINS/Remote+access+API Jenkins / JENKINS-37065 Sync jobs between two jenkins dashboards using job import plugin API & Linux command line Change By: Emilio Escobar Status: Open Resolved Resolution: Not A Defect 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-37084) Help needed in gearman implementation
Title: Message Title Emilio Escobar updated an issue Jenkins / JENKINS-37084 Help needed in gearman implementation Change By: Emilio Escobar Component/s: job-import-plugin 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-37882) Job Import page shows "New Null" instead of "New Item"
Title: Message Title Emilio Escobar assigned an issue to Emilio Escobar Jenkins / JENKINS-37882 Job Import page shows "New Null" instead of "New Item" Change By: Emilio Escobar Assignee: Emilio Escobar 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-30108) NumberFormatException when numBuilds is empty
Title: Message Title Emilio Escobar resolved as Fixed https://github.com/jenkinsci/plot-plugin/commit/e7bab51199f96a929609eb98db2ff959a13636af Jenkins / JENKINS-30108 NumberFormatException when numBuilds is empty Change By: Emilio Escobar Status: Open Resolved 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options,
[JIRA] (JENKINS-30108) NumberFormatException when numBuilds is empty
Title: Message Title Emilio Escobar commented on JENKINS-30108 Re: NumberFormatException when numBuilds is empty This issue is duplicating https://issues.jenkins-ci.org/browse/JENKINS-25849 which is already fixed in this master commit: https://github.com/jenkinsci/plot-plugin/commit/e7bab51199f96a929609eb98db2ff959a13636af But the fixed version hasn't been released yet. 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-19090) can't delete the project
Title: Message Title Emilio Escobar assigned an issue to Emilio Escobar Jenkins / JENKINS-19090 can't delete the project Change By: Emilio Escobar Assignee: Emilio Escobar 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-39436) Add sendServerVersion option
Title: Message Title Emilio Escobar updated an issue Jenkins / JENKINS-39436 Add sendServerVersion option Change By: Emilio Escobar Support sendServerVersion option to unset server version http header. There is a HTTP header which returns the Jetty server version:plata:winstone escoem$ curl -I https://JENKINS_SERVER/HTTP/1.1 302 FoundDate: Wed, 02 Nov 2016 13:32:14 GMTExpires: Thu, 01 Jan 1970 00:00:00 GMTLocation: https://JENKINS_SERVER/securityRealm/commenceLogin?from=%2F*Server: Jetty(9.2.z-SNAPSHOT)*Set-Cookie: JSESSIONID.dsaw=daseawew;Path=/;Secure;HttpOnlyX-Content-Type-Options: nosniffX-Hudson: 1.395X-Hudson-CLI-Port: 10081X-Jenkins: 2.7.4.4X-Jenkins-CLI-Host: IPX-Jenkins-CLI-Port: 10081X-Jenkins-CLI2-Port: 10081X-Jenkins-Session: dsawConnection: keep-aliveJetty support a configuration option for sending or not the Server version (by default is sent). 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
[JIRA] (JENKINS-39436) Add sendServerVersion option
Title: Message Title Emilio Escobar created an issue Jenkins / JENKINS-39436 Add sendServerVersion option Issue Type: New Feature Assignee: Emilio Escobar Components: winstone-jetty Created: 2016/Nov/02 10:43 AM Priority: Minor Reporter: Emilio Escobar Support sendServerVersion option to unset server version http header. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39436) Add sendServerVersion option
Title: Message Title Emilio Escobar started work on JENKINS-39436 Change By: Emilio Escobar Status: Open In Progress 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-38857) Three options (True, False, Cancel) for input step
Title: Message Title Emilio Escobar created an issue Jenkins / JENKINS-38857 Three options (True, False, Cancel) for input step Issue Type: New Feature Assignee: Unassigned Components: pipeline-input-step-plugin Created: 2016/Oct/10 10:40 AM Priority: Minor Reporter: Emilio Escobar it would be good to have three buttons (configurable), true, false and abort instead of def res = input message: 'Do you want to continue?', parameters: [[$class: 'BooleanParameterDefinition', defaultValue: false, description: 'Continue', name: 'res']] Thanks. Add Comment
[JIRA] (JENKINS-38504) Make AWS Cloudformation Plugin Pipeline compatible
Title: Message Title Emilio Escobar created an issue Jenkins / JENKINS-38504 Make AWS Cloudformation Plugin Pipeline compatible Issue Type: New Feature Assignee: Unassigned Components: jenkins-cloudformation Created: 2016/Sep/26 1:17 PM Priority: Minor Reporter: Emilio Escobar See the migration guide. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38418) Failed to load persisted workflow state (remote-loader)
Title: Message Title Emilio Escobar commented on JENKINS-38418 Re: Failed to load persisted workflow state (remote-loader) Sure @recampbell just build the pipeline and restart Jenkins while sleep is executed. 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-38418) Failed to load persisted workflow state (remote-loader)
Title: Message Title
Emilio Escobar commented on JENKINS-38418
Re: Failed to load persisted workflow state (remote-loader)
Oleg Nenashev Yes, I am.
Started by user anonymous
[Pipeline] node
Running on master in /jenkins-home/workspace/pi1
[Pipeline] {
[Pipeline] stage (Load a file from GitHub)
Using the ‘stage’ step without a block argument is deprecated
Entering stage Load a file from GitHub
Proceeding
[Pipeline] node
Running on master in /jenkins-home/workspace/pi1@2
[Pipeline] {
[Pipeline] dir
Running in /jenkins-home/workspace/pi1@2/libLoader
[Pipeline] {
[Pipeline] deleteDir
[Pipeline] echo
Checking out https://github.com/jenkinsci/workflow-remote-loader-plugin.git, branch=master
[Pipeline] checkout
Cloning the remote Git repository
Cloning repository https://github.com/jenkinsci/workflow-remote-loader-plugin.git
> git init /jenkins-home/workspace/pi1@2/libLoader # timeout=10
Fetching upstream changes from https://github.com/jenkinsci/workflow-remote-loader-plugin.git
> git --version # timeout=10
> git fetch --tags --progress https://github.com/jenkinsci/workflow-remote-loader-plugin.git +refs/heads/*:refs/remotes/origin/*
> git config remote.origin.url https://github.com/jenkinsci/workflow-remote-loader-plugin.git # timeout=10
> git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
> git config remote.origin.url https://github.com/jenkinsci/workflow-remote-loader-plugin.git # timeout=10
Fetching upstream changes from https://github.com/jenkinsci/workflow-remote-loader-plugin.git
> git fetch --tags --progress https://github.com/jenkinsci/workflow-remote-loader-plugin.git +refs/heads/*:refs/remotes/origin/*
> git rev-parse origin/master^{commit} # timeout=10
Checking out Revision 270024bf048c2210eabf0c5ff067476f55875727 (origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 270024bf048c2210eabf0c5ff067476f55875727
[Pipeline] echo
Loading from examples/fileLoader/helloworld.groovy
[Pipeline] load
[Pipeline] { (examples/fileLoader/helloworld.groovy)
[Pipeline] }
[Pipeline] // load
[Pipeline] deleteDir
[Pipeline] }
[Pipeline] // dir
[Pipeline] }
[Pipeline] // node
[Pipeline] sleep
Sleeping for 15 sec
[Pipeline] sh
[pi1] Running shell script
+ pwd
/jenkins-home/workspace/pi1
[Pipeline] sh
[pi1] Running shell script
+ sleep 10
[Pipeline] echo
Hello, world!
[Pipeline] stage (1)
Using the ‘stage’ step without a block argument is deprecated
Entering stage 1
Proceeding
[Pipeline] echo
here at stage1
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
Finished: SUCCESS
Add Comment
[JIRA] (JENKINS-38418) Failed to load persisted workflow state (remote-loader)
Title: Message Title
Emilio Escobar created an issue
Jenkins / JENKINS-38418
Failed to load persisted workflow state (remote-loader)
Issue Type:
Bug
Assignee:
Oleg Nenashev
Components:
pipeline, workflow-cps-plugin, workflow-remote-loader-plugin
Created:
2016/Sep/21 1:57 PM
Environment:
Version: 1.651.3 workflow-cps:2.17 workflow-cps-global-lib:2.3 workflow-job:2.6 workflow-remote-loader:1.3
Priority:
Minor
Reporter:
Emilio Escobar
The pipeline is unable to resume when using remote-loader-
node {
stage 'Load a file from GitHub'
def helloworld = fileLoader.fromGit('examples/fileLoader/helloworld', 'https://github.com/jenkinsci/workflow-remote-loader-plugin.git', 'master', null, '')
sleep 15
sh 'pwd'
sh 'sleep 10'
helloworld.printHello()
stage '1'
print 'here at stage1'
}
[Pipeline] End of Pipeline
java.io.IOException: Failed to load persisted workflow state
at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$3.onSuccess(CpsFlowExecution.java:585)
at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$3.onSuccess(CpsFlowExecution.java:583)
at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$4$1.run(CpsFlowExecution.java:626)
at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$1.run(CpsVmExecutorService.java:32)
at
