[JIRA] (JENKINS-48798) Error when using HP ALM Quality in a Post Build step
Title: Message Title Roy Lu commented on JENKINS-48798 Re: Error when using HP ALM Quality in a Post Build step Which post build step did you use? 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-48192) HP ALM SaaS 12.50 -"Cannot append QCSession cookies" error for Execute HP tests using HP ALM Lab Management" Build Step with HPE plugin version 5.2
Title: Message Title Roy Lu commented on JENKINS-48192 Re: HP ALM SaaS 12.50 -"Cannot append QCSession cookies" error for Execute HP tests using HP ALM Lab Management" Build Step with HPE plugin version 5.2 Is it still reproducible? How is it on 5.3? If still get the same error, please contact ALM RnD, you may need to provide ALM logs for investigation. 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-45979) test output is run together
Title: Message Title Roy Lu commented on JENKINS-45979 Re: test output is run together Which build step did you use? 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-46843) Run Cleanup Test Case if Test is Failed
Title: Message Title Roy Lu assigned an issue to xiwen zhao Jenkins / JENKINS-46843 Run Cleanup Test Case if Test is Failed Change By: Roy Lu Assignee: Roy Lu xiwen zhao 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-47061) Couldnt connect to HP AML v12.21 patch 5
Title: Message Title Roy Lu commented on JENKINS-47061 Re: Couldnt connect to HP AML v12.21 patch 5 How is it in 5.3? Could you provide the console output? 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-46741) Connection to ALM server by https refused
Title: Message Title Roy Lu commented on JENKINS-46741 Re: Connection to ALM server by https refused How is it now? You may need to check your credential. 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-21986) RunTestSet Function Within AlmTestSetsRunner.cs Incorrectly Setting Test Execution Duration
Title: Message Title Roy Lu commented on JENKINS-21986 Re: RunTestSet Function Within AlmTestSetsRunner.cs Incorrectly Setting Test Execution Duration xiwen zhao Heres' some advise on HPToolsLaucher which I don't understand. Please check and reply if you can. 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-22435) Unable to connect to ALM QC 11.5. Jenkins throws error saying "server is not available"
Title: Message Title Roy Lu commented on JENKINS-22435 Re: Unable to connect to ALM QC 11.5. Jenkins throws error saying "server is not available" I'll close it if no problem. 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-21987) RunTestSet Function Within AlmTestSetsRunner.cs Incorrectly Using Timeout Parameter
Title: Message Title Roy Lu commented on JENKINS-21987 Re: RunTestSet Function Within AlmTestSetsRunner.cs Incorrectly Using Timeout Parameter xiwen zhao Heres' some advise on HPToolsLaucher which I don't understand. Please check and reply if you can. 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-51098) Job Config History plugin by default saves all changes in Cluster Stats plugin log, which leads to high disk usage
Title: Message Title Alexandre Aubert created an issue Jenkins / JENKINS-51098 Job Config History plugin by default saves all changes in Cluster Stats plugin log, which leads to high disk usage Issue Type: Improvement Assignee: Mirko Friedenhagen Components: jobconfighistory-plugin Created: 2018-05-03 07:13 Environment: Windows XP SP3, Hudson 1.364, Job Config History 1.4, Global Build Stats 0.1-alpha4 Priority: Minor Reporter: Alexandre Aubert (This report should relate to both "jobconfighistory" and "global-build-stats" components but latter doesn't exist in Jira) 1. Global Build Stats plugin saves log into global-build-stats.xml in Hudson home directory. 2. Job Config History plugin saves copy of global-build-stats.xml for each change in it. Each copy of global-build-stats.xml takes about 1-3 Mb for my Hudson setup, so after few months of using both of pointed plugins "configuration history" for global-build-stats.xml took about 7 Gb of space. Solution for this issue is to add "global-build-stats" into "system configuration exclude file pattern" in Job Config History configuration (http://HUDSON/configure). My suggestion is to do one of: 1. Describe this issue on Global Build Stats/Job Config History plugins wiki. 2. Store log for Global Build Stats not in .xml file. Thanks
[JIRA] (JENKINS-51098) Job Config History plugin by default saves all changes in Cluster Stats plugin log, which leads to high disk usage
Title: Message Title Alexandre Aubert updated an issue Jenkins / JENKINS-51098 Job Config History plugin by default saves all changes in Cluster Stats plugin log, which leads to high disk usage Change By: Alexandre Aubert Environment: Windows XP SP3,Hudson 1 jenkins 2 . 364, 107.2 Job Config History 1 2 . 4, 18 Global Build Cluster Stats 0. 1-alpha4 4.6 (This report should relate to both "jobconfighistory" and "global-build-stats" components but latter doesn't exist in Jira)1. Global Build Stats plugin saves log into global-build-stats.xml in Hudson home directory.2. Job Config History plugin saves copy of global-build- cluster stats .xml plugin data for each change in it. (around every minute) Each copy of global-build-stats.xml takes about 1-3 10 Mb for my Hudson jenkins setup, so after few months days of using both of pointed plugins "configuration history" for global-build-stats.xml took about 7 20 Gb of space.Solution for this issue is to add " global cluster - build- stats" into "system configuration exclude file pattern" in Job Config History configuration (http:// HUDSON JENKINS /configure). My suggestion is It would also be nice to do one of:1. Describe describe this issue on Global Build Cluster Stats/Job Config History plugins wiki. 2. Store log for Global Build Stats not in .xml file. Thanks Add Comment
[JIRA] (JENKINS-21987) RunTestSet Function Within AlmTestSetsRunner.cs Incorrectly Using Timeout Parameter
Title: Message Title Roy Lu assigned an issue to Bogdan Girman Jenkins / JENKINS-21987 RunTestSet Function Within AlmTestSetsRunner.cs Incorrectly Using Timeout Parameter Change By: Roy Lu Assignee: Roy Lu Bogdan Girman 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-21986) RunTestSet Function Within AlmTestSetsRunner.cs Incorrectly Setting Test Execution Duration
Title: Message Title Roy Lu assigned an issue to Ofir Shaked Jenkins / JENKINS-21986 RunTestSet Function Within AlmTestSetsRunner.cs Incorrectly Setting Test Execution Duration Change By: Roy Lu Assignee: Roy Lu Ofir Shaked 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-21987) RunTestSet Function Within AlmTestSetsRunner.cs Incorrectly Using Timeout Parameter
Title: Message Title Roy Lu assigned an issue to Evan Chen Jenkins / JENKINS-21987 RunTestSet Function Within AlmTestSetsRunner.cs Incorrectly Using Timeout Parameter Change By: Roy Lu Assignee: Bogdan Girman Evan Chen 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-51099) Poll SCM Schedule "every minute * * * * *" displays wrong hint
Title: Message Title Morris Yang created an issue Jenkins / JENKINS-51099 Poll SCM Schedule "every minute * * * * *" displays wrong hint Issue Type: Bug Assignee: Unassigned Attachments: report.png, report2.png, report3.png Components: core Created: 2018-05-03 07:25 Environment: Jenkins ver. 2.107.2 Priority: Minor Reporter: Morris Yang I try to set the short period for testing configruation. If set small than 5 minutes, the display text make me confused. There are some test cases. * * * * * */1 * * * * H/2 * * * * The result is wrong in high probability. Thanks
[JIRA] (JENKINS-21986) RunTestSet Function Within AlmTestSetsRunner.cs Incorrectly Setting Test Execution Duration
Title: Message Title Roy Lu assigned an issue to Evan Chen Jenkins / JENKINS-21986 RunTestSet Function Within AlmTestSetsRunner.cs Incorrectly Setting Test Execution Duration Change By: Roy Lu Assignee: Ofir Shaked Evan Chen 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-46843) Run Cleanup Test Case if Test is Failed
Title: Message Title Roy Lu assigned an issue to Evan Chen Jenkins / JENKINS-46843 Run Cleanup Test Case if Test is Failed Change By: Roy Lu Assignee: xiwen zhao Evan Chen 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-51100) Jenkins multibranch pipeline keeps scheduling jobs to new nodes
Title: Message Title Esben Nielsen created an issue Jenkins / JENKINS-51100 Jenkins multibranch pipeline keeps scheduling jobs to new nodes Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2018-05-03 07:45 Environment: Linux System Properties Name ↓ Value awt.toolkit sun.awt.X11.XToolkit BUILD_TIMESTAMP 2018-05-03 09:42:22 CEST com.sun.akuma.Daemon daemonized executable-war /usr/lib/jenkins/jenkins.war file.encoding UTF-8 file.encoding.pkg sun.io file.separator / java.awt.graphicsenv sun.awt.X11GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.print.PSPrinterJob java.class.path /usr/lib/jenkins/jenkins.war java.class.version 52.0 java.endorsed.dirs /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-2.b14.fc22.x86_64/jre/lib/endorsed java.ext.dirs /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-2.b14.fc22.x86_64/jre/lib/ext:/usr/java/packages/lib/ext java.home /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-2.b14.fc22.x86_64/jre java.io.tmpdir /tmp java.library.path /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib java.runtime.name OpenJDK Runtime Environment java.runtime.version 1.8.0_91-b14 java.specification.name Java Platform API Specification java.specification.vendor Oracle Corporation java.specification.version 1.8 java.vendor Oracle Corporation java.vendor.url http://java.oracle.com/ java.vendor.url.bug http://bugreport.sun.com/bugreport/ java.version 1.8.0_91 java.vm.info mixed mode java.vm.name OpenJDK 64-Bit Server VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendor Oracle Corporation java.vm.specification.version 1.8 java.vm.vendor Oracle Corporation java.vm.version 25.91-b14 jenkins.branch.WorkspaceLocatorImpl.PATH_MAX 1 JENKINS_HOME /dsk1/scbuild/work_SCNXT_REDUNDANT_CP4_merge_to_master/buildserver/jenkins2/config jna.loaded true jna.platform.library.path /usr/lib64:/lib64:/usr/lib:/lib:/usr/lib/vmware-tools/lib64/libvmGuestLibJava.so:/usr/lib/vmware-tools/lib32/libvmGuestLibJava.so:/usr/lib/vmware-tools/lib64/libvmGuestLib.so:/usr/lib/vmware-tools/lib32/libvmGuestLib.so:/usr/lib64/atlas:/usr/lib64/dyninst:/usr/lib64/mysql:/usr/lib64/iscsi:/usr/lib64/bind99:/usr/lib64/llvm:/usr/lib64/tcl8.6:/usr/lib/vmware-tools/lib64/libDeployPkg.so:/usr/lib/vmware-tools/lib32/libDeployPkg.so jnidispatch.path /tmp/jna-1643019237/jna612827273317987997.tmp line.separator mail.smtp.sendpartial true mail.smtps.sendpartial true os.arch amd64 os.name Linux os.version 4.4.14-200.fc22.x86_64 path.separator : sun.arch.data.model 64 sun.boot.class.path /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-2.b14.
[JIRA] (JENKINS-51083) += doesn't append to list
Title: Message Title Michael Werner commented on JENKINS-51083 Re: += doesn't append to list Actually i can reproduce the problem with << and .add(). The size of the list is 2 in my example, so the object gets added. If i use a String in instead of the class TemplateParameter then this problem does not occur. I think the problem is maybe not related to the addition of another object. 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-51093) Custom WAR Packager - Support building with versions from Incrementals repo
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51093 Re: Custom WAR Packager - Support building with versions from Incrementals repo Code changed in jenkins User: Oleg Nenashev Path: custom-war-packager-lib/src/main/java/io/jenkins/tools/warpackager/lib/impl/MavenHPICustomWARPOMGenerator.java custom-war-packager-lib/src/main/java/io/jenkins/tools/warpackager/lib/impl/MavenWARPackagePOMGenerator.java custom-war-packager-lib/src/main/java/io/jenkins/tools/warpackager/lib/impl/POMGenerator.java custom-war-packager-maven-plugin/src/it/incrementals/config.yml custom-war-packager-maven-plugin/src/it/incrementals/invoker.properties custom-war-packager-maven-plugin/src/it/incrementals/pom.xml http://jenkins-ci.org/commit/custom-war-packager/ace264d18f02b858f1d07727a76fce9a72ffb130 Log: JENKINS-51093 - Add support of artifacts from Incrementals repo (JEP-305) 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-51093) Custom WAR Packager - Support building with versions from Incrementals repo
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51093 Re: Custom WAR Packager - Support building with versions from Incrementals repo Code changed in jenkins User: Oleg Nenashev Path: custom-war-packager-lib/src/main/java/io/jenkins/tools/warpackager/lib/impl/MavenHPICustomWARPOMGenerator.java custom-war-packager-lib/src/main/java/io/jenkins/tools/warpackager/lib/impl/MavenWARPackagePOMGenerator.java custom-war-packager-lib/src/main/java/io/jenkins/tools/warpackager/lib/impl/POMGenerator.java custom-war-packager-maven-plugin/src/it/incrementals/config.yml custom-war-packager-maven-plugin/src/it/incrementals/invoker.properties custom-war-packager-maven-plugin/src/it/incrementals/pom.xml http://jenkins-ci.org/commit/custom-war-packager/8aff49abcbeab381202a74b3d28d605465ac580f Log: Merge pull request #23 from oleg-nenashev/incrementals JENKINS-51093 - Add support of artifacts from Incrementals repo (JEP-305) Compare: https://github.com/jenkinsci/custom-war-packager/compare/b3a78a6829ce...8aff49abcbea *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. 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-51101) MC Wizard dialog shows empty during the first time successfully login.
Title: Message Title Mia Chen created an issue Jenkins / JENKINS-51101 MC Wizard dialog shows empty during the first time successfully login. Issue Type: Bug Assignee: Ofir Shaked Attachments: image-2018-05-03-16-59-40-921.png Components: hp-application-automation-tools-plugin Created: 2018-05-03 09:01 Labels: MobileCenter Priority: Major Reporter: Mia Chen General Description: MC Wizard dialog shows empty during the first time successfully login, and if we click the 'DEVICE' tab once again, the dialog will be reloaded successfully. Steps to reproduce: 1. login jenkins and update the plugin for automation script execution; 2. go to configuration of Jenkins to add MC server 3. go to configuration of project and select the added MC server 4. click on MC wizard. 5. Input user name and password, login MC Server. Expected: After successfully login, the device information will be loaded successfully. Actual: After successfully login, the dialog shows 'Empty', as below:
[JIRA] (JENKINS-51098) Job Config History plugin by default saves all changes in Cluster Stats plugin log, which leads to high disk usage
Title: Message Title Jochen Gietzen assigned an issue to Jochen Gietzen Jenkins / JENKINS-51098 Job Config History plugin by default saves all changes in Cluster Stats plugin log, which leads to high disk usage Change By: Jochen Gietzen Assignee: Mirko Friedenhagen Jochen Gietzen 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-50176) Locked resources using the variable parameter do not get reset to the variable once released to another requester and only appear as null on subsequent locks
Title: Message Title Jeroen Bogers commented on JENKINS-50176 Re: Locked resources using the variable parameter do not get reset to the variable once released to another requester and only appear as null on subsequent locks Issue is also solved in PR #87 which has already been merged to master. Waiting for next release now. 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-51098) Job Config History plugin by default saves all changes in Cluster Stats plugin log, which leads to high disk usage
Title: Message Title Jochen Gietzen resolved as Done We added a hint to the Wiki-Page of Job Config History. If you want it to be placed on the Wiki-Page of Cluster Stats, please contact them directly. Jenkins / JENKINS-51098 Job Config History plugin by default saves all changes in Cluster Stats plugin log, which leads to high disk usage Change By: Jochen Gietzen Status: Open Resolved Resolution: Done 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
[JIRA] (JENKINS-51102) need to restart jenkins service often
Title: Message Title Parag Hiralikar created an issue Jenkins / JENKINS-51102 need to restart jenkins service often Issue Type: Task Assignee: Unassigned Components: slave-status-plugin Created: 2018-05-03 09:19 Priority: Major Reporter: Parag Hiralikar i need to restart jenkins service on slaves very often whenver nodes shows offline Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51103) Sometimes failed to save the information into jenkins job after selecting required information on wizard dialog.
Title: Message Title Mia Chen created an issue Jenkins / JENKINS-51103 Sometimes failed to save the information into jenkins job after selecting required information on wizard dialog. Issue Type: Bug Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 2018-05-03 09:22 Labels: MobileCenter Priority: Minor Reporter: Mia Chen General Description: Sometimes failed to save the information into jenkins job after selecting required information on wizard dialog. Steps to recreate: 1. login jenkins and update the plugin for automation script execution; 2. go to configuration of Jenkins to add MC server 3. go to configuration of project and select the added MC server 4. click on MC wizard. 5. select specific device and AUT action 6. click on save and close button. expect result: selection should be saved actual result: no information saved, it shows as 'Undefined'. MC server Version: MC 2.70 build 10512 plugin: 5.4 Add Comment
[JIRA] (JENKINS-51093) Custom WAR Packager - Support building with versions from Incrementals repo
Title: Message Title Oleg Nenashev updated JENKINS-51093 Jenkins / JENKINS-51093 Custom WAR Packager - Support building with versions from Incrementals repo Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed 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-51104) Error message 'MC lognin information or proxy is incorrect.' shows up for successful login.
Title: Message Title Mia Chen created an issue Jenkins / JENKINS-51104 Error message 'MC lognin information or proxy is incorrect.' shows up for successful login. Issue Type: Bug Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 2018-05-03 09:29 Labels: MobileCenter Priority: Minor Reporter: Mia Chen General Description: Error message 'MC lognin information or proxy is incorrect.' shows up for successful login. Steps to recreate: 1. login jenkins and update the plugin for automation script execution; 2. go to configuration of Jenkins to add MC server 3. go to configuration of project and select the added MC server 4. click on MC wizard. 5. login the MC Server with incorrect password. 6. Error message appears as expected: 'MC lognin information or proxy is incorrect' 6. Input the correct user name and password. expect result: Login successfully, and the error message disappeared. actual result: Login successfully, but the error message still there. MC server Version: MC 2.70 build 10512 plugin: 5.4
[JIRA] (JENKINS-51102) need to restart jenkins service often
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-51102 need to restart jenkins service often Change By: Oleg Nenashev Component/s: _unsorted Component/s: slave-status-plugin 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-51102) need to restart jenkins service often
Title: Message Title Oleg Nenashev commented on JENKINS-51102 Re: need to restart jenkins service often The issue is not diagnosable in the current state. Please follow the guidelines here: https://wiki.jenkins.io/display/JENKINS/How+to+report+an+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-51098) Job Config History plugin by default saves all changes in Cluster Stats plugin log, which leads to high disk usage
Title: Message Title Alexandre Aubert commented on JENKINS-51098 Re: Job Config History plugin by default saves all changes in Cluster Stats plugin log, which leads to high disk usage Perfect ! Thanks for your reactivity ! 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-28332) Warn when java version not compatible with upgrade
Title: Message Title Rene Affourtit closed an issue as Won't Do Closing ancient issue. As Daniel stated, read the release notes. Jenkins / JENKINS-28332 Warn when java version not compatible with upgrade Change By: Rene Affourtit Status: Open Closed Resolution: Won't Do 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
[JIRA] (JENKINS-40192) java.io.IOException: Cannot run program "git" (in directory "/home/jenkins/workspace/pipeline"): error=2, No such file or directory
Title: Message Title Huseyin Yurtseven commented on JENKINS-40192 Re: java.io.IOException: Cannot run program "git" (in directory "/home/jenkins/workspace/pipeline"): error=2, No such file or directory Nicolas De Loof same issue happens to me. I checked which git and echo $PATH they seem ok, i alse checked echo git --help it shows the help instructions but the error still be there like: ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: Could not init /var/lib/jenkins/workspace/blutv.com.tr/develop at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$5.execute(CliGitAPIImpl.java:772) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:564) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1120) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1160) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:113) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:85) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:75) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: hudson.plugins.git.GitException: Error performing command: git init /var/lib/jenkins/workspace/blutv.com.tr/develop at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2003) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1964) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1960) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1597) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$5.execute(CliGitAPIImpl.java:770) ... 14 more Caused by: java.io.IOException: Cannot run program "git" (in directory "/var/lib/jenkins/workspace/blutv.com.tr/develop"): error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at hudson.Proc$LocalProc.(Proc.java:249) at hudson.Proc$LocalProc.(Proc.java:218) at hudson.Launcher$LocalLauncher.launch(Launcher.java:929) at hudson.Launcher$ProcStarter.start(Launcher.java:449) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1992) ... 18 more Caused by: java.io.IOException: error=2, No such file or directory at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.(UNIXProcess.java:247) at java.lang.ProcessImpl.start(ProcessImpl.java:134) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) ... 23 more
[JIRA] (JENKINS-50888) NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information
Title: Message Title Reinhold Füreder commented on JENKINS-50888 Re: NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information Yes, I am with Tom Ghyselinck, it still happens and exactly as Tom writes: "this issue was not fixed for me" "I still see the errors when changing build information in older builds (which do not show up in the stage view). Please note that it are builds that were started with plugin version 2.20 installed." However, in contrast to him I solely updated the two attached HPI files (and have not installed other required plugin updates in the last ~1-2 weeks) 2018-05-03 12:18:33 WARNING [org.eclipse.jetty.server.handler.ContextHandler$Context log] Error while serving https://***/job/ACME-Pipeline%20(Branch)/801/submitDescription java.lang.reflect.InvocationTargetException at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:347) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:860) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:225) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.ja
[JIRA] (JENKINS-50888) NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information
Title: Message Title
Reinhold Füreder edited a comment on JENKINS-50888
Re: NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information
Yes, I am with [~tom_ghyselinck], it still happens and exactly as Tom writes:* "this issue was not fixed for me"* "I still see the errors when changing build information in older builds (which do not show up in the stage view). Please note that it are builds that were started with plugin version 2.20 installed."* However, in contrast to him I solely updated the two attached HPI files (and have not installed other required plugin updates in the last ~ 1- 2 weeks : last plugin updates are from 2018-04-19 07:15:58; while core is up-to-date 2.119 ){noformat}2018-05-03 12:18:33 WARNING [org.eclipse.jetty.server.handler.ContextHandler$Context log] Error while serving https://***/job/ACME-Pipeline%20(Branch)/801/submitDescriptionjava.lang.reflect.InvocationTargetExceptionat org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:347)at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77)at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26)at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184)at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117)at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129)at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715)at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845)at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374)at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715)at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845)at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:248)at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715)at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845)at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)at org.kohsuke.stapler.Stapler.service(Stapler.java:238)at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:860)at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650)at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154)at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:225)at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151)at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134)at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151)at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61)at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151)at jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:125)at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151)at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157)at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1637)at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:99)at org.eclipse.jetty.servlet.ServletHandler$CachedChain
[JIRA] (JENKINS-50888) NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information
Title: Message Title Reinhold Füreder commented on JENKINS-50888 Re: NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information And also exactly as Tom Ghyselinck described, adding the logger did not change anything and led to NO additional logging whatsoever. And I can view the build in Blue Ocean without any problems I must admit however, that I don't understand this item in your comment: 4. Update the custom log result (take a support bundle and grab it out of that if needed). Please note that I am now updating all Jenkins plugins (at long last) to the very latest and thus also replace the two attached manual installed ones... 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-47427) Poll per change with pipeline jobs
Title: Message Title Daniel Hagström commented on JENKINS-47427 Re: Poll per change with pipeline jobs Bad news, I'm afraid. As far as I can tell, the update introduced some problematic behaviour. I'll try to explain with a example. In a project that polls once per minute and a build taking ~2-3 minutes, submits happen with the following timings: Changelist @1 is submitted, which triggers a build, #1, within a minute. All good. During building of #1 with changelist @1, changelists @2 and @3 are submitted. The multibranch polling log has this: Changes detected: master (1 → 3) Scheduled build for branch: master When #1 is done, build #2 starts. Only changelist @2 is included in the build, as it should with incremental builds. The console output of the actual build job has this: 00:00:00.849 ... p4 change -o 3 + 00:00:00.860 ... p4 describe -s 3 + 00:00:00.872 ... found change: 3 00:00:00.872 ... p4 change -o 2 + 00:00:00.882 ... p4 describe -s 2 + 00:00:00.893 ... found change: 2 However, after automatically triggering #2 with @2, the multibranch polling log has this: ... p4 files -e //redacted/master/Jenkinsfile_Android + ‘Jenkinsfile_Android’ found ... p4 changes -m1 //redacted/master/... + No changes detected: master (still at 3) And no further builds are automatically triggered. That's a problem. If at this point I manually trigger another build, #3, it has @3 only, so the incremental build-functionality "works". However, we keep lagging behind, with the rate of one submit per submit more than the first 1 during building. The polling log seems to note the highest number it has seen when polling, not the highest the job has built. So, in reality, if we have more changelists than we can build over a given time, we're still not getting incremental builds. We're getting incremental builds that as time goes on lags more and more behind, unless somebody manually triggers builds, one for each submit not included in the polling. That's not very useful. Thoughts? ping Karl Wirth Add Comment
[JIRA] (JENKINS-48933) Unstoppable Multibranch Pipeline Scan
Title: Message Title rsandell commented on JENKINS-48933 Re: Unstoppable Multibranch Pipeline Scan Did a quick dive into the depths of JGit and there are possibilities to specify connection and read timeouts, but the Jenkins git-client-plugin doesn't provide any facilities to set it from what I can see. Strange though that JGit doesn't respond to any Thread.interrupt(), from what I could see there are no explicit checks for it. As a workaround have you tried switching to cli git instead of using JGit? 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-43568) readProperties java.exe locks properties file
Title: Message Title rsandell commented on JENKINS-43568 Re: readProperties java.exe locks properties file Daniel Baum What version are you on? This issue should have been fixed in 1.4.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-51003) Allow non-administrators to use "Query and Trigger Gerrit Patches"
Title: Message Title rsandell commented on JENKINS-51003 Re: Allow non-administrators to use "Query and Trigger Gerrit Patches" You can give the manual trigger permission to anyone. The code path you are linking to only shows that the permission is implicitly set for administrators. 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-51003) Allow non-administrators to use "Query and Trigger Gerrit Patches"
Title: Message Title rsandell closed an issue as Won't Fix Jenkins / JENKINS-51003 Allow non-administrators to use "Query and Trigger Gerrit Patches" Change By: rsandell Status: Open Closed Resolution: Won't Fix 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-43568) readProperties java.exe locks properties file
Title: Message Title Daniel Baum commented on JENKINS-43568 Re: readProperties java.exe locks properties file We are on version 1.3.0. Thanks for the reply. I will upgrade when we have a chance to test the build and see if that fixes it. 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-50080) Integration Test for Remote API
Title: Message Title Manuel Hampp assigned an issue to Manuel Hampp Jenkins / JENKINS-50080 Integration Test for Remote API Change By: Manuel Hampp Assignee: Ulli Hafner Manuel Hampp 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-50080) Integration Test for Remote API
Title: Message Title Manuel Hampp started work on JENKINS-50080 Change By: Manuel Hampp 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-50345) Exclude Jobs managed by JobDSL from config history?
Title: Message Title Jochen Gietzen resolved as Won't Fix So, since the created jobs aren't of a specific dslJob type, you cannot simply exclude those jobs, created by the dslJob Plugin. Workaround: You can exclude changes by Users. I looked up (on my local machine) which user the dslJob Plugin uses. Seems to be the SYSTEM user. So by putting the userId of SYSTEM in the Exclude users field in the Jenkins Configuration (/configure ) one should be able to avoid detecting the dslJob generated Jobs. But: As soon as a user changes something, he will get everything the dslJob Plugin did written to his change. And you might exclude other Plugins, using the SYSTEM user as well. There might be a possibility. If you are interested in it, please give a seperate Issue or as a Pull Request: It might be possible to integrate a pattern exclusion for the names of the job. If your dsl generated Jobs are called "my-wonderful-dsl-job-nr-1.dslJOB" and "my-perfect-dsl-job-nr-30.dslJOB" you could then exclude it by giving a pattern like ".+.dslJOB.*" (just e.g.). This could help, iff your dsl generated jobs were named consistently. But please consider, that this would exclude every change of the job, regardless of whom did those. Jenkins / JENKINS-50345 Exclude Jobs managed by JobDSL from config history? Change By: Jochen Gietzen Status: Open Resolved Resolution: Won't Fix Add Comment
[JIRA] (JENKINS-50084) Integration Test for ReferenceFinder
Title: Message Title Arne Schöntag updated an issue Jenkins / JENKINS-50084 Integration Test for ReferenceFinder Change By: Arne Schöntag Reference JobTestfälle:Angabe in Konfiguration: Nicht Vorhandener Job -> Fehler Vorhandener Job -> Ok Zirkuläre Abhängigkeit? - self -> self - self -> otherBuild ...-> self Fehler in der Anzeige der Konfiguration?Build Status abhängig vom Status des Reference Jobs: ReferenceJob ok -> Grün (Success) ReferenceJob failed -> Gelb (instabil) ReferenceJob ok (aber instabil) -> Gelb (instabil) oder Grün (Success)? ReferenceJob existiert nicht (z.b. gelöscht oder umbenannt oder Fehlerhaft gespeichert) -> Rot (Failed), Gelb (Instabil) oder Grün (Success)? 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-issu
[JIRA] (JENKINS-50084) Integration Test for ReferenceFinder
Title: Message Title Arne Schöntag commented on JENKINS-50084 Re: Integration Test for ReferenceFinder Testfälle, die mir spontan eingefallen sind hinzugefügt. 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-50084) Integration Test for ReferenceFinder
Title: Message Title Arne Schöntag edited a comment on JENKINS-50084 Re: Integration Test for ReferenceFinder Testfälle, die mir spontan eingefallen sind in die Description hinzugefügt. 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-50084) Integration Test for ReferenceFinder
Title: Message Title Arne Schöntag updated an issue Jenkins / JENKINS-50084 Integration Test for ReferenceFinder Change By: Arne Schöntag Reference JobTestfälle:Angabe in Konfiguration: Nicht Vorhandener Job -> Fehler Vorhandener Job -> Ok Zirkuläre Abhängigkeit? - self -> zu self - self -> zu otherBuild ... -> zu self Fehler in der Anzeige der Konfiguration?Build Status abhängig vom Status des Reference Jobs: ReferenceJob ok -> Grün (Success) ReferenceJob failed -> Gelb (instabil) ReferenceJob ok (aber instabil) -> Gelb (instabil) oder Grün (Success)? ReferenceJob existiert nicht (z.b. gelöscht oder umbenannt oder Fehlerhaft gespeichert) -> Rot (Failed), Gelb (Instabil) oder Grün (Success)? 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
[JIRA] (JENKINS-50084) Integration Test for ReferenceFinder
Title: Message Title Arne Schöntag updated an issue Jenkins / JENKINS-50084 Integration Test for ReferenceFinder Change By: Arne Schöntag Reference JobTestfälle:Angabe in Konfiguration: Nicht Vorhandener Job / Illegale Eingabe -> Fehler Vorhandener Job -> Ok Zirkuläre Abhängigkeit? - self zu self - self zu otherBuild ...zu self Fehler in der Anzeige der Konfiguration?Build Status abhängig vom Status des Reference Jobs: ReferenceJob ok -> Grün (Success) ReferenceJob failed -> Gelb (instabil) ReferenceJob ok (aber instabil) -> Gelb (instabil) oder Grün (Success)? ReferenceJob existiert nicht (z.b. gelöscht oder umbenannt oder Fehlerhaft gespeichert) -> Rot (Failed), Gelb (Instabil) oder Grün (Success)? 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 em
[JIRA] (JENKINS-50084) Integration Test for ReferenceFinder
Title: Message Title Arne Schöntag updated an issue Jenkins / JENKINS-50084 Integration Test for ReferenceFinder Change By: Arne Schöntag Reference JobTestfälle: Angabe in Konfiguration: Nicht Vorhandener Job Ignore Previous Result + / Illegale Eingabe - > Fehler Vorhandener Job Overall Success +/ - > Ok Zirkuläre Abhängigkeit? - self zu self - self zu otherBuild ...zu self Fehler in der Anzeige der Konfiguration?Build Status abhängig vom Status des Reference Jobs: Job ReferenceJob ok -> Grün (Success) ReferenceJob failed -> Gelb (instabil) ReferenceJob ok (aber instabil) -> Gelb (instabil) oder Grün (Success)? ReferenceJob existiert nicht (z.b. gelöscht oder umbenannt oder Fehlerhaft gespeichert) -> Rot (Failed), Gelb (Instabil) oder Grün (Success)? Vergleich mit einem anderen Build 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 "J
[JIRA] (JENKINS-51105) JEP-200 compatibility for ClearCase UCM Plugin
Title: Message Title Christopher Shannon created an issue Jenkins / JENKINS-51105 JEP-200 compatibility for ClearCase UCM Plugin Issue Type: Bug Assignee: Praqma Support Components: clearcase-ucm-plugin Created: 2018-05-03 12:57 Environment: Jenkins 2.107.1 ClearCase UCM Plugin 1.7.0 Labels: JEP-200 Priority: Critical Reporter: Christopher Shannon Many of these seen, but all seemingly related to net.praqma.clearcase.ucm.entities.Stream. SEVERE: Failed to save build record java.io.IOException: java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class hudson.model.FreeStyleBuild at hudson.XmlFile.write(XmlFile.java:200) at hudson.model.Run.save(Run.java:1923) at hudson.model.Run.execute(Run.java:1784) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Caused by: java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class hudson.model.FreeStyleBuild at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) a
[JIRA] (JENKINS-51106) Empty BufferedReader is returned if we use Java API of Timestamper plug-in without using appendLog param
Title: Message Title Dinesh Reddy created an issue Jenkins / JENKINS-51106 Empty BufferedReader is returned if we use Java API of Timestamper plug-in without using appendLog param Issue Type: Bug Assignee: Steven G Brown Components: timestamper-plugin Created: 2018-05-03 12:59 Priority: Minor Reporter: Dinesh Reddy Based on the given documentation, I have tried to use Timestamper Java API to access the build log including the plain timestamps. BufferedReader reader = TimestamperAPI.get().read(currentBuild,"time=HH:mm:ss") But, I am receiving an empty buffer. After checking the out timestamper plug-in code and debugging the code, I understood that we need to pass "appendLog" param also to get the proper BufferedReader. So the modified code I am using right now is something like below. BufferedReader reader = TimestamperAPI.get().read(currentBuild,"time=HH:mm:ss&appendLog") Add Comment
[JIRA] (JENKINS-51107) Paused for input is displayed even though I don't have Job.BUILD permission
Title: Message Title Vincent Latombe updated an issue Jenkins / JENKINS-51107 Paused for input is displayed even though I don't have Job.BUILD permission Change By: Vincent Latombe Issue Type: Improvement Bug 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-51107) Paused for input is displayed even though I don't have Job.BUILD permission
Title: Message Title Vincent Latombe created an issue Jenkins / JENKINS-51107 Paused for input is displayed even though I don't have Job.BUILD permission Issue Type: Improvement Assignee: Unassigned Components: pipeline-input-step-plugin Created: 2018-05-03 13:20 Priority: Minor Reporter: Vincent Latombe On a build where I don't have Job.BUILD permission, the manual approval action is displayed anyway (regular pipeline, and BO as well). When I click on the approval, obviously it fails, complaining that I don't have the required permission. The actions should be hidden or appear differently so that an approval can't even be requested Add Comment
[JIRA] (JENKINS-50224) Pipeline stage view not displaying Stages
Title: Message Title Hartmut Schreiber commented on JENKINS-50224 Re: Pipeline stage view not displaying Stages Same issue for two other instances of v2.107.2. 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-47427) Poll per change with pipeline jobs
Title: Message Title W Basu closed an issue as Fixed Released in 1.8.10 Jenkins / JENKINS-47427 Poll per change with pipeline jobs Change By: W Basu Status: Resolved Closed 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-49474) Hash the Perforce ticket when saving it in the Credentials.xml
Title: Message Title W Basu closed an issue as Fixed Released in 1.8.10 Jenkins / JENKINS-49474 Hash the Perforce ticket when saving it in the Credentials.xml Change By: W Basu Status: Resolved Closed 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-44706) Tracking of P4 Credentials is slowing down REST API queries
Title: Message Title W Basu closed an issue as Fixed Released in 1.8.10 Jenkins / JENKINS-44706 Tracking of P4 Credentials is slowing down REST API queries Change By: W Basu Status: Resolved Closed Assignee: Paul Allen 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-51091) Make test results available on currentBuild
Title: Message Title
Sean MacKay commented on JENKINS-51091
Re: Make test results available on currentBuild
Interesting, so do none of the test results pages in normal or Blue Ocean UI function without the junit plugin? Or is the way the data is eventually saved into the finished build just even harder to access? I assumed the workaround with AbstractTestResultAction pulled the results from the same final location which both nunit and junit post to, but I haven't tested to confirm so I'm not sure. And that's interesting. I assume you could use it in a scripting pipeline like this. Does the same work in Declarative pipeline?
def results = junit '*.xml';
sh "echo ${results.getFailCount()}"
Unfortunately the `nunit` plugin doesn't seem to behave the same way (I use both). Yet it still posts the results to the same final place, so those results should still be available from one location regardless of which plugin posts there. That's why I assumed there would be a way to read them, but I don't know enough about the architecture in place to really be sure of anything. I'll do some testing and see if I can at least confirm what the behaviour of each approach is.
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 unsubsc
[JIRA] (JENKINS-50434) Misbehaviour of feature: Pin the workspace to the build host
Title: Message Title W Basu updated an issue Jenkins / JENKINS-50434 Misbehaviour of feature: Pin the workspace to the build host Change By: W Basu Labels: P4_A P4_B 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-47427) Poll per change with pipeline jobs
Title: Message Title Karl Wirth reopened an issue Original fix was released but reports that fix does not build correctly. We are investigating. Jenkins / JENKINS-47427 Poll per change with pipeline jobs Change By: Karl Wirth Resolution: Fixed Status: Closed Reopened 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://
[JIRA] (JENKINS-47427) Poll per change with pipeline jobs
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-47427 Poll per change with pipeline jobs Change By: Karl Wirth Labels: P4_A P4_SUPPORT 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-50434) Misbehaviour of feature: Pin the workspace to the build host
Title: Message Title
Karl Wirth commented on JENKINS-50434
Re: Misbehaviour of feature: Pin the workspace to the build host
Proving very difficult to fix. The concept of a job having different workspaces is alien to Jenkins so the correct information is currently not (and unlikely to ever be) provided to P4Jenkins to clean up properly. For now we are going to have to recommend that pin at build host is no longer used and {NODE_NAME} is used in workspace name instead.
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-50080) Integration Test for Remote API
Title: Message Title Ulli Hafner commented on JENKINS-50080 Re: Integration Test for Remote API Vielleicht können Sie die Methode aus unserer UI Test Suite integrieren. 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-50408) Highlight difficult to see after clicking on stage
Title: Message Title Chad Bercea updated an issue Jenkins / JENKINS-50408 Highlight difficult to see after clicking on stage Change By: Chad Bercea Attachment: Screen Shot 2018-05-03 at 9.49.49 AM.png 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-50888) NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-50888 NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information Change By: Sam Van Oort Attachment: workflow-cps.hpi 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-50888) NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information
Title: Message Title Sam Van Oort commented on JENKINS-50888 Re: NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information Reinhold Füreder Tom Ghyselinck Reproduced this – having eliminated all the other possibilities made it quick. This enables what should be the final fix, which enables serializing even if the execution was never loaded. Please try the attached SNAPSHOT – it should be released to the update center soon but that will take a few hours to be publicly available. workflow-cps.hpi 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-50408) Highlight difficult to see after clicking on stage
Title: Message Title Chad Bercea commented on JENKINS-50408 Re: Highlight difficult to see after clicking on stage Nicolae Pascu I am in favor of using the blue we are deploying in the system in a 2px stroke or border, roughly 2px larger than the object "selected" giving a little space. I tried red and orange but it ended up looking like an error and yellow was too low contrast. Blue feels safe and having the line not touch the object creates a visual break. I anticipate this being enough of a touch to show a "selected state" while also not distracting the user from their work. 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-50692) Allow incrementals deployment from core
Title: Message Title Jesse Glick updated JENKINS-50692 Merged toward 2.120. Jenkins / JENKINS-50692 Allow incrementals deployment from core Change By: Jesse Glick Status: In Review Resolved Resolution: Fixed 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-50692) Allow incrementals deployment from core
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50692 Re: Allow incrementals deployment from core Code changed in jenkins User: Jesse Glick Path: .gitignore .mvn/extensions.xml .mvn/maven.config Jenkinsfile cli/pom.xml core/pom.xml pom.xml test/pom.xml war/pom.xml http://jenkins-ci.org/commit/jenkins/3fb17fb0bbb824a6c929af3809022c280cb6270a Log: JENKINS-50692 INFRA-1571 #3394: JEP-305 Incrementals in core *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. 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-48933) Unstoppable Multibranch Pipeline Scan
Title: Message Title Kevin Lannen commented on JENKINS-48933 Re: Unstoppable Multibranch Pipeline Scan ++We have used both JGit and the cli git and both have this issue. We would prefer to use cli git as it seems to be more reliable in other areas but it seemed to hang more during branch indexing then JGit does. 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-48933) Unstoppable Multibranch Pipeline Scan
Title: Message Title Kevin Lannen edited a comment on JENKINS-48933 Re: Unstoppable Multibranch Pipeline Scan ++ We have used both JGit and the cli git and both have this issue. We would prefer to use cli git as it seems to be more reliable in other areas but it seemed to hang more during branch indexing then JGit does. 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-51094) Custom WAR Packager - Support building with LATEST versions from Incrementals repo
Title: Message Title Raul Arabaolaza commented on JENKINS-51094 Re: Custom WAR Packager - Support building with LATEST versions from Incrementals repo IMO this is not blocking JENKINS-51008 as long as JENKINS-50953 is done 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-51109) Allow incremental releases in Stapler
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-51109 Allow incremental releases in Stapler Issue Type: Improvement Assignee: Unassigned Components: core Created: 2018-05-03 14:26 Labels: stapler Priority: Minor Reporter: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51109) Allow incremental releases in Stapler
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-51109 Allow incremental releases in Stapler Change By: Oleg Nenashev Assignee: Oleg Nenashev 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-51108) Allow incrementals releases in Remoting
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-51108 Allow incrementals releases in Remoting Issue Type: Improvement Assignee: Jeff Thompson Components: remoting Created: 2018-05-03 14:25 Priority: Minor Reporter: Oleg Nenashev 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 Issu
[JIRA] (JENKINS-50953) Tool to offer incremental updates
Title: Message Title Raul Arabaolaza commented on JENKINS-50953 Re: Tool to offer incremental updates With this tool in place allowing to update the incrementals versions easily, I agree to use CWP to implement the missing parts in JENKINS-51008 as there would be a deterministic way to get the proper versions to use to test 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-51008) Complete the PCT flow started in JENKINS-50540 for git plugin
Title: Message Title Raul Arabaolaza commented on JENKINS-51008 Re: Complete the PCT flow started in JENKINS-50540 for git plugin Oleg Nenashev No, JENKINS-50953 is enough IMO 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-51008) Complete the PCT flow started in JENKINS-50540 for git plugin
Title: Message Title Raul Arabaolaza edited a comment on JENKINS-51008 Re: Complete the PCT flow started in JENKINS-50540 for git plugin [~oleg_nenashev] No, With this and JENKINS-50953 is enough IMO 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-50888) NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50888 Re: NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information Code changed in jenkins User: Sam Van Oort Path: src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java src/test/java/org/jenkinsci/plugins/workflow/cps/PersistenceProblemsTest.java http://jenkins-ci.org/commit/workflow-cps-plugin/9a27f3070805ce189f18ed640bf30cdd8cc07cc7 Log: Fix and test for JENKINS-50888 by supporting serialization of execution before onLoad was called 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-50888) NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50888 Re: NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information Code changed in jenkins User: Sam Van Oort Path: src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java src/test/java/org/jenkinsci/plugins/workflow/cps/PersistenceProblemsTest.java http://jenkins-ci.org/commit/workflow-cps-plugin/54424895869f36d6c7377e167c5c1fa4ca959dc0 Log: Merge pull request #224 from svanoort/fix-final-lazy-load-issue-JENKINS-50888 Fix and test for JENKINS-50888 by supporting serialization of execution before onLoad was called Compare: https://github.com/jenkinsci/workflow-cps-plugin/compare/bdab2e1011b0...54424895869f *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. 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-50888) NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information
Title: Message Title Sam Van Oort commented on JENKINS-50888 Re: NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information PR link with the final fix 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-50888) NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information
Title: Message Title Sam Van Oort closed an issue as Fixed Resolved with the final 2.51 release of workflow-cps. Jenkins / JENKINS-50888 NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information Change By: Sam Van Oort Status: Reopened Closed Resolution: Fixed 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-issu
[JIRA] (JENKINS-51110) no test results visible in blueocean when following link from classic -> BO
Title: Message Title Joshua Hoblitt created an issue Jenkins / JENKINS-51110 no test results visible in blueocean when following link from classic -> BO Issue Type: Bug Assignee: Unassigned Attachments: blueocean-to-classic-to-blueocean-losses-tests-results.webm Components: blueocean-plugin Created: 2018-05-03 15:06 Environment: core 2.89.4 LTS blueocean 1.5.0 (final release) Labels: blueocean junit Priority: Minor Reporter: Joshua Hoblitt When exiting from a BO build view with junit test results (failures or all successful) to the classic UI, then following the link from the classic UI -> BO, the test results disappear. I noticed this after upgrading from BO 1.5.0-beta-2 -> 1.5.0 but I have not tested prior versions to see when this behavior started.
[JIRA] (JENKINS-51091) Make test results available on currentBuild
Title: Message Title Sam Van Oort commented on JENKINS-51091 Re: Make test results available on currentBuild Red flag for me: if we do off-master, this one would add some nontrivial extra complexity to that implementation. 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-51003) Allow non-administrators to use "Query and Trigger Gerrit Patches"
Title: Message Title Matthew Webber commented on JENKINS-51003 Re: Allow non-administrators to use "Query and Trigger Gerrit Patches" You can give the manual trigger permission to anyone. I'm using the Role Strategy plugin, which may be the problem here. The "Manual Trigger" privilege certainly appears as an available option. The attached screenshot shows that I have granted access to all authenticated users. Unfortunately, even with this only administrators can see the option. Is this a problem with Role Strategy, or with the way the Gerrit Trigger plugin does things? Thanks 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-51003) Allow non-administrators to use "Query and Trigger Gerrit Patches"
Title: Message Title Matthew Webber updated an issue Jenkins / JENKINS-51003 Allow non-administrators to use "Query and Trigger Gerrit Patches" Change By: Matthew Webber Attachment: Manual_Trigger.png 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-51003) Allow non-administrators to use "Query and Trigger Gerrit Patches"
Title: Message Title Matthew Webber updated JENKINS-51003 Jenkins / JENKINS-51003 Allow non-administrators to use "Query and Trigger Gerrit Patches" Change By: Matthew Webber Status: Closed In 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-34414) Code that raises groovy.lang.MissingMethodException will prevent parallel from finishing
Title: Message Title Sam Van Oort commented on JENKINS-34414 Re: Code that raises groovy.lang.MissingMethodException will prevent parallel from finishing Probably the exception triggers a CPS VM-level error that forces the Flow to end – not sure how viable that is? 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-50997) java.lang.UnsupportedOperationException in set map with each
Title: Message Title Sam Van Oort commented on JENKINS-50997 Re: java.lang.UnsupportedOperationException in set map with each Andrew Bayer any notions? 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-47498) Select compatible plugin versions using a BOM
Title: Message Title Jesse Glick commented on JENKINS-47498 Re: Select compatible plugin versions using a BOM Added to JENKINS-50686 since we might be able to use JENKINS-50953 to update the contents of the BOM. 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-50997) java.lang.UnsupportedOperationException in set map with each
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-50997 java.lang.UnsupportedOperationException in set map with each Change By: Andrew Bayer 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-50997) java.lang.UnsupportedOperationException in set map with each
Title: Message Title
Andrew Bayer commented on JENKINS-50997
Re: java.lang.UnsupportedOperationException in set map with each
This is due to IteratorHack in workflow-cps, which is how we're able to do iteration over map entries without serialization errors. You'll need to work around this - say, with something like:
Map buildStatus = ['a':'C', 'b':'N', 'c':'R', 'd':'R']
List nextBuildBranches = ['c', 'd']
nextBuildBranches.each { b ->
buildStatus.put(b, "C")
}
println buildStatus
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-51111) Navigating to downstream job via Blue Ocean Triggered Builds does not show tests in Tests tab
Title: Message Title Roger Wooley created an issue Jenkins / JENKINS-5 Navigating to downstream job via Blue Ocean Triggered Builds does not show tests in Tests tab Issue Type: Bug Assignee: Unassigned Attachments: 01_Job1.png, 02_Job2.png, 03_Job2_Tests_Via_Job1.png, 04_Job2_Direct.png, 05_Job2_Tests.png, 06_Job2_Tests.png Components: blueocean-plugin Created: 2018-05-03 15:39 Environment: Jenkins 2.117 Blue Ocean 1.5 Priority: Minor Reporter: Roger Wooley Steps to reproduce using two jobs: First job: triggers the second job (wait = true) Second job: record unit tests Open Blue Ocean from the first job, click Triggered Builds to access the second job The Tests tab will say no results are recorded Exit Blue Ocean, and access it again from the second job The Tests tab will show results I noticed this happening both while the job was running and complete.
[JIRA] (JENKINS-51111) Navigating to downstream job via Blue Ocean Triggered Builds does not show tests in Tests tab
Title: Message Title Roger Wooley updated an issue Jenkins / JENKINS-5 Navigating to downstream job via Blue Ocean Triggered Builds does not show tests in Tests tab Change By: Roger Wooley Steps to reproduce using two jobs: # * First job: triggers the second job (wait = true) # * Second job: record unit tests # * Open Blue Ocean from the first job, click Triggered Builds to access the second job # * The Tests tab will say no results are recorded # * Exit Blue Ocean, and access it again from the second job # * The Tests tab will show resultsI noticed this happening both while the job was running and complete. 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-51057) EventDispatcher and ConcurrentLinkedQueue ate my JVM
Title: Message Title Christian Höltje commented on JENKINS-51057 Re: EventDispatcher and ConcurrentLinkedQueue ate my JVM Our Jenkins server has been up 23 hours and we're already seeing large numbers of the EventDispacher objects: Class Size (Kb) % size Instances % instances Source [int[] https://ghenkins.bigdatalab.ibm.com/monitoring?part=source&class=int] 1,056,446 26 868,075 1 [char[] https://ghenkins.bigdatalab.ibm.com/monitoring?part=source&class=char] 447,243 11 2,837,232 4 [java.lang.Object[] https://ghenkins.bigdatalab.ibm.com/monitoring?part=source&class=java.lang.Object] 250,560 6 4,813,216 7 java.lang.StackTraceElement 239,176 6
[JIRA] (JENKINS-51057) EventDispatcher and ConcurrentLinkedQueue ate my JVM
Title: Message Title
Christian Höltje edited a comment on JENKINS-51057
Re: EventDispatcher and ConcurrentLinkedQueue ate my JVM
Our Jenkins server has been up 23 hours and we're already seeing large numbers of the EventDispacher objects: || Class|| Size (Kb)|| % size|| Instances|| % instances|| Source|||[ int[]|https://ghenkins.bigdatalab.ibm.com/monitoring?part=source&class=int]|1,056,446|26|868,075|1| ||[char[]|https://ghenkins.bigdatalab.ibm.com/monitoring?part=source&class=char]|447,243|11|2,837,232|4| ||[java.lang.Object[]|https://ghenkins.bigdatalab.ibm.com/monitoring?part=source&class=java.lang.Object]|250,560|6|4,813,216|7| ||[java.lang.StackTraceElement|https://ghenkins.bigdatalab.ibm.com/monitoring?part=source&class=java.lang.StackTraceElement]|239,176|6|7,653,653|11| ||[byte[]|https://ghenkins.bigdatalab.ibm.com/monitoring?part=source&class=byte]|165,917|4|581,581|0| ||[java.lang.String|https://ghenkins.bigdatalab.ibm.com/monitoring?part=source&class=java.lang.String]|146,722|3|6,260,161|9| ||[ org.jenkinsci.plugins.ssegateway.sse.EventDispatcher$Retry|https://ghenkins.bigdatalab.ibm.com/monitoring?part=source&class=org.jenkinsci.plugins.ssegateway.sse.EventDispatcher$Retry]|96,964|2|3,102,853|4| ||[java.util.concurrent.ConcurrentLinkedQueue$Node|https://ghenkins.bigdatalab.ibm.com/monitoring?part=source&class=java.util.concurrent.ConcurrentLinkedQueue$Node]|73,163|1|3,121,633|4| | It isn't a problem (yet) but this is alarming. Our other, Jenkins server has no references to {{EventDispatcher$Retry}} in the memory histogram, even when expanding details.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
-
[JIRA] (JENKINS-51080) Custom WAR Packager - Support of Incremental releases (JEP-305)
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-51080 Custom WAR Packager - Support of Incremental releases (JEP-305) Change By: Oleg Nenashev Labels: essentials 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.
