[JIRA] (JENKINS-49404) A way to force some settings on all jobs in the instance
Title: Message Title Mikael Gaunin updated an issue Jenkins / JENKINS-49404 A way to force some settings on all jobs in the instance Change By: Mikael Gaunin We would like to be able to force some settings on all jobs in the instance somehow In our case:1) Not run concurrent builds. If a build is in progress and another build is in the queue, do not allow any further builds to be triggered or queued. This can be set in individual jobs already but we want to make it an instance setting we apply to all job types on that instance2) Abort after a certain running time. Again, users are able to set this on individual jobs but would like to impose this restriction at instance level to prevent jobs from overrunning and hoarding executors Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubs
[JIRA] (JENKINS-47022) DropDown is loosing focus on selection of an option
Title: Message Title Nicolae Pascu updated JENKINS-47022 Jenkins / JENKINS-47022 DropDown is loosing focus on selection of an option Change By: Nicolae Pascu Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49404) A way to force some settings on all jobs in the instance
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49404 A way to force some settings on all jobs in the instance Change By: Oleg Nenashev Component/s: _unsorted Component/s: global-variable-string-parameter-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49404) A way to force some settings on all jobs in the instance
Title: Message Title Oleg Nenashev commented on JENKINS-49404 Re: A way to force some settings on all jobs in the instance The component is not correct, fixed it Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49404) A way to force some settings on all jobs in the instance
Title: Message Title Oleg Nenashev commented on JENKINS-49404 Re: A way to force some settings on all jobs in the instance Javier Raez Have you tried creating Groovy script triggers for this purpose (https://github.com/jenkinsci/groovy-events-listener-plugin)? It should resolve the use-case though the UX may be far from perfect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49487) Groovy Postbuild under Promotion Actions always opens empty "Classpath entry" resulting "Save" exception
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49487 Groovy Postbuild under Promotion Actions always opens empty "Classpath entry" resulting "Save" exception Change By: Oleg Nenashev Component/s: script-security-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49487) Groovy Postbuild under Promotion Actions always opens empty "Classpath entry" resulting "Save" exception
Title: Message Title Oleg Nenashev assigned an issue to Stefan Wolf Jenkins / JENKINS-49487 Groovy Postbuild under Promotion Actions always opens empty "Classpath entry" resulting "Save" exception Change By: Oleg Nenashev Assignee: Oleg Nenashev Stefan Wolf Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49487) Groovy Postbuild under Promotion Actions always opens empty "Classpath entry" resulting "Save" exception
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49487 Groovy Postbuild under Promotion Actions always opens empty "Classpath entry" resulting "Save" exception Change By: Oleg Nenashev Component/s: groovy-postbuild-plugin Component/s: promoted-builds-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49487) Groovy Postbuild under Promotion Actions always opens empty "Classpath entry" resulting "Save" exception
Title: Message Title Oleg Nenashev commented on JENKINS-49487 Re: Groovy Postbuild under Promotion Actions always opens empty "Classpath entry" resulting "Save" exception The issue is not specific to Promoted Builds, it's how the Script Security plugin gets rendered due to its layout. IMO it should be fixed on its side Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49487) Groovy Postbuild under Promotion Actions always opens empty "Classpath entry" resulting "Save" exception
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-49487 Groovy Postbuild under Promotion Actions always opens empty "Classpath entry" resulting "Save" exception Change By: Oleg Nenashev Assignee: Stefan Wolf Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49487) Groovy Postbuild under Promotion Actions always opens empty "Classpath entry" resulting "Save" exception
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-49487 Groovy Postbuild under Promotion Actions always opens empty "Classpath entry" resulting "Save" exception Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49487) Groovy Postbuild under Promotion Actions always opens empty "Classpath entry" resulting "Save" exception
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49487 Groovy Postbuild under Promotion Actions always opens empty "Classpath entry" resulting "Save" exception Change By: Oleg Nenashev Component/s: promoted-builds-plugin Component/s: groovy-postbuild-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49433) Ommiting "default" value for selfPromotion() causes NPE in JobDSL integration
Title: Message Title Oleg Nenashev started work on JENKINS-49433 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47802) Job's Promotion Status History page does not display Build name
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-47802 Job's Promotion Status History page does not display Build name Change By: Oleg Nenashev Labels: newbie-friendly Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48634) Promoted Builds plugin cannot reexecute promotion- java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48634 Re: Promoted Builds plugin cannot reexecute promotion- java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject Code changed in jenkins User: Oleg Nenashev Path: src/main/java/hudson/plugins/promoted_builds/Status.java http://jenkins-ci.org/commit/promoted-builds-plugin/3849c36245c3ffe4e1d0d4b602c37b2bb13c7c88 Log: Merge pull request #110 from oleg-nenashev/JENKINS-48634 JENKINS-48634 - implement more robust form handling in Status#doBuild() Compare: https://github.com/jenkinsci/promoted-builds-plugin/compare/41412fb9ca3d...3849c36245c3 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48634) Promoted Builds plugin cannot reexecute promotion- java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48634 Re: Promoted Builds plugin cannot reexecute promotion- java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject Code changed in jenkins User: Oleg Nenashev Path: src/main/java/hudson/plugins/promoted_builds/Status.java http://jenkins-ci.org/commit/promoted-builds-plugin/7520623cd415beab40d47bacf4b271147775939c Log: JENKINS-48634 - implement more robust form handling in Status#doBuild() Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49454) Issue with HP ALM Quality Center Plugin
Title: Message Title Rijo Varghese commented on JENKINS-49454 Re: Issue with HP ALM Quality Center Plugin Michael FazioYes I got the above graph. Currently its displaying the following exception. I'm not sure what are the values needed for the field "User Defined Field" where can I find it. It would be of great help if you can show some demo (Screenshot/ Document) on how to configure User Defined Field. The Exception: ERROR: Build step failed with exception org.jenkinsci.plugins.qc.client.QualityCenterException: qccore.invalid-value-type-for-field Failed to convert the "user-05" field of a "test. The object N/A cannot be converted to type Integer org.hp.qc.api.entities.InvalidValueForFieldException: Failed to convert the "user-05" field of a "test. The object N/A cannot be converted to type Integer at org.hp.qc.impl.util.ClassUtil.convertIfNecessary(ClassUtil.java:176) at org.hp.qc.impl.util.ClassUtil.convertIfNecessary(ClassUtil.java:154) at org.hp.qc.impl.entities.EntityImpl.convertIfNecessary(EntityImpl.java:343) at org.hp.qc.impl.entities.EntityImpl.setFieldValue(EntityImpl.java:269) at org.hp.qc.impl.entities.EntityImpl.setFieldValue(EntityImpl.java:287) at org.hp.qc.web.restapi.entities.AbstractBaseResource.performPOSTEntity(AbstractBaseResource.java:154) at org.hp.qc.web.restapi.entities.FirstLevelResource.create(FirstLevelResource.java:74) at sun.reflect.GeneratedMethodAccessor411.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.wink.server.internal.handlers.InvokeMethodHandler.handleRequest(InvokeMethodHandler.java:51) at org.apache.wink.server.handlers.AbstractHandler.handleRequest(AbstractHandler.java:33) at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:26) at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:22) at org.apache.wink.server.handlers.AbstractHandlersChain.doChain(AbstractHandlersChain.java:61) at org.apache.wink.server.internal.handlers.CreateInvocationParametersHandler.handleRequest(CreateInvocationParametersHandler.java:54) at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:26) at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:22) at org.apache.wink.server.handlers.AbstractHandlersChain.doChain(AbstractHandlersChain.java:61) at org.apache.wink.server.internal.handlers.FindResourceMethodHandler.handleResourceMethod(FindResourceMethodHandler.java:151) at org.apache.wink.server.internal.handlers.FindResourceMethodHandler.handleRequest(FindResourceMethodHandler.java:65) at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:26) at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:22) at org.apache.wink.server.handlers.AbstractHandlersChain.doChain(AbstractHandlersChain.java:61) at org.apache.wink.server.internal.handlers.FindRootResourceHandler.handleRequest(FindRootResourceHandler.java:93) at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:26) at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:22) at org.apache.wink.server.handlers.AbstractHandlersChain.doChain(AbstractHandlersChain.java:61) at org.apache.wink.server.internal.handlers.HeadMethodHandler.handleRequest(HeadMethodHandler.java:53) at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:26) at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:22) at or
[JIRA] (JENKINS-49463) jenkins needs a DRY mode which disables schedulers
Title: Message Title Oleg Nenashev edited a comment on JENKINS-49463 Re: jenkins needs a DRY mode which disables schedulers DRY This issue is a bit wider, because somebody will need to disable all dependency/polling triggering in plugins (e.g. in Maven projects).It is a valiant goal, but also a pretty big chunk of work.[~ssbarnea] do you plan to work on this task in short-term? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45128) Locking resource by label breaks windows batch execution
Title: Message Title J P updated an issue Jenkins / JENKINS-45128 Locking resource by label breaks windows batch execution Change By: J P Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49433) Ommiting "default" value for selfPromotion() causes NPE in JobDSL integration
Title: Message Title Oleg Nenashev updated JENKINS-49433 Jenkins / JENKINS-49433 Ommiting "default" value for selfPromotion() causes NPE in JobDSL integration Change By: Oleg Nenashev Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49433) Ommiting "default" value for selfPromotion() causes NPE in JobDSL integration
Title: Message Title Oleg Nenashev commented on JENKINS-49433 Re: Ommiting "default" value for selfPromotion() causes NPE in JobDSL integration Created https://github.com/jenkinsci/promoted-builds-plugin/pull/111 with a hotfix Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49486) Approvers field doesn't expand variable in the build
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-49486 Approvers field doesn't expand variable in the build Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49486) Approvers field doesn't expand variable in the build
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49486 Approvers field doesn't expand variable in the build Change By: Oleg Nenashev Issue Type: Bug New Feature Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48966) Executable permission of archived artifact is not preserved
Title: Message Title Oleg Nenashev resolved as Duplicate AFAICT it is not specific to Promoted Builds and duplicates JENKINS-13128. Please reopen if you see any specific behavior in Promoted Builds which affects it Jenkins / JENKINS-48966 Executable permission of archived artifact is not preserved Change By: Oleg Nenashev Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from
[JIRA] (JENKINS-48966) Executable permission of archived artifact is not preserved
Title: Message Title Oleg Nenashev resolved as Duplicate AFAICT it is not specific to Promoted Builds and duplicates JENKINS-13128. Please reopen if you see any specific behavior in Promoted Builds which affects it Jenkins / JENKINS-48966 Executable permission of archived artifact is not preserved Change By: Oleg Nenashev Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from
[JIRA] (JENKINS-49486) Approvers field doesn't expand variable in the build
Title: Message Title Oleg Nenashev commented on JENKINS-49486 Re: Approvers field doesn't expand variable in the build IMHO it is rather a new feature request, not a defect. Reason: support of properties in this field is not documented anywhere AFAICT. Please correct me if I am wrong Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49488) Promote immediately once the build is complete based on build parameters not working
Title: Message Title Oleg Nenashev commented on JENKINS-49488 Re: Promote immediately once the build is complete based on build parameters not working t should work well according to the code. Could you please provide full build.xml file? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49427) mail commander plugin not working
Title: Message Title Oleg Nenashev commented on JENKINS-49427 Re: mail commander plugin not working Mahesh Ingale Firstly you should provide information about your issue so that others can investigate or reproduce it: https://wiki.jenkins.io/display/JENKINS/How+to+report+an+issue Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49476) Jenkins Error Code 7 on KDE Neon (Ubuntu 16.04LTS)
Title: Message Title Oleg Nenashev commented on JENKINS-49476 Re: Jenkins Error Code 7 on KDE Neon (Ubuntu 16.04LTS) "pam_unix(sudo:session): session closed for user root" It seems there are some permission issues on your system which block Jenkins from starting. Would it be possible to get a full service script startup log? Just run it on your own from sudo with -ex flags Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49225) Graph not generated on scheduled performance jobs
Title: Message Title Kasper Maylann commented on JENKINS-49225 Re: Graph not generated on scheduled performance jobs Hi Artem We schedule the job the standard way with a Build trigger marking it to build periodically based on a CRON _expression_. There is no errors in the log and no graphs when refreshing. Only if I click Build now it generates a graph. Kind regards Kasper Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49466) job directory empty when using declarative pipeline
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49466 job directory empty when using declarative pipeline Change By: Oleg Nenashev Component/s: pipeline-model-definition-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49498) Dutch translation of 'allow users to sign-up' is wrong and creates a security hazard
Title: Message Title Daniel Beck moved an issue Jenkins / JENKINS-49498 Dutch translation of 'allow users to sign-up' is wrong and creates a security hazard Change By: Daniel Beck Project: Security Issues Jenkins Key: SECURITY JENKINS - 728 49498 Workflow: Security v1.2 JNJira + In-Review Component/s: core Component/s: core Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received t
[JIRA] (JENKINS-49498) Dutch translation of 'allow users to sign-up' is wrong and creates a security hazard
Title: Message Title Daniel Beck commented on JENKINS-49498 Re: Dutch translation of 'allow users to sign-up' is wrong and creates a security hazard The point of the private security tracker is to be able to prepare security updates in private and perform a coordinated release. A public PR discloses the issue, negating all benefits of the entire process overhead. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49499) Jenkins admin logs through Logger List not getting captured
Title: Message Title Anand Shekhar created an issue Jenkins / JENKINS-49499 Jenkins admin logs through Logger List not getting captured Issue Type: Task Assignee: Unassigned Components: audit-trail-plugin Created: 2018-02-12 09:46 Priority: Major Reporter: Anand Shekhar Jenkins Events like "Manage and Assign Roles" are not getting captured. Need these events to be captured in the jenkins logger Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49472) Log channel name in Stream Corruption exceptions
Title: Message Title Oleg Nenashev updated JENKINS-49472 Jenkins / JENKINS-49472 Log channel name in Stream Corruption exceptions Change By: Oleg Nenashev Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48718) Jenkins 2.89.2: org.apache.commons.jelly.JellyTagException: JSONObject["displayStrategy"] not found.
Title: Message Title kandhavelu muthuvelan commented on JENKINS-48718 Re: Jenkins 2.89.2: org.apache.commons.jelly.JellyTagException: JSONObject["displayStrategy"] not found. im also getting same problem after upgrading jenkins,how to sort it out. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49469) Nodejs plugin should be able to access npmrc files configured inside folders
Title: Message Title Nikolas Falco commented on JENKINS-49469 Re: Nodejs plugin should be able to access npmrc files configured inside folders Sven Brosi what means "If a npmrc file is created inside a folder" ? The dropdown in build step or build environment option shows only files of kind "Npm config file" present in "Config File Management" through the config plugin. If you want nodejs use a custom .npmrc placed somewhere than add npm_config_userconfig to environment that point to you file. Consider that npm lookup some default places. Have a look here https://docs.npmjs.com/files/npmrc#files Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49469) Nodejs plugin should be able to access npmrc files configured inside folders
Title: Message Title Nikolas Falco edited a comment on JENKINS-49469 Re: Nodejs plugin should be able to access npmrc files configured inside folders [~lidl] what means "If a npmrc file is created inside a folder" ?The dropdown in build step or build environment option shows only files of kind "Npm config file" present in "Config File Management" through the config plugin.If you want nodejs use a custom .npmrc placed somewhere than add *npm_config_userconfig* to environment that point to you your file. Consider that npm lookup some default places. Have a look here [ https://docs.npmjs.com/files/npmrc#files ]For example if you put the .npmrc in the root of the job workspace is it used by default and have precedence on other files Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49469) Nodejs plugin should be able to access npmrc files configured inside folders
Title: Message Title Nikolas Falco edited a comment on JENKINS-49469 Re: Nodejs plugin should be able to access npmrc files configured inside folders [~lidl] what means "If a npmrc file is created inside a folder" ?The dropdown in build step or build environment option shows only files of kind "Npm config file" present in "Config File Management" through the config plugin.If you want nodejs use a custom .npmrc placed somewhere than add *npm_config_userconfig* to environment that point to your file. Consider that npm lookup some default places. Have a look here [https://docs.npmjs.com/files/npmrc#files ] . For example if you put the .npmrc in the root of the job workspace is it used by default and have precedence on other files Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49500) In every pipeline build with triggers, a new trigger is created and the old one is stopped
Title: Message Title valentina armenise created an issue Jenkins / JENKINS-49500 In every pipeline build with triggers, a new trigger is created and the old one is stopped Issue Type: Improvement Assignee: Unassigned Components: workflow-job-plugin Created: 2018-02-12 10:16 Priority: Minor Reporter: valentina armenise Pipeline trigger job properties get recreated (deleted and re-added) from scratch in each build. This is not ideal and could also cause some trigger downtime, ad there seems to be a period of time where a job could have no trigger at all. Add Comment
[JIRA] (JENKINS-49469) Nodejs plugin should be able to access npmrc files configured inside folders
Title: Message Title Nikolas Falco edited a comment on JENKINS-49469 Re: Nodejs plugin should be able to access npmrc files configured inside folders [~lidl] what means "If a npmrc file is created inside a folder" ?The dropdown in build step or build environment option shows only files of kind "Npm config file" present in "Config File Management" through the config plugin.If you want nodejs use a custom .npmrc placed somewhere than add *npm_config_userconfig* to as environment variable that point to your file. Consider that npm lookup some default places. Have a look here [https://docs.npmjs.com/files/npmrc#files].For example if you put the .npmrc in the root of the job workspace is it used by default and have precedence on other files Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49469) Nodejs plugin should be able to access npmrc files configured inside folders
Title: Message Title Bart Devriendt commented on JENKINS-49469 Re: Nodejs plugin should be able to access npmrc files configured inside folders Nikolas Falco With folder we mean a folder in Jenkins where you can group jobs. When you create a new item you can select folder. On folder level it is possible to define configuration files. But the nodejs plugin doesn't take these into account when showing the list of available configuration files. We use folders to group jobs per team and also apply security rules on these folders. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49469) Nodejs plugin should be able to access npmrc files configured inside folders
Title: Message Title Bart Devriendt edited a comment on JENKINS-49469 Re: Nodejs plugin should be able to access npmrc files configured inside folders [~nfalco]With folder we mean a folder in Jenkins where you can group jobs. When you create a new item you can select the option folder. On folder level it is possible to define configuration files. But the nodejs plugin doesn't take these into account when showing the list of available configuration files. We use folders to group jobs per team and also apply security rules on these folders. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49469) Nodejs plugin should be able to access npmrc files configured inside folders
Title: Message Title Nikolas Falco commented on JENKINS-49469 Re: Nodejs plugin should be able to access npmrc files configured inside folders thank you now it's clear. I should check how use the config-file-provider plugin API to get files of folder because now seems returns only global Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49501) Facing NoClasssFoundError on running jobs in Jenkins 2.7.2
Title: Message Title shashi kiran created an issue Jenkins / JENKINS-49501 Facing NoClasssFoundError on running jobs in Jenkins 2.7.2 Issue Type: Bug Assignee: Unassigned Components: workflow-job-plugin Created: 2018-02-12 10:36 Environment: OS - Linux Java version - 1.8 Jenkins version - 2.7.2 Jenkins running as a service Priority: Critical Reporter: shashi kiran Issue occured after an upgrade to one of the plugin - CucumberReports which in turn upgraded pipeline plugins after which the issue occured. Cucumber Report plugin has been uninstalled now. Logs - FATAL: org/jenkinsci/plugins/workflow/job/WorkflowRun java.lang.NoClassDefFoundError: org/jenkinsci/plugins/workflow/job/WorkflowRun at org.jenkinsci.plugins.workflow.job.WorkflowJob$SCMListenerImpl.onCheckout(WorkflowJob.java:621) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:609) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1741) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Circumstance - getting the issue on running any job.
[JIRA] (JENKINS-48649) ......aa
Title: Message Title shashi kiran commented on JENKINS-48649 Re: ..aa Is there any resolution for this issue? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48649) ......aa
Title: Message Title shashi kiran edited a comment on JENKINS-48649 Re: ..aa Facing the same error after upgrading one of the plugins. Is there any resolution for this issue? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49502) trigger properties in scripted pipeline require 2 builds to get registered
Title: Message Title valentina armenise updated an issue Jenkins / JENKINS-49502 trigger properties in scripted pipeline require 2 builds to get registered Change By: valentina armenise Summary: trigger properties in scripted pipeline require 2 builds to be get registered in the UI Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49502) trigger properties in scripted pipeline require 2 builds to be registered in the UI
Title: Message Title
valentina armenise created an issue
Jenkins / JENKINS-49502
trigger properties in scripted pipeline require 2 builds to be registered in the UI
Issue Type:
Bug
Assignee:
Unassigned
Components:
workflow-job-plugin
Created:
2018-02-12 11:03
Priority:
Minor
Reporter:
valentina armenise
When defining trigger in a declarative pipeline, it will suffice to write
pipeline {
agent any
triggers {
cron('H H(0-7) * * *')
}
}
and build once. After the first build accessing the job config UI will show the trigger configuration. However if you do the same thing with a scripted pipeline
node {
properties([pipelineTriggers([cron('H H(0-7) * * *')])])
}
you need two builds to register the trigger (it won't appear in the UI and won't be working until the second manual build).
[JIRA] (JENKINS-49503) Lockable Resources does not unlock after manual unlock via GUI
Title: Message Title David Pamanek created an issue Jenkins / JENKINS-49503 Lockable Resources does not unlock after manual unlock via GUI Issue Type: Bug Assignee: Unassigned Components: lockable-resources-plugin Created: 2018-02-12 11:28 Priority: Major Reporter: David Pamanek When I manually lock some resource via GUI than some pipeline job stop at the point when it is waiting for that resource. So far so good. But when I unlock the resource, pipeline job remain freezed in the state waiting for this resource and it never continues even if the resource is free to use. Add Comment
[JIRA] (JENKINS-26684) Maven build step fail to launch mvn process when special chars are present in build variables
Title: Message Title Oliver Gondža assigned an issue to Unassigned Jenkins / JENKINS-26684 Maven build step fail to launch mvn process when special chars are present in build variables Change By: Oliver Gondža Assignee: Oliver Gondža Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26684) Maven build step fail to launch mvn process when special chars are present in build variables
Title: Message Title Oliver Gondža updated JENKINS-26684 Jenkins / JENKINS-26684 Maven build step fail to launch mvn process when special chars are present in build variables Change By: Oliver Gondža Status: Reopened Open Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29781) BuildTrigger does not reflect moving around declaring job between folders
Title: Message Title Oliver Gondža closed an issue as Won't Do Have not become a priority in a while so closing. Jenkins / JENKINS-29781 BuildTrigger does not reflect moving around declaring job between folders Change By: Oliver Gondža Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-29781) BuildTrigger does not reflect moving around declaring job between folders
Title: Message Title Oliver Gondža stopped work on JENKINS-29781 Change By: Oliver Gondža Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23281) Jenkins.getUser(...) is debilitatingly slow with a large number of users
Title: Message Title Oleg Nenashev commented on JENKINS-23281 Re: Jenkins.getUser(...) is debilitatingly slow with a large number of users I'd guess that JENKINS-47429 solves this issue. It has been released in 2.89.3. Andrew Bayer please confirm Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49459) New parametrization feature of PC Plugin affects the configuration of the job
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49459 Re: New parametrization feature of PC Plugin affects the configuration of the job Code changed in jenkins User: Yafim Kazak Path: src/main/java/com/hpe/application/automation/tools/model/PcModel.java src/main/java/com/hpe/application/automation/tools/pc/PcClient.java src/main/java/com/hpe/application/automation/tools/run/PcBuilder.java http://jenkins-ci.org/commit/hpe-application-automation-tools-plugin/c2d9879ab11f3aa3be023e13d00542ba1063843c Log: Merge pull request #61 from danieldanan/latest fixing defect https://issues.jenkins-ci.org/browse/JENKINS-49459: New parametrization feature of PC Plugin affects the configuration of the job Compare: https://github.com/jenkinsci/hpe-application-automation-tools-plugin/compare/4132dfe563f3...c2d9879ab11f Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49459) New parametrization feature of PC Plugin affects the configuration of the job
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49459 Re: New parametrization feature of PC Plugin affects the configuration of the job Code changed in jenkins User: danieldanan Path: src/main/java/com/hpe/application/automation/tools/model/PcModel.java src/main/java/com/hpe/application/automation/tools/pc/PcClient.java src/main/java/com/hpe/application/automation/tools/run/PcBuilder.java http://jenkins-ci.org/commit/hpe-application-automation-tools-plugin/5c3db55356b69fe547f9989b7b1f51183c6e2d0d Log: fixing defect https://issues.jenkins-ci.org/browse/JENKINS-49459 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49274) Reverse proxy auth is not authenticating users
Title: Message Title Krasimir Popov commented on JENKINS-49274 Re: Reverse proxy auth is not authenticating users What kind of webserver you use to proxy the requests. You need to ensure that all other unnecessary authentication headers are removed (Not proxied to jenkins jetty server). In the case of swarm it is basic auth and the header that you have to remove is Authorization. For nginx proxy_set_header Authorization ""; For Apache RequestHeader set Authorization "" I believe that this is more feature rather then a bug, jenkins security is improved and now there is better order of security layers. If Authorization header is present then jenkins follows to that and you will get 401. Your X-Forwarded-For header is ignored in that case. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49368) Last Changes causes the JENKINS-45892
Title: Message Title Emil Wypych commented on JENKINS-49368 Re: Last Changes causes the JENKINS-45892 Hello, Rafael Pestano ! Could you please update me on the status of this issue? Have you already checked this? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49466) job directory empty when using declarative pipeline
Title: Message Title Andrew Bayer resolved as Duplicate Jenkins / JENKINS-49466 job directory empty when using declarative pipeline Change By: Andrew Bayer Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49426) parallel steps only show branchname as prefix in console output
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-49426 parallel steps only show branchname as prefix in console output Change By: Andrew Bayer Component/s: workflow-cps-plugin Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49388) Passing variables to a Jenkinsfile shell script within "sh"
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-49388 Passing variables to a Jenkinsfile shell script within "sh" Change By: Andrew Bayer Component/s: pipeline-model-definition-plugin Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49388) Passing variables to a Jenkinsfile shell script within "sh"
Title: Message Title Andrew Bayer resolved as Not A Defect You're setting a variable named FOO in the script block, but it's only in that scope. In general, if you need to do this kind of variable-passing, I'd recommend you use Scripted Pipeline, not Declarative. Jenkins / JENKINS-49388 Passing variables to a Jenkinsfile shell script within "sh" Change By: Andrew Bayer Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscr
[JIRA] (JENKINS-49325) @script folder contains full git checkout and is not deleted on cleanup
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-49325 @script folder contains full git checkout and is not deleted on cleanup Change By: Andrew Bayer Component/s: workflow-multibranch-plugin Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49504) ssh-slaves-plugin does not honor global /etc/ssh/ssh_known_hosts
Title: Message Title Philipp Hahn created an issue Jenkins / JENKINS-49504 ssh-slaves-plugin does not honor global /etc/ssh/ssh_known_hosts Issue Type: Bug Assignee: Oleg Nenashev Components: ssh-slaves-plugin Created: 2018-02-12 13:04 Environment: jenkins 2.46.2 ssh-slaves-plugin 1.25.1 Priority: Minor Reporter: Philipp Hahn src/main/java/hudson/plugins/sshslaves/verifiers/KnownHostsFileKeyVerificationStrategy.java only uses the "per-user" file "~/.ssh/known_hosts", but not the global "/etc/ssh/ssh_known_hosts" files. (we roll out that global file to all our hosts to improve security and to remove the "per-user" burdon to verify each host). As "ssh" does not add the host key to the "per-user" file if it is already in the "global" file, this breaks starting a Jenkins slave per ssh until the keys from the global file are manually copied to the "per-user" file. The ssh-slaves-plugin should also honor the global file (if it exists). Add Comment
[JIRA] (JENKINS-49505) workflow-{cps,job,multibranch,support} require step-api 2.13, although 2.14 was released 3 months ago
Title: Message Title
Christian Wansart created an issue
Jenkins / JENKINS-49505
workflow-{cps,job,multibranch,support} require step-api 2.13, although 2.14 was released 3 months ago
Issue Type:
Bug
Assignee:
Unassigned
Components:
workflow-cps-plugin, workflow-job-plugin, workflow-multibranch-plugin, workflow-support-plugin
Created:
2018-02-12 13:10
Labels:
plugin pipeline
Priority:
Minor
Reporter:
Christian Wansart
Jenkins informs me about security updates for workflow-{cps,job,multibranch,support} but I get a warning in the Update Center for each of them:
Warning: This plugin requires dependent plugins be upgraded and at least one of these dependent plugins claims to use a different settings format than the installed version. Jobs using that plugin may need to be reconfigured, and/or you may not be able to cleanly revert to the prior version without manually restoring old settings. Consult the plugin release notes for details.
I checked the dependencies and as it seems, those four plugins require workflow-step-api in version 2.13, but 2.14 was released 3 months ago, according to its plugin site.
[JIRA] (JENKINS-49506) Kubernetes Pipeline Plugin's BuildImageTaskis not compatible with Jenkins 2.102+ (JEP-200)
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-49506 Kubernetes Pipeline Plugin's BuildImageTaskis not compatible with Jenkins 2.102+ (JEP-200) Issue Type: Bug Assignee: Ioannis Canellos Components: kubernetes-pipeline-plugin Created: 2018-02-12 13:40 Priority: Minor Reporter: Oleg Nenashev Follow-up to https://github.com/jenkinsci/kubernetes-pipeline-plugin/pull/66 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-23281) Jenkins.getUser(...) is debilitatingly slow with a large number of users
Title: Message Title Baptiste Mathus commented on JENKINS-23281 Re: Jenkins.getUser(...) is debilitatingly slow with a large number of users At least the style used between Andrew and Sam Van Oort seems to confirm this is the same issue: "debilitatingly slow" and "Absolutely atrocious performance" looks like perfect duplicate to me Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49506) Kubernetes Pipeline Plugin's BuildImageTask was not compatible with Jenkins 2.102+ (JEP-200)
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49506 Kubernetes Pipeline Plugin's BuildImageTask was not compatible with Jenkins 2.102+ (JEP-200) Change By: Oleg Nenashev Summary: Kubernetes Pipeline Plugin's BuildImageTaskis BuildImageTask was not compatible with Jenkins 2.102+ (JEP-200) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49506) Kubernetes Pipeline Plugin's BuildImageTask was not compatible with JEP-200
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49506 Kubernetes Pipeline Plugin's BuildImageTask was not compatible with JEP-200 Change By: Oleg Nenashev Summary: Kubernetes Pipeline Plugin's BuildImageTask was not compatible with Jenkins 2.102+ ( JEP-200 ) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49497) Proxy not set when doing lightweight checkout
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-49497 Proxy not set when doing lightweight checkout Change By: Mark Waite Component/s: git-plugin Component/s: scm-api-plugin Component/s: git-client-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49506) Kubernetes Pipeline Plugin's BuildImageTask was not compatible with JEP-200
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49506 Kubernetes Pipeline Plugin's BuildImageTask was not compatible with JEP-200 Change By: Oleg Nenashev Follow-up to https://github.com/jenkinsci/kubernetes-pipeline-plugin/pull/66 . We worked around the issue by adding a custom whitelist on the core's side (Jenkins 2.102+), but generally it is recommended to merge the change so that we could cleanup the core eventually Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49497) Proxy not set when doing lightweight checkout
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-49497 Proxy not set when doing lightweight checkout Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23281) Jenkins.getUser(...) is debilitatingly slow with a large number of users
Title: Message Title Baptiste Mathus edited a comment on JENKINS-23281 Re: Jenkins.getUser(...) is debilitatingly slow with a large number of users At least the style used between Andrew and [~svanoort] seems to confirm this is the same issue: "debilitatingly slow" and "Absolutely atrocious performance" looks look like perfect duplicate duplicates to me :D . Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43106) pipeline job hangs forever at checkout GitSCM - after git rev-list (sporadic)
Title: Message Title Mark Waite edited a comment on JENKINS-43106 Re: pipeline job hangs forever at checkout GitSCM - after git rev-list (sporadic) [~vrobert78] thanks very much for your investigation and for sharing your results. I'd like to close this bug as a duplicate of JENKINS-48357. JENKINS- 43857 48357 will remain open until the fix is released in the Jira plugin. Is that OK? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43106) pipeline job hangs forever at checkout GitSCM - after git rev-list (sporadic)
Title: Message Title Mark Waite resolved as Duplicate Jenkins / JENKINS-43106 pipeline job hangs forever at checkout GitSCM - after git rev-list (sporadic) Change By: Mark Waite Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43198) JGit Clean before checkout fails (jgit and gitignore with dir/subdir pattern)
Title: Message Title Mark Waite commented on JENKINS-43198 Re: JGit Clean before checkout fails (jgit and gitignore with dir/subdir pattern) Tests from PR239 have been merged. The final assertion in that new test will be ignored until JGit 1.10.1 is included in the git client plugin. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46636) `dir` does not change working directory for contained steps
Title: Message Title Giovanni Silva commented on JENKINS-46636 Re: `dir` does not change working directory for contained steps Logs: Docker version is older than 17.12, working directory will be /var/jenkins_home/workspace/gsilva-pro_master-FNQGFOZNCGYYR7K4UGJOX5A6UTRZHRZ2ZIJHDRTUJOUALWVMZQJA not /var/jenkins_home/workspace/gsilva-pro_master-FNQGFOZNCGYYR7K4UGJOX5A6UTRZHRZ2ZIJHDRTUJOUALWVMZQJA/web-ui Output of docker version: Docker version 17.12.0-ce, build c97c6d6 Host ubuntu server 16.04 LTS Jenkins Blue Ocean running as a docker container version: 1.4.1 · Core 2.89.3 · 61988a2 This is a annoying specially because my repository has multprojects Angular and Java, and I need to change directory for start the builds. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google
[JIRA] (JENKINS-23281) Jenkins.getUser(...) is debilitatingly slow with a large number of users
Title: Message Title Sam Van Oort commented on JENKINS-23281 Re: Jenkins.getUser(...) is debilitatingly slow with a large number of users The user caching behavior has been tweaked a couple times a couple different ways, so I think the variant here can either be closed as no longer applicable or a dupe (doing it now). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46636) `dir` does not change working directory for contained steps
Title: Message Title Giovanni Silva commented on JENKINS-46636 Re: `dir` does not change working directory for contained steps Maybe the code that checks for version has a bug, that do not parse 17.12.0-ce Or maybe the container jenkis has no access to docker. But I'm running with docker.sock mapped correctly Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23281) Jenkins.getUser(...) is debilitatingly slow with a large number of users
Title: Message Title Sam Van Oort closed an issue as Duplicate Jenkins / JENKINS-23281 Jenkins.getUser(...) is debilitatingly slow with a large number of users Change By: Sam Van Oort Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23281) Jenkins.getUser(...) is debilitatingly slow with a large number of users
Title: Message Title Andrew Bayer commented on JENKINS-23281 Re: Jenkins.getUser(...) is debilitatingly slow with a large number of users Yeah, sounds fine to me. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49482) Hide empty 'Deployed Artifacts:'
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49482 Re: Hide empty 'Deployed Artifacts:' Code changed in jenkins User: Cyrille Le Clerc Path: jenkins-plugin/src/main/images/maven-repository.png jenkins-plugin/src/main/images/maven-repository.pxm jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/MavenArtifact.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/MavenSpyLogProcessor.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginDao.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginH2Dao.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginNullDao.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/DependenciesLister.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/FindbugsAnalysisPublisher.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/GeneratedArtifactsPublisher.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/InvokerRunsPublisher.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/JunitTestsPublisher.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/MavenLinkerPublisher.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/MavenLinkerPublisher2.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/MavenReport.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/PipelineGraphPublisher.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/TasksScannerPublisher.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/util/XmlUtils.java jenkins-plugin/src/main/resources/org/jenkinsci/plugins/pipeline/maven/publishers/MavenLinkerPublisher/summary.jelly jenkins-plugin/src/main/resources/org/jenkinsci/plugins/pipeline/maven/publishers/MavenReport/jobMain.jelly jenkins-plugin/src/main/resources/org/jenkinsci/plugins/pipeline/maven/publishers/MavenReport/summary.jelly jenkins-plugin/src/main/resources/sql/h2/06_migration.sql jenkins-plugin/src/main/webapp/icons/maven-repository.png jenkins-plugin/src/main/webapp/images/24x24/maven-repository.png jenkins-plugin/src/main/webapp/images/48x48/maven-repository.png jenkins-plugin/src/test/java/org/jenkinsci/plugins/pipeline/maven/DependencyGraphTest.java jenkins-plugin/src/test/java/org/jenkinsci/plugins/pipeline/maven/MavenPublisherTest.java jenkins-plugin/src/test/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginH2DaoTest.java jenkins-plugin/src/test/java/org/jenkinsci/plugins/pipeline/maven/publishers/DependenciesListerTest.java jenkins-plugin/src/test/java/org/jenkinsci/plugins/pipeline/maven/publishers/GeneratedArtifactsReporterTest.java jenkins-plugin/src/test/java/org/jenkinsci/plugins/pipeline/maven/util/XmlUtilsTest.java jenkins-plugin/src/test/resources/h2/pipleine-maven-plugin.trace.db jenkins-plugin/src/test/resources/org/jenkinsci/plugins/pipeline/maven/maven-spy-deploy-jar.xml http://jenkins-ci.org/commit/pipeline-maven-plugin/4bc703f4590d7e9da6a61352698094423ef5ed09 Log: JENKINS-49482 Netter display of deployed artifacts.
[JIRA] (JENKINS-49361) I am not able to see any plugins under Manage plugins..and also getting below error while trying to install new plugins.
Title: Message Title Durgarao Paila commented on JENKINS-49361 Re: I am not able to see any plugins under Manage plugins..and also getting below error while trying to install new plugins. Thanks for the update Oleg. Could you please suggest how i can resolve this?? Best Regards, Durga Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23281) Jenkins.getUser(...) is debilitatingly slow with a large number of users
Title: Message Title Sam Van Oort edited a comment on JENKINS-23281 Re: Jenkins.getUser(...) is debilitatingly slow with a large number of users [~batmat] Other choice phrasings "user lookup is slower than molasses in winter" and "I like to watch pain paint dry while fetching changelog entries for a large branch." Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23281) Jenkins.getUser(...) is debilitatingly slow with a large number of users
Title: Message Title Sam Van Oort commented on JENKINS-23281 Re: Jenkins.getUser(...) is debilitatingly slow with a large number of users Baptiste Mathus Other choice phrasings "user lookup is slower than molasses in winter" and "I like to watch pain dry while fetching changelog entries for a large branch." Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49378) Using fileExists in when condition causes exception
Title: Message Title Robby Pocase commented on JENKINS-49378 Re: Using fileExists in when condition causes exception I'll likely retest with the _expression_ impl wrapped in a function. I could see that working if its entirely parse related. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49482) Hide empty 'Deployed Artifacts:'
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49482 Re: Hide empty 'Deployed Artifacts:' Code changed in jenkins User: Cyrille Le Clerc Path: jenkins-plugin/src/main/images/maven-repository.png jenkins-plugin/src/main/images/maven-repository.pxm jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/MavenArtifact.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/MavenSpyLogProcessor.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginDao.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginH2Dao.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginNullDao.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/DependenciesLister.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/FindbugsAnalysisPublisher.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/GeneratedArtifactsPublisher.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/InvokerRunsPublisher.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/JunitTestsPublisher.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/MavenLinkerPublisher.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/MavenLinkerPublisher2.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/MavenReport.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/PipelineGraphPublisher.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/TasksScannerPublisher.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/util/XmlUtils.java jenkins-plugin/src/main/resources/org/jenkinsci/plugins/pipeline/maven/publishers/MavenLinkerPublisher/summary.jelly jenkins-plugin/src/main/resources/org/jenkinsci/plugins/pipeline/maven/publishers/MavenReport/jobMain.jelly jenkins-plugin/src/main/resources/org/jenkinsci/plugins/pipeline/maven/publishers/MavenReport/summary.jelly jenkins-plugin/src/main/resources/sql/h2/06_migration.sql jenkins-plugin/src/main/webapp/icons/maven-repository.png jenkins-plugin/src/main/webapp/images/24x24/maven-repository.png jenkins-plugin/src/main/webapp/images/48x48/maven-repository.png jenkins-plugin/src/test/java/org/jenkinsci/plugins/pipeline/maven/DependencyGraphTest.java jenkins-plugin/src/test/java/org/jenkinsci/plugins/pipeline/maven/MavenPublisherTest.java jenkins-plugin/src/test/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginH2DaoTest.java jenkins-plugin/src/test/java/org/jenkinsci/plugins/pipeline/maven/publishers/DependenciesListerTest.java jenkins-plugin/src/test/java/org/jenkinsci/plugins/pipeline/maven/publishers/GeneratedArtifactsReporterTest.java jenkins-plugin/src/test/java/org/jenkinsci/plugins/pipeline/maven/util/XmlUtilsTest.java jenkins-plugin/src/test/resources/h2/pipleine-maven-plugin.trace.db jenkins-plugin/src/test/resources/org/jenkinsci/plugins/pipeline/maven/maven-spy-deploy-jar.xml http://jenkins-ci.org/commit/pipeline-maven-plugin/00f70295817205ee3fcbcd18387deb2dee6cdfc9 Log: JENKINS-49482 Store artifact deployment details in the database and fix display of deployed artifacts. (#125)
[JIRA] (JENKINS-49378) Using fileExists in when condition causes exception
Title: Message Title Andrew Bayer commented on JENKINS-49378 Re: Using fileExists in when condition causes exception Leave this open regardless - I need to figure out how to make ExpressionConditional more resilient for serialization anyway. =) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49038) Jenkins does not start due to a deadlock
Title: Message Title Fly Cricket updated an issue Jenkins / JENKINS-49038 Jenkins does not start due to a deadlock Change By: Fly Cricket Attachment: claim-plugin-2.15.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49038) Jenkins does not start due to a deadlock
Title: Message Title Fly Cricket commented on JENKINS-49038 Re: Jenkins does not start due to a deadlock I've uploaded the HPI via the Jenkins GUI. Jenkins could be restarted without a deadlock. A second restart also worked. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49046) WithTimeout Annotation does not work
Title: Message Title Jesse Glick commented on JENKINS-49046 Re: WithTimeout Annotation does not work Sorry, I thought you were talking about JUnit’s Timeout rule. Yeah @WithTimeout ought to work if it is there. I do not recall ever using it though, and it is not tested, so perhaps it got broken at some point, most likely 2.25. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49490) Failed to run AVD creation on MAC
Title: Message Title theexplorer commented on JENKINS-49490 Re: Failed to run AVD creation on MAC Thanks a lot Christopher Orr , now i am getting this error : please check ! [android] Starting Android emulator $ /Users/sumit.kathuria/Library/Android/sdk/emulator/emulator -skin 320x480 -ports 5760,5761 -report-console tcp:5840,max=60 -prop persist.sys.language=en -prop persist.sys.country=US -avd hudson_en-US_160_HVGA_android-24_google_apis-x86 -no-window _RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL. emulator: WARNING: Requested adb port (5761) is outside the recommended range [,5586]. ADB may not function properly for the emulator. See -help-port for details. [android] Emulator reported that the console is available on port 5,760 [android] Waiting for emulator to finish booting... $ /Users/sumit.kathuria/Library/Android/sdk/platform-tools/adb -s emulator-5760 wait-for-device shell getprop init.svc.bootanim [android] Emulator reported that the startup process is 'stopped' $ /Users/sumit.kathuria/Library/Android/sdk/platform-tools/adb -s emulator-5760 shell logcat -v time [android] Attempting to unlock emulator screen $ /Users/sumit.kathuria/Library/Android/sdk/platform-tools/adb -s emulator-5760 shell wm dismiss-keyguard $ /Users/sumit.kathuria/Library/Android/sdk/platform-tools/adb -s emulator-5760 shell input keyevent 4 [android] Emulator is ready for use (took 13 seconds) [android] Stopping Android emulator emulator: Saving state on exit with session uptime 7540 ms [android] Archiving emulator log $ /Users/sumit.kathuria/Library/Android/sdk/platform-tools/adb kill-server Finished: SUCCESS Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49225) Graph not generated on scheduled performance jobs
Title: Message Title Artem Fedorov updated an issue Jenkins / JENKINS-49225 Graph not generated on scheduled performance jobs Change By: Artem Fedorov Attachment: first.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49507) Jenkins Branch Source Plugin Can't Choose Node/Slave
Title: Message Title Fred Ferguson created an issue Jenkins / JENKINS-49507 Jenkins Branch Source Plugin Can't Choose Node/Slave Issue Type: New Feature Assignee: Ivo Verberk Components: github-branch-source-plugin, nomad-plugin Created: 2018-02-12 15:12 Priority: Minor Reporter: Fred Ferguson We've discovered a problem involving the use of the github branch source plugin and the nomad cloud plugin. We want to be in a situation where no builds are running on the Jenkins master and all are using nomad slaves. Other job types, say freestyle allow to "Restrict where this project can be run" and we specify the name of our Nomad cloud. However there is no option to do that for our Github Organization. When we start a job and there are no cloud slaves running it will sit waiting for an executor until a different job type runs, which starts up a cloud and then the github job jumps on the slave after the original job. It can't create slaves of its own. We plan to primarily use the github branch source (organization) so this presents us with a significant problem. Add Comment
[JIRA] (JENKINS-49225) Graph not generated on scheduled performance jobs
Title: Message Title Artem Fedorov updated an issue Jenkins / JENKINS-49225 Graph not generated on scheduled performance jobs Change By: Artem Fedorov Attachment: second.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49224) Rebuild plugin (v1.25) does not remember merge request params
Title: Message Title
alex d updated an issue
Jenkins / JENKINS-49224
Rebuild plugin (v1.25) does not remember merge request params
Change By:
alex d
Created this issue because an email was sent to the authors, to no avail (two addresses bounced, please also consider updating the contact details at [https://plugins.jenkins.io/rebuild] ). Our Jenkins (v 2.32.3) is successfully configured to run a job upon a GitLab merge request. However, when we hit the Rebuild button of such a job (in our example job 55), a different branch (i.e. master) is being built (for job 56) one would expect that at least the merge request SHA1 would be re-used. the screen shots also show different build input information. Maybe we are misunderstanding the purpose of the plugin? (I've highlighted the associated commits if that can help - it mainly shows that the rebuild uses the master branch). {color:#00}| | * 7f2cb10 (LAH-533-jk-merges) test | | * 6040553 test | | * 07f7bff test | | * 7d99599 LAH-533 JK branch | |/ |/| * | fc4cbc0 Merge branch 'LAH-532-fix-test-suites' into 'master' |\ \ | * | 7bcf795 optional arguments are not required by default. | * | b6efac2 *(tag: job/55*) Fixed ansible tests. | * | 29ef9a6 Rename doc to docs |/ / * | 9072bf5 (*tag: job/56*) Merge branch 'LAH-531-TP-merge' into 'master' |\ \ | * \ 2936294 Merge branch 'LAH-343-vm-ip' into LAH-531-TP-merge | |\ \ {color}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49485) jenkin crashes with {"message":"Bad credentials","documentation_url":"https://developer.github.com/v3"}
Title: Message Title
Jesse Perez reopened an issue
I changed "OAuth Scope(s)" to "read:org, user:email, repo" as you suggested and getting same java dump... java.io.FileNotFoundException: https://api.github.com/user at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:243) at com.squareup.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:210) at com.squareup.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:25) at org.kohsuke.github.Requester.parse(Requester.java:612) at org.kohsuke.github.Requester.parse(Requester.java:594) at org.kohsuke.github.Requester._to(Requester.java:272) Caused: org.kohsuke.github.GHFileNotFoundException: {"message":"Bad credentials","documentation_url":"https://developer.github.com/v3"} at org.kohsuke.github.Requester.handleApiError(Requester.java:686) at org.kohsuke.github.Requester._to(Requester.java:293) at org.kohsuke.github.Requester.to(Requester.java:234) at org.kohsuke.github.GitHub.getMyself(GitHub.java:384) at org.kohsuke.github.GitHub.(GitHub.java:158) at org.kohsuke.github.GitHubBuilder.build(GitHubBuilder.java:207) at org.jenkinsci.plugins.GithubAuthenticationToken.getGitHub(GithubAuthenticationToken.java:211) at org.jenkinsci.plugins.GithubAuthenticationToken.(GithubAuthenticationToken.java:126) at org.jenkinsci.plugins.GithubSecurityRealm$1.authenticate(GithubSecurityRealm.java:478) Caused: java.lang.RuntimeException at org.jenkinsci.plugins.GithubSecurityRealm$1.authenticate(GithubSecurityRealm.java:482) Is there any other logs or places we can look for more clues? Thanks, Jesse
Jenkins / JENKINS-49485
jenkin crashes with {"message":"Bad credentials","documentation_url":"https://developer.github.com/v3"}
Change By:
Jesse Perez
Resolution:
Cannot Reproduce
Status:
Resolved Reopened
[JIRA] (JENKINS-49225) Graph not generated on scheduled performance jobs
Title: Message Title Artem Fedorov commented on JENKINS-49225 Re: Graph not generated on scheduled performance jobs Kasper I configured Build periodically with the following value "*/1 * * * *" that means build each minute and I got the following result: At the first build in my job history I haven't Performance report graphs, because plugins cannot compare the first build with nothing. A few minutes after I have more builds and all of them have graphs in Performance Report As I understand your screenshots now you executed manually Builds 60 & 61. Than you removed them and settup build periodically (build 62 and also removed build 62). And after it you open the first build (#63) that doesn't contains graphs, because it haven't builds story. Is my assumption correct? Could you reproduce my experiment? Thanks, Artem Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49508) warnings-plugin aborts if unable to git-blame.
Title: Message Title
Erik Jonsson created an issue
Jenkins / JENKINS-49508
warnings-plugin aborts if unable to git-blame.
Issue Type:
Bug
Assignee:
Ulli Hafner
Components:
warnings-plugin
Created:
2018-02-12 15:30
Priority:
Major
Reporter:
Erik Jonsson
The warnings-plugin will abort the build if it's unable to git-blame on the reported lines. In my source project some .c-files are generated, obviously these will not be in git. There must be some way to skip the blame-step or at least not abort the build if the plugin is unable to parse some of the warnings. Using GitBlamer to create author and commit information for all warnings. GIT_COMMIT=6c3c3da9609eb7a9907bdb4a3b3806f90a97f6e6, workspace=/repo/bbiswjenk/fem023-eiffel003/workspace/instanttoolsmith_flasm > git rev-parse 6c3c3da9609eb7a9907bdb4a3b3806f90a97f6e6^{commit} # timeout=10 No blame results for request [132, 2126]>. No blame results for request [64410]>. No blame results for request [132, 2126]>. No blame results for request [16174]>.
Add Comment
