[JIRA] (JENKINS-42029) Add "pin build at label" to Preview Check Only populate options
Title: Message Title peter anderson commented on JENKINS-42029 Re: Add "pin build at label" to Preview Check Only populate options hit tab and the ticket got assigned to me - sorry about that. Anyway, I have noticed that the functionality to set `pin` from jobDSL exists, but it doesn't appear in the Jenkins UI. I am not sure if it wasn't intended to show up in populate -> previewonly or if it is meant to show up in the UI. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42029) Add "pin build at label" to Preview Check Only populate options
Title: Message Title peter anderson assigned an issue to Unassigned Jenkins / JENKINS-42029 Add "pin build at label" to Preview Check Only populate options Change By: peter anderson Assignee: peter anderson Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42029) Add "pin build at label" to Preview Check Only populate options
Title: Message Title peter anderson assigned an issue to peter anderson Jenkins / JENKINS-42029 Add "pin build at label" to Preview Check Only populate options Change By: peter anderson Assignee: peter anderson Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54511) When using the SpecWorkspaceImpl workspaces are update twice every build
Title: Message Title peter anderson commented on JENKINS-54511 Re: When using the SpecWorkspaceImpl workspaces are update twice every build Looking at the other JIRA it only talks about the "root" changing, nothing about the "host". Can you confirm that the flip-flopping of the "host" has also been fixed Paul Allen? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52661) P4 Plugin fails to parse changelog
Title: Message Title peter anderson updated an issue Jenkins / JENKINS-52661 P4 Plugin fails to parse changelog Change By: peter anderson Attachment: changelog2.xml Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52661) P4 Plugin fails to parse changelog
Title: Message Title peter anderson updated an issue Jenkins / JENKINS-52661 P4 Plugin fails to parse changelog Change By: peter anderson Attachment: changelog2.xml Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54671) Script not found results in success in durable-task-plugin
Title: Message Title
peter anderson created an issue
Jenkins / JENKINS-54671
Script not found results in success in durable-task-plugin
Issue Type:
Bug
Assignee:
Unassigned
Components:
durable-task-plugin
Created:
2018-11-16 11:07
Environment:
CloudBees Jenkins Enterprise 2.121.1.2-rolling Durable Task Plugin: 1.22
Priority:
Major
Reporter:
peter anderson
When running the powershell task, if the path you pass doesn't exist, the step does not cause the build to fail: pipeline: node("WINDOWS_MACHINE") { powershell("a_file_that_doesnt_exist") } output: Running in Durability level: MAX_SURVIVABILITY [Pipeline] node Running on in D:\J\workspace\TEST_POWERSHELL_STEP [Pipeline] { [Pipeline] powershell [TEST_POWERSHELL_STEP] Running PowerShell script powershell.exe : a_file_that_doesnt_exist : The term 'a_file_that_doesnt_exist' is not recognized as the name of a cmdlet, function, At D:\J\workspace\TEST_POWERSHELL_STEP@tmp\durable-feef7c1b\powershellWrapper.ps1:5 char:3 + & powershell -NoProfile -NonInteractive -ExecutionPolicy Bypass -Fi ... + ~~~ + CategoryInfo : NotSpecified: (a_file_that_doe...let, function, :String) [], RemoteException + FullyQualifiedErrorId : NativeCommandError script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At D:\J\workspace\TEST_POWERSHELL_STEP@tmp\durable-feef7c1b\powershellScript.ps1:1 char:1 + a_file_that_doesnt_exist + + CategoryInfo : ObjectNotFound: (a_file_that_doesnt_exist:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline Finished: SUCCESS — I would expect that
[JIRA] (JENKINS-54511) When using the SpecWorkspaceImpl workspaces are update twice every build
Title: Message Title peter anderson updated an issue Jenkins / JENKINS-54511 When using the SpecWorkspaceImpl workspaces are update twice every build Change By: peter anderson Summary: When using the SpecWorkspaceImpl workspaces are update twice every build Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54511) When using the SpecWorkspaceImpl workspaces are update every build
Title: Message Title
peter anderson created an issue
Jenkins / JENKINS-54511
When using the SpecWorkspaceImpl workspaces are update every build
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
Jenkins.template-configscripts.txt
Components:
p4-plugin
Created:
2018-11-07 11:05
Environment:
Docker CloudBees Jenkins Enterprise 2.121.1.2-rolling p4 plugin version: 1.8.9
Labels:
p4-plugin
Priority:
Major
Reporter:
peter anderson
if you are using variables for the root or host properties in your SpecWorkspaceImpl spec file, the p4 plugin will update the workspace two times a build: Host property: If it isn't set in the spec file it will set it to '' (blank) and then it will update then set the host value on the client spec to the currently running node host name. Root property: If you are using a variable (e.g. ${WORKSPACE}) the root is first set to 'WORKSPACE' and then it is set to current workspace you have specified in your jenkinsfile (using the ws() task). Although everything still syncs correctly, over time this results in thousands of revisions on the same workspace that hasn't really changed. This can have a significant impact on the ability to backup the given perforce server. I think the whole client spec should be expanded/resolved before it "updates" the client spec. This should prevent the updating of a client spec on every build. diff of
[JIRA] (JENKINS-52661) P4 Plugin fails to parse changelog
Title: Message Title peter anderson edited a comment on JENKINS-52661 Re: P4 Plugin fails to parse changelog I have added another case where the xml parser fails. This time it appears to be related to the perforce commit comment containing a unicode character: !screenshot-1.png|thumbnail! These kinds of errors cause the job to fail in jenkins - this is a big problem considering some builds trigger of the success of another build. They shouldn't be failing for this reason. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52661) P4 Plugin fails to parse changelog
Title: Message Title peter anderson updated an issue Jenkins / JENKINS-52661 P4 Plugin fails to parse changelog Change By: peter anderson Attachment: screenshot-1.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52661) P4 Plugin fails to parse changelog
Title: Message Title peter anderson commented on JENKINS-52661 Re: P4 Plugin fails to parse changelog I have added another case where the xml parser fails. This time it appears to be related to the perforce commit comment containing a unicode character: Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52661) P4 Plugin fails to parse changelog
Title: Message Title
peter anderson updated an issue
Jenkins / JENKINS-52661
P4 Plugin fails to parse changelog
Change By:
peter anderson
Some Jenkins jobs fail because the P4 plugin is not able to parse the changelog: {noformat}org.xml.sax.SAXParseException; systemId: file:/var/jenkins_home/jobs/Maintenance/builds/4/changelog5.xml; lineNumber: 1; columnNumber: 1; Premature end of file. at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:203) at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:177) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:400) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:327) at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1472) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:1014) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:602) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:505) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:841) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:770) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:643) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:327) at javax.xml.parsers.SAXParser.parse(SAXParser.java:328) at org.jenkinsci.plugins.p4.changes.P4ChangeParser.parse(P4ChangeParser.java:50) Caused: org.xml.sax.SAXException: Could not parse perforce changelog: org.xml.sax.SAXParseException; systemId: file:/var/jenkins_home/jobs/Maintenance/builds/4/changelog5.xml; lineNumber: 1; columnNumber: 1; Premature end of file. at org.jenkinsci.plugins.p4.changes.P4ChangeParser.parse(P4ChangeParser.java:54) at org.jenkinsci.plugins.workflow.job.WorkflowRun.onCheckout(WorkflowRun.java:847) at org.jenkinsci.plugins.workflow.job.WorkflowRun.access$1500(WorkflowRun.java:143) at org.jenkinsci.plugins.workflow.job.WorkflowRun$SCMListenerImpl.onCheckout(WorkflowRun.java:1041) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:127) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:85) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:75) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:290) at
[JIRA] (JENKINS-49141) P4 plugin removed BOM from utf8 files
Title: Message Title peter anderson commented on JENKINS-49141 Re: P4 plugin removed BOM from utf8 files p4 ticket: RE: Perforce Jenkins Plugin Bug ref:_00DA09M15._5000G1RiJb9:ref The guys at p4 have reproduced the bug and will work with Paul Allen to fix it. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49141) P4 plugin removed BOM from utf8 files
Title: Message Title peter anderson commented on JENKINS-49141 Re: P4 plugin removed BOM from utf8 files Hey Paul Allen, any chance you will be able to take a look at this in the near future? Although its not a "blocker" as such, I don't feel comfortable upgrading when the plugin behaviour is so different to the exe behaviour Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
