[JIRA] [core] (JENKINS-28446) UnlabeledLoad.computeQueueLength() includes labeled jobs
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-28446 UnlabeledLoad.computeQueueLength() includes labeled jobs Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28446) UnlabeledLoad.computeQueueLength() includes labeled jobs
Title: Message Title Oleg Nenashev commented on JENKINS-28446 Re: UnlabeledLoad.computeQueueLength() includes labeled jobs Seems the issue exists starting from the first version of UnlabeledLoad: https://github.com/jenkinsci/jenkins/commit/be1f8f91a3dcdcdfd2ed07198659e7eb68abf1f7 Jenkins.getInstance().getQueue().countBuildableItemsFor(null) is misused in the call (BTW the behavior is not documented). This method returns all tasks count if you call it with a null param. We will need a new method to maintain the backward compatibility Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24155) Jenkins Slaves Go Offline In Large Quantities and Don't Reconnect Until Reboot
Title: Message Title Vladimir Lazarev commented on JENKINS-24155 Re: Jenkins Slaves Go Offline In Large Quantities and Don't Reconnect Until Reboot We have "peer reconnecting" issue ones per 2 weeks. After applying the WA proposed by Amal connections with crashing during heavy jobs (high CPU load and long duration) on regular basis. So be aware... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28446) UnlabeledLoad.computeQueueLength() includes labeled jobs
Title: Message Title Oleg Nenashev commented on JENKINS-28446 Re: UnlabeledLoad.computeQueueLength() includes labeled jobs recampbell FYI, if you use computeQueueLength() in your code, it's recommended to switch to computeSnapshot() for the sake of a better performance. BTW, this issue will also happen in this call, so it is not a workaround. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28446) UnlabeledLoad.computeQueueLength() includes labeled jobs
Title: Message Title Oleg Nenashev started work on JENKINS-28446 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-28448) "Publish Assets delete files when no shelve is used for review
Title: Message Title amit yedidia created an issue Jenkins / JENKINS-28448 "Publish Assets delete files when no shelve is used for review Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 18/May/15 8:13 AM Environment: p4-plugin 1.21 Jenkins 1.609 Priority: Major Reporter: amit yedidia I am triggering "Build Review" option on shelved CL's via REST API. The configuration is set to publish the assets using "Submit" But when I just run the configuration directly from Jenkins (Using "Build Now") with no shelve given, the publish delete all the files in the server (I needed to "backout" to restore the files) Add Comment
[JIRA] [sonar] (JENKINS-28449) Jenkins with Sonar plugin version 2.2/2.2.1 deadlock problems
Title: Message Title Timo van der Laan created an issue Jenkins / JENKINS-28449 Jenkins with Sonar plugin version 2.2/2.2.1 deadlock problems Issue Type: Bug Assignee: Sonar Team Components: sonar Created: 18/May/15 8:14 AM Environment: jenkins 1.609 or higher, sonar plugin 2.2 or 2.2.1, redhat 6, jdk 7 or 8 Priority: Major Reporter: Timo van der Laan See also 27864. We have experienced deadlock problems with restarting jenkins. Investigation learned that they seem to be caused by the sonar plugin version 2.2 and 2.2.1. We found what we think is the culprit by looking at a lot of the deadlock reports. Different plugins were seen in those reports, but 1 was always there: ◾locked <0xe1044ca8> (a hudson.plugins.sonar.SonarPublisher$DescriptorImpl) at hudson.plugins.sonar.SonarPublisher$DescriptorImpl.(SonarPublisher.java:420) Reverting back to plugin version 2.1 resolved the problem.
[JIRA] [core] (JENKINS-27864) 1.608 with git plugin deadlock
Title: Message Title Timo van der Laan resolved as Fixed Opened a new issue as asked (JENKINS-28449) Jenkins / JENKINS-27864 1.608 with git plugin deadlock Change By: Timo van der Laan Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-28450) Publish Assets submit files even if build steps marked as failure
Title: Message Title amit yedidia created an issue Jenkins / JENKINS-28450 Publish Assets submit files even if build steps marked as failure Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 18/May/15 8:16 AM Environment: p4-plugin 1.21 Jenkins 1.609 Priority: Major Reporter: amit yedidia I am triggering "Build Review" option on shelved CL's via REST API. The configuration is set to publish the assets using "Submit" The publish asset take place even if the build steps before fail. The proper behavior should be that the files are not submitted. Add Comment
[JIRA] [core] (JENKINS-27864) 1.608 with git plugin deadlock
Title: Message Title Timo van der Laan commented on JENKINS-27864 Re: 1.608 with git plugin deadlock Opened issue JENKINS-28449, closing this one Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-13978) Add posibility to copy view
Title: Message Title Marco Ambu commented on JENKINS-13978 Re: Add posibility to copy view Does anyone know the status of this change? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28444) Invalid cc:, bcc: recipients handling when mail address contains a dot
Title: Message Title Adonai Elohim updated an issue Jenkins / JENKINS-28444 Invalid cc:, bcc: recipients handling when mail address contains a dot Change By: Adonai Elohim Attachment: build.log Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28444) Invalid cc:, bcc: recipients handling when mail address contains a dot
Title: Message Title Adonai Elohim commented on JENKINS-28444 Re: Invalid cc:, bcc: recipients handling when mail address contains a dot Attached build log (names masked) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24155) Jenkins Slaves Go Offline In Large Quantities and Don't Reconnect Until Reboot
Title: Message Title Vladimir Lazarev edited a comment on JENKINS-24155 Re: Jenkins Slaves Go Offline In Large Quantities and Don't Reconnect Until Reboot We have "peer reconnecting" issue ones per 2 weeks. After applying the WA proposed by Amal connections with are crashing during heavy jobs (high CPU load and long duration) on regular basis.So be aware... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27565) Nodes can be removed as idle before the assigned tasks have started
Title: Message Title stephenconnolly commented on JENKINS-27565 Re: Nodes can be removed as idle before the assigned tasks have started I have taken a look at the Azure cloud implementation... why did I do that? I knew what I was going to find before I looked... oh yes yet another completely borked cloud implementation which does everything hacky wrong ways because nobody actually knows the correct way to implement a cloud provider in Jenkins. I would not be surprised if the AzureSlaveCleanTaskThread causes issues, it seems to be doing lots of things it shouldn't... I really need to get the time to implement a clean cloud provisioning API so that people will stop using the current completely broken one (and just so that people who have tried to implement the Cloud API feel better, I have not seen any cloud implementation that is 100% correct... largely because the existing API is so woefully underspecified) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-28370) Error when trying to integrate to non-existing integration branch (Praqma case 13015)
Title: Message Title Bue Petersen updated an issue Jenkins / JENKINS-28370 Error when trying to integrate to non-existing integration branch (Praqma case 13015) Change By: Bue Petersen Summary: Error when trying to integrate to non-existing integration branch Case (Praqma case 13015 ) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [prioritysorter-plugin] (JENKINS-28280) Wrong Job Group is shown in the selector
Title: Message Title Kyrre Havik Eriksen commented on JENKINS-28280 Re: Wrong Job Group is shown in the selector I found out that I was missing one config.jelly when I did this last time. See https://github.com/jenkinsci/priority-sorter-plugin/pull/28 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26025) Build History window does not show all builds
Title: Message Title Daniel Beck resolved as Incomplete No response to comment in several months, so resolving as incomplete. Jenkins / JENKINS-26025 Build History window does not show all builds Change By: Daniel Beck Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration-plugin] (JENKINS-21640) scm-sync-configuration plugin doesn't work anymore with Subversion Plugin >=2.0
Title: Message Title Alan Birtles commented on JENKINS-21640 Re: scm-sync-configuration plugin doesn't work anymore with Subversion Plugin >=2.0 and broken again in 1.613, svn 2.5 and scm 0.0.8 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28380) Give expression examples for restricting where builds can run
Title: Message Title Daniel Beck assigned an issue to Daniel Beck I'm fairly sure this help existed. Jenkins / JENKINS-28380 Give _expression_ examples for restricting where builds can run Change By: Daniel Beck Assignee: Daniel Beck Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-28451) few problems when trying to install maven EventSpy when running from jenkins maven project
Title: Message Title Shalom Kazaz created an issue Jenkins / JENKINS-28451 few problems when trying to install maven EventSpy when running from jenkins maven project Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 18/May/15 9:28 AM Environment: linux debian latest jenkins maven-plugin 2.9 Labels: plugin maven eventspy mavencli maven-plugin Priority: Trivial Reporter: Shalom Kazaz We have developed a maven EventSpy to report progress of maven phases and mojos. when running from command line with -Dmaven.ext.class.path=PATH-TO-JAR it works fine as expected. when running under jenkins in a maven project , the jenkins maven-plugin ignores -Dmaven.ext.class.path and does not add our EventSpy jar to the classpath. this forces us to place the jar in maven ext folder which is not a good idea when managing many slaves and especially if we want jenkins to auto install maven. So we placed our spy jar in maven's lib/ext folder. But when placing the jar in
[JIRA] [maven-plugin] (JENKINS-28451) few problems when trying to install maven EventSpy when running from jenkins maven project
Title: Message Title
Shalom Kazaz updated an issue
Jenkins / JENKINS-28451
few problems when trying to install maven EventSpy when running from jenkins maven project
Change By:
Shalom Kazaz
We have developed a maven EventSpy to report progress of maven phases and mojos.when running from command line with -Dmaven.ext.class.path=PATH-TO-JAR it works fine as expected.when running under jenkins in a maven project , the jenkins maven-plugin ignores -Dmaven.ext.class.path and does not add our EventSpy jar to the classpath.this forces us to place the jar in maven ext folder which is not a good idea when managing many slaves and especially if we want jenkins to auto install maven. this also complicates our code because we don't want this spy for all our maven builds, but when the jar is in maven ext folder it will always be there and we have to set the plugin active or not by setting another system property from the jenkins job. So we placed our spy jar in maven's lib/ext folder.But when placing the jar in maven ext folder our EventSpy is added twice to maven's EventSpyDispatcher. the problem is in Maven32Launcher from the artifact maven32-interceptor:1.6, Maven32Launcher executes this line in it's main method:{code:java}Maven maven = (Maven) container.lookup( "org.apache.maven.Maven", "default" ){code}this causes plexus container to initialize EventSpyDispatcher as its a @Requirement of DefaulrMaven, and then also our EventSpy is injected to the EventSpyDispatcher instance.then Maven32Launcher executes this code:{code:java}List spies = container.lookupList( EventSpy.class );if (spies != null && !spies.isEmpty()){eventSpies.addAll( spies );}eventSpyDispatcher.setEventSpies( eventSpies );{code}this will find our EventSpy again and will add it again to the list of spies resulting in doubling the events we get from maven.to solve it currently we added our own EventSpyDIspatcher class that removes duplicate EventSpy from the event spies list. we annotated the class with @Component( role = EventSpyDispatcher.class ) and plexus is using our class instead of the default EventSpyDispatcher but I feel I can't trust this solution.another issue is while running from jenkins some events are received before the spy's init is called, for example DefaultSettingsBuildingRequest event.I feel that jenkins maven plugin should not break maven's command line interface even if some features are rarely used. and thus maven.ext.class.path should not be ignored when running in a maven project.
Add Comment
[JIRA] [performance-plugin] (JENKINS-27373) Performance Plugin fails with java.lang.ArithmeticException: / by zero (divide by zero)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27373 Re: Performance Plugin fails with java.lang.ArithmeticException: / by zero (divide by zero) Code changed in jenkins User: hitesh Path: src/main/java/hudson/plugins/performance/ThroughputUriReport.java http://jenkins-ci.org/commit/performance-plugin/75327e7680d387d5174ba4a6f1ced1dafef16cdd Log: fixes JENKINS-27373 Fix for divide by zero. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multijob-plugin] (JENKINS-28263) Use same changeset number for all phases
Title: Message Title
Thomas Fields commented on JENKINS-28263
Re: Use same changeset number for all phases
My predefined parameters are specified like you said but in the downstream phase if I enter:
$P4_CHANGELIST in the P4 Label field I get:
[Jenkins] $ p4 -s changes -s submitted -m 1 //Jenkins_External/...@$P4_CHANGELIST [Jenkins] $ p4 -s changes -s submitted //Jenkins_External/...@223146,@-1 No changes found. >> [External] has no changes since last build, so it will be skipped.
Note: I was expecting @$P4_CHANGELIST to be converted to a changelist number in this instance.
and if I specify $ {P4_CHANGELIST} in the P4 Label field I get: FATAL: <${P4_CHANGELIST}
>: Found unresolved macro at '$ {P4_CHANGELIST}' ${P4_CHANGELIST}
Are you certain this functionality works? Could you test it locally?
Thanks
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-24869) POM_VERSION is not resetted
Title: Message Title r04r r04r commented on JENKINS-24869 Re: POM_VERSION is not resetted This also affects me. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [slack-plugin] (JENKINS-27985) Slack post may have failed. Response: Private integrations can't post to public channels
Title: Message Title ben slaughter commented on JENKINS-27985 Re: Slack post may have failed. Response: Private integrations can't post to public channels I had a similar issue, This could be because you added the integration to Slack as a private integration (added to your own profile) and therefore can only post to Direct message, and the private room you have access to. If you are a Slack admin, try and add the integration to your slack team, this should give the integration the ability to post to public rooms. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [batch-task-plugin] (JENKINS-24581) tasks status icon not visible at overview of single task
Title: Message Title acollins commented on JENKINS-24581 Re: tasks status icon not visible at overview of single task I'm interested helping to fix this bug. I've checked out batch-task-plugin-master from GitHub. Can anyone point me to the right docs to get started? BatchTask implements Queue.Task, does that need to change for newer versions of Jenkins? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-26582) ISE from RunMap.put using /git/notifyCommit on a matrix project
Title: Message Title philbeiler commented on JENKINS-26582 Re: ISE from RunMap.put using /git/notifyCommit on a matrix project I was having a hard time following the comments, it that it would actually fix the dead thread problem. Now that this fix was integrated into the head (according to emails that I recieved from the Jenkins server, I decided to retry the test, but I get the same results.. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-26582) ISE from RunMap.put using /git/notifyCommit on a matrix project
Title: Message Title philbeiler edited a comment on JENKINS-26582 Re: ISE from RunMap.put using /git/notifyCommit on a matrix project I was having a hard time following the comments, it that it would actually fix the dead thread problem. Now that this fix was integrated into the head (according to emails that I recieved received from the Jenkins server, I decided to retry the test, but I get the same results.. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-26582) ISE from RunMap.put using /git/notifyCommit on a matrix project
Title: Message Title philbeiler updated an issue Jenkins / JENKINS-26582 ISE from RunMap.put using /git/notifyCommit on a matrix project Change By: philbeiler Attachment: screenshot-3.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-26582) ISE from RunMap.put using /git/notifyCommit on a matrix project
Title: Message Title philbeiler commented on JENKINS-26582 Re: ISE from RunMap.put using /git/notifyCommit on a matrix project Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-26582) ISE from RunMap.put using /git/notifyCommit on a matrix project
Title: Message Title philbeiler edited a comment on JENKINS-26582 Re: ISE from RunMap.put using /git/notifyCommit on a matrix project I was having a hard time following the comments, it that it if these changes would actually fix the dead thread problem. Now that this fix was integrated into the head (according to emails that I received from the Jenkins server, I decided to retry the test, but I get the same results.. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-hook-plugin] (JENKINS-28452) Push event web hook triggers all jobs regardless of Branch Specifier
Title: Message Title Michael Giuliano created an issue Jenkins / JENKINS-28452 Push event web hook triggers all jobs regardless of Branch Specifier Issue Type: Bug Assignee: Javier Palacios Components: gitlab-hook-plugin Created: 18/May/15 10:28 AM Environment: AWS Linux AMI, Version 2015.03 Priority: Blocker Reporter: Michael Giuliano This started happening since 1.4.0. I have had to downgrade to 1.3.1 as this is a blocker. We have 2 jobs for each repository. The 2 jobs have the following Branch Specifiers: origin/feature/* origin/master Jenkins 1.613 is running on Amazon Linux Image. This issue seems related to the plugin itself rather than Jenkins, but please let me know if you need any more details if you cannot replicate. Thanks, Michael
[JIRA] [prioritysorter-plugin] (JENKINS-28280) Wrong Job Group is shown in the selector
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28280 Re: Wrong Job Group is shown in the selector Code changed in jenkins User: emsa23 Path: src/main/resources/jenkins/advancedqueue/jobinclusion/strategy/JobInclusionJobProperty/config.jelly http://jenkins-ci.org/commit/priority-sorter-plugin/a1e32f94d2b82384ad076a1de6dbf050b62f1b1b Log: Merge pull request #28 from Kyrremann/ JENKINS-28280 _The_selected-attribut_was_inverted JENKINS-28280 The selected value was inverted Compare: https://github.com/jenkinsci/priority-sorter-plugin/compare/5d7cc0e68b96...a1e32f94d2b8 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [batch-task-plugin] (JENKINS-24581) tasks status icon not visible at overview of single task
Title: Message Title Tom FENNELLY commented on JENKINS-24581 Re: tasks status icon not visible at overview of single task Can someone attach another screenshot to show what's been lost i.e. a before and after. Thanks. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-hook-plugin] (JENKINS-28452) Push event web hook triggers all jobs regardless of Branch Specifier
Title: Message Title Javier Palacios commented on JENKINS-28452 Re: Push event web hook triggers all jobs regardless of Branch Specifier Could you supply a piece of log for one of those unwated builds? Piece from 'INFO: gitlab web hook triggered for' until the build success/failure if possible. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [batch-task-plugin] (JENKINS-24581) tasks status icon not visible at overview of single task
Title: Message Title podskalsky updated an issue Jenkins / JENKINS-24581 tasks status icon not visible at overview of single task A old screen shot - OK Change By: podskalsky Attachment: 2015-05-18 13_16_29-Clipboard.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [batch-task-plugin] (JENKINS-24581) tasks status icon not visible at overview of single task
Title: Message Title podskalsky updated an issue Jenkins / JENKINS-24581 tasks status icon not visible at overview of single task Change By: podskalsky Attachment: LATEST SCREENSHOT.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [batch-task-plugin] (JENKINS-24581) tasks status icon not visible at overview of single task
Title: Message Title podskalsky commented on JENKINS-24581 Re: tasks status icon not visible at overview of single task Added screenshots ... from FIREFOX !!! OLD OK (taken from a internal manual) LATEST NOT OK Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28286) jenkins.log growing extremely fast
Title: Message Title Régis Desgroppes closed an issue as Cannot Reproduce Sorry, I should have investigated more before filing this issue. I'll reopen when/if I manage to isolate it. Jenkins / JENKINS-28286 jenkins.log growing extremely fast Change By: Régis Desgroppes Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [batch-task-plugin] (JENKINS-24581) tasks status icon not visible at overview of single task
Title: Message Title Tom FENNELLY commented on JENKINS-24581 Re: tasks status icon not visible at overview of single task @poskalsky Thanks Andreas. @acollins Ashley, I have not look at this issue myself but Daniel (Beck) has indicated that the issue is in Jenkins Core. See his comment from Sept 5th last year. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [batch-task-plugin] (JENKINS-24581) tasks status icon not visible at overview of single task
Title: Message Title Tom FENNELLY edited a comment on JENKINS-24581 Re: tasks status icon not visible at overview of single task @poskalsky Thanks Andreas.@acollins Ashley, I have not look at this issue myself but Daniel (Beck) has indicated that the issue is in Jenkins Core. See his comment from Sept 5th last year. It would be awesome if you could come up with a fix proposal. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28437) /lib/layout/task also initiates GET request when post=true
Title: Message Title Daniel Beck commented on JENKINS-28437 Re: /lib/layout/task also initiates GET request when post=true Does this affect 1.609 (for lts-candidate)? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28422) Jenkins is hanging after a restart (deadlock)
Title: Message Title Daniel Beck commented on JENKINS-28422 Re: Jenkins is hanging after a restart (deadlock) Workaround: Disable the Green Balls plugin. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-agent-plugin] (JENKINS-27555) ssh-agent plugin leaking file descriptors leaving behind jenkinsXXXXXX.jnr socket files
Title: Message Title Niels Wegner commented on JENKINS-27555 Re: ssh-agent plugin leaking file descriptors leaving behind jenkinsXX.jnr socket files On our server the leaking seems to be triggered by failed builds: console of the job ... [ssh-agent] Using credentials glassfish (ssh-Key des Users glassfish) [ssh-agent] Looking for ssh-agent implementation... [ssh-agent] Java/JNR ssh-agent [ssh-agent] Started. [workspace] $ /bin/sh -xe /tmp/hudson1734179112612087977.sh + echo 'SSH_AUTH_SOCK = /tmp/jenkins2561807664873537168.jnr' SSH_AUTH_SOCK = /tmp/jenkins2561807664873537168.jnr ... Bad authentication response: 0 Build step 'Execute shell' marked failed builds as failure [ssh-agent] Stopped. ... Even if it says Stopped, there is an open socket hanging around: bash > netstat -anp | grep "/tmp/jenkins2561807664873537168.jnr" unix 2 [ ACC ] STREAM LISTENING 31717270 - /tmp/jenkins2561807664873537168.jnr Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28422) Jenkins is hanging after a restart (deadlock)
Title: Message Title Daniel Beck commented on JENKINS-28422 Re: Jenkins is hanging after a restart (deadlock) Update Metrics Plugin to 3.0.7 or newer. See https://wiki.jenkins-ci.org/display/JENKINS/Metrics+Plugin#MetricsPlugin-Version3.0.7%283rdOctober2014%29 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28422) Jenkins is hanging after a restart (deadlock)
Title: Message Title Daniel Beck resolved as Not A Defect Assuming caused by outdated Metrics Plugin, but issue does not contain enough information to say for sure. Please follow the instructions on https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue in the future. Jenkins / JENKINS-28422 Jenkins is hanging after a restart (deadlock) Change By: Daniel Beck Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-28294) "JDK 5 not supported with Maven" error with JDK 6
Title: Message Title Erwan Lacoste commented on JENKINS-28294 Re: "JDK 5 not supported with Maven" error with JDK 6 We have the same problem here when trying to use the IBM JDK. Is it possible that the Maven plugin makes a confusion between Maven 3.3.X that requires Java 7 and 3.2.X that is OK with Java 6? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28422) Jenkins is hanging after a restart (deadlock)
Title: Message Title Thomas Ferreira commented on JENKINS-28422 Re: Jenkins is hanging after a restart (deadlock) Dear, Thank you for this answer, but sadly, metrics is currently already on version 3.0.9. Any other Idea? Best regards, Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28422) Jenkins is hanging after a restart (deadlock)
Title: Message Title Thomas Ferreira reopened an issue Jenkins / JENKINS-28422 Jenkins is hanging after a restart (deadlock) Change By: Thomas Ferreira Resolution: Not A Defect Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28437) /lib/layout/task also initiates GET request when post=true
Title: Message Title Oleg Nenashev commented on JENKINS-28437 Re: /lib/layout/task also initiates GET request when post=true Daniel, seems it exists starting from 1.504 (https://github.com/jenkinsci/jenkins/commit/b9c18a7b4c6d194645a20312352cd4d4994eafb4) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration-plugin] (JENKINS-15128) Renaming job doesn't work with Git
Title: Message Title Eran Cohen commented on JENKINS-15128 Re: Renaming job doesn't work with Git not fixed: May 18, 2015 3:29:48 PM SEVERE hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy [deleteHierarchy] Problem during remove : The git command failed. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration-plugin] (JENKINS-15128) Renaming job doesn't work with Git
Title: Message Title Eran Cohen reopened an issue Jenkins / JENKINS-15128 Renaming job doesn't work with Git Change By: Eran Cohen Resolution: Fixed Status: Resolved Reopened Assignee: Frédéric Camblor Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28444) Invalid cc:, bcc: recipients handling when mail address contains a dot
Title: Message Title Alex Earl commented on JENKINS-28444 Re: Invalid cc:, bcc: recipients handling when mail address contains a dot Everything looks ok in the log. Which users from the list didn't receive the email? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory-plugin] (JENKINS-26899) Multiple domain authentication when not part of the same forest
Title: Message Title Sagayaraj David commented on JENKINS-26899 Re: Multiple domain authentication when not part of the same forest We also face this problem. When two Active Directory domains are configured, the xml API call is not successful; however the same user is successfully able to login on the web interface. It looks like it is always trying to authenticate as Anonymous even though we pass the User and API token. We invoke the API as below: wget -d -O JobInfo.xml --http-user=MyUser --http-password=MyAPIToken --secure-protocol=TLSv1 http://jenkins.mydomain/job/TESTJOB/api/xml Error message: Authentication required
[JIRA] [active-directory-plugin] (JENKINS-26899) Multiple domain authentication when not part of the same forest
Title: Message Title Sagayaraj David edited a comment on JENKINS-26899 Re: Multiple domain authentication when not part of the same forest We also face this problem. When two Active Directory domains are configured, the xml API call is not successful; however the same user is successfully able to login on the web interface. It looks like it is always trying to authenticate as Anonymous even though we pass the User and API token.We invoke the API as below: wget -d -O JobInfo.xml --http-user=MyUser --http-password=MyAPIToken --secure-protocol=TLSv1 http://jenkins.mydomain/job/TESTJOB/api/xmlError message:Authentication required
[JIRA] [jira-plugin] (JENKINS-28453) No known JIRA project corresponding to id: 'RCFOPS-112'
Title: Message Title Jeff Blaine created an issue Jenkins / JENKINS-28453 No known JIRA project corresponding to id: 'RCFOPS-112' Issue Type: Bug Assignee: Unassigned Attachments: jira-jenkins-fail.jpg Components: jira-plugin Created: 18/May/15 2:06 PM Priority: Minor Reporter: Jeff Blaine The default (unset) pattern does not properly match our JIRA issues names that are simple defaults. Our build history "keys" still are just numbers and not links to JIRA as expected. Thoughts would be very welcome. May 18, 2015 8:10:52 AM hudson.plugins.jira.JiraChangeLogAnnotator annotate INFO: No known JIRA project corresponding to id: 'RCFOPS-112' Add Comment
[JIRA] [gitlab-hook-plugin] (JENKINS-28452) Push event web hook triggers all jobs regardless of Branch Specifier
Title: Message Title
Michael Giuliano commented on JENKINS-28452
Re: Push event web hook triggers all jobs regardless of Branch Specifier
Below is the Jenkins log for the push event from GitLab. Push is done on master, which should only match the 'test-build' project, not the 'test-branch'
INFO: gitlab web hook triggered for
- repo url: g...@gitlab.zoopla.co.uk:mgiuliano/test-jenkins.git
- branch: master
- with payload:
{
"object_kind": "push",
"before": "658871fc969682b05a8f8f896b3d9601c9ddb32b",
"after": "163214aa43fc118d958a26b697128bfbadd9ae4b",
"ref": "refs/heads/master",
"checkout_sha": "163214aa43fc118d958a26b697128bfbadd9ae4b",
"message": null,
"user_id": 2,
"user_name": "Michael Giuliano",
"user_email": "michael.giuli...@zpg.co.uk",
"project_id": 117,
"repository": {
"name": "test-jenkins",
"url": "g...@gitlab.zoopla.co.uk:mgiuliano/test-jenkins.git",
"description": "",
"homepage": "https://gitlab.zoopla.co.uk/mgiuliano/test-jenkins",
"git_http_url": "https://gitlab.zoopla.co.uk/mgiuliano/test-jenkins.git",
"git_ssh_url": "g...@gitlab.zoopla.co.uk:mgiuliano/test-jenkins.git",
"visibility_level": 0
},
"commits": [
{
"id": "163214aa43fc118d958a26b697128bfbadd9ae4b",
"message": "Bump version: 1.0.1 → 1.0.2\n",
"timestamp": "2015-05-18T11:12:39+01:00",
"url": "https://gitlab.zoopla.co.uk/mgiuliano/test-jenkins/commit/163214aa43fc118d958a26b697128bfbadd9ae4b",
"author": {
"name": "Michael Giuliano",
"email": "michael.giuli...@zpg.co.uk"
}
}
],
"total_commits_count": 1
}
INFO: matching projects:
- test-branch
- test-build
INFO: test-build scheduled for build
INFO: test-build #4 main build action completed: SUCCESS
The build itself does nothing but echo "Hello" in a shell script.
I hope this helps.
Thanks, Michael
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [email-ext-plugin] (JENKINS-28444) Invalid cc:, bcc: recipients handling when mail address contains a dot
Title: Message Title Adonai Elohim commented on JENKINS-28444 Re: Invalid cc:, bcc: recipients handling when mail address contains a dot At least BCC became CC I'll attach another log without quotes shortly. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28454) Add integration support with Jenkins Workflow DSL
Title: Message Title Daren Smith created an issue Jenkins / JENKINS-28454 Add integration support with Jenkins Workflow DSL Issue Type: Improvement Assignee: Jesse Glick Components: workflow-plugin, ws-cleanup-plugin Created: 18/May/15 2:16 PM Priority: Minor Reporter: Daren Smith Add support for the integration for Jenkins Workflow DSL. Having the means to clean workspaces utilizing the workflow plugin is missing currently and users must resort to scripting this capability, which has it limitations since Antbuilder is not whitelisted as a for groovy CPS libraries. Being able to delete workspaces from the workflow DSL based on patterns would be very useful. Add Comment
[JIRA] [windows-slaves-plugin] (JENKINS-28278) Environment variables "stuck" on windows slave
Title: Message Title Brendan Billingsley commented on JENKINS-28278 Re: Environment variables "stuck" on windows slave I'm seeing this same exact behavior but for RHEL jnlp slaves. I have two slaves that have had this problem, and two that have not. One of the slaves that had this problem is on the same machine but running as a different user from the one that has not experienced the issue. I would disagree that this is a minor issue. Whenever our slave machines get rebooted (or otherwise have environment change) I have to manually check each slave and possibly delete/recreate it. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28446) UnlabeledLoad.computeQueueLength() includes labeled jobs
Title: Message Title
recampbell updated an issue
Jenkins / JENKINS-28446
UnlabeledLoad.computeQueueLength() includes labeled jobs
Change By:
recampbell
The {{Jenkins#unlabeledLoad}} LoadStatistics incorrectly counts labeled jobs from computeQueueLength().Steps to reproduce:# Create a job with a label 'foo'# Run the job and ensure it is the only job in the queue# Evaluating {{Jenkins.getInstance().unlabeledLoad.computeQueueLength()}} will return 1This causes the {{Jenkins.unlabeledLoadProvisioner}} to provision slaves with null labels even though they will not be able to run the labeled jobs.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28444) Invalid cc:, bcc: recipients handling when mail address contains a dot
Title: Message Title Adonai Elohim commented on JENKINS-28444 Re: Invalid cc:, bcc: recipients handling when mail address contains a dot Just sent mail to myself and BCC'd to colleague through Outlook He got it and does not see himself as a recipient Anyways, I see Ext plugin adds it as explicit RCPT, this should not happen if the person is BCC'd, does it? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28444) Invalid cc:, bcc: recipients handling when mail address contains a dot
Title: Message Title Alex Earl commented on JENKINS-28444 Re: Invalid cc:, bcc: recipients handling when mail address contains a dot I meant DavMail, not Outlook. See "How SMTP actually works" on http://stackoverflow.com/questions/2750211/sending-bcc-emails-using-a-smtp-server. Based on that, you would still see the BCC person as a RCPT entry with the mailserver. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28444) Invalid cc:, bcc: recipients handling when mail address contains a dot
Title: Message Title Adonai Elohim commented on JENKINS-28444 Re: Invalid cc:, bcc: recipients handling when mail address contains a dot Ok, I'll go take a look at DavMail source. Don't close this issue, I'll update it with non-quoted version soon Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco-plugin] (JENKINS-27766) Jacoco with Jenkins on Apache Tomcat
Title: Message Title Maninder Singh updated an issue Jenkins / JENKINS-27766 Jacoco with Jenkins on Apache Tomcat Change By: Maninder Singh Ubuntu 14.04 Gradle 2.2.1 Jenkins 1.609jacoco Jenkins plugin:1.0.19 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco-plugin] (JENKINS-27766) Jacoco with Jenkins on Apache Tomcat: /jacoco/classes does not exist
Title: Message Title Maninder Singh updated an issue Jenkins / JENKINS-27766 Jacoco with Jenkins on Apache Tomcat: /jacoco/classes does not exist Change By: Maninder Singh Summary: Jacoco with Jenkins on Apache Tomcat : /jacoco/classes does not exist Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28425) UI: Build history overflows
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-28425 UI: Build history overflows Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28444) Invalid cc:, bcc: recipients handling when mail address contains a dot
Title: Message Title Alex Earl commented on JENKINS-28444 Re: Invalid cc:, bcc: recipients handling when mail address contains a dot I won't close until resolved. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28425) UI: Build history overflows
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28425 Re: UI: Build history overflows Code changed in jenkins User: Tom Fennelly Path: war/src/main/webapp/css/style.css http://jenkins-ci.org/commit/jenkins/84236bf6d7351622e7916b9cf1a4be59b0ebbaa6 Log: Merge pull request #1705 from thomassuckow/feature/history-overflow [FIXED JENKINS-28425] Fix build history styling badness Compare: https://github.com/jenkinsci/jenkins/compare/c1e3a64eea88...84236bf6d735 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28425) UI: Build history overflows
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28425 Re: UI: Build history overflows Code changed in jenkins User: Thomas Suckow Path: war/src/main/webapp/css/style.css http://jenkins-ci.org/commit/jenkins/97cffbe2e421d4e847ec91223cb995342319ac70 Log: [FIXED JENKINS-28425] Fix build history styling badness Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28444) Invalid cc:, bcc: recipients handling when mail address contains a dot
Title: Message Title Alex Earl commented on JENKINS-28444 Re: Invalid cc:, bcc: recipients handling when mail address contains a dot Does your mail server support bcc? I sent to addresses with dots in cc and bcc to gmail with no problems. I even put quotes around some addresses like you have. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28333) Browse users is broken
Title: Message Title Alexandru Gheorghe commented on JENKINS-28333 Re: Browse users is broken Still there even with 1.613: May 18, 2015 4:32:55 PM jenkins.util.ProgressiveRendering$1 run WARNING: failed to compute /user/xyz/builds java.lang.ArrayIndexOutOfBoundsException: 1 at hudson.plugins.git.GitChangeSet.parseCommit(GitChangeSet.java:104) at hudson.plugins.git.GitChangeSet.(GitChangeSet.java:89) at hudson.plugins.git.GitChangeLogParser.parseCommit(GitChangeLogParser.java:73) at hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:67) at hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:44) at hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:25) at hudson.scm.ChangeLogParser.parse(ChangeLogParser.java:57) at org.jenkinsci.plugins.multiplescms.MultiSCMChangeLogParser$LogSplitter.endElement(MultiSCMChangeLogParser.java:99) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:609) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1782) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2973) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:606) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:848) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:777) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:648) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:332) at javax.xml.parsers.SAXParser.parse(SAXParser.java:328) at org.jenkinsci.plugins.multiplescms.MultiSCMChangeLogParser.parse(MultiSCMChangeLogParser.java:135) at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:924) at hudson.model.AbstractBuild.getChangeSet(AbstractBuild.java:892) at hudson.model.AbstractBuild.hasParticipant(AbstractBuild.java:393) at hudson.model.User.relatedTo(User.java:607) at hudson.model.User.access$000(User.java:112) at hudson.model.User$2.apply(User.java:629) at hudson.model.User$2.apply(User.java:627) at com.google.common.collect.Iterators$7.computeNext(Iterators.java:649) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at jenkins.widgets.RunListProgressiveRendering.compute(RunListProgressiveRendering.java:60) at jenkins.util.ProgressiveRendering$1.run(ProgressiveRendering.java:123) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) at java.util.concurrent.ThreadPoolExecutor.runWork
[JIRA] [windows-slaves-plugin] (JENKINS-28278) Environment variables "stuck" on windows slave
Title: Message Title Brendan Billingsley edited a comment on JENKINS-28278 Re: Environment variables "stuck" on windows slave I'm seeing this same exact behavior but for RHEL jnlp slaves started by a script . I have two slaves that have had this problem, and two that have not. One of the slaves that had this problem is on the same machine but running as a different user from the one that has not experienced the issue.I would disagree that this is a minor issue. Whenever our slave machines get rebooted (or otherwise have environment change) I have to manually check each slave and possibly delete/recreate it. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28455) Build History badges don't wrap
Title: Message Title Tom FENNELLY created an issue Jenkins / JENKINS-28455 Build History badges don't wrap Issue Type: Bug Assignee: Tom FENNELLY Components: core Created: 18/May/15 2:40 PM Labels: build-history user-experience ui Priority: Minor Reporter: Tom FENNELLY Instead, the overflow out across the page. The problem is that there's no space between the badges to trigger the wrapping. Add Comment
[JIRA] [envinject-plugin] (JENKINS-28278) Environment variables "stuck" on windows slave
Title: Message Title Nathan Neulinger commented on JENKINS-28278 Re: Environment variables "stuck" on windows slave Glad to see someone else is seeing it and it's not just my imagination. Until I found this it was a complete brain stumper trying to figure out what was going on since the symptom/behavior made no sense whatsoever. I don't know whether it's something with the remote connection or with the environment setting plugin. Out of curiosity - do you have the EnvInject plugin installed as well? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject-plugin] (JENKINS-28278) Environment variables "stuck" on windows slave
Title: Message Title Nathan Neulinger updated an issue Jenkins / JENKINS-28278 Environment variables "stuck" on windows slave Change By: Nathan Neulinger Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject-plugin] (JENKINS-28278) Environment variables "stuck" on windows slave
Title: Message Title Brendan Billingsley commented on JENKINS-28278 Re: Environment variables "stuck" on windows slave I don't have the EnvInject plugin installed. I'm similarly glad someone else has this issue as I was also going a little crazy trying to figure out what was going on. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject-plugin] (JENKINS-28278) Environment variables "stuck" on windows slave
Title: Message Title Nathan Neulinger updated an issue Jenkins / JENKINS-28278 Environment variables "stuck" on windows slave Change By: Nathan Neulinger Component/s: envinject-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [windows-slaves-plugin] (JENKINS-28278) Environment variables "stuck" on windows slave
Title: Message Title Nathan Neulinger updated an issue Jenkins / JENKINS-28278 Environment variables "stuck" on windows slave Change By: Nathan Neulinger Component/s: envinject-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-28290) Git plugin prevents build display on missing header entries in changelog.xml
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-28290 Git plugin prevents build display on missing header entries in changelog.xml Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-28290) Git plugin prevents build display on missing header entries in changelog.xml
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28290 Re: Git plugin prevents build display on missing header entries in changelog.xml Code changed in jenkins User: Nicolas De Loof Path: src/main/java/hudson/plugins/git/GitChangeSet.java http://jenkins-ci.org/commit/git-plugin/11c38d3ca6006538dcefe3866b75a4b973f4e4ab Log: [FIX JENKINS-28290] prevent ArrayIndexOutOfBoundException parent may be null when shallow clone is used Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-28290) Git plugin prevents build display on missing header entries in changelog.xml
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28290 Re: Git plugin prevents build display on missing header entries in changelog.xml Code changed in jenkins User: Nicolas De loof Path: src/main/java/hudson/plugins/git/GitChangeSet.java http://jenkins-ci.org/commit/git-plugin/83fe7252c07548c2f1f6629968b04f4407566e91 Log: Merge pull request #321 from ndeloof/ JENKINS-28290 [FIX JENKINS-28290] prevent ArrayIndexOutOfBoundException Compare: https://github.com/jenkinsci/git-plugin/compare/b88b388aee10...83fe7252c075 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28456) http://jenkins-ci.org/changelog does not show 1.614, but 1.614 is latest available
Title: Message Title boris ivan created an issue Jenkins / JENKINS-28456 http://jenkins-ci.org/changelog does not show 1.614, but 1.614 is latest available Issue Type: Bug Assignee: Unassigned Components: core Created: 18/May/15 3:24 PM Priority: Minor Reporter: boris ivan 1.614 is the latest available for download, but 1.614 does not show up in the changelog. Logging this bug as minor, since it's not a huge deal. Add Comment
[JIRA] [core] (JENKINS-28425) UI: Build history overflows
Title: Message Title dogfood commented on JENKINS-28425 Re: UI: Build history overflows Integrated in jenkins_main_trunk #4144 [FIXED JENKINS-28425] Fix build history styling badness (Revision 97cffbe2e421d4e847ec91223cb995342319ac70) Result = SUCCESS thomas.suckow : 97cffbe2e421d4e847ec91223cb995342319ac70 Files : war/src/main/webapp/css/style.css Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [log-parser-plugin] (JENKINS-28457) Please add support for providing config through Config File Provider Plugin
Title: Message Title Dan Dumont created an issue Jenkins / JENKINS-28457 Please add support for providing config through Config File Provider Plugin Issue Type: Bug Assignee: rgoren Components: log-parser-plugin Created: 18/May/15 3:45 PM Priority: Major Reporter: Dan Dumont See: https://wiki.jenkins-ci.org/display/JENKINS/Config+File+Provider+Plugin I have set up a generic file via this plugin, but I cannot use it because in the job I cannot pick the entries from this plugin (understandable because you don't support it). Unfortunately, I cannot rely on the fallback behavior of copying the config locally to the job and using that file explicitly because this plugin does not allow me to enter in a specific path... it only allows me to choose from a dropdown. We cannot allow everyone access to the master jenkins config, so forcing people to use that to configure this plugin is not really acceptable. Add Comment
[JIRA] [prioritysorter-plugin] (JENKINS-24962) Cannot assign a JobGroup to a Nested (sub) View
Title: Message Title Magnus Sandberg resolved as Fixed Supported in 3.2 Jenkins / JENKINS-24962 Cannot assign a JobGroup to a Nested (sub) View Change By: Magnus Sandberg Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-28055) Pipeline arrows are not displaying or displayed incorrectly
Title: Message Title Stephan Pauxberger commented on JENKINS-28055 Re: Pipeline arrows are not displaying or displayed incorrectly Downgrade to JQuery Plugin 1.7.2-1 seems to solve both problems (wrong arrows and JS errors) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-hook-plugin] (JENKINS-28452) Push event web hook triggers all jobs regardless of Branch Specifier
Title: Message Title Javier Palacios commented on JENKINS-28452 Re: Push event web hook triggers all jobs regardless of Branch Specifier Is there an "INFO: test-branch scheduled for build" message anywhere in the logs? From what you have pasted looks like a misleading text: when it says "INFO: matching projects", the long meaning is "projects tracking g...@gitlab.zoopla.co.uk:mgiuliano/test-jenkins.git". The 'schedule for build' message is the trace that the build has already been triggered, and I see it only for master job. The reason behind is that to make cleaner the implementation of some features (mainly, template based creation), the project matching is done in two phases, one for overall matching (enabled, git & git-url), and a fine-grained round that actually checks for the tracked branch. So, in your case, both projects must succeed on the first round, but only one will actually run after looking for the second match. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-28458) Deleting views when the containing folder has already been deleted leads to NPE
Title: Message Title Stephan Pauxberger created an issue Jenkins / JENKINS-28458 Deleting views when the containing folder has already been deleted leads to NPE Issue Type: Bug Assignee: Daniel Spilker Components: job-dsl-plugin Created: 18/May/15 4:00 PM Priority: Minor Reporter: Stephan Pauxberger Simple case of missing NPE guard: Create a dsl that creates a folder a view in that folder run the dsl now remove the folder and the view rerun the job NPE occurs
[JIRA] [delivery-pipeline-plugin] (JENKINS-28055) Pipeline arrows are not displaying or displayed incorrectly
Title: Message Title Patrik Boström commented on JENKINS-28055 Re: Pipeline arrows are not displaying or displayed incorrectly Managed to to reproduce the problem, upgrade of JQuery plugin broke the JQuery UI plugin. There are two possible workarounds: 1 Downgrade jquery plugin to 1.7.2-1 as suggested by Stephan Pauxberger 2 Disable jquery-ui plugin, delivery pipeline plugin had this as a requirement before but it is not needed anymore. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28444) Invalid cc:, bcc: recipients handling when mail address contains a dot
Title: Message Title Alex Earl commented on JENKINS-28444 Re: Invalid cc:, bcc: recipients handling when mail address contains a dot This actually has nothing to do with dots in the email address. It has to do with a bug I introduced that parsed the cc and bcc stuff incorrectly. I was not seeing it on the code I was using because I had already fixed it. I should have run earlier with the released version of the code. Should have a fix in the next version. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28444) Invalid cc:, bcc: recipients handling when mail address contains a dot
Title: Message Title Alex Earl resolved as Fixed Jenkins / JENKINS-28444 Invalid cc:, bcc: recipients handling when mail address contains a dot Change By: Alex Earl Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-28444) Invalid cc:, bcc: recipients handling when mail address contains a dot
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28444 Re: Invalid cc:, bcc: recipients handling when mail address contains a dot Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/EmailRecipientUtils.java http://jenkins-ci.org/commit/email-ext-plugin/cea631c421b7964ba710d21c3a4131d7a881f739 Log: Fix JENKINS-28444 Fix incorrect check for > 0 size on the bcc an cc lists. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-hook-plugin] (JENKINS-28452) Push event web hook triggers all jobs regardless of Branch Specifier
Title: Message Title Michael Giuliano commented on JENKINS-28452 Re: Push event web hook triggers all jobs regardless of Branch Specifier Hi, sorry this was the logs after I downgraded. The ones using 1.4.0 read: INFO: matching projects: - test-branch - test-build INFO: project test-branch merge target matches master INFO: test-branch scheduled for build test-build scheduled for build INFO: test-build #3 main build action completed: SUCCESS Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multijob-plugin] (JENKINS-22483) Job execution deadlock on safeRestart
Title: Message Title Patrick Nielsen reopened an issue I'm able to produce this issue using multijob plugin and trying to do a safeShutdown api and get a deadlock on waiting for jenkins to shutdown. Jobs required to reproduce, The child Jobs are serial not multiphase. Parent Job Child 1 Job Child 2 Job What happens is parent job is running during the time the URL API call is made. Jenkins behavior is let all jobs finish and queue any future jobs. This allows the childjob 1 or 2 to get in the queue. The parent job is holding on to the child job calls waiting for them to complete but that won't happen since they are in queue. Jenkins / JENKINS-22483 Job execution deadlock on safeRestart Change By: Patrick Nielsen Resolution: Cannot Reproduce Status: Closed Reopened Add Comment
[JIRA] [ci-game-plugin] (JENKINS-28459) Add Job DSL support for ci-game plugin
Title: Message Title
Ben Hocker created an issue
Jenkins / JENKINS-28459
Add Job DSL support for ci-game plugin
Issue Type:
New Feature
Assignee:
redsolo
Components:
ci-game-plugin
Created:
18/May/15 4:33 PM
Priority:
Minor
Reporter:
Ben Hocker
It would be nice to add the cigame plugin using Job DSL without breaking into a config block.
//CI game
configure { project ->
project / publishers << 'hudson.plugins.cigame.GamePublisher' {}
}
Add Comment
[JIRA] [gitlab-hook-plugin] (JENKINS-28452) Push event web hook triggers all jobs regardless of Branch Specifier
Title: Message Title Javier Palacios commented on JENKINS-28452 Re: Push event web hook triggers all jobs regardless of Branch Specifier There is the point: INFO: project test-branch merge target matches master The fine grained match I comment before does also checks for branches merged in the job, not only the configured refspec. The push to master triggers the test-build as expected, but also the test-branch jobs because master is merged into them. This is actually a non-configurable behaviour, as I did consider it highly desirable. Is that behaviour actually a not-feature in your case? And did you want to use any of the (other) new features on 1.4.0? It could be a good point to add to future releases, but it you answer affirmatively to both questions, I'll try to add into a near-future release. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-hook-plugin] (JENKINS-28452) Push event web hook triggers all jobs regardless of Branch Specifier
Title: Message Title Michael Giuliano commented on JENKINS-28452 Re: Push event web hook triggers all jobs regardless of Branch Specifier In my scenario, the branch job is a test-run job. The job is triggered when a feature branch is pushed to GitLab. It then attempts a merge into the integration branch (in this case master) to check if it would merge cleanly if the merge request was accepted. So this job is a pre-check to tell the feature branch developer that his work won't integrate cleanly, without having to get the reviewer involved yet. Only when this branch job passes, can the developer create a merge request and submit it for code review. This allow for less time wasted on the reviewers. The reviewer, once happy, merges the branch to master, and deletes the feature branch. This triggers the build job. At this stage, when the branch job is triggered again, it fails because the feature branch no longer exists. So indeed, I would have liked to have this behaviour as an option, not as a default. The way it works now is very implicit and not very obvious. It would be better to be able to configure this behaviour. I am not using any of the 1.4.0 features specifically, I was upgrading to stay up to date. So if this doesn't get patched or added to the next release, I will be stuck to the 1.3 release forever, which might be an issue in the future. So yes, if you could add it as soon as you can, it would be greatly appreciated. Thanks for your help with this. Best, Michael Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues
[JIRA] [analysis-collector-plugin] (JENKINS-28360) Missing static analysis results in weather popup
Title: Message Title David Bishop commented on JENKINS-28360 Re: Missing static analysis results in weather popup Ah! Well, my developers are now asking me for the broken-out results to show in the health report as well, so if you have any ideas as to somewhere else I can look I'm all ears. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
