[JIRA] (JENKINS-56392) classic -> blue-ocean links to subfolder jobs are wrong
Title: Message Title Björn Pedersen commented on JENKINS-56392 Re: classic -> blue-ocean links to subfolder jobs are wrong https://github.com/jenkinsci/blueocean-plugin/pull/2042 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197982.1551715632000.6314.1574693701011%40Atlassian.JIRA.
[JIRA] (JENKINS-56392) classic -> blue-ocean links to subfolder jobs are wrong
Title: Message Title Björn Pedersen updated an issue Jenkins / JENKINS-56392 classic -> blue-ocean links to subfolder jobs are wrong Change By: Björn Pedersen Summary: classic -> blue-ocean links from classic do not use https to subfolder jobs are wrong Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197982.1551715632000.6283.1574688780145%40Atlassian.JIRA.
[JIRA] (JENKINS-60229) Jenkins 2.205 unable to get updates / update details
Title: Message Title Björn Pedersen commented on JENKINS-60229 Re: Jenkins 2.205 unable to get updates / update details https://issues.jenkins-ci.org/browse/INFRA-2345 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203204.157429000.4472.1574262120432%40Atlassian.JIRA.
[JIRA] (JENKINS-60229) Jenkins 2.205 unable to get updates / update details
Title: Message Title Björn Pedersen edited a comment on JENKINS-60229 Re: Jenkins 2.205 unable to get updates / update details https://issues.jenkins-ci.org/browse/INFRA-2345 There are expired certificates used to sign these tool bundles. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203204.157429000.4474.1574262120460%40Atlassian.JIRA.
[JIRA] (JENKINS-59903) durable-task v1.31 breaks sh steps in pipeline when running in a Docker container
Title: Message Title Björn Pedersen commented on JENKINS-59903 Re: durable-task v1.31 breaks sh steps in pipeline when running in a Docker container Here we are also affected (rolled back to 1.30) for docker.inside steps. The problems is that the new wrapper binary is at a location that is (on purpose) not exposed inside the docker container. Only the workspace and auxilliary workspace (workspace@tmp ) are currently mapped into the container by default. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202653.1571840997000.1308.1571995922034%40Atlassian.JIRA.
[JIRA] (JENKINS-56951) JIRA plugin config incorrectly mixed with properties section
Title: Message Title Björn Pedersen created an issue Jenkins / JENKINS-56951 JIRA plugin config incorrectly mixed with properties section Issue Type: Bug Assignee: Francisco Fernández Attachments: screenshot-forge.frm2.tum.de-2019.04.10-06-50-16.png, screenshot-forge.frm2.tum.de-2019.04.10-06-55-55.png Components: cloudbees-folder-plugin, core, jira-plugin Created: 2019-04-10 04:58 Priority: Minor Reporter: Björn Pedersen See screenshot, the Jira plugin config (here on Folder level and on multibranch projects) is intermixed with the folder properties section ( as can be seen by the "Enable ..-based security" item that is not related to jira) . In normal pipeline jobs, they are correctly separated. Add Comment
[JIRA] (JENKINS-56392) blue-ocean links from classic do not use https
Title: Message Title Björn Pedersen commented on JENKINS-56392 Re: blue-ocean links from classic do not use https Yes, in the current version the redirect goes to https. But it still does not work correctly: Link in the classic UI to blue ocean: https://forge.frm2.tum.de/jenkins/blue/organizations/jenkins/Administration%2FDeployWebapps First response is (note that now the escaped slash has been expanded): HTTP/1.1 302 Found Date: Thu, 04 Apr 2019 05:15:22 GMT Server: Jetty(9.4.z-SNAPSHOT) X-Content-Type-Options: nosniff X-Blueocean-Refresher: f4df0e2b Location: https://forge.frm2.tum.de/jenkins/blue/organizations/jenkins/Administration/DeployWebapps/ Keep-Alive: timeout=5, max=100 Connection: Keep-Alive Transfer-Encoding: chunked Setup: Apache in front of jenkins, so it seems it is the redirect to append the missing slash at the end that causes this behaviour (Manually add the slash results in a successful page load) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56392) blue-ocean links from classic do not use https
Title: Message Title Björn Pedersen commented on JENKINS-56392 Re: blue-ocean links from classic do not use https Even so with setting the proxy header to https explicitly the request will use https, it still fails with a 404. Note that the redirect actually happens inside jenkins (server: jetty), not on the apache side. It seems like adding a slash at the end of the URL actually will load the right page, maybe that is the missing part. (I still consider relying on the incoming request headers to determine the host/protocol a security flaw, absolute urls should always use the configured Jenkins URL independent from the incoming request). Can you point me to the code where these urls are compute, then I'll try to find a patch for it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56392) blue-ocean links from classic do not use https
Title: Message Title Björn Pedersen created an issue Jenkins / JENKINS-56392 blue-ocean links from classic do not use https Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2019-03-04 16:07 Priority: Minor Reporter: Björn Pedersen trying to open a job located in a folder from the classic view (open- blue ocean link) raises a 404 error. The URL in the link has correct escaping of slashes Inspecting the http-requests seems to indicate that jenkins sends an intermediate page via Location: that is not using https. Initals request (https) GET /jenkins/blue/organizations/jenkins/debocker%2FBuildEntangleContainersV2 HTTP/1.1 Host: User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:65.0) Gecko/20100101 Firefox/65.0 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,/;q=0.8 Accept-Language: en-US,en;q=0.5 Accept-Encoding: gzip, deflate, br Referer: https:///jenkins/job/debocker/job/BuildEntangleContainersV2/ Connection: keep-alive Cookie: screenResolution=1920x1200; jenkins-timestamper-offset=-360; jenkins-timestamper=none; jenkins-timestamper-local=true; Upgrade-Insecure-Requests: 1 Response: HTTP/1.1 302 Found Date: Mon, 04 Mar 2019 15:43:13 GMT Server: Jetty(9.4.z-SNAPSHOT) X-Content-Type-Options: nosniff X-Blueocean-Refresher: . Location: http://forge.frm2.tum.de/jenkins/blue/organizations/jenkins/debocker/BuildEntangleContainersV2/ Keep-Alive: timeout=5, max=86 Connection: Keep-Alive Transfer-Encoding: chunked Note the http in there. Possibly also related to JENKINS-46347
[JIRA] (JENKINS-55340) warnings-ng: pylint parser should use new-style labels
Title: Message Title Björn Pedersen commented on JENKINS-55340 Re: warnings-ng: pylint parser should use new-style labels In your example, Episode is the class (or function?) that is missing the docstring. This part could be used to calculate module/package information for python projects. But that would be a separate topic. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55340) warnings-ng: pylint parser should use new-style labels
Title: Message Title Björn Pedersen commented on JENKINS-55340 Re: warnings-ng: pylint parser should use new-style labels https://github.com/jenkinsci/analysis-model/pull/73 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55340) warnings-ng: pylint parser should use new-style labels
Title: Message Title Björn Pedersen commented on JENKINS-55340 Re: warnings-ng: pylint parser should use new-style labels Yes , that is related. I'll try if I can provide a pull request for this. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55340) warnings-ng: pylint parser should use new-style labels
Title: Message Title
Björn Pedersen created an issue
Jenkins / JENKINS-55340
warnings-ng: pylint parser should use new-style labels
Issue Type:
Improvement
Assignee:
Ulli Hafner
Components:
warnings-ng-plugin
Created:
2018-12-27 05:56
Priority:
Trivial
Reporter:
Björn Pedersen
Currently the category for the builtin parser is set to the old-style numeric warnings ("msg_id") (W0xxx). I think it would be better to use the textual representation by default ( the "symbol"), as these are easily human-readable, while the numeric ones always require a lookup.
Add Comment
[JIRA] (JENKINS-55339) warnings next-generation: wiki link to issue tracker references a private filter
Title: Message Title Björn Pedersen created an issue Jenkins / JENKINS-55339 warnings next-generation: wiki link to issue tracker references a private filter Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2018-12-27 05:49 Priority: Minor Reporter: Björn Pedersen The wiki points to https://issues.jenkins-ci.org/issues/?filter=10025, but Jira does not find the filter: The requested filter doesn't exist or is private. Add Comment This message was sent by
[JIRA] (JENKINS-55293) Unable to set healthy levels to 0
Title: Message Title Björn Pedersen created an issue Jenkins / JENKINS-55293 Unable to set healthy levels to 0 Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2018-12-21 10:00 Priority: Minor Reporter: Björn Pedersen I tried to set the health report level to healthy: 0 unhealthy: 1 this causes an error, that both healthy and unhealthy should be set. (guess : code needs to discriminiate between NULL/unset and 0/zero.) Add Comment This message was sent by
[JIRA] (JENKINS-54987) BlueOcean not opening builds created within folders
Title: Message Title Björn Pedersen updated an issue Jenkins / JENKINS-54987 BlueOcean not opening builds created within folders Change By: Björn Pedersen Component/s: cloudbees-folder-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54987) BlueOcean not opening builds created within folders
Title: Message Title Björn Pedersen commented on JENKINS-54987 Re: BlueOcean not opening builds created within folders I observe the same effect. Further analyis: On clicking the link, the following request happen: GET https://server/jenkins/blue/organizations/jenkins/Generic%2FPythonGenericPylint/detail/PythonGenericPylint/801 [HTTP/1.1 302 Found 12ms] 10:47:12.199 GET http://server/jenkins/blue/organizations/jenkins/Generic/PythonGenericPylint/detail/PythonGenericPylint/801/ Note the missing "/" at the end of the first request. This then results in a redirect to the to a http endpoint that loses the encoded slash. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54941) missing whitelist: String.valueO(int)
Title: Message Title Björn Pedersen created an issue Jenkins / JENKINS-54941 missing whitelist: String.valueO(int) Issue Type: Improvement Assignee: Andrew Bayer Components: script-security-plugin Created: 2018-11-29 12:35 Priority: Minor Reporter: Björn Pedersen A follow-up for JENKINS-27390: String.valueOf(Object) is whitelisted, but e.g. String.valueOf(int) is missing. (Probably float and other types could be affected as well) Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-54894) Server becomes compute bound and unresponsive to http requests after org.jenkinsci.plugins.workflow.support.concurrent.Timeout lambda$ping$0
Title: Message Title Björn Pedersen commented on JENKINS-54894 Re: Server becomes compute bound and unresponsive to http requests after org.jenkinsci.plugins.workflow.support.concurrent.Timeout lambda$ping$0 From the error message this looks the root cause here is a ldap missconfiguration ( looping ldap referrals). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54061) org.apache.commons.jelly.impl.TagScript.handleException
Title: Message Title Björn Pedersen reopened an issue I got a similar stacktrace after upgrading to 1.29.0. This renders the ui unusable, as the trace appears on all pages. Jenkins / JENKINS-54061 org.apache.commons.jelly.impl.TagScript.handleException Change By: Björn Pedersen Resolution: Cannot Reproduce Status: Closed Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51123) Deadlock in CpsFlowExecution
Title: Message Title Björn Pedersen commented on JENKINS-51123 Re: Deadlock in CpsFlowExecution Is this fixed by the fix for issue 51132 as well? 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Björn Pedersen updated an issue Jenkins / JENKINS-51132 workflow blocks on cps.CpsFlowExecution.getCurrentHeads Change By: Björn Pedersen Priority: Minor Critical 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Björn Pedersen updated an issue Jenkins / JENKINS-51132 workflow blocks on cps.CpsFlowExecution.getCurrentHeads Change By: Björn Pedersen After some time, jenkins hangs on workflow-related requests: This occured after an update of workflow-cps from 2.49 and workflow-jobs from 2.19.2 current requests [ !https://forge.frm2.tum.de/jenkins/monitoring?resource=hourglass.png|width=16,height=16! View in a new page|https://host/jenkins/monitoring?part=currentRequests] !https://host/jenkins/monitoring?resource=bullets/minus.png|id=contextDetailshttp28023Img! Details || Thread|| Request|| Elapsed time (ms)|| Mean time (ms)|| Cpu time (ms)|| Mean cpu time (ms)|| Executed method|| Kill|||Handling GET /jenkins/view/NICOS/job/NicosPipelineDocker/wfapi/runs from xxx.xx.xx. : RequestHandlerThread[#6]| [/view/NICOS/job/NicosPipelineDocker/wfapi/runs?since=%235853=true&_=1525424331349 ajax GET| 226,453|108|8|18|org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.getCurrentHeads([CpsFlowExecution.java:962|https://forge.frm2.tum.de/jenkins/monitoring?part=source=org.jenkinsci.plugins.workflow.cps.CpsFlowExecution#962])|[!https://forge.frm2.tum.de/jenkins/monitoring?resource=stop.png|width=16,height=16!|https://forge.frm2.tum.de/jenkins/monitoring?action="">|Handling GET /jenkins/ from xxx.xxx.xxx..xxx : RequestHandlerThread[#46] View/index.jelly View/sidepanel.jelly ExecutorStepExecution/PlaceholderTask/PlaceholderExecutable/executorCell.jelly| [/ GET|https://forge.frm2.tum.de/jenkins/monitoring?part=graph=http9b051a0212745888c373b46ee5f27d9d6d905d45]|!https://forge.frm2.tum.de/jenkins/monitoring?resource=dbweb.png|width=16,height=16! 108,266|9,526|61|8,280|org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.getCurrentHeads([CpsFlowExecution.java:962|https://forge.frm2.tum.de/jenkins/monitoring?part=source=org.jenkinsci.plugins.workflow.cps.CpsFlowExecution#962])|[!https://forge.frm2.tum.de/jenkins/monitoring?resource=stop.png|width=16,height=16!|https://forge.frm2.tum.de/jenkins/monitoring?action="">h3. !https://forge.frm2.tum.de/jenkins/monitoring?resource=systeminfo.png! Add Comment
[JIRA] (JENKINS-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Björn Pedersen updated an issue Jenkins / JENKINS-51132 workflow blocks on cps.CpsFlowExecution.getCurrentHeads Change By: Björn Pedersen After some time, jenkins hangs on workflow-related requests: This occured after an update of workflow-cps from 2.49 and workflow-jobs from 2.19.2 current requests [!/host/jenkins/monitoring?resource=pdf.png! PDF|https://hostjenkins/monitoring?part=currentRequests=pdf] [ !https://forge.frm2.tum.de/jenkins/monitoring?resource=hourglass.png|width=16,height=16! View in a new page|https://host/jenkins/monitoring?part=currentRequests] !https://host/jenkins/monitoring?resource=bullets/minus.png|id=contextDetailshttp28023Img! Details || Thread|| Request|| Elapsed time (ms)|| Mean time (ms)|| Cpu time (ms)|| Mean cpu time (ms)|| Executed method|| Kill|||Handling GET /jenkins/view/NICOS/job/NicosPipelineDocker/wfapi/runs from xxx.xx.xx. : RequestHandlerThread[#6]| [/view/NICOS/job/NicosPipelineDocker/wfapi/runs?since=%235853=true&_=1525424331349 ajax GET| 226,453|108|8|18|org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.getCurrentHeads([CpsFlowExecution.java:962|https://forge.frm2.tum.de/jenkins/monitoring?part=source=org.jenkinsci.plugins.workflow.cps.CpsFlowExecution#962])|[!https://forge.frm2.tum.de/jenkins/monitoring?resource=stop.png|width=16,height=16!|https://forge.frm2.tum.de/jenkins/monitoring?action="">|Handling GET /jenkins/ from xxx.xxx.xxx..xxx : RequestHandlerThread[#46] View/index.jelly View/sidepanel.jelly ExecutorStepExecution/PlaceholderTask/PlaceholderExecutable/executorCell.jelly| [/ GET|https://forge.frm2.tum.de/jenkins/monitoring?part=graph=http9b051a0212745888c373b46ee5f27d9d6d905d45]|!https://forge.frm2.tum.de/jenkins/monitoring?resource=dbweb.png|width=16,height=16! 108,266|9,526|61|8,280|org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.getCurrentHeads([CpsFlowExecution.java:962|https://forge.frm2.tum.de/jenkins/monitoring?part=source=org.jenkinsci.plugins.workflow.cps.CpsFlowExecution#962])|[!https://forge.frm2.tum.de/jenkins/monitoring?resource=stop.png|width=16,height=16!|https://forge.frm2.tum.de/jenkins/monitoring?action="">h3. !https://forge.frm2.tum.de/jenkins/monitoring?resource=systeminfo.png! Add Comment
[JIRA] (JENKINS-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Björn Pedersen created an issue Jenkins / JENKINS-51132 workflow blocks on cps.CpsFlowExecution.getCurrentHeads Issue Type: Bug Assignee: Unassigned Attachments: st1.log Components: workflow-cps-plugin, workflow-job-plugin Created: 2018-05-04 09:54 Environment: jenkins 2.118 / 2.119 workflow-cps 2.51 workflow-jobs 2.21 Priority: Minor Reporter: Björn Pedersen After some time, jenkins hangs on workflow-related requests: This occured after an update of workflow-cps from 2.49 and workflow-jobs from 2.19. 2 current requests Unable to render embedded object: File (/host/jenkins/monitoring?resource=pdf.png) not found. PDF [ View in a new page|https://host/jenkins/monitoring?part=currentRequests] Details Thread Request Elapsed time (ms) Mean time (ms) Cpu time (ms) Mean cpu time (ms)
[JIRA] (JENKINS-39010) Comment Added event does not work
Title: Message Title Björn Pedersen commented on JENKINS-39010 Re: Comment Added event does not work Ry Jones: I think this actually excpected behaviour: The plugin filters it's own comments to avoid trigger-loops. One solution: use the gerrit ssh cli to post the review 'DO BUILD 1' with another account to force triggering, or just trigger the other job directly (there are different ways to do that in jenkins...) 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-39971) Manual update button hidden if no plugins to update availabe.
Title: Message Title Björn Pedersen commented on JENKINS-39971 Re: Manual update button hidden if no plugins to update availabe. https://github.com/jenkinsci/jenkins/pull/2668 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39971) Manual update button hidden if no plugins to update availabe.
Title: Message Title Björn Pedersen commented on JENKINS-39971 Re: Manual update button hidden if no plugins to update availabe. See comment on https://github.com/jenkinsci/jenkins/commit/a51edf7c652c9eaef100ffa94e594ccd2c5b67a3. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39971) Manual update button hidden if no plugins to update availabe.
Title: Message Title Björn Pedersen created an issue Jenkins / JENKINS-39971 Manual update button hidden if no plugins to update availabe. Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Nov/23 1:34 PM Priority: Minor Reporter: Björn Pedersen The 'Update now' button in the plugin manager is not visible on the 'Available plugins', if there are no updates. One hsa to switch to the advanced tab to find it. As soon as at least one update is available, the button appears. Probably it gets hidden together with the "update plugins" button as the complete bottom-sticker div is gone. (note: component set to core, as I could find a plugin manager comp.) Add Comment
[JIRA] (JENKINS-36139) For comapt with jgit4 TreeWalk.release needs to be replaced.
Title: Message Title Björn Pedersen resolved as Fixed As http://example.com]https://github.com/jenkinsci/gerrit-trigger-plugin/pull/291 is released in 2.22.0, I think this can be resolved. Jenkins / JENKINS-36139 For comapt with jgit4 TreeWalk.release needs to be replaced. Change By: Björn Pedersen Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-36492) 2.7.1 update check shows weekly version instead of LTS
Title: Message Title Björn Pedersen updated an issue Jenkins / JENKINS-36492 2.7.1 update check shows weekly version instead of LTS https://github.com/jenkinsci/backend-update-center2/pull/89 should fix this. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37153) Parallel Job with same test case for different gerrit id for a same repo in Gerrit plugin
Title: Message Title Björn Pedersen commented on JENKINS-37153 Re: Parallel Job with same test case for different gerrit id for a same repo in Gerrit plugin Just enable parallel builds of the job and have enough executors available. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36492) 2.7.1 update check shows weekly version instead of LTS
Title: Message Title Björn Pedersen reopened an issue I observe the inverse behaviour now: a 2.17 install offers upgrade to 2.19.1 LTS instead 2.24. Jenkins / JENKINS-36492 2.7.1 update check shows weekly version instead of LTS Change By: Björn Pedersen Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
[JIRA] (JENKINS-36139) For comapt with jgit4 TreeWalk.release needs to be replaced.
Title: Message Title Björn Pedersen commented on JENKINS-36139 Re: For comapt with jgit4 TreeWalk.release needs to be replaced. The problem is fixed for me with 2.22.0-beta1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36139) For comapt with jgit4 TreeWalk.release needs to be replaced.
Title: Message Title Björn Pedersen created an issue Jenkins / JENKINS-36139 For comapt with jgit4 TreeWalk.release needs to be replaced. Issue Type: Bug Assignee: rsandell Components: gerrit-trigger-plugin Created: 2016/Jun/22 9:13 AM Priority: Minor Reporter: Björn Pedersen See https://groups.google.com/forum/#!topic/jenkinsci-dev/XHwAba2kMc8 for details. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] [gerrit-trigger-plugin] (JENKINS-34753) Sec-170-releated: gerrit-trigger needs to declare parameters
Title: Message Title Björn Pedersen commented on JENKINS-34753 Re: Sec-170-releated: gerrit-trigger needs to declare parameters Fix is released, so I think this can be closed. https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger#GerritTrigger-Version2.21.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] [gerrit-trigger-plugin] (JENKINS-34753) Sec-170-releated: gerrit-trigger needs to declare parameters
Title: Message Title Björn Pedersen created an issue Jenkins / JENKINS-34753 Sec-170-releated: gerrit-trigger needs to declare parameters Issue Type: Bug Assignee: rsandell Components: gerrit-trigger-plugin Created: 2016/May/12 8:49 AM Environment: Jenskins 2.3+ Priority: Major Reporter: Björn Pedersen Injecting arbitrary parameters is now forbidden, so the plugin should declare them to the jobs. See https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-05-11 Major impacts: Undeclared vars are not present anymore log flooding with (list really contains all gerrit trigger vars): A workaround is possible by setting system properties. May 12, 2016 9:53:01 AM WARNING hudson.model.ParametersAction filter Skipped parameter `GERRIT_EVENT_TYPE` as
[JIRA] [gerrit-trigger-plugin] (JENKINS-33933) Gerrit-trigger: null-pointer exception in GerritTriggerBuildChooser
Title: Message Title
Björn Pedersen updated an issue
Jenkins / JENKINS-33933
Gerrit-trigger: null-pointer exception in GerritTriggerBuildChooser
Change By:
Björn Pedersen
In my test install I can not trigger jobs anymore: I always get a null-pointer exception in BuildChooser (see log below). {quote} { { code} Manually triggered by user pedersen for Gerrit: https:///review/3200[lockable-resources] acquired lock on [Test1][EnvInject] - Loading node environment variables.Baue auf Master in Arbeitsbereich /usr/local/jenkins/jobs/ResiSingleCounterMulti/workspace > /usr/local/bin/git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > /usr/local/bin/git config remote.origin.url ssh://:29418/ # timeout=10Fetching upstream changes from ssh://:29418/ > /usr/local/bin/git --version # timeout=10using GIT_SSH to set credentials > /usr/local/bin/git fetch --tags --progress ssh://:29418/ refs/changes/00/3200/2 > /usr/local/bin/git rev-parse efa17ba464d2392714029effc904c9fb8612e255^{commit} # timeout=10Checking out Revision efa17ba464d2392714029effc904c9fb8612e255 (master) > /usr/local/bin/git config core.sparsecheckout # timeout=10 > /usr/local/bin/git checkout -f efa17ba464d2392714029effc904c9fb8612e255 > /usr/local/bin/git rev-parse FETCH_HEAD^{commit} # timeout=10 > /usr/local/bin/git rev-list b8aa077a767bace642bbe5cbd88cae7eef3cab14 # timeout=10Polling SCM changes on masterUsing strategy: Gerrit Trigger[poll] Last Built Revision: Revision efa17ba464d2392714029effc904c9fb8612e255 (refs/changes/00/3200/2) > /usr/local/bin/git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repositories > /usr/local/bin/git config remote.origin.url ssh://:29418/.git # timeout=10Fetching upstream changes from ssh://:29418/.git > /usr/local/bin/git --version # timeout=10using GIT_ASKPASS to set credentials > /usr/local/bin/git fetch --tags --progress ssh://:29418/.git refs/changes/00/3200/2 --depth=1Polling for changes inERROR: Build step failed with exceptionjava.lang.NullPointerException at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTriggerBuildChooser$GetGerritEventRevision.invoke(GerritTriggerBuildChooser.java:217) at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTriggerBuildChooser$GetGerritEventRevision.invoke(GerritTriggerBuildChooser.java:212) at hudson.plugins.git.GitSCM$BuildChooserContextImpl.actOnBuild(GitSCM.java:864) at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTriggerBuildChooser.getCandidateRevisions(GerritTriggerBuildChooser.java:107) at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:663) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:528) at hudson.scm.SCM.compareRemoteRevisionWith(SCM.java:381) at hudson.scm.SCM.poll(SCM.java:398) at hudson.model.AbstractProject.pollWithWorkspace(AbstractProject.java:1468) at hudson.model.AbstractProject._poll(AbstractProject.java:1438) at hudson.model.AbstractProject.poll(AbstractProject.java:1349) at com.tikal.jenkins.plugins.multijob.MultiJobBuilder.getScmChange(MultiJobBuilder.java:173) at com.tikal.jenkins.plugins.multijob.MultiJobBuilder.perform(MultiJobBuilder.java:243) at
[JIRA] [gerrit-trigger-plugin] (JENKINS-33933) Gerrit-trigger: null-pointer exception in GerritTriggerBuildChooser
Title: Message Title
Björn Pedersen updated an issue
Jenkins / JENKINS-33933
Gerrit-trigger: null-pointer exception in GerritTriggerBuildChooser
Change By:
Björn Pedersen
In my test install I can not trigger jobs anymore: I always get a null-pointer exception in BuildChooser (see log below). {quote } {{ } Manually triggered by user pedersen for Gerrit: https:///review/3200[lockable-resources] acquired lock on [Test1][EnvInject] - Loading node environment variables.Baue auf Master in Arbeitsbereich /usr/local/jenkins/jobs/ResiSingleCounterMulti/workspace > /usr/local/bin/git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > /usr/local/bin/git config remote.origin.url ssh://:29418/ # timeout=10Fetching upstream changes from ssh://:29418/ > /usr/local/bin/git --version # timeout=10using GIT_SSH to set credentials > /usr/local/bin/git fetch --tags --progress ssh://:29418/ refs/changes/00/3200/2 > /usr/local/bin/git rev-parse efa17ba464d2392714029effc904c9fb8612e255^{commit} # timeout=10Checking out Revision efa17ba464d2392714029effc904c9fb8612e255 (master) > /usr/local/bin/git config core.sparsecheckout # timeout=10 > /usr/local/bin/git checkout -f efa17ba464d2392714029effc904c9fb8612e255 > /usr/local/bin/git rev-parse FETCH_HEAD^{commit} # timeout=10 > /usr/local/bin/git rev-list b8aa077a767bace642bbe5cbd88cae7eef3cab14 # timeout=10Polling SCM changes on masterUsing strategy: Gerrit Trigger[poll] Last Built Revision: Revision efa17ba464d2392714029effc904c9fb8612e255 (refs/changes/00/3200/2) > /usr/local/bin/git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repositories > /usr/local/bin/git config remote.origin.url ssh://:29418/.git # timeout=10Fetching upstream changes from ssh://:29418/.git > /usr/local/bin/git --version # timeout=10using GIT_ASKPASS to set credentials > /usr/local/bin/git fetch --tags --progress ssh://:29418/.git refs/changes/00/3200/2 --depth=1Polling for changes inERROR: Build step failed with exceptionjava.lang.NullPointerException at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTriggerBuildChooser$GetGerritEventRevision.invoke(GerritTriggerBuildChooser.java:217) at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTriggerBuildChooser$GetGerritEventRevision.invoke(GerritTriggerBuildChooser.java:212) at hudson.plugins.git.GitSCM$BuildChooserContextImpl.actOnBuild(GitSCM.java:864) at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTriggerBuildChooser.getCandidateRevisions(GerritTriggerBuildChooser.java:107) at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:663) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:528) at hudson.scm.SCM.compareRemoteRevisionWith(SCM.java:381) at hudson.scm.SCM.poll(SCM.java:398) at hudson.model.AbstractProject.pollWithWorkspace(AbstractProject.java:1468) at hudson.model.AbstractProject._poll(AbstractProject.java:1438) at hudson.model.AbstractProject.poll(AbstractProject.java:1349) at com.tikal.jenkins.plugins.multijob.MultiJobBuilder.getScmChange(MultiJobBuilder.java:173) at com.tikal.jenkins.plugins.multijob.MultiJobBuilder.perform(MultiJobBuilder.java:243) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at
[JIRA] [gerrit-trigger-plugin] (JENKINS-33933) Gerrit-trigger: null-pointer exception in GerritTriggerBuildChooser
Title: Message Title
Björn Pedersen updated an issue
Jenkins / JENKINS-33933
Gerrit-trigger: null-pointer exception in GerritTriggerBuildChooser
Change By:
Björn Pedersen
In my test install I can not trigger jobs anymore: I always get a null-pointer exception in BuildChooser (see log below). {quote } {{ } Manually triggered by user pedersen for Gerrit: https:///review/3200[lockable-resources] acquired lock on [Test1][EnvInject] - Loading node environment variables.Baue auf Master in Arbeitsbereich /usr/local/jenkins/jobs/ResiSingleCounterMulti/workspace > /usr/local/bin/git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > /usr/local/bin/git config remote.origin.url ssh://:29418/ # timeout=10Fetching upstream changes from ssh://:29418/ > /usr/local/bin/git --version # timeout=10using GIT_SSH to set credentials > /usr/local/bin/git fetch --tags --progress ssh://:29418/ refs/changes/00/3200/2 > /usr/local/bin/git rev-parse efa17ba464d2392714029effc904c9fb8612e255^{commit} # timeout=10Checking out Revision efa17ba464d2392714029effc904c9fb8612e255 (master) > /usr/local/bin/git config core.sparsecheckout # timeout=10 > /usr/local/bin/git checkout -f efa17ba464d2392714029effc904c9fb8612e255 > /usr/local/bin/git rev-parse FETCH_HEAD^{commit} # timeout=10 > /usr/local/bin/git rev-list b8aa077a767bace642bbe5cbd88cae7eef3cab14 # timeout=10Polling SCM changes on masterUsing strategy: Gerrit Trigger[poll] Last Built Revision: Revision efa17ba464d2392714029effc904c9fb8612e255 (refs/changes/00/3200/2) > /usr/local/bin/git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repositories > /usr/local/bin/git config remote.origin.url ssh://:29418/.git # timeout=10Fetching upstream changes from ssh://:29418/.git > /usr/local/bin/git --version # timeout=10using GIT_ASKPASS to set credentials > /usr/local/bin/git fetch --tags --progress ssh://:29418/.git refs/changes/00/3200/2 --depth=1Polling for changes inERROR: Build step failed with exceptionjava.lang.NullPointerException at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTriggerBuildChooser$GetGerritEventRevision.invoke(GerritTriggerBuildChooser.java:217) at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTriggerBuildChooser$GetGerritEventRevision.invoke(GerritTriggerBuildChooser.java:212) at hudson.plugins.git.GitSCM$BuildChooserContextImpl.actOnBuild(GitSCM.java:864) at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTriggerBuildChooser.getCandidateRevisions(GerritTriggerBuildChooser.java:107) at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:663) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:528) at hudson.scm.SCM.compareRemoteRevisionWith(SCM.java:381) at hudson.scm.SCM.poll(SCM.java:398) at hudson.model.AbstractProject.pollWithWorkspace(AbstractProject.java:1468) at hudson.model.AbstractProject._poll(AbstractProject.java:1438) at hudson.model.AbstractProject.poll(AbstractProject.java:1349) at com.tikal.jenkins.plugins.multijob.MultiJobBuilder.getScmChange(MultiJobBuilder.java:173) at com.tikal.jenkins.plugins.multijob.MultiJobBuilder.perform(MultiJobBuilder.java:243) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at
[JIRA] [gerrit-trigger-plugin] (JENKINS-33933) Gerrit-trigger: null-pointer exception in GerritTriggerBuildChooser
Title: Message Title Björn Pedersen reopened an issue Seems to reoccur due to unknow reasons. Jenkins / JENKINS-33933 Gerrit-trigger: null-pointer exception in GerritTriggerBuildChooser Change By: Björn Pedersen Resolution: Fixed Status: Closed 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] [gerrit-trigger-plugin] (JENKINS-33933) Gerrit-trigger: null-pointer exception in GerritTriggerBuildChooser
Title: Message Title Björn Pedersen closed an issue as Fixed With 1.19.0 the error is gone again. Jenkins / JENKINS-33933 Gerrit-trigger: null-pointer exception in GerritTriggerBuildChooser Change By: Björn Pedersen Status: Open Closed 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] [gerrit-trigger-plugin] (JENKINS-33933) Gerrit-trigger: null-pointer exception in GerritTriggerBuildChooser
Title: Message Title
Björn Pedersen created an issue
Jenkins / JENKINS-33933
Gerrit-trigger: null-pointer exception in GerritTriggerBuildChooser
Issue Type:
Bug
Assignee:
rsandell
Components:
gerrit-trigger-plugin
Created:
2016/Mar/31 12:41 PM
Environment:
jenkins 1.655/ jenkins 2.0-alpha/beta gerrit-trigger-plugin 2.18.3+, also with f1a6a39 applied
Priority:
Critical
Reporter:
Björn Pedersen
In my test install I can not trigger jobs anymore: I always get a null-pointer exception in BuildChooser (see log below).
{{Manually triggered by user pedersen for Gerrit: https:///review/3200 [lockable-resources] acquired lock on [Test1] [EnvInject] - Loading node environment variables. Baue auf Master in Arbeitsbereich /usr/local/jenkins/jobs/ResiSingleCounterMulti/workspace > /usr/local/bin/git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > /usr/local/bin/git config remote.origin.url ssh://:29418/ # timeout=10 Fetching upstream changes from ssh://:29418/ > /usr/local/bin/git --version # timeout=10 using GIT_SSH to set credentials > /usr/local/bin/git fetch --tags --progress ssh://:29418/ refs/changes/00/3200/2 > /usr/local/bin/git rev-parse efa17ba464d2392714029effc904c9fb8612e255^
[JIRA] [extended-choice-parameter-plugin] (JENKINS-31458) Exception when saving job configuration
Title: Message Title Björn Pedersen commented on JENKINS-31458 Re: Exception when saving job configuration Going back to 1.636 is not an option, as 1.638 fixes some critical security 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] [extended-choice-parameter-plugin] (JENKINS-31733) Extended Choice Parameter throw exception for Check Boxes type
Title: Message Title Björn Pedersen commented on JENKINS-31733 Re: Extended Choice Parameter throw exception for Check Boxes type https://github.com/FelixJo/extended-choice-parameter-plugin/commit/37c7d12f5593d59b3c9f3b477d642a1495ba76fe seems to be a possible fix... 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] [extended-choice-parameter-plugin] (JENKINS-31733) Extended Choice Parameter throw exception for Check Boxes type
Title: Message Title Björn Pedersen commented on JENKINS-31733 Re: Extended Choice Parameter throw exception for Check Boxes type I can confirm this. My first guess is that is related to https://github.com/jenkinsci/jenkins/pull/1888/commits as 1.636 is not affected. 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] [extended-choice-parameter-plugin] (JENKINS-31458) Exception when saving job configuration
Title: Message Title Björn Pedersen commented on JENKINS-31458 Re: Exception when saving job configuration Duplicated by https://issues.jenkins-ci.org/browse/JENKINS-31733 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] [extended-choice-parameter-plugin] (JENKINS-31458) Exception when saving job configuration
Title: Message Title Björn Pedersen commented on JENKINS-31458 Re: Exception when saving job configuration Likely caused by https://github.com/jenkinsci/jenkins/pull/1888 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] [gerrit-trigger-plugin] (JENKINS-30104) Upcoming gerrit change may break trigger-on-vote
Title: Message Title Bjrn Pedersen created an issue Jenkins / JENKINS-30104 Upcoming gerrit change may break trigger-on-vote Issue Type: Task Assignee: rsandell Components: gerrit-trigger-plugin Created: 24/Aug/15 9:35 AM Priority: Minor Reporter: Bjrn Pedersen https://gerrit-review.googlesource.com/#/c/68242 appends all votes on each review event, so that possibly the trigger-on vote-changed feature break. Maybe someone can take a look? Add Comment
[JIRA] [core] (JENKINS-29771) Rendering: Footer elements not re-positionable
Title: Message Title Bjrn Pedersen updated an issue Jenkins / JENKINS-29771 Rendering: Footer elements not re-positionable Old (jenkins-1.618): New( jenkins 1.623) Change By: Bjrn Pedersen Attachment: jenkins1.618.png Attachment: jenkins1.623.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-29771) Rendering: Footer elements not re-positionable
Title: Message Title
Bjrn Pedersen commented on JENKINS-29771
Re: Rendering: Footer elements not re-positionable
The html is injected into the page with: https://software.sandia.gov/trac/fast/wiki/PageMarkup
old html generated:
Unable to render embedded object: File (attachment-name.jpg) not found.
div id=footer-container class=hidden-xs
div id=footer
div id=l10n-footer style=display: block; float:
left;/div
span class=page_generated/span
span class=rest_api/span
span class=jenkins_ver/span
div id=l10n-dialog class=dialog/div
script/script
script/script
script type=text/_javascript_/script
table width=100%/table
div class=site-banner
div class=topbar
div class=mlz_services/div
/div
/div
div class=site-banner/div
/div
/div
div/div
/body
/html
our css:
div.topbar {
margin: 0px;
background: #000 none repeat scroll 0% 0%;
height: 26px;
padding: 0px;
font-family: Lucida Grande,verdana,arial,helvetica,sans-serif;
font-size: 10px;
font-weight: bold;
vertical-align: middle;
top: 0px;
left: 0px;
position: absolute;
width: 100%;
new html:
footer
div class=container-fluid
::before
div class=row
::before
div id=footer class=col-md-6/div
div class=col-md-18
span class=page_generated/span
span class=rest_api/span
span class=jenkins_ver/span
div id=l10n-dialog class=dialog/div
script/script
div class=site-banner
div class=topbar
div class=mlz_services
ul/ul
/div
/div
/div
/div
::after
/div
::after
/div
/footer
Due to the wrapping inside the container-fluid it is impossible to get the content to the top of the page.
Unable to render embedded object: File (attachment-name.jpg) not found.
Base problem: There are only 2 extension points available:
page header, used for e.g. css/ js
[JIRA] [core] (JENKINS-29771) Rendering: Footer elements not re-positionable
Title: Message Title Bjrn Pedersen created an issue Jenkins / JENKINS-29771 Rendering: Footer elements not re-positionable Issue Type: Bug Assignee: Unassigned Components: core Created: 04/Aug/15 6:43 AM Priority: Minor Reporter: Bjrn Pedersen e0fcf91910782cea30d5bacb1f15077088628ef3 changed the insert-point for the pageDecorator.footer content. As they are now inside a layout div, it is impossible to move this content e.g. to the top of the page. This breaks valid use cases. Add Comment
[JIRA] [gerrit-trigger] (JENKINS-21064) Form too large if there are many patchsets in the selection list (manual trigger)
Björn Pedersen reopened JENKINS-21064 Form too large if there are many patchsets in the selection list (manual trigger) I checked the code and stepped through with Firebug. There is a logical flaw inside: On checking a patch, this patch is addded to the selectedIds input. But as the checkboxes are input fields in the form as well, all the data is sent beack to the server (1.1Mb of data for ~500 patch-sets in ~200 open changes) The serverside then just uses the selectedIds field. Of course one can increase the limit, but that seems only like a workaorund, not a solution. Additionally, as normally only the latest patchset can get merged anyway, the list would much shorter if by default only this set is listed. Change By: Björn Pedersen (12/Sep/14 7:24 AM) Resolution: WontFix Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-21064) Form too large if there are many patchsets in the selection list (manual trigger)
Björn Pedersen commented on JENKINS-21064 Form too large if there are many patchsets in the selection list (manual trigger) Possible solution for the too large form: use two forms in src/main/resources/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/actions/manual/ManualTriggerAction/index.jelly One for the table with empty target (and no submit button) One for the submitButton and the hidden selectedIds input. Then only selected changes will get sent. Possible solution to only show most recent patchsets: add a flag in the search form and pre-filter the ajax reponse on the server side This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-21064) Form too large if there are many patchsets in the selection list (manual trigger)
Björn Pedersen edited a comment on JENKINS-21064 Form too large if there are many patchsets in the selection list (manual trigger) Possible solution for the too large form: use two forms in src/main/resources/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/actions/manual/ManualTriggerAction/index.jelly One for the table with empty target (and no submit button) One for the submitButton and the hidden selectedIds input. Then only selected changes will get sent. Possible solution to only show most recent patchsets: add a flag in the search form and pre-filter the ajax reponse on the server side ( call queryJava(queryString, false , true ,false, false) instead of queryJava(queryString, true , true ,false, false) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-24312) NPE if session was left open for a longer time
Björn Pedersen resolved JENKINS-24312 as Fixed NPE if session was left open for a longer time probably a duplicate of 24317 Change By: Björn Pedersen (25/Aug/14 12:45 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-24312) NPE if session was left open for a longer time
Björn Pedersen commented on JENKINS-24312 NPE if session was left open for a longer time Seems to be related to 24317 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-24312) NPE if session was left open for a longer time
Björn Pedersen created JENKINS-24312 NPE if session was left open for a longer time Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 19/Aug/14 6:50 AM Description: If I have a jenkins session open for a longer time, I get a NPE (Oops page, stack trace on this page just says NPE Exception) on the first load of a jenkins page. After reloading I am still logged in and everything is fine again. Project: Jenkins Priority: Minor Reporter: Björn Pedersen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ui-changes] (JENKINS-23829) Layout: Job history may overlap main job status
Björn Pedersen created JENKINS-23829 Layout: Job history may overlap main job status Issue Type: Bug Assignee: Unassigned Attachments: broken_layout.png Components: ui-changes Created: 16/Jul/14 1:42 PM Description: See screenshot: The table for the build results may overlap the status output Project: Jenkins Priority: Major Reporter: Björn Pedersen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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] (JENKINS-22515) Git plugin: Wipe out workspaces should be kept
Björn Pedersen created JENKINS-22515 Git plugin: Wipe out workspaces should be kept Issue Type: Improvement Assignee: Nicolas De Loof Components: git, git-client Created: 07/Apr/14 6:50 AM Description: The wipe-out workspace option should not be eliminated, as it is quite useful for generic jobs that build many different projects in the same workspace. In this scenrio you do not gain from the old repo, as each run potentially clones a completly unrelated repository. Project: Jenkins Priority: Minor Reporter: Björn Pedersen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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] (JENKINS-22515) Git plugin: Wipe out workspaces should be kept
Björn Pedersen commented on JENKINS-22515 Git plugin: Wipe out workspaces should be kept https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin under Changelog as a link to: https://wiki.jenkins-ci.org/display/JENKINS/Git+plugin+rewrite+plans where that point is mentioned. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvnc] (JENKINS-22101) Setting per-job xauthority fails
Björn Pedersen created JENKINS-22101 Setting per-job xauthority fails Issue Type: Bug Assignee: Levon Saldamli Components: xvnc Created: 10/Mar/14 2:21 PM Description: After upgrading xvnc to 1.16 all vnc-enabled jobs kept failing. The problem was, that the vncserver did shut down due to Xauth-failures before anything useful could run. I could work around it by explictly adding -auth $XAUTHORTIY in the global setup of the plugin. It would be better if this flags just gets append to the commandline automatically. Environment: Linux / TightVNC Server version 1.3.9 Project: Jenkins Priority: Major Reporter: Björn Pedersen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [selenium] (JENKINS-22069) Client can not register to Selenium grid if jenkins is served via a proxy
Björn Pedersen created JENKINS-22069 Client can not register to Selenium grid if jenkins is served via a proxy Issue Type: Bug Affects Versions: current Assignee: Richard Lavoie Components: selenium Created: 06/Mar/14 4:40 PM Description: VirtualBox Stage 2 launcher completed adding seleniumProtocol=WebDriver,browserName=firefox,maxInstances=1 Mrz 06, 2014 5:24:20 PM org.openqa.grid.internal.utils.SelfRegisteringRemote startRemoteServer WARNING: error getting the parameters from the hub. The node may end up with wrong timeouts.Connection to http://proxyhost: refuse Actually the proxy does not listen on port , these requests should go directly to the "real" jenkinshost. Project: Jenkins Priority: Major Reporter: Björn Pedersen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-21709) Job link broken if using jenkins with prefix configured
Björn Pedersen
created JENKINS-21709
Job link broken if using jenkins with prefix configured
Issue Type:
Bug
Assignee:
Unassigned
Components:
jenkins-multijob-plugin
Created:
07/Feb/14 10:15 AM
Description:
The cause seems to be the absolut link in src/main/resources/com/tikal/jenkins/plugins/multijob/MultiJobBuild/main.jelly, here a ${rootURL} is missing.
62 a href=""${builder.jobName}/a
Project:
Jenkins
Priority:
Major
Reporter:
Björn Pedersen
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-21709) Job link broken if using jenkins with prefix configured
Björn Pedersen commented on JENKINS-21709 Job link broken if using jenkins with prefix configured See https://github.com/nmorey/tikal-multijob-plugin/commit/8b7f1faa16711b8ca86d96a3646cf5b85c3bdeae for a fix. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-21067) New server config not reachable if using a prefix in URL
Björn Pedersen commented on JENKINS-21067 New server config not reachable if using a prefix in URL Thanks, working again in beta4 now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-21064) Form too large if there are many patchsets in the selection list (manual trigger)
Björn Pedersen created JENKINS-21064 Form too large if there are many patchsets in the selection list (manual trigger) Issue Type: Bug Assignee: rsandell Components: gerrit-trigger Created: 18/Dec/13 10:21 AM Description: java.lang.IllegalStateException: Form too large 476344320 at org.eclipse.jetty.server.Request.extractParameters(Request.java:352) at org.eclipse.jetty.server.Request.getParameterNames(Request.java:813) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:67) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:960) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1021) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:865) at
[JIRA] [gerrit-trigger] (JENKINS-21067) New server config not reachable if using a prefix in URL
Björn Pedersen created JENKINS-21067 New server config not reachable if using a prefix in URL Issue Type: Bug Assignee: rsandell Components: gerrit-trigger Created: 18/Dec/13 12:23 PM Description: On jenkins instances the URL for the server configuration does not consider this prefix. Project: Jenkins Priority: Major Reporter: Björn Pedersen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-21064) Form too large if there are many patchsets in the selection list (manual trigger)
Björn Pedersen commented on JENKINS-21064 Form too large if there are many patchsets in the selection list (manual trigger) One possible solution would be to only list the latest patchset of each change by default. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-21067) New server config not reachable if using a prefix in URL
Björn Pedersen commented on JENKINS-21067 New server config not reachable if using a prefix in URL It is maybe a problem with with the absoulte path generatrion in GerritServer: getUrlName. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [claim] (JENKINS-17734) Claim Report view reports Error Status: 500
Björn Pedersen commented on JENKINS-17734 Claim Report view reports Error Status: 500 Are there any news on this problem? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18867) Wrong binding for the remove logs button
Björn Pedersen commented on JENKINS-18867 Wrong binding for the remove logs button Yes this version is fixing the problem. As I've seen it is mainly a problem of the jquery plugin changing the behaviuor of st:bind, correct? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18867) Wrong binding for the remove logs button
Björn Pedersen commented on JENKINS-18867 Wrong binding for the remove logs button Firefox 22 Jenkins 1.523 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18867) Wrong binding for the remove logs button
Björn Pedersen created JENKINS-18867 Wrong binding for the remove logs button Issue Type: Bug Assignee: Frédéric Camblor Components: scm-sync-configuration Created: 22/Jul/13 1:12 PM Description: Wrong binding for the 'remove logs' footer button. The result is a JS-Error: Timestamp: 22.07.2013 15:11:09 Error: SyntaxError: syntax error Source File: http://./jenkins/ Line: 355, Column: 25 Source Code: var plugin = script src=''margin-top:0;margin-bottom:10px;'>and the output of the script as plain text. Project: Jenkins Priority: Minor Reporter: Björn Pedersen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18867) Wrong binding for the remove logs button
Björn Pedersen
commented on JENKINS-18867
Wrong binding for the remove logs button
Here I have (this time with google-chrome):
{{
script type="text/_javascript_"
function removeLog() {
alert("Only administrators can purge logs !");
return;
var plugin = script src='' type='text/_javascript_'/scriptmakeStaplerProxy('/jenkins/$stapler/bound/47f87312-880f-40fc-9a12-0a75149deedc','xx',['purgeScmSyncConfigLogs']);
plugin.purgeScmSyncConfigLogs();
alert("SCM Sync Config errors purged ! You can refresh the page.");
}
/script
}}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18614) Config screen loading dialog permanently blocks config
Björn Pedersen commented on JENKINS-18614 Config screen loading dialog permanently blocks config Duplicate of https://issues.jenkins-ci.org/browse/JENKINS-18595? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-18123) it.generateHelper() in /gerrit-trigger/. Reason: java.lang.NullPointerException
Björn Pedersen commented on JENKINS-18123 it.generateHelper() in /gerrit-trigger/. Reason: java.lang.NullPointerException I can confirm this after upgrading to current gerrit master (2.7-rc1-346-g5c72550) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-18123) it.generateHelper() in /gerrit-trigger/. Reason: java.lang.NullPointerException
Björn Pedersen commented on JENKINS-18123 it.generateHelper() in /gerrit-trigger/. Reason: java.lang.NullPointerException Further testing showed that it is was missing permission: "Stream events" (global capabilities) that is new in master. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ssh-slaves] (JENKINS-17364) Latest version injects ssh credentials on each restart
Björn Pedersen commented on JENKINS-17364 Latest version injects ssh credentials on each restart That was the version as of 26/mar. In the current version this behaviour seems to be fixed again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-14955) Wrong links created on summary on a multijob execution
Björn Pedersen
commented on JENKINS-14955
Wrong links created on summary on a multijob execution
The bug still exist in 1.9, one change is still necessary:
index d347b07..b2f453f 100644
a/src/main/resources/com/tikal/jenkins/plugins/multijob/MultiJobBuild/main.jelly
+++ b/src/main/resources/com/tikal/jenkins/plugins/multijob/MultiJobBuild/main.jelly
@@ -17,7 +17,7 @@
td class="no-wrap"
j:choose
j:when test="${builder.url.length() 0}"
a href=""
+ a href=""
build #${builder.buildNumber}
/a
/j:when
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-14952) Downstream job build links are broken when jenkins is not hosted on the root context
Björn Pedersen commented on JENKINS-14952 Downstream job build links are broken when jenkins is not hosted on the root context see comment at https://issues.jenkins-ci.org/browse/JENKINS-14955 for the missing change. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17364) Latest version injects ssh credentials on each restart
Björn Pedersen created JENKINS-17364 Latest version injects ssh credentials on each restart Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: ssh-slaves Created: 26/Mar/13 2:47 PM Description: With the latest ssh-lsaves plugin, the ssh credentials from existing slaves are injected on each restart. The credentials should only get injected if no corresponding credetials entry is there already. Environment: FreeBSD Project: Jenkins Priority: Major Reporter: Björn Pedersen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17364) Latest version injects ssh credentials on each restart
Björn Pedersen updated JENKINS-17364 Latest version injects ssh credentials on each restart Change By: Björn Pedersen (26/Mar/13 2:48 PM) Description: Withthelatestssh- lsaves slaves plugin,thesshcredentialsfromexistingslavesareinjectedoneachrestart.Thecredentialsshouldonlygetinjectedifnocorrespondingcredetialsentryistherealready. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17337) Failed to load job on Matrix jobs
Björn Pedersen commented on JENKINS-17337 Failed to load job on Matrix jobs I get the same problem on FreeBSD 9. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16851) Strategy GerritTrigger missing with git plugin 1.1.28
Björn Pedersen commented on JENKINS-16851 Strategy GerritTrigger missing with git plugin 1.1.28 The infinite loop could be: https://issues.jenkins-ci.org/browse/JENKINS-16849 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16851) Strategy GerritTrigger missing with plugin 1.1.28
Björn Pedersen commented on JENKINS-16851 Strategy GerritTrigger missing with plugin 1.1.28 After reverting git-plugin to 1.1.26 everything is back to normal here. The change was introduced in git 1.1.27, 1.1.28 was just a minor bugfix. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16851) Strategy GerritTrigger missing with git plugin 1.1.28
Björn Pedersen updated JENKINS-16851 Strategy GerritTrigger missing with git plugin 1.1.28 Change By: Björn Pedersen (18/Feb/13 3:18 PM) Summary: StrategyGerritTriggermissingwith git plugin1.1.28 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16851) Strategy GerritTrigger missing with plugin 1.1.28
Björn Pedersen created JENKINS-16851 Strategy GerritTrigger missing with plugin 1.1.28 Issue Type: Bug Assignee: rsandell Components: gerrit-trigger, git Created: 18/Feb/13 7:35 AM Description: After upgrading to git plugin 1.1.28 the GerritTrigger strategy is not available anymore, all gerrit trigger jobs fail. Project: Jenkins Priority: Critical Reporter: Björn Pedersen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16851) Strategy GerritTrigger missing with plugin 1.1.28
Björn Pedersen commented on JENKINS-16851 Strategy GerritTrigger missing with plugin 1.1.28 Changes in the BuildChooserDeafault/Inverse in git plugin: -import hudson.plugins.git.IGitAPI; +import hudson.plugins.git.client.IGitAPI; This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-9341) Gerrit trigger retrigger redirects to wrong URL
Björn Pedersen commented on JENKINS-9341 Gerrit trigger retrigger redirects to wrong URL This problem reappeared in jenkins 1.501. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14955) Wrong links created on summary on a multijob execution
Björn Pedersen commented on JENKINS-14955 Wrong links created on summary on a multijob execution I can confirm this behaviour: it only occurs if jenkins is started with --prefix=something. The links in the console output are correct. (same as https://issues.jenkins-ci.org/browse/JENKINS-14952) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
