[JIRA] [websphere-deployer-plugin] (JENKINS-28369) getting IncompatibleClassChangeError while deploying EAR into WAS8.5 through Jenkins using GitHub
Title: Message Title swetha sreeramoju updated an issue Jenkins / JENKINS-28369 getting IncompatibleClassChangeError while deploying EAR into WAS8.5 through Jenkins using GitHub Change By: swetha sreeramoju Component/s: websphere-deployer-plugin Component/s: jenkins-testswarm 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-existant integration branch
Title: Message Title
Jan Krag updated an issue
Jenkins / JENKINS-28370
Error when trying to integrate to non-existant integration branch
Change By:
Jan Krag
Weneed Ifyouspecifyanintegrationbranchthatdoesn'texistontheremote,thepluginfails,withthefollowingerror:{code}Failed to commitmergedchanges.Errormessagebelow(nothingtosquash)Alreadyup-to-date.HEADdetachedatxxxnothingtocommit,workingdirectoryclean{code}Thisisbecauseitdoesa{{gitcheckout-Bintegration_branch}}Ifthespecifiedintegrationbranchdoesn'thaveamatchingbranchontheremote,gitcheckoutwillhappilycreateanewlocalbranchpointingtothecurrentHEADwithoutcomplaining.Thisisnormalandexpectedgitbehaviour,butinthiscasehastheobviousside-effectthattheresultingmergeisempty,asitwillbemergingfromHEAD(thereadybranch)toanewbranchpointingtothesamecommitasHEAD.Asitdoesn'treallymakesensetointegratetoanon-existingintegrationbranch,situationslikethisshouldbeconsideredconfigurationerrors.Thepluginshouldsomehow checkthattheintegrationbranchexists somehow .
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] [docker-build-step-plugin] (JENKINS-28371) Not able to access Docker build step plugin
Title: Message Title manoj Kumar updated an issue Jenkins / JENKINS-28371 Not able to access Docker build step plugin Change By: manoj Kumar 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] [core] (JENKINS-28372) Automatic JDK installation hangs acquiring semaphore
Title: Message Title Wisen Tanasa created an issue Jenkins / JENKINS-28372 Automatic JDK installation hangs acquiring semaphore Issue Type: Bug Assignee: Unassigned Components: core Created: 13/May/15 9:12 AM Environment: Jenkins 1.553 Priority: Major Reporter: Wisen Tanasa We have just upgraded Jenkins from 1.516 to version 1.553. We never had this problem in 1.516. The automatic installation of JDK is done by pulling the installer from one of our FTP servers. The problem is intermittent, sometimes it happens, sometimes it's not. The problem weirdly is happening even though the tools have been installed successfully. We resolve the problem temporarily by restarting Jenkins. Thread dump Executor #10 for master : executing Function_Set_Common_Data_Management_Nightly #1043 prio=5 WAITING sun.misc.Unsafe.park(Native Method) java.util.concurrent.locks.LockSupport.park(LockSupport.java:156) java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:811)
[JIRA] [docker-build-step-plugin] (JENKINS-28371) Not able to access Docker build step plugin
Title: Message Title manoj Kumar updated an issue Jenkins / JENKINS-28371 Not able to access Docker build step plugin Change By: manoj Kumar Attachment: screenshot-8.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] [copy-project-link-plugin] (JENKINS-13517) CopyProjectLink plugin: does not work with jobs using 'display name' feature
Title: Message Title SCM/JIRA link daemon commented on JENKINS-13517 Re: CopyProjectLink plugin: does not work with jobs using 'display name' feature Code changed in jenkins User: Oliver Gondža Path: src/main/java/hudson/plugins/copyProjectLink/CopyAction.java http://jenkins-ci.org/commit/copy-project-link-plugin/4fa35d6ba88ab35513dcf213ed3f17c2817ffe3a Log: Merge pull request #3 from etherfoundry/master Resolving issue JENKINS-13517 (DisplayName) Compare: https://github.com/jenkinsci/copy-project-link-plugin/compare/eb604e69ca94...4fa35d6ba88a 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] [copy-project-link-plugin] (JENKINS-13517) CopyProjectLink plugin: does not work with jobs using 'display name' feature
Title: Message Title SCM/JIRA link daemon commented on JENKINS-13517 Re: CopyProjectLink plugin: does not work with jobs using 'display name' feature Code changed in jenkins User: etherfoundry Path: src/main/java/hudson/plugins/copyProjectLink/CopyAction.java http://jenkins-ci.org/commit/copy-project-link-plugin/79bc4c465f4a4611d00cb1027f95ca6ac5c1f8fe Log: Resolving issue JENKINS-13517 caused by using DisplayName that prevented copying of projects with a Display Name set. 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-25326) Throttle Concurrent Builds doesn't work when builds are in cloudbees folders
Title: Message Title vijay konenki edited a comment on JENKINS-25326 Re: Throttle Concurrent Builds doesn't work when builds are in cloudbees folders Iamexperiencingthesameissuetoowithjenkins1.611,cloudbeesfolderpluginfrom4.6.1to latest 4.8 andthrottleconcurrentbuild1.8.4.Icreatedtwofreestyleprojectsinthetoplevelandtestedforconcurrency,onejobwaswaitingfortheothertocomplete.Imovedboththejobsintoafolderandstartedbothatthesametime,nowtheconcurrencydoesnotwork.Boththejobsstarted simultaneously. inparallel Pleaseletmeknowifyouneedmoredetails.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] [core] (JENKINS-27739) Changes to slave environment variables are ignored by master
Title: Message Title David Rubio commented on JENKINS-27739 Re: Changes to slave environment variables are ignored by master We have the same problem with Jenkins 1.613 (and older versions too) with EnvInject 1.90. This is a pretty bad issue for us because we keep changing the variables of one of our slaves when installing new libraries. Hopefully it'll be fixed 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] [analysis-collector-plugin] (JENKINS-28360) Missing static analysis results in weather popup
Title: Message Title Ulli Hafner commented on JENKINS-28360 Re: Missing static analysis results in weather popup Can you please switch the values? It is for the number of warnings for 100% and 0% health, resp. I.e. the number of warnings for 100% should be smaller than the number of warnings for 0%. 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] [clover-plugin] (JENKINS-3277) Clover Weather Report on main page does not use criteria
Title: Message Title Nick Johns commented on JENKINS-3277 Re: Clover Weather Report on main page does not use criteria This problem is affecting my project too. The administration screen for the coverage thresholds is missing a setting. I can work around this by manually set this setting in the XML config for the job by adding an elementCoverage element with the required value. This results in builds correctly reflecting the weather report. However when making changes to the job via the Jenkins interface this element is lost, requiring me to reapply the manual change. Please add the elementCoverage fields to the admin screen. Cheers, Nick 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] [docker-build-step-plugin] (JENKINS-28371) Not able to access Docker build step plugin
Title: Message Title manoj Kumar updated an issue Jenkins / JENKINS-28371 Not able to access Docker build step plugin Change By: manoj Kumar Attachment: screenshot-6.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] [maven-invoker-plugin] (JENKINS-28373) apache maven 3.3.3 cannot be invoked anymore on windows
Title: Message Title
Thomas Wabner updated an issue
Jenkins / JENKINS-28373
apache maven 3.3.3 cannot be invoked anymore on windows
Change By:
Thomas Wabner
Thenewapache maven version3.3.3hasremovedthemvn.batfileandintroducedanewfilemvn.cmd.Ifweusethisversioninourmavenstylebuilds,wegetmoreorlessthefollowingerror:{{FATAL:Couldn’tfindanyexecutableinD:\current-maven}}Ilookslike,theJenkinsmavenbuildalwayscallsmvn.batinsteadofmvnonly.Itcanbefixedbycreatingalinkwith{{mklink}}onwindowslike{{current-maven/binmklinkmvn.batmvn.cmd}}
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-invoker-plugin] (JENKINS-28373) apache maven 3.3.3 cannot be invoked anymore on windows
Title: Message Title
Thomas Wabner updated an issue
Jenkins / JENKINS-28373
apache maven 3.3.3 cannot be invoked anymore on windows
Change By:
Thomas Wabner
Thenewapacheversion3.3.3hasremovedthemvn.batfileandintroducedanewfilemvn.cmd.Ifweusethisversioninourmavenstylebuilds,wegetmoreorlessthefollowingerror:{{FATAL:Couldn’tfindanyexecutableinD:\current-maven}}Ilookslike,theJenkinsmavenbuildalwayscallsmvn.batinsteadofmvnonly.Itcanbefixed my by creatingalinkwith {{ mklink }} onwindowslike{{current-maven/binmklinkmvn.batmvn.cmd}}
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] [nodelabelparameter-plugin] (JENKINS-28374) NodeLabel vs Rebuild plugin - (pending—Waiting for next available executor)
Title: Message Title Luke Robertson created an issue Jenkins / JENKINS-28374 NodeLabel vs Rebuild plugin - (pending—Waiting for next available executor) Issue Type: Bug Assignee: Luke Robertson Components: nodelabelparameter-plugin, rebuild-plugin Created: 13/May/15 10:02 AM Environment: Jenkins 1.611, NodeLabel 1.5.1, Rebuild 1.22 Priority: Major Reporter: Luke Robertson When using the multi-job plugin to instruct a child job to run on a specified node, the child job cannot be rebuilt using the rebuild plugin. When the job is rebuilt, the value of the NodeChoice field is populated on the screen however this is not read in by the NodeLabel plugin. The job then hangs in the queue with the status (pending—Waiting for next available executor). If the child job is built directly without a parent job, the rebuild successfully reads the Node label and then runs on the given node. Looking at the difference in the HTML, the input field for the node choice has a differing name on scendario 1 against scenario two: Scenario 1 (failed): input name=label value=
[JIRA] [multiple-scms-plugin] (JENKINS-27638) GIT : Fatal : ClassCastException: hudson.scm.SCMRevisionState$None cannot be cast to org.jenkinsci.plugins.multiplescms.MultiSCMRevisionState
Title: Message Title Brantone resolved as Fixed Jenkins / JENKINS-27638 GIT : Fatal : ClassCastException: hudson.scm.SCMRevisionState$None cannot be cast to org.jenkinsci.plugins.multiplescms.MultiSCMRevisionState Change By: Brantone 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] [multiple-scms-plugin] (JENKINS-27638) GIT : Fatal : ClassCastException: hudson.scm.SCMRevisionState$None cannot be cast to org.jenkinsci.plugins.multiplescms.MultiSCMRevisionState
Title: Message Title Brantone commented on JENKINS-27638 Re: GIT : Fatal : ClassCastException: hudson.scm.SCMRevisionState$None cannot be cast to org.jenkinsci.plugins.multiplescms.MultiSCMRevisionState Fix: https://github.com/jenkinsci/multiple-scms-plugin/pull/9 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-28368) Error JDK 5 not supported to run Maven while running Java 6
Title: Message Title Victor Nol commented on JENKINS-28368 Re: Error JDK 5 not supported to run Maven while running Java 6 I am wondering if it's not related to the fact that the maven31-agent.jar and co are compiled using Java 7 since Jenkins only support Java 7… but these artifacts should be able to support older version of Java even though Jenkins does not, no? Because it becomes impossible to use something else than Java 7 to execute jobs in Jenkins then… 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] [multiple-scms-plugin] (JENKINS-27638) GIT : Fatal : ClassCastException: hudson.scm.SCMRevisionState$None cannot be cast to org.jenkinsci.plugins.multiplescms.MultiSCMRevisionState
Title: Message Title Brantone assigned an issue to Brantone Jenkins / JENKINS-27638 GIT : Fatal : ClassCastException: hudson.scm.SCMRevisionState$None cannot be cast to org.jenkinsci.plugins.multiplescms.MultiSCMRevisionState Change By: Brantone Assignee: KevinBell Brantone 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-13779) Git Publisher (tagging) can't work with multipe SCM (ClassCastException: org.jenkinsci.plugins.multiplescms.MultiSCM cannot be cast to hudson.plugins.git.GitSCM)
Title: Message Title Brantone commented on JENKINS-13779 Re: Git Publisher (tagging) can't work with multipe SCM (ClassCastException: org.jenkinsci.plugins.multiplescms.MultiSCM cannot be cast to hudson.plugins.git.GitSCM) Potential fix would be similar to https://github.com/jenkinsci/multiple-scms-plugin/pull/9 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] [docker-build-step-plugin] (JENKINS-28371) Not able to access Docker build step plugin
Title: Message Title manoj Kumar updated an issue Jenkins / JENKINS-28371 Not able to access Docker build step plugin Change By: manoj Kumar Attachment: screenshot-2.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] [copy-project-link-plugin] (JENKINS-22363) Upgrade of copy-project-link from v1.1 to v1.2 fails
Title: Message Title Oliver Gondža assigned an issue to Oliver Gondža Jenkins / JENKINS-22363 Upgrade of copy-project-link from v1.1 to v1.2 fails Change By: Oliver Gondža Assignee: OliverGondža 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-28353) Error in documentation
Title: Message Title Daniel Spilker commented on JENKINS-28353 Re: Error in documentation https://github.com/jenkinsci/job-dsl-plugin/pull/486 Will be fixed in 1.35. Support for Parameterized Trigger Plugin is a mess and should be redone... 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] [copy-project-link-plugin] (JENKINS-13517) CopyProjectLink plugin: does not work with jobs using 'display name' feature
Title: Message Title Oliver Gondža resolved as Fixed Fixed in 1.4. Jenkins / JENKINS-13517 CopyProjectLink plugin: does not work with jobs using 'display name' feature Change By: Oliver Gondža Status: InProgress 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] [jenkins-testswarm] (JENKINS-28369) getting IncompatibleClassChangeError while deploying EAR into WAS8.5 through Jenkins using GitHub
Title: Message Title swetha sreeramoju created an issue Jenkins / JENKINS-28369 getting IncompatibleClassChangeError while deploying EAR into WAS8.5 through Jenkins using GitHub Issue Type: Bug Assignee: Unassigned Components: jenkins-testswarm Created: 13/May/15 8:26 AM Environment: Jenkins 1.611 with JDK 1.7, Remote WAS 8.5 running on JDK 1.6, Eclipse Luna, Windows 7 32-bit Priority: Major Reporter: swetha sreeramoju I have Jenkins of 1.611 version, JDK 1.7 and remote WAS8.5 is running on JDK 1.6 version. When I am trying to deploy EAR or WAR file by the help of Github (i.e., I am pushing the project from eclipse Luna which has java 7 configuration), Iam facing the following error: Connecting to IBM WebSphere Application Server... The following artifacts will be deployed in this order... --- SpringWSEAR.ear --- Error deploying to IBM WebSphere Application Server: org.jenkinsci.plugins.websphere.services.deployment.DeploymentServiceException: at org.jenkinsci.plugins.websphere.services.deployment.WebSphereDeploymentService.getAppName(WebSphereDeploymentService.java:122) at
[JIRA] [docker-build-step-plugin] (JENKINS-28371) Not able to access Docker build step plugin
Title: Message Title manoj Kumar updated an issue Jenkins / JENKINS-28371 Not able to access Docker build step plugin Change By: manoj Kumar Attachment: screenshot-4.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] [docker-build-step-plugin] (JENKINS-28371) Not able to access Docker build step plugin
Title: Message Title manoj Kumar updated an issue Jenkins / JENKINS-28371 Not able to access Docker build step plugin Change By: manoj Kumar Attachment: screenshot-5.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] [pretested-integration-plugin] (JENKINS-28370) Error when trying to integrate to non-existing integration branch Case 13015
Title: Message Title Jan Krag updated an issue Jenkins / JENKINS-28370 Error when trying to integrate to non-existing integration branch Case 13015 Change By: Jan Krag Summary: Errorwhentryingtointegratetonon- existant existing integrationbranch Case13015 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] [copy-project-link-plugin] (JENKINS-18910) CopyProjectLink plugin: does not work with non-root url (http://hostname/jenkins)
Title: Message Title Oliver Gondža resolved as Fixed Vincent Latombe, I presume this is fixed. Jenkins / JENKINS-18910 CopyProjectLink plugin: does not work with non-root url (http://hostname/jenkins) Change By: Oliver Gondža Status: InProgress Resolved Assignee: VincentLatombe 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] [core] (JENKINS-28120) Jenkins core to require Java7
Title: Message Title Krzysztof Malinowski commented on JENKINS-28120 Re: Jenkins core to require Java7 We have some older slaves which run SunOS-5.9 for which Oracle does not provide Java7. Slave upgrade is not a solution either since there are some native legacy tools used in the build system which can only run on this machine. Does this mean I will have to stop upgrading Jenkins in order to have SunOS-5.9 slaves connected? 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-27708) Concurrent build limits not honored on Jenkins 1.607
Title: Message Title Andrei Costescu commented on JENKINS-27708 Re: Concurrent build limits not honored on Jenkins 1.607 Dirk, did you find a solution to the new problem - builds not starting when they should? I didn't update Jenkins recently to avoid hitting new bugs. 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] [github-plugin] (JENKINS-28369) getting IncompatibleClassChangeError while deploying EAR into WAS8.5 through Jenkins using GitHub
Title: Message Title swetha sreeramoju updated an issue Jenkins / JENKINS-28369 getting IncompatibleClassChangeError while deploying EAR into WAS8.5 through Jenkins using GitHub Change By: swetha sreeramoju Labels: jenkinspluginsversion 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-13779) Git Publisher (tagging) can't work with multipe SCM (ClassCastException: org.jenkinsci.plugins.multiplescms.MultiSCM cannot be cast to hudson.plugins.git.GitSCM)
Title: Message Title Brantone updated an issue Jenkins / JENKINS-13779 Git Publisher (tagging) can't work with multipe SCM (ClassCastException: org.jenkinsci.plugins.multiplescms.MultiSCM cannot be cast to hudson.plugins.git.GitSCM) Change By: Brantone Component/s: template-project-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] [github-plugin] (JENKINS-28369) getting IncompatibleClassChangeError while deploying EAR into WAS8.5 through Jenkins using GitHub
Title: Message Title swetha sreeramoju updated an issue Jenkins / JENKINS-28369 getting IncompatibleClassChangeError while deploying EAR into WAS8.5 through Jenkins using GitHub Change By: swetha sreeramoju Component/s: github-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] [pretested-integration-plugin] (JENKINS-28370) Error when trying to push to integrate to non-existant integration branch
Title: Message Title Mads Nielsen created an issue Jenkins / JENKINS-28370 Error when trying to push to integrate to non-existant integration branch Issue Type: Bug Assignee: Praqma Support Components: pretested-integration-plugin Created: 13/May/15 8:50 AM Priority: Minor Reporter: Mads Nielsen We need to check that the integration branch exists somehow. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [docker-build-step-plugin] (JENKINS-28371) Not able to access Docker build step plugin
Title: Message Title manoj Kumar updated an issue Jenkins / JENKINS-28371 Not able to access Docker build step plugin Change By: manoj Kumar Attachment: screenshot-7.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] [maven-invoker-plugin] (JENKINS-28373) apache maven 3.3.3 cannot be invoked anymore on windows
Title: Message Title
Thomas Wabner updated an issue
Jenkins / JENKINS-28373
apache maven 3.3.3 cannot be invoked anymore on windows
Change By:
Thomas Wabner
Thenewapacheversion3.3.3hasremovedthemvn.batfileandintroducedanewfilemvn.cmd.Ifweusethisversioninourmavenstylebuilds,wegetmoreorlessthefollowingerror:{{FATAL:Couldn’tfindanyexecutableinD:\current-maven}}Ilookslike,theJenkinsmavenbuildalwayscallsmvn.batinsteadofmvnonly.Itcanbefixedmycreatingalinkwithmklinkonwindowslike{{current-maven/binmklinkmvn.batmvn.cmd }}
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-invoker-plugin] (JENKINS-28373) apache maven 3.3.3 cannot be invoked anymore on windows
Title: Message Title
Thomas Wabner created an issue
Jenkins / JENKINS-28373
apache maven 3.3.3 cannot be invoked anymore on windows
Issue Type:
Bug
Assignee:
olamy
Components:
maven-invoker-plugin
Created:
13/May/15 9:29 AM
Environment:
Jenkins Node running on Windows
Priority:
Major
Reporter:
Thomas Wabner
The new apache version 3.3.3 has removed the mvn.bat file and introduced a new file mvn.cmd. If we use this version in our maven style builds, we get more or less the following error:
FATAL: Couldn’t find any executable in D:\current-maven
I looks like, the Jenkins maven build always calls mvn.bat instead of mvn only.
It can be fixed my creating a link with mklink on windows like
{{current-maven/bin mklink mvn.bat mvn.cmd }}
[JIRA] [core] (JENKINS-25326) Throttle Concurrent Builds doesn't work when builds are in cloudbees folders
Title: Message Title vijay konenki commented on JENKINS-25326 Re: Throttle Concurrent Builds doesn't work when builds are in cloudbees folders I am experiencing the same issue too with jenkins 1.611, cloudbees folder plugin from 4.6.1 to latest and throttle concurrent build 1.8.4. I created two free style projects in the top level and tested for concurrency, one job was waiting for the other to complete. I moved both the jobs into a folder and started both at the same time, now the concurrency doesnot work. Both the jobs started simultaneously. Please let me know if you need more details. 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] [multiple-scms-plugin] (JENKINS-27638) GIT : Fatal : ClassCastException: hudson.scm.SCMRevisionState$None cannot be cast to org.jenkinsci.plugins.multiplescms.MultiSCMRevisionState
Title: Message Title Brantone edited a comment on JENKINS-27638 Re: GIT : Fatal : ClassCastException: hudson.scm.SCMRevisionState$None cannot be cast to org.jenkinsci.plugins.multiplescms.MultiSCMRevisionState Fix Fixedin :https://github.com/jenkinsci/multiple-scms-plugin/pull/9 ...waitingonmerge. 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] [nodelabelparameter-plugin] (JENKINS-22185) Job with NodeLabel Parameter Plugin does not build in parallel on all nodes which share a label.
Title: Message Title Gert Ceulemans commented on JENKINS-22185 Re: Job with NodeLabel Parameter Plugin does not build in parallel on all nodes which share a label. When using a Node parameter with multiple nodes selected it will run the job on all selected nodes and the Allow multi node selection for concurrent builds option is chosen. I would expect the same to happen for a Label parameter when checking Run on all nodes matching the label otherwise this checkbox is pretty useless since there is the Restrict where this project can be run option. Running the same job on all machines with the same label without having to add a trigger job is extremely useful, it can be used to limit test jobs to a subset of the test slaves e.g. all Windows 7 test slaves. Unfortunately the Node parameter requires much more maintenance compared to using labels. 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-existant integration branch
Title: Message Title Jan Krag updated an issue Jenkins / JENKINS-28370 Error when trying to integrate to non-existant integration branch Change By: Jan Krag Summary: Errorwhentryingto pushto integratetonon-existantintegrationbranch 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] [docker-build-step-plugin] (JENKINS-28371) Not able to access Docker build step plugin
Title: Message Title manoj Kumar updated an issue Jenkins / JENKINS-28371 Not able to access Docker build step plugin Change By: manoj Kumar Attachment: screenshot-1.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] [docker-build-step-plugin] (JENKINS-28371) Not able to access Docker build step plugin
Title: Message Title manoj Kumar created an issue Jenkins / JENKINS-28371 Not able to access Docker build step plugin Issue Type: Bug Assignee: vjuranek Components: docker-build-step-plugin Created: 13/May/15 9:02 AM Priority: Minor Reporter: manoj Kumar I installed docker-build-step plugin in my Jenkins instance but I am unable to find anything related to docker-build-step plugin inside global/project configuration. Please see the screenshot attached. Add Comment
[JIRA] [pretested-integration-plugin] (JENKINS-28370) Error when trying to integrate to non-existant integration branch
Title: Message Title Jan Krag commented on JENKINS-28370 Re: Error when trying to integrate to non-existant integration branch I have two suggestions for solutions: We change the git checkout line to: git checkout -B integration --track origin/integration This will make it fail if the tracking branch doesn't exist. The nicer solution would be to separately verify that the branch exists. This would allow printing an explicit, friendly error message. (Also making it much easier to match this specific problem with Failure Cause plugin) The best way to check if the branch exists, is git ls-remote --exit-code . origin/integration. This will fail with a non-zero exit code if the branch doesn't exist, otherwise print out the sha and branch ref. 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] [copy-project-link-plugin] (JENKINS-22363) Upgrade of copy-project-link from v1.1 to v1.2 fails
Title: Message Title Oliver Gondža resolved as Fixed Caused by optional dependency (cloudbees-folders plugin) not being installed. Fixed in 1.3. Jenkins / JENKINS-22363 Upgrade of copy-project-link from v1.1 to v1.2 fails Change By: Oliver Gondža 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] [android-emulator-plugin] (JENKINS-28378) Option to start emulators only if there are no devices connected already.
Title: Message Title Sren Ranneries created an issue Jenkins / JENKINS-28378 Option to start emulators only if there are no devices connected already. Issue Type: New Feature Assignee: Christopher Orr Components: android-emulator-plugin Created: 13/May/15 1:22 PM Labels: configuration Priority: Minor Reporter: Sren Ranneries We have a setup where develpers may make their device available for jenkins to run tests on. It would be nice if the android emulator plugin could perform a check to see if any devices already are connected to the adb server before starting any new emulator instances. Add Comment
[JIRA] [build-blocker-plugin] (JENKINS-28376) jobs get stuck in queue from time to time
Title: Message Title Manni Heumann commented on JENKINS-28376 Re: jobs get stuck in queue from time to time The strange thing (at least on our instance) is that the queued jobs show no reason for being blocked. Usually, when the build blocker plugin blocks job A because job B is running, the Build Queue widget will accurately reflect this. But now jobs simply end up in the queue and the widget will give no reason for them being blocked. 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] [deploy-plugin] (JENKINS-28377) Add functionality for NTLM authentication
Title: Message Title Edward Quick created an issue Jenkins / JENKINS-28377 Add functionality for NTLM authentication Issue Type: Bug Assignee: Unassigned Attachments: deploy_settings.jpg, jenkins_output.txt Components: deploy-plugin Created: 13/May/15 12:52 PM Labels: plugin security Priority: Minor Reporter: Edward Quick The following tomcat manager can only be accessed by NTLM. This works fine with curl as shown below: $ curl -k --ntlm -u INTRANET\quickedw_web -c cookie https://10.72.19.10:8203/manager/list Enter host password for user 'INTRANET\quickedw_web': OK - Listed applications for virtual host localhost /manager:running:1:manager /probe:running:0:probe But when using the deploy-plugin this fails. My settings are in illustated in the attached screenshot, along with the jenkins output. This is the response logged in tomcat: May 13, 2015 1:42:45 PM
[JIRA] [perforce-plugin] (JENKINS-28367) perforce plugin don't support P4 ticket authentication
Title: Message Title Rob Petti assigned an issue to Unassigned Jenkins / JENKINS-28367 perforce plugin don't support P4 ticket authentication Change By: Rob Petti Assignee: RobPetti 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-27864) 1.608 with git plugin deadlock
Title: Message Title Timo van der Laan reopened an issue We have experienced deadlock problems here also. However they seem to be caused by the sonar plugin version 2.2 and 2.2.1. We found the culprit by looking at 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.init(SonarPublisher.java:420) Reverting back to plugin version 2.1 resolved the problem. Jenkins / JENKINS-27864 1.608 with git plugin deadlock Change By: Timo van der Laan Resolution: Duplicate Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [build-blocker-plugin] (JENKINS-28376) jobs get stuck in queue from time to time
Title: Message Title Dirk von Husen commented on JENKINS-28376 Re: jobs get stuck in queue from time to time Added a link to JENKINS-27708 , because the behavior described in some of the comments sound very similar. 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] [perforce-plugin] (JENKINS-28367) perforce plugin don't support P4 ticket authentication
Title: Message Title Rob Petti commented on JENKINS-28367 Re: perforce plugin don't support P4 ticket authentication How have you passed the ticket into the plugin? It should work fine if you just specify it in place of the password. Alternatively, add it manually to your tickets file on your slave. 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] [android-emulator-plugin] (JENKINS-28378) Option to start emulators only if there are no devices connected already.
Title: Message Title Sren Ranneries started work on JENKINS-28378 Change By: Sren Ranneries Status: Open InProgress 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] [hp-operations-orchestration-automation-execution-plugin] (JENKINS-25373) Test New Feature
Title: Message Title Dan Albu closed an issue as Fixed Closing this test ticket Jenkins / JENKINS-25373 Test New Feature Change By: Dan Albu Status: Resolved Closed Assignee: LucianRevnic DanAlbu 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] [build-blocker-plugin] (JENKINS-28376) jobs get stuck in queue from time to time
Title: Message Title Dirk von Husen created an issue Jenkins / JENKINS-28376 jobs get stuck in queue from time to time Issue Type: Bug Assignee: Unassigned Components: build-blocker-plugin Created: 13/May/15 12:47 PM Environment: Jenkins 1.613, BuildBlockerPlugin 1.6 Priority: Major Reporter: Dirk von Husen Were using the build blocker plugin to prevent certain jobs to be processed at the same time. There jobs are triggered indepenently by time or commits to the scm. From time to time, jobs get stuck in the queue. What I noticed is, that jobs get stuck in the queue, in case more than one job gets queued up, eg. because one job is currently processed, which blocks the second job, and now the third one gets triggered. In case only one job gets queued up, everything looks fine. Help is greatly appreciated...
[JIRA] [embeddable-build-status-plugin] (JENKINS-28375) Provide additional badges (even for some plugins)
Title: Message Title Pablo Bendersky created an issue Jenkins / JENKINS-28375 Provide additional badges (even for some plugins) Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: embeddable-build-status-plugin Created: 13/May/15 12:13 PM Priority: Minor Reporter: Pablo Bendersky It would be great if this plugin had the ability to generate additional badges based on other job metrics such as: Unit tests run / failed Cobertura % (if cobertura is installed) PMD metrics. Add Comment
[JIRA] [copy-project-link-plugin] (JENKINS-18910) CopyProjectLink plugin: does not work with non-root url (http://hostname/jenkins)
Title: Message Title Vincent Latombe commented on JENKINS-18910 Re: CopyProjectLink plugin: does not work with non-root url (http://hostname/jenkins) Indeed, my bad, I forgot to update the status 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] [android-emulator-plugin] (JENKINS-28378) Option to start emulators only if there are no devices connected already.
Title: Message Title Sren Ranneries assigned an issue to Sren Ranneries Jenkins / JENKINS-28378 Option to start emulators only if there are no devices connected already. Change By: Sren Ranneries Assignee: ChristopherOrr SrenRanneries 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-27708) Concurrent build limits not honored on Jenkins 1.607
Title: Message Title Dirk von Husen commented on JENKINS-27708 Re: Concurrent build limits not honored on Jenkins 1.607 No, did not find a solution so far. I am going to create an issue here soon. Since we were still using an older version, I wanted to update first, check if the problem is still there and then come back to this issue. Unfortunately the problem still exists, even after the update to version 1.613. 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] [build-blocker-plugin] (JENKINS-28376) jobs get stuck in queue from time to time
Title: Message Title
Dirk von Husen commented on JENKINS-28376
Re: jobs get stuck in queue from time to time
Yep, same thing here. First the widget shows the reason why the builds are blocked ('blocked by ...'), but when the blocking build is done and the next job could be dequeued, the content of the widget changes and only shows something like 'processed'...
Our instance here runs on german, so actually I do not know the exact descriptions in english
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-27708) Concurrent build limits not honored on Jenkins 1.607
Title: Message Title Dirk von Husen edited a comment on JENKINS-27708 Re: Concurrent build limits not honored on Jenkins 1.607 No,didnotfindasolutionsofar.Iamgoingtocreateanissueheresoon.Sincewewerestillusinganolderversion,Iwantedtoupdatefirst,checkiftheproblemisstillthereandthencomebacktothisissue.Unfortunatelytheproblemstillexists,evenaftertheupdatetoversion1.613. -pleasenoticeJENKINS-28376 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] [websphere-deployer-plugin] (JENKINS-28369) getting IncompatibleClassChangeError while deploying EAR into WAS8.5 through Jenkins using GitHub
Title: Message Title Christopher Orr closed an issue as Duplicate Duplicate of JENKINS-22393. Jenkins / JENKINS-28369 getting IncompatibleClassChangeError while deploying EAR into WAS8.5 through Jenkins using GitHub Change By: Christopher Orr Status: Open Closed Resolution: Duplicate 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-28225) Add include filters for build trigger
Title: Message Title Paul Allen commented on JENKINS-28225 Re: Add include filters for build trigger How are you triggering the Jenkins Job? Polling by SCM or a Perforce trigger? The free Perforce Swarm review tool can trigger the Jenkins job for a particular Perforce project/codeline. 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-28120) Jenkins core to require Java7
Title: Message Title Jesse Glick commented on JENKINS-28120 Re: Jenkins core to require Java7 Does this mean I will have to stop upgrading Jenkins in order to have SunOS-5.9 slaves connected? Sounds that way, unless you can find an OpenJDK 7 port. 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] [websphere-deployer-plugin] (JENKINS-28369) getting IncompatibleClassChangeError while deploying EAR into WAS8.5 through Jenkins using GitHub
Title: Message Title Christopher Orr updated an issue Jenkins / JENKINS-28369 getting IncompatibleClassChangeError while deploying EAR into WAS8.5 through Jenkins using GitHub Change By: Christopher Orr Component/s: github-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] [envinject-plugin] (JENKINS-27665) NPE after updating EnvInject Plugin from 1.90 to 1.91.1
Title: Message Title Signiant Devops commented on JENKINS-27665 Re: NPE after updating EnvInject Plugin from 1.90 to 1.91.1 We've just ran into this as well and it's really bad. We've hit it using the Promoted builds plugin (which I'm guessing uses EnvInject to set the vars). What happens is that all environment variables for a build are lost after a Jenkins restart AFTER we have promoted that build. The test case is: Run a build promote said build (any promotion process) check in the logs - see we got the NPE Check in the jobs folder for the build (ie. in our case /var/lib/jenkins/myproject/builds/574 Note that the injectedEnvVars.txt file is 0 bytes What we see is that subsequent promotions of the same build are fine...until Jenkins is restarted. After which, presumably, it reads the file and zaps all the variables. 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] [vsphere-cloud-plugin] (JENKINS-25955) Restart (and clean) Guest before build
Title: Message Title Jason Swager commented on JENKINS-25955 Re: Restart (and clean) Guest before build From the perspective of a slave, there is no mechanism that can be used to clean a slave between runs of a job. The closest feature that the vSphere Plugin has is the ability to run a specific number of jobs, then revert the VM back to a snapshot. Because clean is ambiguous (remove files, directories, restore files to original state, stop services/processes, run database commands), this sort of logic in a slave plugin is probably not the right place for it. One possible solution: if you have a job that is supposed to run on the slave and needs to be cleaned up after, use either the PostBuild step to clean it up. Or move the cleanup logic to a separate job that gets run immediately after your own job. 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] [mercurial-plugin] (JENKINS-28364) Polling does not work concurrently
Title: Message Title Jesse Glick resolved as Not A Defect IIRC there is a system property you can set to make SCM polling run in multiple threads. Nothing specific to the Mercurial plugin as far as I know. Jenkins / JENKINS-28364 Polling does not work concurrently Change By: Jesse Glick Status: Open Resolved Resolution: NotADefect 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] [vsphere-cloud-plugin] (JENKINS-25955) Restart (and clean) Guest before build
Title: Message Title Alexey Larsky commented on JENKINS-25955 Re: Restart (and clean) Guest before build Under clean i mean revert to snapshoot or permanent state. 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] [vsphere-cloud-plugin] (JENKINS-25955) Restart (and revert) Guest before build
Title: Message Title Alexey Larsky updated an issue Jenkins / JENKINS-25955 Restart (and revert) Guest before build Change By: Alexey Larsky Summary: Restart(and clean revert )Guestbeforebuild 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-28301) P4 workflow checkout should accept a changelist parameter
Title: Message Title Paul Allen commented on JENKINS-28301 Re: P4 workflow checkout should accept a changelist parameter There are a few ways to do this. 1. Set Change or Label using Build Review (see docs on GitHub) 2. Use the pin at label/change to fix a Job to a point in time. 3. Use the incremental option. For points 2 and 3, I do need to update the docs when I get a free moment. 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-28220) Wrong executable permission on checked out file
Title: Message Title Paul Allen commented on JENKINS-28220 Re: Wrong executable permission on checked out file Do you have an unusual UMASK set for the jenkins OS user? This might be a P4Java bug, I'll look into 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] [vsphere-cloud-plugin] (JENKINS-25955) Restart (and revert) Guest before build
Title: Message Title Jason Swager commented on JENKINS-25955 Re: Restart (and revert) Guest before build Reverting to a snapshot after X builds is a feature of the vSphere Plugin. Have you tried it? Does it work for you? I've seen uses of the plugin - particularly the build step parts for creating/deleting snapshots - where a Job is run to update the slave with new software, then a new snapshot. 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-27051) Create specific disable / enable job permission
Title: Message Title Mihai Plasoianu commented on JENKINS-27051 Re: Create specific disable / enable job permission +1, we have the same problem as described by Daniel Beck. Users need to disable/enable nightly jobs quite often, it would be nice if we could allow them to do so, without them being able to touch other settings. 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-28123) Jobs stay queued forever if a node with the label is initially unavailable
Title: Message Title Christian Goetze commented on JENKINS-28123 Re: Jobs stay queued forever if a node with the label is initially unavailable I did check what it does: https://groups.google.com/forum/#!topic/jenkinsci-users/-4S9VYbocyA 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-28123) Jobs stay queued forever if a node with the label is initially unavailable
Title: Message Title
Christian Goetze commented on JENKINS-28123
Re: Jobs stay queued forever if a node with the label is initially unavailable
I run that snippet I showed:
jenkins.model.Jenkins.instance.labels.each { it.reset() }
I'll check what trimLabels() does...
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] [embeddable-build-status-plugin] (JENKINS-17798) build badge icon requires authentication
Title: Message Title Bob Rockers commented on JENKINS-17798 Re: build badge icon requires authentication Sorry to bug everyone on a successfully closed ticket, but where do I actually configure this setting? This is exactly the problem I need to overcome with github's camo image proxy but I cannot find the VIEW_STATUS setting anywhere. 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-28123) Jobs stay queued forever if a node with the label is initially unavailable
Title: Message Title Daniel Beck commented on JENKINS-28123 Re: Jobs stay queued forever if a node with the label is initially unavailable Well, that is embarassing Did the reset() work? 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] [other] (JENKINS-2487) Please wait, getting ready to work takes very long
Title: Message Title Paul Draper commented on JENKINS-2487 Re: Please wait, getting ready to work takes very long @huybrechts, http://n4.nabble.com/Restart-hudson-takes-too-much-time-td386719.html is dead. @Jesse this seems pretty specific. Create dozens of projects and thousands of builds and then start Jenkins. Large numbers of projects and builds slowing down Jenkins startup has been corroborated by many people on this issue. Are you not able to reproduce this issue? What details do you lack? 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] [other] (JENKINS-2487) Please wait, getting ready to work takes very long
Title: Message Title Paul Draper edited a comment on JENKINS-2487 Re: Please wait, getting ready to work takes very long @huybrechts,http://n4.nabble.com/Restart-hudson-takes-too-much-time-td386719.htmlisdead.@Jessethis seems is prettyspecific.Createdozensofprojectsandthousandsofbuilds(aspertheissuedescription)andthenstartJenkins.LargenumbersofprojectsandbuildsslowingdownJenkinsstartuphasbeencorroboratedbymanypeopleonthisissue.Areyounotabletoreproducethisissue?Whatdetailsdoyoulack? 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] [other] (JENKINS-2487) Please wait, getting ready to work takes very long
Title: Message Title Paul Draper edited a comment on JENKINS-2487 Re: Please wait, getting ready to work takes very long @huybrechts,http://n4.nabble.com/Restart-hudson-takes-too-much-time-td386719.htmlisdead.@Jessethisseemsprettyspecific.Createdozensofprojectsandthousandsofbuilds (aspertheissuedescription) andthenstartJenkins.LargenumbersofprojectsandbuildsslowingdownJenkinsstartuphasbeencorroboratedbymanypeopleonthisissue.Areyounotabletoreproducethisissue?Whatdetailsdoyoulack? 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-28357) Cannot use Jelly Template after recent 2.40 fix
Title: Message Title Jon Starbird commented on JENKINS-28357 Re: Cannot use Jelly Template after recent 2.40 fix This particular one is Windows 7 Ultimate. Another one is on Windows 7 Pro with the same Jenkins version but only 2.40 of the plugin, on that one it still works without the extension but I'm not on the 2.40.1. 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-24718) Git plugin should populate 'scmName' property in api output
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-24718 Git plugin should populate 'scmName' property in api output Change By: Mark Waite Component/s: git-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] [dependency-check-jenkins-plugin] (JENKINS-28395) java.lang.NullPointerException after upgrade to v1.2.11
Title: Message Title Alex Mondshain created an issue Jenkins / JENKINS-28395 java.lang.NullPointerException after upgrade to v1.2.11 Issue Type: Bug Assignee: Unassigned Components: dependency-check-jenkins-plugin Created: 14/May/15 4:17 AM Environment: 1.612 Labels: plugin Priority: Major Reporter: Alex Mondshain After upgrade to v1.2.11 i am getting the following error [DependencyCheck] OWASP Dependency-Check Plugin v1.2.11 [DependencyCheck] Executing Dependency-Check with the following options: ERROR: Build step failed with exception java.lang.NullPointerException at org.jenkinsci.plugins.DependencyCheck.DependencyCheckExecutor.performBuild(DependencyCheckExecutor.java:95) at org.jenkinsci.plugins.DependencyCheck.AbstractDependencyCheckBuilder$2.call(AbstractDependencyCheckBuilder.java:96) at org.jenkinsci.plugins.DependencyCheck.AbstractDependencyCheckBuilder$2.call(AbstractDependencyCheckBuilder.java:93) at hudson.remoting.UserRequest.perform(UserRequest.java:121)
[JIRA] [cvs-plugin] (JENKINS-28242) Missing class hudson.scm.cvs.Messages
Title: Message Title Harald Albers closed an issue as Not A Defect Closing because it is an IDE configuration issue. Jenkins / JENKINS-28242 Missing class hudson.scm.cvs.Messages Change By: Harald Albers Status: Resolved Closed 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 after reloading config
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-26582 ISE from RunMap.put after reloading config Here is what I have so far. Despite appearances, this is not a core bug. A change made as part of the implementation of JENKINS-24380 merely made an erroneous condition be displayed as such. The critical point (and the reason why existing automated tests did not catch this) is that the bug is not manifested when you trigger a matrix build normally—only when you install the Git plugin and use /git/notifyCommit. The main bug is in matrix-project: MatrixConfiguration.newBuild assumes without checking that the newly created MatrixRun in fact has a unique build number. If this was created as part of a MatrixBuild, then that will be true, since the MatrixProject uses the default (sane) implementation of newBuild. And that is exactly what happens—normally. But it turns out that there is nothing blocking a MatrixRun from being created other ways. For example, if you ping job/label_exp=S1/build you will get this error, because the number of the last parent MatrixBuild is unchanged, and there was already a MatrixRun with that number. Of course you would not normally go to this URL—it is not exposed in the UI—but there is nothing stopping you from doing that, or I guess from using the CLI to do the same. I presume the initial …since its parent has no builds at all exception has the same cause: an attempt to directly start a MatrixRun without a parent MatrixBuild. Now the reason why this appears with Git notifications is that GitStatus.JenkinsAbstractProjectListener.onNotifyCommit is wrong, too. If you look at SubversionRepositoryStatus or MercurialStatus, you will see that they check whether there is an SCMTrigger for the project which does not ignorePostCommitHooks. If there is not, they print a message (No subversion jobs using SCM polling or all jobs using SCM polling are ignoring post-commit hooks, No SCMTrigger on …), and then do nothing. And if sha1 is unspecified, GitStatus does the same. But if you specify sha1, it immediately schedules a build (with RevisionParameterAction), rather than using polling, even if there is no SCMTrigger. For a top-level project, that is probably fine. But MatrixConfiguration.getScm delegates to its parent, so each configuration shows up in the list of projects matching the specified repo. Thus means that the Git plugin schedules not only the top-level MatrixProject into the queue, but each MatrixConfiguration! And when those children are run directly, the error appears because they are trying to create builds which duplicate an existing number: either that of the last matrix build (if the configurations get scheduled before the parent), or that of the current matrix build (if after). Change By: Jesse Glick
[JIRA] [mercurial-plugin] (JENKINS-28364) Polling does not work concurrently
Title: Message Title Ivan Kurnosov reopened an issue It was closed by mistake, there is no such a property in Jenkins CI. Jenkins / JENKINS-28364 Polling does not work concurrently Change By: Ivan Kurnosov Resolution: NotADefect 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] [email-ext-plugin] (JENKINS-28212) Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher
Title: Message Title Alex Earl resolved as Fixed Should be fixed in the next release, which I will do later today. Jenkins / JENKINS-28212 Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher Change By: Alex Earl Status: InProgress 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] [veracode-scanner-plugin] (JENKINS-28387) Make VeracodeNotifier a SimpleBuildStep
Title: Message Title Nigel Harniman created an issue Jenkins / JENKINS-28387 Make VeracodeNotifier a SimpleBuildStep Issue Type: New Feature Assignee: Mike Bockus Components: veracode-scanner-plugin Created: 13/May/15 9:11 PM Labels: workflow Priority: Major Reporter: Nigel Harniman Would allow for use from workflows. Add Comment
[JIRA] [workflow-plugin] (JENKINS-28385) Step to obtain raw contextual objects
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-28385 Step to obtain raw contextual objects Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 13/May/15 7:19 PM Priority: Major Reporter: Jesse Glick Sometimes it is useful to directly work with Jenkins model objects from a Workflow, such as the FilePath representing the workspace for the enclosing node block. Currently you cannot access these. It would be useful to have a Step which just gave access to a specified contextual object (given as a String class name I suppose). Typically you would need to run in whole-script approval mode, since relevant methods on such objects are not likely to be safe to whitelist for use from the sandbox. Add Comment
[JIRA] [core] (JENKINS-28123) Jobs stay queued forever if a node with the label is initially unavailable
Title: Message Title Christian Goetze commented on JENKINS-28123 Re: Jobs stay queued forever if a node with the label is initially unavailable Actually, that's the point, it didn't appear to work. This being said, this isn't an urgent issue for me anymore, as I simply split the job into two separate jobs with their custom static label setting. Since I generate the jobs via the job DSL plugin, it's no big deal for me. The label assignment plugin failure mode makes it too risky to expose. I spend a whole night debugging the wrong job (the parent job trying to launch it) until I figured out it was the child job's label assignment 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] [email-ext-plugin] (JENKINS-28357) Cannot use Jelly Template after recent 2.40 fix
Title: Message Title Alex Earl commented on JENKINS-28357 Re: Cannot use Jelly Template after recent 2.40 fix I'm not sure where to go on this one. I can't replicate it at all, even using the jpi file you provided. Maybe a remote screen sharing or something? 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-28123) Jobs stay queued forever if a node with the label is initially unavailable
Title: Message Title ikedam resolved as Not A Defect It looks an issue of how to change labels of nodes and not of groovy-label-assignment. Jenkins / JENKINS-28123 Jobs stay queued forever if a node with the label is initially unavailable Change By: ikedam Status: Open Resolved Resolution: NotADefect 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] [mercurial-plugin] (JENKINS-28364) Polling does not work concurrently
Title: Message Title Ivan Kurnosov commented on JENKINS-28364 Re: Polling does not work concurrently If there is - what is it? If there is not - why it's not a bug? 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] [copy-to-slave-plugin] (JENKINS-28386) Workflow support for Copy to Slave plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28386 Re: Workflow support for Copy to Slave plugin Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/workflow-plugin/b07c6a491c37edd69162c3be75bf22fa43066356 Log: JENKINS-28386 Noting. 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-28212) Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28212 Re: Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/EmailRecipientUtils.java src/main/java/hudson/plugins/emailext/ExtendedEmailPublisherDescriptor.java src/main/resources/hudson/plugins/emailext/ExtendedEmailPublisher/config.groovy src/main/resources/hudson/plugins/emailext/ExtendedEmailPublisher/global.groovy http://jenkins-ci.org/commit/email-ext-plugin/faac7b4b7da32c1c45748629631a76989628a3cb Log: Fix JENKINS-28212 Serialize the descriptor id's instead of the descriptors themselves. 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] [other] (JENKINS-2487) Please wait, getting ready to work takes very long
Title: Message Title Daniel Beck commented on JENKINS-2487 Re: Please wait, getting ready to work takes very long has been corroborated by many people on this issue. It's less clear if you consider that Jenkins implemented lazy loading of build records from Oct 2012 to some time in early/mid 2013 (until the major issues were worked out). Then there's the case that some plugins have a tendency to require loading all build records, which defeats this optimization. What details do you lack? Stack traces would be helpful. Lists of installed plugins. Maybe even Support Core plugin support bundles. And of course everything with recent Jenkins versions only. And even then, at least my expectation is that many different causes contribute to a long startup time, which will need to be fixed one by one rather than gathered in a catch-all issue. 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] [copy-to-slave-plugin] (JENKINS-28386) Workflow support for Copy to Slave plugin
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-28386 Workflow support for Copy to Slave plugin Issue Type: New Feature Assignee: Vivekanand SV Components: copy-to-slave-plugin Created: 13/May/15 7:23 PM Labels: workflow Priority: Major Reporter: Jesse Glick CopyToSlaveBuildWrapper looks like it could be made compatible with Workflow (implement SimpleBuildWrapper) without major refactoring. (Unclear to me why this is a BuildWrapper rather than a Builder.) Similarly, CopyToMasterNotifier could be made to implement SimpleBuildStep. (Again unclear why this is a Publisher rather than a Builder.) Add Comment
[JIRA] [prioritysorter-plugin] (JENKINS-24962) Cannot assign a JobGroup to a Nested (sub) View
Title: Message Title SCM/JIRA link daemon commented on JENKINS-24962 Re: Cannot assign a JobGroup to a Nested (sub) View Code changed in jenkins User: emsa23 Path: pom.xml src/main/java/jenkins/advancedqueue/jobinclusion/strategy/ViewBasedJobInclusionStrategy.java src/test/java/jenkins/advancedqueue/test/NestedViewTest.java src/test/resources/jenkins/advancedqueue/test/NestedViewTest/config.xml src/test/resources/jenkins/advancedqueue/test/NestedViewTest/jenkins.advancedqueue.PriorityConfiguration.xml src/test/resources/jenkins/advancedqueue/test/NestedViewTest/jenkins.advancedqueue.PrioritySorterConfiguration.xml http://jenkins-ci.org/commit/priority-sorter-plugin/c4fd31bffee58f7222ed1c72a1d9ca4794f9c0af Log: Added support for ViewGroup in ViewBasedJobInclusion. This also fixes JENKINS-24962 as NestedView is based on ViewGroup 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.
