[JIRA] (JENKINS-41375) JobConfigHistory fails to revert
Title: Message Title Stefan Brausch commented on JENKINS-41375 Re: JobConfigHistory fails to revert The user should have job config permissions. 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-41375) JobConfigHistory fails to revert
Title: Message Title Antoni Yanev commented on JENKINS-41375 Re: JobConfigHistory fails to revert Which user does the plugin uses? 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-41375) JobConfigHistory fails to revert
Title: Message Title Stefan Brausch commented on JENKINS-41375 Re: JobConfigHistory fails to revert Users without the config permissions don't see the restore button. It you see the button, you should have the rights. Can you give me more information about your OS? It's possible to change and save the job configs without problems? 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-41375) JobConfigHistory fails to revert
Title: Message Title Antoni Yanev commented on JENKINS-41375 Re: JobConfigHistory fails to revert Ok, so it's not the permission, because I can see the button. The OS is Windows Server 2008 R2. Yes, the configs are changed and saved without problems. 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-41535) NodeJS installation configuration is not persisted to file
Title: Message Title Ricky Lippmann commented on JENKINS-41535 Re: NodeJS installation configuration is not persisted to file We encountered same Issue here on both of our jenkins systems: Windows Server 2012 with jenkins 2.43 and NodeJSPlugin 1.0.0 Debian 8.7 with jenkins 2.43 and NodeJSPlugin 1.0.0 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-41608) Older or Unreadable Data warning after taking scm-api plugin update
Title: Message Title Stephen Connolly closed an issue as Not A Defect This is entirely expected and was detailed in the blog post at the end of the "Summary for busy Jenkins Administrators" section: After an upgrade you will see the data migration warning Jenkins / JENKINS-41608 Older or Unreadable Data warning after taking scm-api plugin update Change By: Stephen Connolly Status: Open Closed Assignee: Stephen Connolly Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41615) svn plug-in kerberos
Title: Message Title Tobiasz Ogórek updated an issue Jenkins / JENKINS-41615 svn plug-in kerberos Change By: Tobiasz Ogórek Summary: Problem while checking for updates svn plug- in Jenkins kerberos 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-41167) credential is not saving the credentials (iframe cross origin policy issue)
Title: Message Title pooja shah updated an issue Jenkins / JENKINS-41167 credential is not saving the credentials (iframe cross origin policy issue) Change By: pooja shah Attachment: Screen Shot 2017-02-01 at 2.51.44 pm.png Attachment: Screen Shot 2017-02-01 at 2.51.58 pm.png Attachment: Screen Shot 2017-02-01 at 2.52.14 pm.png 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-41167) credential is not saving the credentials (iframe cross origin policy issue)
Title: Message Title pooja shah updated an issue Jenkins / JENKINS-41167 credential is not saving the credentials (iframe cross origin policy issue) Change By: pooja shah Attachment: Screen Shot 2017-02-01 at 2.52.14 pm.png 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-41167) credential is not saving the credentials (iframe cross origin policy issue)
Title: Message Title pooja shah updated an issue Jenkins / JENKINS-41167 credential is not saving the credentials (iframe cross origin policy issue) Change By: pooja shah Attachment: Screen Shot 2017-02-01 at 2.51.58 pm.png 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-41167) credential is not saving the credentials (iframe cross origin policy issue)
Title: Message Title pooja shah updated an issue Jenkins / JENKINS-41167 credential is not saving the credentials (iframe cross origin policy issue) Change By: pooja shah Attachment: Screen Shot 2017-02-01 at 2.51.44 pm.png 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-41167) credential is not saving the credentials (iframe cross origin policy issue)
Title: Message Title pooja shah updated an issue Jenkins / JENKINS-41167 credential is not saving the credentials (iframe cross origin policy issue) Change By: pooja shah Attachment: high-level log.png Attachment: select.js break.png Attachment: select.js line 156.png 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-19725) Unable to unmarshall response (Couldn't initialize a SAX driver to create an XMLReader)
Title: Message Title Sjoerd van Gestel commented on JENKINS-19725 Re: Unable to unmarshall response (Couldn't initialize a SAX driver to create an XMLReader) We experiance this issue with files bigger than 14Mb, if you add xerces-2.9.0.jar to the s3 pugin lib folder it should be solved (/var/lib/jenkins/plugins/s3/WEB-INF/lib/) 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-41167) credential is not saving the credentials (iframe cross origin policy issue)
Title: Message Title pooja shah edited a comment on JENKINS-41167 Re: credential is not saving the credentials (iframe cross origin policy issue) [~stephenconnolly] yes have upgraded credentials plugin to 2.1.11 but no luck, attached few more screen-shots showing potential error places. [~dbeckham] : sorry , i'm on 2.23 so can't find "Administrative Monitors" and to upgrade 2.24 there is only way I see is to fresh download and setup everything which is a little tedious task than any soft upgrade facility, please let me know if there is any upgrade shell or apt-get kind of command. or equivalent anything in 2.23 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-40690) One of files fails with SdkClientException: Couldn't initialize a SAX driver to create an XMLReader
Title: Message Title Sjoerd van Gestel commented on JENKINS-40690 Re: One of files fails with SdkClientException: Couldn't initialize a SAX driver to create an XMLReader We experience this issue with files bigger than 14Mb, if you add xerces-2.9.0.jar to the s3 pugin lib folder it should be solved (/var/lib/jenkins/plugins/s3/WEB-INF/lib/) 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-41167) credential is not saving the credentials (iframe cross origin policy issue)
Title: Message Title pooja shah commented on JENKINS-41167 Re: credential is not saving the credentials (iframe cross origin policy issue) Stephen Connolly yes have upgraded credentials plugin to 2.1.11 but no luck, attached few more screen-shots showing potential error places. Unable to render embedded object: File (Screen Shot 2017-02-01 at 2.51.44 pm.png) not found. Unable to render embedded object: File (Screen Shot 2017-02-01 at 2.51.58 pm.png) not found. Unable to render embedded object: File (Screen Shot 2017-02-01 at 2.52.14 pm.png) not found. Daniel Beckham, i'm on 2.23 so can't find "Administrative Monitors" and to upgrade 2.24 there is only way I see is to fresh download and setup everything which is a little tedious task than any soft upgrade facility, please let me know if there is any upgrade shell or apt-get kind of command. or equivalent anything in 2.23 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-41615) Problem while checking for updates in Jenkins
Title: Message Title Tobiasz Ogórek updated an issue Jenkins / JENKINS-41615 Problem while checking for updates in Jenkins Change By: Tobiasz Ogórek Summary: svn plug- Problem while checking for updates in kerberos Jenkins 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-19725) Unable to unmarshall response (Couldn't initialize a SAX driver to create an XMLReader)
Title: Message Title Sjoerd van Gestel edited a comment on JENKINS-19725 Re: Unable to unmarshall response (Couldn't initialize a SAX driver to create an XMLReader) We experiance experience this issue with files bigger than 14Mb, if you add xerces-2.9.0.jar to the s3 pugin lib folder it should be solved (/var/lib/jenkins/plugins/s3/WEB-INF/lib/) 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-41167) credential is not saving the credentials (iframe cross origin policy issue)
Title: Message Title pooja shah edited a comment on JENKINS-41167 Re: credential is not saving the credentials (iframe cross origin policy issue) [~stephenconnolly] yes have upgraded credentials plugin to 2.1.11 but no luck, attached few more screen-shots showing potential error places. !Screen Shot 2017-02-01 at 2.51.44 pm.png|thumbnail! !Screen Shot 2017-02-01 at 2.51.58 pm.png|thumbnail! !Screen Shot 2017-02-01 at 2.52.14 pm.png|thumbnail![~dbeckham], i'm on 2.23 so can't find "Administrative Monitors" and to upgrade 2.24 there is only way I see is to fresh download and setup everything which is a little tedious task than any soft upgrade facility, please let me know if there is any upgrade shell or apt-get kind of command. or equivalent anything in 2.23 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-19725) Unable to unmarshall response (Couldn't initialize a SAX driver to create an XMLReader)
Title: Message Title Sjoerd van Gestel edited a comment on JENKINS-19725 Re: Unable to unmarshall response (Couldn't initialize a SAX driver to create an XMLReader) We experience this issue with files bigger than 14Mb, if you add xerces-2.9.0.jar to the s3 pugin plugin lib folder it should be solved (/var/lib/jenkins/plugins/s3/WEB-INF/lib/) 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-40690) One of files fails with SdkClientException: Couldn't initialize a SAX driver to create an XMLReader
Title: Message Title Sjoerd van Gestel edited a comment on JENKINS-40690 Re: One of files fails with SdkClientException: Couldn't initialize a SAX driver to create an XMLReader We experience this issue with files bigger than 14Mb, if you add xerces-2.9.0.jar to the s3 pugin plugin lib folder it should be solved (/var/lib/jenkins/plugins/s3/WEB-INF/lib/) 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-41167) credential is not saving the credentials (iframe cross origin policy issue)
Title: Message Title pooja shah updated an issue Jenkins / JENKINS-41167 credential is not saving the credentials (iframe cross origin policy issue) Change By: pooja shah Attachment: select.js line 156.png 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-41167) credential is not saving the credentials (iframe cross origin policy issue)
Title: Message Title pooja shah updated an issue Jenkins / JENKINS-41167 credential is not saving the credentials (iframe cross origin policy issue) Change By: pooja shah Attachment: credential plugin-select.js break.png 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-41612) Job DSL plugin does not function on Windows agents
Title: Message Title Daniel Spilker commented on JENKINS-41612 Re: Job DSL plugin does not function on Windows agents Ah, sorry. A fix is on the way: https://github.com/jenkinsci/job-dsl-plugin/pull/991 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-41167) credential is not saving the credentials (iframe cross origin policy issue)
Title: Message Title pooja shah updated an issue Jenkins / JENKINS-41167 credential is not saving the credentials (iframe cross origin policy issue) Change By: pooja shah Attachment: select.js break.png 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-38898) Managed artifacts fails to upload to S3 - no errors logged
Title: Message Title Sjoerd van Gestel commented on JENKINS-38898 Re: Managed artifacts fails to upload to S3 - no errors logged same issue here: Error parsing the X-Amz-Credential parameter; the region 'us-east-1' is wrong; expecting 'eu-west-1' 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-41167) credential is not saving the credentials (iframe cross origin policy issue)
Title: Message Title
pooja shah edited a comment on JENKINS-41167
Re: credential is not saving the credentials (iframe cross origin policy issue)
[~stephenconnolly] yes have upgraded credentials plugin to 2.1.11 but no luck, attached few more screen-shots showing potential error places.```window.credentials.addSubmit = function (e) {var id;var containerId = "container" + (iota++);var responseDialog = new YAHOO.widget.Panel("wait" + (iota++), {fixedcenter: true,close: true,draggable: true,zindex: 4,modal: true,visible: false});responseDialog.setHeader("Error");responseDialog.setBody("");responseDialog.render(document.body);var target; // iframefunction attachIframeOnload(target, f) {if (target.attachEvent) {target.attachEvent("onload", f);} else {target._onload_ = f;}}var f = $('credentials-dialog-form');// create a throw-away IFRAME to avoid back button from loading the POST result backid = "iframe" + (iota++);target = document.createElement("iframe");target.setAttribute("id", id);target.setAttribute("name", id);target.setAttribute("style", "height:100%; width:100%");$(containerId).appendChild(target);attachIframeOnload(target, function () {if (target.contentWindow && target.contentWindow.applyCompletionHandler) { {color:red}# BREAKS HERE{color}// apply-aware server is expected to set this handlertarget.contentWindow.applyCompletionHandler(window);} else {// otherwise this is possibly an error from the server, so we need to render the whole content.var r = YAHOO.util.Dom.getClientRegion();responseDialog.cfg.setProperty("width", r.width * 3 / 4 + "px");responseDialog.cfg.setProperty("height", r.height * 3 / 4 + "px");responseDialog.center();responseDialog.show();}window.setTimeout(function () {// otherwise Firefox will fail to leave the "connecting" state$(id).remove();}, 0)});f.target = target.id;try {buildFormTree(f);f.submit(); {color:red}# BREAKS HERE{color}} finally {f.target = null;}window.credentials.dialog.hide();return false;};``` [~dbeckham]: sorry, i'm on 2.23 so can't find "Administrative Monitors" and to upgrade 2.24 there is only way I see is to fresh download and setup everything which is a little tedious task than any soft upgrade facility, please let me know if there is any upgrade shell or apt-get kind of command. or equivalent anything in 2.23
Add Comment
[JIRA] (JENKINS-41167) credential is not saving the credentials (iframe cross origin policy issue)
Title: Message Title
pooja shah edited a comment on JENKINS-41167
Re: credential is not saving the credentials (iframe cross origin policy issue)
[~stephenconnolly] yes have upgraded credentials plugin to 2.1.11 but no luck, attached few more screen-shots showing potential error places. ```window.credentials.addSubmit = function (e) {var id;var containerId = "container" + (iota++);var responseDialog = new YAHOO.widget.Panel("wait" + (iota++), {fixedcenter: true,close: true,draggable: true,zindex: 4,modal: true,visible: false});responseDialog.setHeader("Error");responseDialog.setBody("");responseDialog.render(document.body);var target; // iframefunction attachIframeOnload(target, f) {if (target.attachEvent) {target.attachEvent("onload", f);} else {target._onload_ = f;}}var f = $('credentials-dialog-form');// create a throw-away IFRAME to avoid back button from loading the POST result backid = "iframe" + (iota++);target = document.createElement("iframe");target.setAttribute("id", id);target.setAttribute("name", id);target.setAttribute("style", "height:100%; width:100%");$(containerId).appendChild(target);attachIframeOnload(target, function () {if (target.contentWindow && target.contentWindow.applyCompletionHandler) { {color:red}# BREAKS HERE{color}// apply-aware server is expected to set this handlertarget.contentWindow.applyCompletionHandler(window);} else {// otherwise this is possibly an error from the server, so we need to render the whole content.var r = YAHOO.util.Dom.getClientRegion();responseDialog.cfg.setProperty("width", r.width * 3 / 4 + "px");responseDialog.cfg.setProperty("height", r.height * 3 / 4 + "px");responseDialog.center();responseDialog.show();}window.setTimeout(function () {// otherwise Firefox will fail to leave the "connecting" state$(id).remove();}, 0)});f.target = target.id;try {buildFormTree(f);f.submit(); {color:red}# BREAKS HERE{color}} finally {f.target = null;}window.credentials.dialog.hide();return false;};``` [~dbeckham]: sorry, i'm on 2.23 so can't find "Administrative Monitors" and to upgrade 2.24 there is only way I see is to fresh download and setup everything which is a little tedious task than any soft upgrade facility, please let me know if there is any upgrade shell or apt-get kind of command. or equivalent anything in 2.23
Add Comment
[JIRA] (JENKINS-41167) credential is not saving the credentials (iframe cross origin policy issue)
Title: Message Title pooja shah commented on JENKINS-41167 Re: credential is not saving the credentials (iframe cross origin policy issue) Daniel Beckham: sorry, i'm on 2.23 so can't find "Administrative Monitors" and to upgrade 2.24 there is only way I see is to fresh download and setup everything which is a little tedious task than any soft upgrade facility, please let me know if there is any upgrade shell or apt-get kind of command. or equivalent anything in 2.23 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-38898) Managed artifacts fails to upload to S3 - no errors logged
Title: Message Title Sjoerd van Gestel edited a comment on JENKINS-38898 Re: Managed artifacts fails to upload to S3 - no errors logged same issue here: Publish artifacts to S3 Bucket bucket=-***, file=app-debug.apk region=eu-west-1, will be uploaded from slave=true managed=true , server encryption false Error parsing the X-Amz-Credential parameter; the region 'us-east-1' is wrong; expecting 'eu-west-1' 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-41167) credential is not saving the credentials (iframe cross origin policy issue)
Title: Message Title
pooja shah edited a comment on JENKINS-41167
Re: credential is not saving the credentials (iframe cross origin policy issue)
[~stephenconnolly] yes have upgraded credentials plugin to 2.1.11 but no luck, attached few more screen-shots showing potential error places. ```window.credentials.addSubmit = function (e) {var id;var containerId = "container" + (iota++);var responseDialog = new YAHOO.widget.Panel("wait" + (iota++), {fixedcenter: true,close: true,draggable: true,zindex: 4,modal: true,visible: false});responseDialog.setHeader("Error");responseDialog.setBody("");responseDialog.render(document.body);var target; // iframefunction attachIframeOnload(target, f) {if (target.attachEvent) {target.attachEvent("onload", f);} else {target._onload_ = f;}}var f = $('credentials-dialog-form');// create a throw-away IFRAME to avoid back button from loading the POST result backid = "iframe" + (iota++);target = document.createElement("iframe");target.setAttribute("id", id);target.setAttribute("name", id);target.setAttribute("style", "height:100%; width:100%");$(containerId).appendChild(target);attachIframeOnload(target, function () {if (target.contentWindow && target.contentWindow.applyCompletionHandler) { {color:red}# BREAKS HERE{color} {color:red} with `Uncaught DOMException: Blocked a frame with origin "http://www. from accessing a cross-origin frame` {color} // apply-aware server is expected to set this handlertarget.contentWindow.applyCompletionHandler(window);} else {// otherwise this is possibly an error from the server, so we need to render the whole content.var r = YAHOO.util.Dom.getClientRegion();responseDialog.cfg.setProperty("width", r.width * 3 / 4 + "px");responseDialog.cfg.setProperty("height", r.height * 3 / 4 + "px");responseDialog.center();responseDialog.show();}window.setTimeout(function () {// otherwise Firefox will fail to leave the "connecting" state$(id).remove();}, 0)});f.target = target.id;try {buildFormTree(f);f.submit(); {color:red}# BREAKS HERE{color}} finally {f.target = null;}window.credentials.dialog.hide();return false;};```
Add Comment
[JIRA] (JENKINS-41167) credential is not saving the credentials (iframe cross origin policy issue)
Title: Message Title
pooja shah edited a comment on JENKINS-41167
Re: credential is not saving the credentials (iframe cross origin policy issue)
[~stephenconnolly] yes have upgraded credentials plugin to 2.1.11 but no luck, attached few more screen-shots showing potential error places. ```window.credentials.addSubmit = function (e) {var id;var containerId = "container" + (iota++);var responseDialog = new YAHOO.widget.Panel("wait" + (iota++), {fixedcenter: true,close: true,draggable: true,zindex: 4,modal: true,visible: false});responseDialog.setHeader("Error");responseDialog.setBody("");responseDialog.render(document.body);var target; // iframefunction attachIframeOnload(target, f) {if (target.attachEvent) {target.attachEvent("onload", f);} else {target._onload_ = f;}}var f = $('credentials-dialog-form');// create a throw-away IFRAME to avoid back button from loading the POST result backid = "iframe" + (iota++);target = document.createElement("iframe");target.setAttribute("id", id);target.setAttribute("name", id);target.setAttribute("style", "height:100%; width:100%");$(containerId).appendChild(target);attachIframeOnload(target, function () {if (target.contentWindow && target.contentWindow.applyCompletionHandler) { {color:red}# BREAKS HERE{color} with `Uncaught DOMException: Blocked a frame with origin "http://www. from accessing a cross-origin frame` // apply-aware server is expected to set this handlertarget.contentWindow.applyCompletionHandler(window);} else {// otherwise this is possibly an error from the server, so we need to render the whole content.var r = YAHOO.util.Dom.getClientRegion();responseDialog.cfg.setProperty("width", r.width * 3 / 4 + "px");responseDialog.cfg.setProperty("height", r.height * 3 / 4 + "px");responseDialog.center();responseDialog.show();}window.setTimeout(function () {// otherwise Firefox will fail to leave the "connecting" state$(id).remove();}, 0)});f.target = target.id;try {buildFormTree(f);f.submit(); {color:red}# BREAKS HERE{color}} finally {f.target = null;}window.credentials.dialog.hide();return false;};```
Add Comment
[JIRA] (JENKINS-41167) credential is not saving the credentials (iframe cross origin policy issue)
Title: Message Title
pooja shah edited a comment on JENKINS-41167
Re: credential is not saving the credentials (iframe cross origin policy issue)
[~stephenconnolly] yes have upgraded credentials plugin to 2.1.11 but no luck, attached few more screen-shots showing potential error places. ```window.credentials.addSubmit = function (e) {var id;var containerId = "container" + (iota++);var responseDialog = new YAHOO.widget.Panel("wait" + (iota++), {fixedcenter: true,close: true,draggable: true,zindex: 4,modal: true,visible: false});responseDialog.setHeader("Error");responseDialog.setBody("");responseDialog.render(document.body);var target; // iframefunction attachIframeOnload(target, f) {if (target.attachEvent) {target.attachEvent("onload", f);} else {target._onload_ = f;}}var f = $('credentials-dialog-form');// create a throw-away IFRAME to avoid back button from loading the POST result backid = "iframe" + (iota++);target = document.createElement("iframe");target.setAttribute("id", id);target.setAttribute("name", id);target.setAttribute("style", "height:100%; width:100%");$(containerId).appendChild(target);attachIframeOnload(target, function () {if (target.contentWindow && target.contentWindow.applyCompletionHandler) { {color:red}# BREAKS HERE{color} {color:red}with `Uncaught DOMException: Blocked a frame with origin "http://www. from accessing a cross-origin frame`{color}// apply-aware server is expected to set this handlertarget.contentWindow.applyCompletionHandler(window);} else {// otherwise this is possibly an error from the server, so we need to render the whole content.var r = YAHOO.util.Dom.getClientRegion();responseDialog.cfg.setProperty("width", r.width * 3 / 4 + "px");responseDialog.cfg.setProperty("height", r.height * 3 / 4 + "px");responseDialog.center();responseDialog.show();}window.setTimeout(function () {// otherwise Firefox will fail to leave the "connecting" state$(id).remove();}, 0)});f.target = target.id;try {buildFormTree(f);f.submit(); {color:red}# BREAKS HERE with 'Failed to load resource: net::ERR_CONNECTION_REFUSED' {color}} finally {f.target = null;}window.credentials.dialog.hide();return false;};```
Add Comment
[JIRA] (JENKINS-41167) credential is not saving the credentials (iframe cross origin policy issue)
Title: Message Title
pooja shah commented on JENKINS-41167
Re: credential is not saving the credentials (iframe cross origin policy issue)
Stephen Connolly in my understanding, it can be resolved with right CSP settings, can you please tell me what value should be passed in System.getProperty("hudson.model.DirectoryBrowserSupport.CSP", "VALUE");
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-41167) credential is not saving the credentials (iframe cross origin policy issue)
Title: Message Title
pooja shah edited a comment on JENKINS-41167
Re: credential is not saving the credentials (iframe cross origin policy issue)
[~stephenconnolly] in my understanding, it can be resolved with right CSP settings, can you please tell me what value should be passed in System.getProperty("hudson.model.DirectoryBrowserSupport.CSP", "VALUE"); ?
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-41167) credential is not saving the credentials (iframe cross origin policy issue)
Title: Message Title
pooja shah edited a comment on JENKINS-41167
Re: credential is not saving the credentials (iframe cross origin policy issue)
[~stephenconnolly] in my understanding, it can be resolved with right CSP settings , should make it work. can you please tell me what value should be passed in System.getProperty("hudson.model.DirectoryBrowserSupport.CSP", "VALUE"); ?
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-41499) Regression: show complete log button has shifted to the left
Title: Message Title Thorsten Scherler updated JENKINS-41499 Jenkins / JENKINS-41499 Regression: show complete log button has shifted to the left Change By: Thorsten Scherler Status: In Review 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41561) Pullrequest github executes Jenkinsfile of origin branch
Title: Message Title Stephen Connolly assigned an issue to Stephen Connolly Jenkins / JENKINS-41561 Pullrequest github executes Jenkinsfile of origin branch Change By: Stephen Connolly Assignee: Jesse Glick Stephen Connolly 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-41616) Non-trusted pull requests should use a probe against the trusted revision not the PR's revision
Title: Message Title Stephen Connolly created an issue Jenkins / JENKINS-41616 Non-trusted pull requests should use a probe against the trusted revision not the PR's revision Issue Type: Bug Assignee: Unassigned Components: github-branch-source-plugin Created: 2017/Feb/01 10:08 AM Priority: Minor Reporter: Stephen Connolly See JENKINS-41561, If a PR is not trusted and has a Jenkinsfile but the target branch of the PR does not have a Jenkinsfile, we should not report that as a PR matching the Jenkinsfile criteria as the Jenkinsfile should be sourced from the trusted revision (where there is none) The current behaviour is that the PR will be flagged as matching the criteria and hence a build attempt will be started, but as the trusted revision does not have the Jenkinsfile the build will fail. We should never even try to build in the first case for such an untrusted PR Add Comment
[JIRA] (JENKINS-41561) Pullrequest github executes Jenkinsfile of origin branch
Title: Message Title Stephen Connolly closed an issue as Not A Defect Both of these are intended behaviours. There are improvements to the behaviour planned under JENKINS-36240 Currently, the github branch source attempts to differentiate between pull requests from users who have permission to commit directly to the origin repository and pull requests from randomers on the interwebs creating drive by PRs. The heuristics for detecting whether a given GitHub user is a collaborator can depend on the permissions that were granted to the API token used for scanning, so where that fails, the only PRs that can be assumed "safe" are those from the origin repository itself. JENKINS-36240 proposes to use a new (experimental) API from GitHub that will enable the easier test of asking GitHub "Hey is user jrandomerfromtheinterwebs allowed to commit directly to myorg/trusted-repo" So the plugin will then be able to decide if the PR is trusted or not trusted. When the PR is trusted (i.e. currently if from either an origin repo or from a user listed in the list of collaborators reported to the API token - which is known not to be the full list in a lot of cases) then the Jenkinsfile from the PR will be used. When the PR is not trusted then the Jenkinsfile will not be used, instead the Jenkinsfile from the target branch will be used and if that is missing, so be it. I have created JENKINS-41616 for the component of this request that is a legitimate bug, though not the bug you reported! Thank you very much for this report, as it has identified a bug Jenkins / JENKINS-41561 Pullrequest github executes Jenkinsfile of origin branch Change By: Stephen Connolly Status: Open Closed Resolution: Not A Defect Add Comment
[JIRA] (JENKINS-41617) browser is waiting indefinitely - jvm waiting
Title: Message Title gianluca ragnoni created an issue Jenkins / JENKINS-41617 browser is waiting indefinitely - jvm waiting Issue Type: Bug Assignee: Unassigned Attachments: tdump.txt Components: core Created: 2017/Feb/01 10:11 AM Environment: Windows 10 pro 64-bit Java HotSpot(TM) 64-Bit Server VM (25.112-b15 mixed mode) jenkins version 2.32.1 Priority: Critical Reporter: gianluca ragnoni Browser show "Please wait while Jenkins is getting ready to work" indefinitely running either as windows service or from command line (eg java -jar -jenkins.war) Attached the thread dump. Add Comment
[JIRA] (JENKINS-41223) Multibranch pipelines with Mercurial: build selects oldest head
Title: Message Title Stephen Connolly commented on JENKINS-41223 Re: Multibranch pipelines with Mercurial: build selects oldest head Jesse Glick can you take a look at this. From the description this looks to be the retrieve revision code starting with oldest first (which suggests it has always been an issue) 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-41068) Obsolate branch directories are not removed from job directory on master
Title: Message Title Stephen Connolly commented on JENKINS-41068 Re: Obsolate branch directories are not removed from job directory on master Is this still an issue with the 2.0.x versions? 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-41618) Issue using Jenkins SVN Plugin with https Kerberos authentication
Title: Message Title Tobiasz Ogórek created an issue Jenkins / JENKINS-41618 Issue using Jenkins SVN Plugin with https Kerberos authentication Issue Type: Bug Assignee: Unassigned Components: subversion-plugin Created: 2017/Feb/01 10:16 AM Priority: Blocker Reporter: Tobiasz Ogórek I am writing in connection to issue referenced with impossible to connect to Visual SVN SERVER Enterprise Edition from Jenkins 2.19.4 on another machine. Issue take place using Jenkins SVN Plugin 2.7.1 with https Kerberos authentication, when trying to connect to our Visual SVN SERVER Enterprise Edition. In logs it looks like: _Jan 13, 2017 10:02:29 AM hudson.scm.SubversionSCM$ModuleLocation$DescriptorImpl checkCredentialsId SEVERE: svn: E200015: Authentication cancelled_ Visual SVN Server is configured to Use Windows authentication and at the present, there are checked both of Authentication methods: Basic authentication and Integrated Windows Authentication (It was also tested without Basic authentication with the same result). Similar situation takes place on: Jira v6.3.7 JIRA Subversion plugin v2.0.3.1 Please, let me know, how to solve this issue. Furthermore I would like to ask about Jenkins SVN Plugin 2.7.1/ JIRA Subversion plugin v2.0.3.1 or also SVNKit, if does they support https Kerberos authentication or not? Thanks for support in advance!
[JIRA] (JENKINS-41618) Issue using Jenkins SVN Plugin with https Kerberos authentication
Title: Message Title Tobiasz Ogórek updated an issue Jenkins / JENKINS-41618 Issue using Jenkins SVN Plugin with https Kerberos authentication Change By: Tobiasz Ogórek I am writing in connection to issue referenced with impossible to connect to Visual SVN SERVER Enterprise Edition from Jenkins 2.19.4 on another machine.Issue take place using Jenkins SVN Plugin 2.7.1 with https Kerberos authentication, when trying to connect to our Visual SVN SERVER Enterprise Edition. In logs it looks like: _Jan Jan 13, 2017 10:02:29 AM hudson.scm.SubversionSCM$ModuleLocation$DescriptorImpl checkCredentialsIdSEVERE: svn: E200015: Authentication cancelled_ cancelled Visual SVN Server is configured to Use Windows authentication and at the present, there are checked both of Authentication methods: Basic authentication and Integrated Windows Authentication (It was also tested without Basic authentication with the same result).Similar situation takes place on:Jira v6.3.7JIRA Subversion plugin v2.0.3.1Please, let me know, how to solve this issue. Furthermore I would like to ask about Jenkins SVN Plugin 2.7.1/ JIRA Subversion plugin v2.0.3.1 or also SVNKit, if does they support https Kerberos authentication or not?Thanks for support in advance! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40755) Settings link appears when user does not have edit permissions
Title: Message Title Tom FENNELLY started work on JENKINS-40755 Change By: Tom FENNELLY Status: Open In Progress 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-40913) test run time totals for test suites in table is the run time for the first test suite
Title: Message Title Dennis Truemper updated an issue Jenkins / JENKINS-40913 test run time totals for test suites in table is the run time for the first test suite Change By: Dennis Truemper Attachment: Error..jpg 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-40913) test run time totals for test suites in table is the run time for the first test suite
Title: Message Title Dennis Truemper updated an issue Jenkins / JENKINS-40913 test run time totals for test suites in table is the run time for the first test suite Change By: Dennis Truemper Attachment: Error..jpg 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-40913) test run time totals for test suites in table is the run time for the first test suite
Title: Message Title Dennis Truemper updated an issue Jenkins / JENKINS-40913 test run time totals for test suites in table is the run time for the first test suite Change By: Dennis Truemper Attachment: Error.jpg 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-40913) test run time totals for test suites in table is the run time for the first test suite
Title: Message Title Dennis Truemper updated an issue Jenkins / JENKINS-40913 test run time totals for test suites in table is the run time for the first test suite Change By: Dennis Truemper Attachment: Error.jpg 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-40913) test run time totals for test suites in table is the run time for the first test suite
Title: Message Title Dennis Truemper updated an issue Jenkins / JENKINS-40913 test run time totals for test suites in table is the run time for the first test suite Change By: Dennis Truemper Attachment: Error.jpg 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-40913) test run time totals for test suites in table is the run time for the first test suite
Title: Message Title Dennis Truemper commented on JENKINS-40913 Re: test run time totals for test suites in table is the run time for the first test suite I have a very similar to identical Error. I publish every Subfolder as its own report.xml (so they all have the same name). When it is shown in this plugin I get the total time as runtime for each subreport. I allached the picture Error.jpg 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-41286) "Trigger builds remotely" not saved in Bitbucket Folder
Title: Message Title Gareth Murphy commented on JENKINS-41286 Re: "Trigger builds remotely" not saved in Bitbucket Folder Running into the same issue. Could it possibly be a conflict with the webhook functionality provided under the 'Bitbucket Team/Project > Auto-register webhooks' config? Unfortunately, since Bitbucket Server doesn't expose exactly the same webhook functionality as Bitbucket Cloud, fixing the standard remote build triggering to allow kicking off folder computation would be ideal. 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-41619) NPE in Pipeline Step after update
Title: Message Title Andreas Steffens created an issue Jenkins / JENKINS-41619 NPE in Pipeline Step after update Issue Type: Bug Assignee: Suresh Kumar Components: nexus-artifact-uploader-plugin Created: 2017/Feb/01 10:52 AM Environment: Nexus Uploader Plugin 2.9 workflow-step-api 2.7 job-dsl 1.57 credentials-plugin 2.1.11 Jenkins 2.13 Priority: Major Reporter: Andreas Steffens After Updating the Pipeline Plugins and the Uploader plugin, the later plugin throws an Null-Pointer-Exception when it is executed. Here is the Errormessage: java.lang.NullPointerException at sp.sd.nexusartifactuploader.steps.NexusArtifactUploaderStep$Execution.run(NexusArtifactUploaderStep.java:224) at sp.sd.nexusartifactuploader.steps.NexusArtifactUploaderStep$Execution.run(NexusArtifactUploaderStep.java:203) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:213) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)
[JIRA] (JENKINS-41167) credential is not saving the credentials (iframe cross origin policy issue)
Title: Message Title Daniel Beck commented on JENKINS-41167 Re: credential is not saving the credentials (iframe cross origin policy issue) right CSP settings should make it work Doubt it, as that only applies to files served by DirectoryBrowserSupport (e.g. static HTML pages archived with a build). 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-41303) Managed Files does not list previous config file after update
Title: Message Title Subhas Dandapani commented on JENKINS-41303 Re: Managed Files does not list previous config file after update Dominik Bartholdi We're facing the same issue, Config Files in global scope (which were created sometime back) disappeared, but those inside folder scopes (which were created recently) are present. We were running on latest versions of plugins all the time, and we were on 2.15.x since the day it was released. We don't have openstack config files - only maven/scripts/custom/json. Its really hard to find out what's going on and how to fix. Do you have any suggestions on where to begin? 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-41303) Managed Files does not list previous config file after update
Title: Message Title Subhas Dandapani edited a comment on JENKINS-41303 Re: Managed Files does not list previous config file after update [~imod] We're facing the same issue, Config Files in global scope (which were created sometime back) disappeared, but those inside folder scopes (which were created recently) are present. We were running on latest versions of plugins all the time, and we were on 2.15.x since the day it was released.We don't have openstack config files - only maven/scripts/custom/json. Its really hard to find out what's going on and how to fix. Do you have any Any suggestions on where to begin? 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-38508) git scm poll doesn't ignore changes with pipeline
Title: Message Title
Jukka Lehtniemi commented on JENKINS-38508
Re: git scm poll doesn't ignore changes with pipeline
I can reproduce this (Jenkins 2.43, Git plugin 3.0.1, Pipeline plugin 2.4). Steps to reproduce:
Create a testrepository:
git init /tmp/testrepo}}; cd /tmp/testrepo; echo foo > foo; git add foo; git commit -m foo
Create a new pipeline job with script:
properties([pipelineTriggers([pollSCM('* * * * *')])])
node("master") {
git(url: '/tmp/testrepo', poll:false)
}
Trigger the pipeline once manually
Commit more content to the test repository
echo foo2 >> foo; git commit -a -m foo2
Observe how the build is being triggered in a minute even if the poll=false is set
Add Comment
This message was sent by Atlas
[JIRA] (JENKINS-41303) Managed Files does not list previous config file after update
Title: Message Title Subhas Dandapani commented on JENKINS-41303 Re: Managed Files does not list previous config file after update To be frank, we've been facing a wide variety of issues and breakage of other plugins since the 2.15.x release, is there any long term fix for these issues, because this also seems to be very closely related to the migration of old files... 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-41303) Managed Files does not list previous config file after update
Title: Message Title Subhas Dandapani edited a comment on JENKINS-41303 Re: Managed Files does not list previous config file after update To This plugin is amazing, but to be frank, we've been facing a wide variety of issues and breakage of other plugins since the 2.15.x release, is there any long term fix for these issues, because this also seems to be very closely related to the migration of old files... 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-41303) Managed Files does not list previous config file after update
Title: Message Title Subhas Dandapani edited a comment on JENKINS-41303 Re: Managed Files does not list previous config file after update This plugin is amazing, but to be frank, we've been facing a wide variety of issues and breakage of other plugins since the 2.15.x release, is there any long term fix for these issues, because this issue also seems to be very closely related to the migration of old files... 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-38508) git scm poll doesn't ignore changes with pipeline
Title: Message Title
Jukka Lehtniemi edited a comment on JENKINS-38508
Re: git scm poll doesn't ignore changes with pipeline
I can reproduce this (Jenkins 2.43, Git plugin 3.0.1, Pipeline plugin 2.4).Steps to reproduce:# Create a testrepository:{code}git init /tmp/testrepo }} ; cd /tmp/testrepo; echo foo > foo; git add foo; git commit -m foo{code}# Create a new pipeline job with script:{code}properties([pipelineTriggers([pollSCM('* * * * *')])])node("master") {git(url: '/tmp/testrepo', poll:false)}{code}# Trigger the pipeline once manually# Commit more content to the test repository{code} echo foo2 >> foo; git commit -a -m foo2{code}# Observe how the build is being triggered in a minute even if the {{poll=false}} is set
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-38508) git scm poll doesn't ignore changes with pipeline
Title: Message Title Jukka Lehtniemi updated an issue Jenkins / JENKINS-38508 git scm poll doesn't ignore changes with pipeline Change By: Jukka Lehtniemi Priority: Minor Major 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-38508) git scm poll doesn't ignore changes with pipeline
Title: Message Title
Jukka Lehtniemi edited a comment on JENKINS-38508
Re: git scm poll doesn't ignore changes with pipeline
I can reproduce this (Jenkins 2.43, Git plugin 3.0.1, Pipeline plugin 2.4).Steps to reproduce:# Create a testrepository test repository :{code}git init /tmp/testrepo; cd /tmp/testrepo; echo foo > foo; git add foo; git commit -m foo{code}# Create a new pipeline job with script:{code}properties([pipelineTriggers([pollSCM('* * * * *')])])node("master") {git(url: '/tmp/testrepo', poll:false)}{code}# Trigger the pipeline once manually# Commit more content to the test repository{code} echo foo2 >> foo; git commit -a -m foo2{code}# Observe how the build is being triggered in a minute even if the {{poll=false}} is set
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-41620) Release plugin not passing parameters to ant.bat file
Title: Message Title Ciaran Duncan created an issue Jenkins / JENKINS-41620 Release plugin not passing parameters to ant.bat file Issue Type: Bug Assignee: Peter Hayes Components: release-plugin Created: 2017/Feb/01 11:16 AM Priority: Critical Reporter: Ciaran Duncan Hi. Ive created a new Jenkins Build and am now trying to automate the release of a project with the release plugin. I have set up previous jenkins build before with no problem, but using an ant.bat file this time. On trying to release I've noticed that -D options arent passed in even though they are configured properly (i think) When running the command on the command line and passing in the -D options i need it works perfect, however i need this to be done automatically. Am i missing something? Thanks, Ciaran Add Comment
[JIRA] (JENKINS-41583) job-dsl-plugin is not able to generate paramters is template has empty parameter list.
Title: Message Title Daniel Spilker closed an issue as Cannot Reproduce Jenkins / JENKINS-41583 job-dsl-plugin is not able to generate paramters is template has empty parameter list. Change By: Daniel Spilker Status: Open Closed Resolution: Cannot Reproduce 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-39321) Editable Email Notification doesn't resolve [{$BUILD_STATUS}]
Title: Message Title
Ciaran Duncan closed an issue as Fixed
Jenkins / JENKINS-39321
Editable Email Notification doesn't resolve [{$BUILD_STATUS}]
Change By:
Ciaran Duncan
Status:
Open Closed
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41077) No support for DisableSignUp
Title: Message Title rsandell commented on JENKINS-41077 Re: No support for DisableSignUp I'm not sure I understand what this is about. Signup is only available when using "Jenkins’ own user database", so when using any other authentication type there is no such thing available to disable. 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-41621) Failed to add run to trend report: Operation failed. Error code: 1001
Title: Message Title manjunath B updated an issue Jenkins / JENKINS-41621 Failed to add run to trend report: Operation failed. Error code: 1001 Change By: manjunath B the trend report is not coming up and giving the below error 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-41621) Failed to add run to trend report: Operation failed. Error code: 1001
Title: Message Title manjunath B created an issue Jenkins / JENKINS-41621 Failed to add run to trend report: Operation failed. Error code: 1001 Issue Type: Bug Assignee: Ofir Shaked Attachments: error.jpg Components: hp-application-automation-tools-plugin Created: 2017/Feb/01 11:52 AM Environment: Jenkins Enterprise 2.19.3.1, hp-application-automation-tools-plugin -version 5 Priority: Major Reporter: manjunath B Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39521) Full Log does not render newlines
Title: Message Title James Nord edited a comment on JENKINS-39521 Re: Full Log does not render newlines @i386 [~jamesdumay] this is reproduceable internally - ping me if you want more details. 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-39521) Full Log does not render newlines
Title: Message Title James Nord commented on JENKINS-39521 Re: Full Log does not render newlines @i386 this is reproduceable internally - ping me if you want more details. 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-8927) Create a view from the XML API
Title: Message Title rajasekaran radhakrishnan commented on JENKINS-8927 Re: Create a view from the XML API Patrik Boström Oleg Nenashev May I know the folder location of my view configuration page. curl http://localhost:8080/jenkins/view/MyView/config.xml is not working for me. -raja 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-8927) Create a view from the XML API
Title: Message Title rajasekaran radhakrishnan edited a comment on JENKINS-8927 Re: Create a view from the XML API Also I am unable to create new view using curlcurl -vvv -X POST -d @viewconfig.xml -H "Content-Type: text/xml" http://localhost:8080/jenkins/createView?name=My-Test-View -u admin:e973b7863cbsa11dsacdf2cd9db758091Note: Unnecessary use of -X or --request, POST is already inferred.* Trying 127.0.0.1...* Connected to localhost (127.0.0.1) port 8080 (#0)* Server auth using Basic with user 'admin'> POST /jenkins/createView?name=My-Test-View HTTP/1.1> Host: localhost:8080> Authorization: Basic YWRtaW46ZTk3M2I3ODYzY2IwNTExNzlhY2FmMmNkOWViNzIwOTE YWRtaW46ZTk3M2dsDYzY2IwNTExNzlhY2FmDEWViNzIwOTE => User-Agent: curl/7.47.0> Accept: */*> Content-Type: text/xml> Content-Length: 1410> Expect: 100-continue>< HTTP/1.1 404 Not Found< Date: Wed, 01 Feb 2017 12:00:48 GMT< X-Content-Type-Options: nosniff< Content-Type: text/html; charset=ISO-8859-1< Cache-Control: must-revalidate,no-cache,no-store< Content-Length: 302< Connection: close< Server: Jetty(9.2.z-SNAPSHOT)
[JIRA] (JENKINS-8927) Create a view from the XML API
Title: Message Title rajasekaran radhakrishnan commented on JENKINS-8927 Re: Create a view from the XML API Also I am unable to create new view using curl curl -vvv -X POST -d @viewconfig.xml -H "Content-Type: text/xml" http://localhost:8080/jenkins/createView?name=My-Test-View -u admin:e973b7863cbsa11dsacdf2cd9db758091 Note: Unnecessary use of -X or --request, POST is already inferred. Trying 127.0.0.1... Connected to localhost (127.0.0.1) port 8080 (#0) Server auth using Basic with user 'admin' > POST /jenkins/createView?name=My-Test-View HTTP/1.1 > Host: localhost:8080 > Authorization: Basic YWRtaW46ZTk3M2I3ODYzY2IwNTExNzlhY2FmMmNkOWViNzIwOTE= > User-Agent: curl/7.47.0 > Accept: / > Content-Type: text/xml > Content-Length: 1410 > Expect: 100-continue > < HTTP/1.1 404 Not Found < Date: Wed, 01 Feb 2017 12:00:48 GMT < X-Content-Type-Options: nosniff < Content-Type: text/html; charset=ISO-8859-1 < Cache-Control: must-revalidate,no-cache,no-store < Content-Length: 302 < Connection: close < Server: Jetty(9.2.z-SNAPSHOT)
[JIRA] (JENKINS-8927) Create a view from the XML API
Title: Message Title rajasekaran radhakrishnan commented on JENKINS-8927 Re: Create a view from the XML API PFB the error while creating new view. curl -X POST 'http://admin:password@localhost:8080/jenkins/createView?name=My-Test-View' --data-binary @viewconfig.xml -H "Content-Type: text/xml"Error 404 Not Found HTTP ERROR 404 Problem accessing /jenkins/createView. Reason: Not FoundPowered by Jetty:// My configuration file lokks: my-test-view my-test-view for check false false ecs-testing job/ecs-testing/ 2 my-test-view for check Lightbox false false false false false 3 false Regards, Raja 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-8927) Create a view from the XML API
Title: Message Title Daniel Beck commented on JENKINS-8927 Re: Create a view from the XML API rajasekaran radhakrishnan This is an issue tracker, not a support site. Please don't ask support type questions here. (Also, please don't ask where to ask. Just search a bit.) 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-36783) Artifact download links rely on mime type to determine download vs. view
Title: Message Title Thorsten Scherler updated JENKINS-36783 Jenkins / JENKINS-36783 Artifact download links rely on mime type to determine download vs. view Change By: Thorsten Scherler Status: In Progress Review 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-39864) Page should include build number and branch name
Title: Message Title Thorsten Scherler started work on JENKINS-39864 Change By: Thorsten Scherler Status: Open In Progress 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-41622) Perforce unshelve command override local file without revision verification.
Title: Message Title Alexander Kalach created an issue Jenkins / JENKINS-41622 Perforce unshelve command override local file without revision verification. Issue Type: Bug Assignee: Rob Petti Components: perforce-plugin Created: 2017/Feb/01 12:46 PM Environment: Jenkins ver: 2.32.1 P4 Plugin: 1.4.13 Priority: Major Reporter: Alexander Kalach We use Jenkins for pre-commit verification. To do this - developer shelve changes under CL. Jenkins job Sync to HEAD, unshelve changes, build and run verification. If someone submit changes in shelved file and developer don't update and re-shelve this file before verification - submitted changes will be overridden by shelved file without any errors or merge. Test case: create file test.txt with any content submit this file to Perforce under revision 1 do any changes in this file and shelve it under CL change this file and submit under revision 2 run job load file from SCM(configured in "Source Code Management>Perforce Software") unshelve CL in build steps check that second revision test.txt overridden by file from shelved CL.
[JIRA] (JENKINS-41432) Checkout step doesn't always show changes
Title: Message Title Phil McArdle updated an issue Jenkins / JENKINS-41432 Checkout step doesn't always show changes Change By: Phil McArdle Summary: Checkout step doesn't always show changes 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-41432) Checkout step doesn't show changes
Title: Message Title
Phil McArdle commented on JENKINS-41432
Re: Checkout step doesn't show changes
Another update, and I wish I had a clean repro for this, even one of the original jobs now doesn't show changes in the UI or API despite the p4 commands within the job seeing them. Code is similar to:
def buildCommon(Map args) {
checkout changelog: args.updateChangelog, poll: false, scm: [$class: 'PerforceScm', credential: '', populate: [$class: 'SyncOnlyImpl', have: true, modtime: false, pin: "${BUILD_CHANGELIST}", quiet: false, revert: true], workspace: [$class: 'TemplateWorkspaceImpl', charset: 'none', format: "", pinHost: true, templateName: ""]]
}
def buildVS(Map args) {
buildCommon(args)
}
def buildGCC(Map args) {
buildCommon(args)
}
def stages = [
[, updateChangelog:true, buildCommand:this.&buildVS],
[, updateChangelog:false, buildCommand:this.&buildVS],
[, updateChangelog:false, buildCommand:this.&buildGCC],
]
def builders = [:]
for (stage in stages) {
builders[] = {
stage() {
node() {
ws() {
buildCommand()
}
}
}
}
}
parallel builders
I've removed any variable names, and simplified a few things, but included every element that I think might be relevant. From one job run to the next I can't see any difference that explains why the perforce plugin isn't showing the changes in this run but did for several prior. Nor am I 100% sure how to cause it to work again.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41432) Checkout step doesn't always show changes
Title: Message Title Phil McArdle updated an issue Jenkins / JENKINS-41432 Checkout step doesn't always show changes Change By: Phil McArdle Originally, I have had two pipeline jobs which are identical in the raw XML view, the newer of which experiences this problem when trying to fetch P4 changes. Now, even the original jobs can show the same issue. In the job, I use the checkout step with PerforceScm, instead of using p4sync, because I need access to checkout's changelog: and poll: variables, which p4sync doesn't seem to expose.Use case: I sync the same depot path to multiple workspaces across multiple slaves in parallel for different tests, but if I don't use the checkout step with changelog: false, I will get identical sets of changes for as many times as I call p4sync.I poll on a different job, but also using the checkout step, as the p4sync step doesn't expose the polling filter rules. This job is XML identical to an earlier job, and the newer one has the same problem - no changes seen in the UI or the API.(As an aside, when running perforce in the checkout step, I'm not sure it obeys poll:false but it's difficult to tell because the polling might have been setup from running p4sync once?)-To "fix" the new job, I replace every instance of checkout with a p4sync with otherwise identical parameters, run the job once, and then replace them with checkout again. After this, the job reports changes properly every time.-This worked for a while, but once again both of the 'new' jobs using checkout don't report changes in the UI, though the console log says "saving built changes." and the command output as seen in the log sees the changes. To clarify some more, I have 3 stages that run in parallel, all of which call checkout, and two of which send updateChangelog: false. In my latest case of it not working, I set all 3 stages to updateChangelog: true, ran it once, got 3 sets of identical changes, set 1 stage to true and the other 2 stages to false again, ran it again and it was fine.I 'm sorry I can't report a better bug for this. Add Comment
[JIRA] (JENKINS-41432) Checkout step doesn't always show changes
Title: Message Title Phil McArdle updated an issue Jenkins / JENKINS-41432 Checkout step doesn't always show changes Change By: Phil McArdle Originally, I had two pipeline jobs which are identical in the raw XML view, the newer of which experiences this problem when trying to fetch P4 changes. Now, even the original jobs can show the same issue.In the job, I use the checkout step with PerforceScm, instead of using p4sync, because I need access to checkout's changelog: and poll: variables, which p4sync doesn't seem to expose.Use case: I sync the same depot path to multiple workspaces across multiple slaves in parallel for different tests, but if I don't use the checkout step with changelog: false, I will get identical sets of changes for as many times as I call p4sync.I poll on a different job, but also using the checkout step, as the p4sync step doesn't expose the polling filter rules. This job is XML identical to an earlier job, and the newer one has the same problem - no changes seen in the UI or the API.(As an aside, when running perforce in the checkout step, I'm not sure it obeys poll:false but it's difficult to tell because the polling might have been setup from running p4sync once?)-To "fix" the new job, I replace every instance of checkout with a p4sync with otherwise identical parameters, run the job once, and then replace them with checkout again. After this, the job reports changes properly every time.-This worked for a while, but once again both of the 'new' jobs using checkout don't report changes in the UI, though the console log says "saving built changes." and the command output as seen in the log sees the changes.I'm sorry I can't report a better bug for this. Latest comment might be more helpful: https://issues.jenkins-ci.org/browse/JENKINS-41432?focusedCommentId=285888&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-285888 Add Comment
[JIRA] (JENKINS-41432) Checkout step doesn't always show changes
Title: Message Title
Phil McArdle edited a comment on JENKINS-41432
Re: Checkout step doesn't always show changes
Another update, and I wish I had a clean repro for this, even one of the original jobs now doesn't show changes in the UI or API despite the p4 commands within the job seeing them.Code is similar to:{code:java}def buildCommon(Map args) { checkout changelog: args.updateChangelog, poll: false, scm: [$class: 'PerforceScm', credential: '', populate: [$class: 'SyncOnlyImpl', have: true, modtime: false, pin: "${BUILD_CHANGELIST}", quiet: false, revert: true], workspace: [$class: 'TemplateWorkspaceImpl', charset: 'none', format: "", pinHost: true, templateName: ""]]}def buildVS(Map args) { buildCommon(args)}def buildGCC(Map args) { buildCommon(args)}def stages = [[, updateChangelog:true, buildCommand:this.&buildVS], [, updateChangelog:false, buildCommand:this.&buildVS], [, updateChangelog:false, buildCommand:this.&buildGCC],]def builders = [:]for (stage in stages) { builders[] = { stage() {node() {ws() { buildCommand()}}}}}parallel builders{code}I've removed any variable names, and simplified a few things, but included every element that I think might be relevant.From one job run to the next I can't see any difference that explains why the perforce plugin isn't showing the changes in this run but did for several prior.Nor am I 100% sure how to cause it to work again.
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 uns
[JIRA] (JENKINS-41162) Input descriptions can contain html tags - allow or prevent
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41162 Re: Input descriptions can contain html tags - allow or prevent Code changed in jenkins User: tfennelly Path: src/main/js/page_objects/blueocean/bluePipelineActivity.js src/test/js/log-karaoke/parametrisedPipeline.js src/test/js/params-inputs/encoded-input-text.js src/test/js/params-inputs/multibranch-pipeline.js src/test/resources/test_scripts/parameterPipeline-html-in-descriptions.groovy http://jenkins-ci.org/commit/blueocean-acceptance-test/d78688b1fdc1e48082fb43010ff57783b87df53c Log: Input text markup removal test (JENKINS-41162) 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-41623) Variable Expansion in Global Variables Not Occurring
Title: Message Title
Jason Davis created an issue
Jenkins / JENKINS-41623
Variable Expansion in Global Variables Not Occurring
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2017/Feb/01 1:08 PM
Environment:
Jenkins 2.32.1 Definition Plugin 0.9.1
Priority:
Minor
Reporter:
Jason Davis
For a given global variable built via: Jenkins -> Manage Jenkins -> Configure System
Name: MYPATH
Value: ${WORKSPACE}/../path1/${JOB_BASE_NAME}
...
stage ("stage left") {
steps {
echo "MYPATH is: " + MYPATH
...
The output in the script is:
[Pipeline] echo
MYPATH is: ${WORKSPACE}/../path1/${JOB_BASE_NAME}
In Freestyle scripts the WORKSPACE and JOB_BASE_NAME values are expanded at build time. We use these as a nice way to have a few consistent job behaviors across all jobs, but without variable expansion, it seems we have to build and
[JIRA] (JENKINS-41623) Variable Expansion in Global Variables Not Occurring
Title: Message Title
Jason Davis updated an issue
Jenkins / JENKINS-41623
Variable Expansion in Global Variables Not Occurring
Change By:
Jason Davis
For Not sure about standard Pipeline scripts, but in a Declarative Pipeline script, for a given global variable built via:Jenkins -> Manage Jenkins -> Configure System{code}Name: MYPATH Value: ${WORKSPACE}/../path1/${JOB_BASE_NAME}{code}{code}...stage ("stage left") {steps {echo "MYPATH is: " + MYPATH...{code}The output in the script is:{code}[Pipeline] echoMYPATH is: ${WORKSPACE}/../path1/${JOB_BASE_NAME}{code}In Freestyle scripts the WORKSPACE and JOB_BASE_NAME values are expanded at build time. We use these as a nice way to have a few consistent job behaviors across all jobs, but without variable expansion, it seems we have to build and maintain variables in each job script.
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 Issu
[JIRA] (JENKINS-41617) browser is waiting indefinitely - jvm waiting
Title: Message Title gianluca ragnoni assigned an issue to gianluca ragnoni Jenkins / JENKINS-41617 browser is waiting indefinitely - jvm waiting Change By: gianluca ragnoni Assignee: gianluca ragnoni 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-41617) browser is waiting indefinitely - jvm waiting
Title: Message Title gianluca ragnoni resolved as Fixed The problem was the http proxy. In fact Jenkis was running behind an http proxy. Passing the following parameter to the jenkis.xml and changing the port where Jenkis is listening solved the issue. -Dhttp.proxyHost=10.22.1.45 -Dhttp.proxyPort=8080 Jenkins / JENKINS-41617 browser is waiting indefinitely - jvm waiting Change By: gianluca ragnoni 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 Issu
[JIRA] (JENKINS-41617) browser is waiting indefinitely - jvm waiting
Title: Message Title gianluca ragnoni closed an issue as Fixed Jenkins / JENKINS-41617 browser is waiting indefinitely - jvm waiting Change By: gianluca ragnoni Status: Resolved Closed 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-41303) Managed Files does not list previous config file after update
Title: Message Title Subhas Dandapani commented on JENKINS-41303 Re: Managed Files does not list previous config file after update Update: Restored org.jenkinsci.plugins.configfiles.GlobalConfigFiles.xml and org.jenkinsci.plugins.configfiles.json.JsonConfig.xml from a day old backup and things are back to normal. Restarted Jenkins a few times to make sure they don't disappear after a reload. 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-41588) Review the run details under non-multibranch conditions
Title: Message Title Ernesto Moyano stopped work on JENKINS-41588 Change By: Ernesto Moyano Status: In Progress Open 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-41588) Review the run details under non-multibranch conditions
Title: Message Title Ernesto Moyano started work on JENKINS-41588 Change By: Ernesto Moyano Status: Open In Progress 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-41535) NodeJS installation configuration is not persisted to file
Title: Message Title Christian González commented on JENKINS-41535 Re: NodeJS installation configuration is not persisted to file Can confirm the same problem: Operating System: Distributor ID: Ubuntu Description: Ubuntu 14.04.5 LTS Release: 14.04 Codename: trusty Jenkins Version: Jenkins ver. 2.43 Plugin Version: org.jenkins-ci.plugins:nodejs:1.0 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-41624) deadlock
Title: Message Title Hubert Klusek created an issue Jenkins / JENKINS-41624 deadlock Issue Type: Bug Assignee: Unassigned Attachments: threaddump.txt Components: other Created: 2017/Feb/01 1:48 PM Environment: Jenkins 2.7.3; Windows Server 2008 R2 Enterprise 64; JDK 1.8.0_112 Priority: Critical Reporter: Hubert Klusek Attached file contains threaddump from Java VisualVM. Add Comment
[JIRA] (JENKINS-41625) Com Exception During Run
Title: Message Title Prabir Sooraj created an issue Jenkins / JENKINS-41625 Com Exception During Run Issue Type: Bug Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 2017/Feb/01 1:52 PM Priority: Minor Reporter: Prabir Sooraj Encounter the following exception during the run of a suite. The exception causes the whole build to hang. Unhandled Exception: System.Runtime.InteropServices.COMException: The server threw an exception. (Exception from HRESULT: 0x80010105 (RPC_E_SERVERFAULT)) at Mercury.TD.Client.Ota.QC9.ITestSet.get_TSTestFactory() at HpToolsLauncher.AlmTestSetsRunner.RunTestSet(String tsFolderName, String tsName, Double timeout, QcRunMode runMode, String runHost) at HpToolsLauncher.AlmTestSetsRunner.Run() at HpToolsLauncher.Launcher.RunTests(IAssetRunner runner, String resultsFile) at HpToolsLauncher.Launcher.Run() at HpToolsLauncher.Program.Main(String[] args) Add Comment
[JIRA] (JENKINS-41059) Exception in thread "LittleProxy-JVM-shutdown-hook" java.lang.NoClassDefFoundError
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41059 Re: Exception in thread "LittleProxy-JVM-shutdown-hook" java.lang.NoClassDefFoundError Code changed in jenkins User: Sébastien GLON Path: pom.xml src/main/java/org/jfrog/hudson/pipeline/docker/utils/DockerUtils.java http://jenkins-ci.org/commit/artifactory-plugin/b0411c341e411693566b4dd712e49a558fcbf6b5 Log: JENKINS-41059 update docker-java 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-41059) Exception in thread "LittleProxy-JVM-shutdown-hook" java.lang.NoClassDefFoundError
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41059 Re: Exception in thread "LittleProxy-JVM-shutdown-hook" java.lang.NoClassDefFoundError Code changed in jenkins User: Eyal Ben Moshe Path: pom.xml src/main/java/org/jfrog/hudson/pipeline/docker/utils/DockerUtils.java http://jenkins-ci.org/commit/artifactory-plugin/3fb337b20d3130fea8e22b4bcdb730ecb5ddacf6 Log: Merge pull request #42 from sebglon/master JENKINS-41059 update docker-java 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-41432) Perforce plugin doesn't always show changes
Title: Message Title Phil McArdle updated an issue Jenkins / JENKINS-41432 Perforce plugin doesn't always show changes Change By: Phil McArdle Summary: Checkout step Perforce plugin doesn't always show changes 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.
