[JIRA] (JENKINS-48258) git client plugin occasionally fails with "text file busy" error
Title: Message Title Pavel Novak edited a comment on JENKINS-48258 Re: git client plugin occasionally fails with "text file busy" error [~markewaite] Hello, Mark, I apologize but I can't afford to install beta version.Anyway thanks for the feedback about the update.I noticed it looks like solution was found, good job. From my experience, I did not found any relation between environment, we are running on RHEL and tried with jenkins LTS 2.107.3 and 2.150.2, issue occurs on both machines, randomly and not so frequently. I am guessing if its not having eg. some relation to the credentials which are being used, but I am not sure (eg. stored on the global level and then being used in parallel) 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-55826) how to delete workspace forcely?
Title: Message Title Hokwang Lee created an issue Jenkins / JENKINS-55826 how to delete workspace forcely? Issue Type: Improvement Assignee: Unassigned Components: p4-plugin Created: 2019-01-29 07:55 Priority: Major Reporter: Hokwang Lee I am creating new workspace using template workspace. template workspace is locked. So created workspace is also locked. In this situation, How to delete workspace? I used cleanup true in pipeline. I think I have to change workspace's option every time or you can provide cleanup true with force option. Thanks, Add Comment
[JIRA] (JENKINS-48258) git client plugin occasionally fails with "text file busy" error
Title: Message Title Pavel Novak commented on JENKINS-48258 Re: git client plugin occasionally fails with "text file busy" error Mark Waite Hello, Mark, I apologize but I can't afford to install beta version. Anyway thanks for the feedback about the update. I noticed it looks like solution was found, good job. 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-55825) Team Foundation Server plugin error "the cache file is not valid and cannot be loaded"
Title: Message Title Alberto Lopez created an issue Jenkins / JENKINS-55825 Team Foundation Server plugin error "the cache file is not valid and cannot be loaded" Issue Type: Bug Assignee: Lionel Cabasson Components: msbuild-plugin Created: 2019-01-29 07:40 Labels: plugins windows Priority: Minor Reporter: Alberto Lopez We upgrade Jenkins to 2.150.2 version (before we had 2.89.4 version) and then, all jobs start to fail // code placeholder FATAL: The cache file C:\Windows\System32\config\systemprofile\AppData\Local\Microsoft\Team Foundation\4.0\Cache\VersionControl.config is not valid and cannot be loaded. Please correct or delete the file. org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Final de archivo prematuro. at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown Source) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unknown Source) at com.microsoft.tfs.util.xml.DOMCreateUtils.parse(DOMCreateUtils.java:600) Caused: com.microsoft.tfs.util.xml.XMLException at com.microsoft.tfs.util.xml.DOMCreateUtils.parse(DOMCreateUtils.java:602) at com.microsoft.tfs.util.xml.DOMCreateUtils.parseStream(DOMCreateUtils.java:424) at com.microsoft.tfs.util.xml.DOMCreateUtils.parseStream(DOMCreateUtils.java:357) at com.microsoft.tfs.core.clients.versioncontrol.workspacecache.internal.InternalCacheLoader.readCacheAsDocument(InternalCacheLoader.java:252) Caused: com.microsoft.tfs.core.clients.versioncontrol.exceptions.VersionControlException: The cache file C:\Windows\System32\config\systemprofile\AppData\Local\Microsoft\Team
[JIRA] (JENKINS-55824) Jenkins is loading previous configuration even when new war file is used
Title: Message Title sindhuja bd created an issue Jenkins / JENKINS-55824 Jenkins is loading previous configuration even when new war file is used Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-01-29 07:39 Priority: Critical Reporter: sindhuja bd Removed jenkins war file and installed new war file , but still , jenkins is loading previous configuration. (Loading previous login screen, plugins and everything ) Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-55808) java.nio.file.AccessDeniedException when trying to install a plugin
Title: Message Title sindhuja bd closed an issue as Fixed Issue is resolved when started jenkins as sudo user Jenkins / JENKINS-55808 java.nio.file.AccessDeniedException when trying to install a plugin Change By: sindhuja bd Status: Resolved Closed 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-55808) java.nio.file.AccessDeniedException when trying to install a plugin
Title: Message Title sindhuja bd resolved as Fixed Issue is resolved when started jenkins as sudo user Jenkins / JENKINS-55808 java.nio.file.AccessDeniedException when trying to install a plugin Change By: sindhuja bd Status: Open Resolved Resolution: Fixed 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-55810) Build result would be somehow reset to Failure
Title: Message Title Royce Shen updated an issue Jenkins / JENKINS-55810 Build result would be somehow reset to Failure Change By: Royce Shen Labels: JEP-200 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-55822) Commits to base branches (i.e. master) causes PR build storm
Title: Message Title Brian J Murrell commented on JENKINS-55822 Re: Commits to base branches (i.e. master) causes PR build storm I did manage to find a Build Strategies section a little bit lower in the GitHub Organisation page that did give me the option to select Ignore rebuilding merge branches when only the target branch changed which I think is what I am looking for. I will wait to see some base branch landing happen and see that every PR based on the base branch is not rebuilt and confirm here. 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-29851) global instance cap not respected for spot instances
Title: Message Title A B commented on JENKINS-29851 Re: global instance cap not respected for spot instances Our workaround is to manually launch instances before sending the jobs to Jenkins. This is a luxury we have, based on our configuration, that others may not have. But I wanted to share it anyway. If the instances are already idle (or in use) then the instance cap is respected and additional slaves are not initiated. It suggests to me that, when inspecting the instance cap, instances that are currently booting up are being ignored. 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-53752) Block PRs from forks from untrusted users
Title: Message Title Brian J Murrell commented on JENKINS-53752 Re: Block PRs from forks from untrusted users Any word on the status of this? I would add one more feature to allow those with write or perhaps just admin privileges to approve "untrusted" PRs. 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-55823) REST queries show password
Title: Message Title Aleksi Simell updated JENKINS-55823 Updated influx-java dependency version that uses Basic authentication instead of username+password. Jenkins / JENKINS-55823 REST queries show password Change By: Aleksi Simell Status: Open Fixed but Unreleased Resolution: Fixed 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-55823) REST queries show password
Title: Message Title Aleksi Simell created an issue Jenkins / JENKINS-55823 REST queries show password Issue Type: Bug Assignee: Aleksi Simell Components: influxdb-plugin Created: 2019-01-29 06:22 Environment: InfluxDB-plugin 1.20.2 Priority: Critical Reporter: Aleksi Simell When the plugin writes to InfluxDB, the InfluxDB logs show the actual username and password used. The plugin should prevent that from happening. Add Comment
[JIRA] (JENKINS-37491) Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes
Title: Message Title Brian J Murrell edited a comment on JENKINS-37491 Re: Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes [~aldochristiaan] By _multiple pipeline job_ do you mean GitHub Organisation jobs? Because I agree, the proposed solution here doesn't seem to apply, AFAICT, to the GitHub Source Branch Plugin multibranch-pipeline job.So those users still need a solution to these build storms that just take down your Jenkins machine every time a base branch (i.e. master) is updated. I guess we need [ another ticket |https://issues . jenkins-ci.org/browse/JENKINS-55822]. 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-37491) Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes
Title: Message Title Brian J Murrell edited a comment on JENKINS-37491 Re: Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes [~aldochristiaan] By _multiple pipeline job_ do you mean GitHub Organisation jobs? Because I agree, the proposed solution here doesn't seem to apply, AFAICT, to the GitHub Source Branch Plugin multibranch-pipeline job.So those users still need a solution to these build storms that just take down your Jenkins machine every time a base branch (i.e. master) is updated. I guess we need another ticket. 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-37491) Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes
Title: Message Title Brian J Murrell edited a comment on JENKINS-37491 Re: Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes [~aldochristiaan] By _multiple pipeline job_ do you mean GitHub Organisation jobs? Because I agree, the proposed solution here doesn't seem to apply, AFAICT, to the GitHub Source Branch Plugin multibranch-pipeline job.So those users still need a solution to these build storms that just take down your Jenkins machine every time a base branch (i.e. master) is updated. I guess we need another ticket. 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-55822) Commits to base branches (i.e. master) causes PR build storm
Title: Message Title Brian J Murrell created an issue Jenkins / JENKINS-55822 Commits to base branches (i.e. master) causes PR build storm Issue Type: Bug Assignee: Unassigned Components: github-branch-source-plugin Created: 2019-01-29 05:57 Environment: GitHub Branch Source Plugin: 2.3.6 Priority: Major Reporter: Brian J Murrell As is pretty well documented in JENKINS-37491, when one has many PRs open on a given GitHub project/repo and a new commit lands to the base branch of all of those PRs (I'm looking at you master), all of the open PRs get a build scheduled. This can bring a Jenkins server to it's knees. I don't think we need to rehash the debate about whether every PR should be built against current master to ensure it doesn't break the new master. That can be enforced with branch protection in GitHub if that's something people want to do. But having your Jenkins server crush and take days to flush out when a new commit lands to master is just unworkable. JENKINS-37491 proposed: Install Basic Branch Build Strategies plugin and add the "Change Requests" with "Ignore rebuilding merge branches when only the target branch changed" selected to your build strategies but that doesn't seem to be applicable to GitHub organisation jobs. So what is the solution here? I'm using Pipeline: Multibranch jobs if that matters.
[JIRA] (JENKINS-37491) Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes
Title: Message Title Brian J Murrell commented on JENKINS-37491 Re: Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes Aldo Christian By multiple pipeline job do you mean GitHub Organisation jobs? Because I agree, the proposed solution here doesn't seem to apply, AFAICT, to the GitHub Source Branch Plugin multibranch-pipeline job. So those users still need a solution to these build storms that just take down your Jenkins machine every time a base branch (i.e. master) is updated. I guess we need another ticket. 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-55693) Joda time recommends using java.time in Java 8 and later
Title: Message Title Mark Waite updated JENKINS-55693 Will be included in git plugin 4.0.0 when it releases Jenkins / JENKINS-55693 Joda time recommends using java.time in Java 8 and later Change By: Mark Waite Status: In Review Resolved Resolution: Fixed 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-55693) Joda time recommends using java.time in Java 8 and later
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-55693 Joda time recommends using java.time in Java 8 and later Change By: Mark Waite Status: Resolved Closed 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-19725) Unable to unmarshall response (Couldn't initialize a SAX driver to create an XMLReader)
Title: Message Title Radoslav Ivanov commented on JENKINS-19725 Re: Unable to unmarshall response (Couldn't initialize a SAX driver to create an XMLReader) any progress here? we still get that issue and no suggestions of the above work. 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-55810) Build result would be somehow reset to Failure
Title: Message Title
Royce Shen updated an issue
Jenkins / JENKINS-55810
Build result would be somehow reset to Failure
Change By:
Royce Shen
We have a pipeline job in our environment, ever since we updated Jenkins from 2.89,2 to 2.138.2( also updated some Pipeline & Blueocean relating plugins ), something really strange happened. A build that finishes with SUCCESS would later be set to FAILURE, and the icon that shows the status of the build would also be reset to the red failed one. But in the console log, it still shows SUCCESS. Whereas, a build that finishes with FAILURE would stay failed status.This also resulted in the chaos of mail notification, we keep receiving "Job is back to normal" notification.The attachments are the console log of successful builds and theirs build status icons. Also get something from Jenkins system log:Jan 25, 2019 4:50:42 AM hudson.model.Run executeINFO: TextProc *** / lmportal *** #693 main build action completed: SUCCESSJan 25, 2019 4:50:51 AM hudson.slaves.RetentionStrategy$Demand checkINFO: Launching computer LMTools-nrg7-unn2-lmtools as it has been in demand for 1 min 50 secJan 25, 2019 4:50:51 AM hudson.model.Run execute {color:#172b4d}SEVERE: Failed to save build record{color}{color:#172b4d}java.io.IOException: java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class hudson.model.FreeStyleBuild at hudson.XmlFile.write(XmlFile.java:200) at hudson.model.Run.save(Run.java:2015) at hudson.model.Run.execute(Run.java:1876) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Caused by: java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class hudson.model.FreeStyleBuild at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:209) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:150) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.TreeMarshaller.start(TreeMarshaller.java:82) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.marshal(AbstractTreeMarshallingStrategy.java:37) at com.thoughtworks.xstream.XStream.marshal(XStream.java:1026) at com.thoughtworks.xstream.XStream.marshal(XStream.java:1015) at com.thoughtworks.xstream.XStream.toXML(XStream.java:988) at hudson.XmlFile.write(XmlFile.java:193) ... 5 moreCaused by:
[JIRA] (JENKINS-55810) Build result would be somehow reset to Failure
Title: Message Title
Royce Shen updated an issue
Jenkins / JENKINS-55810
Build result would be somehow reset to Failure
Change By:
Royce Shen
We have a pipeline job in our environment, ever since we updated Jenkins from 2.89,2 to 2.138.2( also updated some Pipeline & Blueocean relating plugins ), something really strange happened. A build that finishes with SUCCESS would later be set to FAILURE, and the icon that shows the status of the build would also be reset to the red failed one. But in the console log, it still shows SUCCESS. Whereas, a build that finishes with FAILURE would stay failed status.This also resulted in the chaos of mail notification, we keep receiving "Job is back to normal" notification.The attachments are the console log of successful builds and theirs build status icons. Also get something from Jenkins system log:Jan 25, 2019 4:50:42 AM hudson.model.Run executeINFO: TextProc/lmportal #693 main build action completed: SUCCESSJan 25, 2019 4:50:51 AM hudson.slaves.RetentionStrategy$Demand checkINFO: Launching computer LMTools-nrg7-unn2-lmtools as it has been in demand for 1 min 50 secJan 25, 2019 4:50:51 AM hudson.model.Run execute {color:# ff 172b4d }SEVERE: Failed to save build record{color} {color:#172b4d}java.io.IOException: java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class hudson.model.FreeStyleBuild at hudson.XmlFile.write(XmlFile.java:200) at hudson.model.Run.save(Run.java:2015) at hudson.model.Run.execute(Run.java:1876) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Caused by: java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class hudson.model.FreeStyleBuild at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:209) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:150) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.TreeMarshaller.start(TreeMarshaller.java:82) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.marshal(AbstractTreeMarshallingStrategy.java:37) at com.thoughtworks.xstream.XStream.marshal(XStream.java:1026) at com.thoughtworks.xstream.XStream.marshal(XStream.java:1015) at com.thoughtworks.xstream.XStream.toXML(XStream.java:988) at hudson.XmlFile.write(XmlFile.java:193) ... 5 moreCaused by:
[JIRA] (JENKINS-51511) Build job serialization is failing on 2.107.3 LTS causing loss of data.
Title: Message Title Royce Shen updated an issue Jenkins / JENKINS-51511 Build job serialization is failing on 2.107.3 LTS causing loss of data. Change By: Royce Shen after upgrading from 2.89.3 to 2.107.3 I'm seeing issues with build record serialization. Build records are not being saved and are lost when the service is restarted. Here is the stack trace.I have the job-dsl 1.69 installed as well. Note I tried reverting to 1.66 but there was no change in behavior.OS : Ubuntu 14.04JDK : 1.8.0_172Installation Type : Debian package SEVERE: Failed to save build recordjava.io.IOException: java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class hudson.model.FreeStyleBuild at hudson.XmlFile.write(XmlFile.java:200) at hudson.model.Run.save(Run.java:1923) at hudson.model.Run.execute(Run.java:1784) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Caused by: java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class hudson.model.FreeStyleBuild at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:209) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:150) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.TreeMarshaller.start(TreeMarshaller.java:82) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.marshal(AbstractTreeMarshallingStrategy.java:37) at com.thoughtworks.xstream.XStream.marshal(XStream.java:1026) at com.thoughtworks.xstream.XStream.marshal(XStream.java:1015) at com.thoughtworks.xstream.XStream.toXML(XStream.java:988) at hudson.XmlFile.write(XmlFile.java:193) ... 5 moreCaused by: java.lang.RuntimeException: Failed to serialize hudson.model.CauseAction#causeBag for class hudson.model.CauseAction at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:209)
[JIRA] (JENKINS-55552) NullPointerException when using Credentials Binding Plugin
Title: Message Title tony kerz commented on JENKINS-2 Re: NullPointerException when using Credentials Binding Plugin thanks p cowlinator you are the man! i burned a few hours on this until i came across your post! i'll have to second the vote to not crash hard when one of the args isn't passed 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-55810) Build result would be somehow reset to Failure
Title: Message Title
Royce Shen updated an issue
Jenkins / JENKINS-55810
Build result would be somehow reset to Failure
Change By:
Royce Shen
We have a pipeline job in our environment, ever since we updated Jenkins from 2.89,2 to 2.138.2( also updated some Pipeline & Blueocean relating plugins ), something really strange happened. A build that finishes with SUCCESS would later be set to FAILURE, and the icon that shows the status of the build would also be reset to the red failed one. But in the console log, it still shows SUCCESS. Whereas, a build that finishes with FAILURE would stay failed status.This also resulted in the chaos of mail notification, we keep receiving "Job is back to normal" notification.The attachments are the console log of successful builds and theirs build status icons. Also get something from Jenkins system log:Jan 25, 2019 4:50:42 AM hudson.model.Run executeINFO: TextProc/lmportal #693 main build action completed: SUCCESSJan 25, 2019 4:50:51 AM hudson.slaves.RetentionStrategy$Demand checkINFO: Launching computer LMTools-nrg7-unn2-lmtools as it has been in demand for 1 min 50 secJan 25, 2019 4:50:51 AM hudson.model.Run execute{color:# FF ff }SEVERE: Failed to save build record{color} Would be very grateful if anyone could figure out why this strange thing happens.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-55418) Pipeline Syntax generator not present
Title: Message Title Andrew Gray commented on JENKINS-55418 Re: Pipeline Syntax generator not present My fault. I was looking in the wrong place on that screen. Is all pipeline syntax generation for the warnings-ng plugin entirely covered by this recordIssues Sample Step? 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-55814) Version 0.3.12 contains breaking changes
Title: Message Title Jie Shen commented on JENKINS-55814 Re: Version 0.3.12 contains breaking changes Hi Julien Tanay, thanks for your reporting. It should not need new configuration for this upgrade. Could you please provide some details here, like what was you version before you upgraded and what error message in your build now? 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-55814) Version 0.3.12 contains breaking changes
Title: Message Title Jie Shen assigned an issue to Jie Shen Jenkins / JENKINS-55814 Version 0.3.12 contains breaking changes Change By: Jie Shen Assignee: Azure DevOps Jie Shen 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-55821) Allow to always pull base images for docker.build() in all pipelines
Title: Message Title
Eugene G updated an issue
Jenkins / JENKINS-55821
Allow to always pull base images for docker.build() in all pipelines
Change By:
Eugene G
The problem looks close to JENKINS-25690 but it is related to the default Jenkins Pipeline functionality.{code:java}pipeline {agent { label 'master' }stages {stage('Build') {steps {script {image = docker.build('myorg/myapp:latest')// image = docker.build('myorg/myapp:latest', '--pull .') // how it must look like now}}}}}{code} It would be nice to have a global option to force Docker to *always* pull base images before build ("--pull" argument). When you have a lot of Jenkinsfiles it is very hard to control that all of them pull base images before each build.Update: but with the ability to bypass the global setting for a specific line with docker.build(). There's a corner case when one image must be build FROM another one that also was built locally. In this situation "--pull" argument will break the second build because it hadn't been pushed to a registry yet .
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
[JIRA] (JENKINS-55821) Allow to always pull base images for docker.build() in all pipelines
Title: Message Title
Eugene G updated an issue
Jenkins / JENKINS-55821
Allow to always pull base images for docker.build() in all pipelines
Change By:
Eugene G
The problem looks close to JENKINS-25690 but it is related to the default Jenkins Pipeline functionality.{code:java}pipeline {agent { label 'master' }stages {stage('Build') {steps {script {image = docker.build('myorg/myapp:latest')// image = docker.build('myorg/myapp:latest', '--pull .') // how it must look like now}}}}}{code} It would be nice to have a global option to force Docker to *always* pull base images before build ("--pull" argument). When you have a lot of Jenkinsfiles it is very hard to control that all of them pull base images before each build. Update: but with the ability to bypass the global setting for a specific line with docker.build(). There's a corner case when one image must be build FROM another one that also was built locally. In this situation "--pull" argument will break the second 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
[JIRA] (JENKINS-55821) Allow to always pull base images for docker.build() in all pipelines
Title: Message Title Eugene G commented on JENKINS-55821 Re: Allow to always pull base images for docker.build() in all pipelines Related StackOverflows: https://stackoverflow.com/questions/45057282/jenkins-docker-how-to-force-pull-base-image-before-build https://stackoverflow.com/questions/52345748/how-to-always-use-the-newest-version-of-a-docker-base-image 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-55821) Allow to always pull base images for docker.build() in all pipelines
Title: Message Title
Eugene G updated an issue
Jenkins / JENKINS-55821
Allow to always pull base images for docker.build() in all pipelines
Change By:
Eugene G
The problem looks close to JENKINS-25690 but it is related to the default Jenkins Pipeline functionality.{code:java}pipeline {agent { label 'master' }stages {stage('Build') {steps {script {image = docker.build('myorg/myapp:latest')// image = docker.build('myorg/myapp:latest', '--pull .') // how it must looks look like now}}}}}{code} It would be nice to have a global option to force Docker to *always* pull base images before build ("--pull" argument). When you have a lot of Jenkinsfiles it is very hard to control that all of them pull base images before each 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-55821) Allow to always pull base images for docker.build() in all pipelines
Title: Message Title
Eugene G updated an issue
Jenkins / JENKINS-55821
Allow to always pull base images for docker.build() in all pipelines
Change By:
Eugene G
The problem looks close to JENKINS-25690 but it is related to the default Jenkins Pipeline functionality.{code:java}pipeline {agent { label 'master' }stages {stage('Build') {steps {script {image = docker.build('myorg/myapp:latest') // image = docker.build('myorg/myapp:latest', '--pull .') // how it must looks like now }}}}}{code} It would be nice to have a global option to force Docker to *always* pull base images before build ("--pull" argument). When you have a lot of Jenkinsfiles it is very hard to control that all of them pull base images before each 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-55821) Allow to always pull base images for docker.build() in all pipelines
Title: Message Title
Eugene G created an issue
Jenkins / JENKINS-55821
Allow to always pull base images for docker.build() in all pipelines
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2019-01-29 00:35
Labels:
docker-build-step Docker
Priority:
Minor
Reporter:
Eugene G
The problem looks close to JENKINS-25690 but it is related to the default Jenkins Pipeline functionality.
pipeline {
agent { label 'master' }
stages {
stage('Build') {
steps {
script {
image = docker.build('myorg/myapp:latest')
}
}
}
}
}
It would be nice to have a global option to force Docker to always pull base images before build ("--pull" argument). When you have a lot of Jenkinsfiles it is very hard to control that all of them pull base images before each build.
[JIRA] (JENKINS-55816) Publish over FTP fails on multi-module project when modules skipped
Title: Message Title Metin Savignano commented on JENKINS-55816 Re: Publish over FTP fails on multi-module project when modules skipped I see what you mean. Just FYI, I've found another variation of this problem here. It looks like the getResult() method returns only the result of the last module/component? 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-55804) Performance: Reduce memory footprint and execution time for RoleMap#newMatchingRoleMap()
Title: Message Title Deepansh Nagaria updated JENKINS-55804 Jenkins / JENKINS-55804 Performance: Reduce memory footprint and execution time for RoleMap#newMatchingRoleMap() Change By: Deepansh Nagaria Status: Closed Fixed but Unreleased 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-55804) Performance: Reduce memory footprint and execution time for RoleMap#newMatchingRoleMap()
Title: Message Title Deepansh Nagaria closed an issue as Fixed Jenkins / JENKINS-55804 Performance: Reduce memory footprint and execution time for RoleMap#newMatchingRoleMap() Change By: Deepansh Nagaria Status: Open Closed Resolution: Fixed 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-54689) Incorrect display build duration time
Title: Message Title Stephen French commented on JENKINS-54689 Re: Incorrect display build duration time I am working on reproducing this error. Can you clarify which two reports of build time disagree? Which display of task execution time are you speaking of? (The pipeline dashboard? For example, I browse to my Jenkins server running on an aws instance at http://54.198.76.254:8080/ , and then click on my project, to take me to the pipeline dashboard. I named my project 'foo'. So the final address in my browser is http://54.198.76.254:8080/job/foo/. This page gives me times for all the different stages of my Jenkins pipeline) And the second source for build time (the JSON source), are you finding this at $BUILD_URL/api/json? For example, when I go to http://54.198.76.254:8080/job/foo/1/api/json?pretty=true I can see a "duration" entry with a value of 17994. 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-55803) Performance: Replace RoleMap#getRolesHavingPermission() usages by iterators
Title: Message Title Deepansh Nagaria commented on JENKINS-55803 Re: Performance: Replace RoleMap#getRolesHavingPermission() usages by iterators I attempted this issue. Here's the pr: https://github.com/jenkinsci/role-strategy-plugin/pull/54 please correct me where ever required. 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-55807) Performance: Get and check the role in havePermissions
Title: Message Title Deepansh Nagaria commented on JENKINS-55807 Re: Performance: Get and check the role in havePermissions I attempted this issue. Here's the pr: https://github.com/jenkinsci/role-strategy-plugin/pull/53 please correct me where ever required. 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-55807) Performance: Get and check the role in havePermissions
Title: Message Title Deepansh Nagaria assigned an issue to Deepansh Nagaria Jenkins / JENKINS-55807 Performance: Get and check the role in havePermissions Change By: Deepansh Nagaria Assignee: Oleg Nenashev Deepansh Nagaria 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-48258) git client plugin occasionally fails with "text file busy" error
Title: Message Title Mark Waite commented on JENKINS-48258 Re: git client plugin occasionally fails with "text file busy" error Thanks Christopher Unkel! 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-48258) git client plugin occasionally fails with "text file busy" error
Title: Message Title Christopher Unkel commented on JENKINS-48258 Re: git client plugin occasionally fails with "text file busy" error FYI, I've been running a snapshot build of beta2 + this fix for nearly 8 months. Prior to this fix I encountered the bug several times a week. It has not happened a single time since installing the snapshot version. It has completely resolved the issue for me. 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-55820) pluginmanager should include full date stamp for last update
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-55820 pluginmanager should include full date stamp for last update Issue Type: Improvement Assignee: Unassigned Components: core Created: 2019-01-28 21:55 Priority: Minor Reporter: Josh Soref Currently it shows: Update information obtained: 4 sec ago But there's no indication of what that's relative to, and it gets stale pretty quickly. It could show both relative and absolute timestamps, or it could require a hover to get absolute. Add Comment
[JIRA] (JENKINS-55681) Release the JAXB Plugin
Title: Message Title Raphael Pionke edited a comment on JENKINS-55681 Re: Release the JAXB Plugin Hi [~batmat],we are using JAXB quite heavily for ur plugin: [https://plugins.jenkins.io/performance-signature-dynatrace]I want to use ur plugin as a dependency for Java 11 compatibility, but the build job of the plugin on ci.jenkins.io fails: [https://ci.jenkins.io/job/Plugins/job/performance-signature-dynatrace-plugin/job/master/54/console]Do u know why? Basically i want to fix https://issues.jenkins-ci.org/browse/JENKINS-55202 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-55681) Release the JAXB Plugin
Title: Message Title Raphael Pionke commented on JENKINS-55681 Re: Release the JAXB Plugin Hi Baptiste Mathus, we are using JAXB quite heavily for ur plugin: https://plugins.jenkins.io/performance-signature-dynatrace I want to use ur plugin as a dependency for Java 11 compatibility, but the build job of the plugin on ci.jenkins.io fails: https://ci.jenkins.io/job/Plugins/job/performance-signature-dynatrace-plugin/job/master/54/console Do u know why? 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-22026) Propagate failure causes from downstream builds
Title: Message Title Jared Jasie commented on JENKINS-22026 Re: Propagate failure causes from downstream builds Tomas Westling rsandell Hi guys - has this fix been abandoned? 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-55816) Publish over FTP fails on multi-module project when modules skipped
Title: Message Title Alex Earl commented on JENKINS-55816 Re: Publish over FTP fails on multi-module project when modules skipped Again, the option to only do things on success, etc is specific to Maven builds. The plugin MUST look at the build status for other builds types. I will look into different options. 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-55816) Publish over FTP fails on multi-module project when modules skipped
Title: Message Title Metin Savignano commented on JENKINS-55816 Re: Publish over FTP fails on multi-module project when modules skipped You've linked to the Jenkins plugin, so I assumed that this was a Jenkins functionality. In the context of Jenkins, I think it would make sense not to determine the build success within the plugin, but instead let Jenkins take care of that. However, maybe it's an idea to create a new option (tickbox) to let the user decide whether the plugin should check the build result or not? 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-55812) Cannot use Incrementals from pom.xml
Title: Message Title Oleg Nenashev commented on JENKINS-55812 Re: Cannot use Incrementals from pom.xml Yes. pom.xml input support has not been tested with Incrementals. It is likely a valid defect, to be triaged 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-55812) Cannot use Incrementals from pom.xml
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-55812 Cannot use Incrementals from pom.xml Change By: Oleg Nenashev Assignee: Oleg Nenashev 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-53022) Cannot disable a job from Blue Ocean UI
Title: Message Title Dont Use assigned an issue to Gavin Mogan Jenkins / JENKINS-53022 Cannot disable a job from Blue Ocean UI Change By: Dont Use Assignee: Dont Use Gavin Mogan 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-53077) Failed to execute 'replaceChild' on 'Node': parameter 1 is not of type 'Node'.
Title: Message Title
Josh Soref edited a comment on JENKINS-53077
Re: Failed to execute 'replaceChild' on 'Node': parameter 1 is not of type 'Node'.
` {{ this.success ` }} is from * prototype.js * [ https://github.com/jenkinsci/jenkins/blob/22aa2e6e766074d11249893e3f35e0b99e20d3d0/war/src/main/webapp/scripts/prototype.js#L1639 ]
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-53077) Failed to execute 'replaceChild' on 'Node': parameter 1 is not of type 'Node'.
Title: Message Title Josh Soref commented on JENKINS-53077 Re: Failed to execute 'replaceChild' on 'Node': parameter 1 is not of type 'Node'. https://github.com/jenkinsci/jenkins/pull/3869 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-53077) Failed to execute 'replaceChild' on 'Node': parameter 1 is not of type 'Node'.
Title: Message Title Josh Soref commented on JENKINS-53077 Re: Failed to execute 'replaceChild' on 'Node': parameter 1 is not of type 'Node'. `this.success` is from prototype.js https://github.com/jenkinsci/jenkins/blob/22aa2e6e766074d11249893e3f35e0b99e20d3d0/war/src/main/webapp/scripts/prototype.js#L1639 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-53077) Failed to execute 'replaceChild' on 'Node': parameter 1 is not of type 'Node'.
Title: Message Title
Josh Soref updated an issue
Jenkins / JENKINS-53077
Failed to execute 'replaceChild' on 'Node': parameter 1 is not of type 'Node'.
Change By:
Josh Soref
e:{code:java}TypeError: Failed to execute 'replaceChild' on 'Node': parameter 1 is not of type 'Node'.at onSuccess (hudson-behavior.js:1524)at klass.respondToReadyState (VM283 prototype.js:1657)at klass.onStateChange (VM283 prototype.js:1600)at XMLHttpRequest. (VM283 prototype.js:414) {code}response.responseText: {{""}}[https://github.com/jenkinsci/jenkins/blob/723e5ed8fb1a5289edc31d82bb9ad67e6d97bcd9/war/src/main/webapp/scripts/hudson-behavior.js#L1524]I verified that:[https://github.com/jenkinsci/jenkins/blob/723e5ed8fb1a5289edc31d82bb9ad67e6d97bcd9/war/src/main/webapp/scripts/hudson-behavior.js#L1523]{code:java}var node = $(div).firstDescendant(); {code}yielded {{null}}.Further investigation shows:{{response.status}} : {{0}}The code for {{this.success()}} used by {{respondToReadyState()}} treats this as a resonse response to call {{this.options.onSuccess}}, but I suspect it would be better handled by {{this.options.onFailure}} or by dropping it or something.See [https://stackoverflow.com/questions/36416389/why-does-my-xmlhttprequest-have-readystate-4-but-status-0] for reports of this case.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You
[JIRA] (JENKINS-55738) NodeMonitor out of disk space message is wrong for master
Title: Message Title Jesse Glick commented on JENKINS-55738 Re: NodeMonitor out of disk space message is wrong for master here the behaviour of changed code is not okay Why do you say that? Error is of Remote call on jenkinsinfra-highmem8ca11 failed Likely a problem in CI infrastructure, not the code being tested. Are there any specific tests needed for this through which I can get to know that whether it works or not? As previously mentioned, I am not aware of any. The issue relates solely to the user interface and test coverage of the UI is low. 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-55807) Performance: Get and check the role in havePermissions
Title: Message Title Deepansh Nagaria assigned an issue to Oleg Nenashev Jenkins / JENKINS-55807 Performance: Get and check the role in havePermissions Change By: Deepansh Nagaria Assignee: Deepansh Nagaria Oleg Nenashev 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-55803) Performance: Replace RoleMap#getRolesHavingPermission() usages by iterators
Title: Message Title Deepansh Nagaria assigned an issue to Deepansh Nagaria Jenkins / JENKINS-55803 Performance: Replace RoleMap#getRolesHavingPermission() usages by iterators Change By: Deepansh Nagaria Assignee: Deepansh Nagaria 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-55803) Performance: Replace RoleMap#getRolesHavingPermission() usages by iterators
Title: Message Title Deepansh Nagaria assigned an issue to Deepansh Nagaria Jenkins / JENKINS-55803 Performance: Replace RoleMap#getRolesHavingPermission() usages by iterators Change By: Deepansh Nagaria Assignee: Oleg Nenashev Deepansh Nagaria 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-55803) Performance: Replace RoleMap#getRolesHavingPermission() usages by iterators
Title: Message Title Deepansh Nagaria assigned an issue to Oleg Nenashev Jenkins / JENKINS-55803 Performance: Replace RoleMap#getRolesHavingPermission() usages by iterators Change By: Deepansh Nagaria Assignee: Deepansh Nagaria Oleg Nenashev 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-55805) Warnings Next Generation Plugin is slow at parsing the log output
Title: Message Title Ronald Brill edited a comment on JENKINS-55805 Re: Warnings Next Generation Plugin is slow at parsing the log output Thanks fr for looking at this.Yes, java and a bunch of PMD Spotbugs and all that stuff. Will provide more details but In detail:* Java* Checkstyle* JavaDoc* PMD* CPD* SpotbugsAll with the jenkins does not respond at the moment (i guess the parser hooks the whole server right now) default settings . 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-55807) Performance: Get and check the role in havePermissions
Title: Message Title Deepansh Nagaria assigned an issue to Deepansh Nagaria Jenkins / JENKINS-55807 Performance: Get and check the role in havePermissions Change By: Deepansh Nagaria Assignee: Oleg Nenashev Deepansh Nagaria 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-40723) Built Dockerfile images are never removed
Title: Message Title Attila Szeremi commented on JENKINS-40723 Re: Built Dockerfile images are never removed I disagree with brushing this ticket off to use `docker-gc` instead. First of all, it makes no sense to use `docker-gc` in the `post` section of the declarative pipeline, because `docker-gc` only removes images that are older than (by default) 1 hour old. The image we'd want to clean is very fresh though. Secondly, `docker-gc` (to me) undesirably removes all other images as well; ones I might still be using. If I have a cron job set to run a Docker image every 2 hours, and `docker-gc` would keep removing the image, then I would need to have the re-download the image from the registry each time, wasting time and bandwidth. It would be great if either the generated image tag would automatically be removed on build finish, or if the image tag were predictable so that I could clean up manually in the end. Or simply just making the image tag available so I could read it. Currently here is how I clean up my built Docker image. I am forced to use imperative scriptsto build the Docker image to get the image tag so that I could clean up in the end. 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-54807) Maven HPI Plugin or Plugin POM should automatically set up Java 11 environment for hpi:run
Title: Message Title Adrien Lecharpentier commented on JENKINS-54807 Re: Maven HPI Plugin or Plugin POM should automatically set up Java 11 environment for hpi:run I just filled a PR to work on this subject. 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-54807) Maven HPI Plugin or Plugin POM should automatically set up Java 11 environment for hpi:run
Title: Message Title Adrien Lecharpentier updated JENKINS-54807 Jenkins / JENKINS-54807 Maven HPI Plugin or Plugin POM should automatically set up Java 11 environment for hpi:run Change By: Adrien Lecharpentier Status: In Progress Review 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-54807) Maven HPI Plugin or Plugin POM should automatically set up Java 11 environment for hpi:run
Title: Message Title Adrien Lecharpentier started work on JENKINS-54807 Change By: Adrien Lecharpentier Status: Open In Progress 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-54807) Maven HPI Plugin or Plugin POM should automatically set up Java 11 environment for hpi:run
Title: Message Title Adrien Lecharpentier assigned an issue to Adrien Lecharpentier Jenkins / JENKINS-54807 Maven HPI Plugin or Plugin POM should automatically set up Java 11 environment for hpi:run Change By: Adrien Lecharpentier Assignee: Adrien Lecharpentier 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-55453) Github PR creating job but not building
Title: Message Title Tyler Pickett commented on JENKINS-55453 Re: Github PR creating job but not building Looking into this some more I'm finding that the IDs keep changing on both ends like they're getting recreated constantly but out of sync. 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-48900) Show "Full Name" on Assign Roles page?
Title: Message Title Mrinal Dutta commented on JENKINS-48900 Re: Show "Full Name" on Assign Roles page? how to get started on JIRA? like how should I resolve any issue or add feature ? 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-54506) Some compiler warnings are misidentified as Javadoc warnings
Title: Message Title Mrinal Dutta started work on JENKINS-54506 Change By: Mrinal Dutta Status: Open In Progress 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-54506) Some compiler warnings are misidentified as Javadoc warnings
Title: Message Title Mrinal Dutta stopped work on JENKINS-54506 Change By: Mrinal Dutta Status: In Progress Open 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-55819) Jenkins occasionally loses parameters passed downstream
Title: Message Title
Andrey Babushkin created an issue
Jenkins / JENKINS-55819
Jenkins occasionally loses parameters passed downstream
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2019-01-28 18:06
Environment:
Jenkins LTS 2.138 deployed from official Docker image pipeline-build-step 2.7 pipeline-model-api 1.2.7 pipeline-model-declarative-agent 1.1.1 pipeline-model-definition 1.2.7 pipeline-model-extensions 1.2.7
Priority:
Minor
Reporter:
Andrey Babushkin
We use pipeline jobs retrieved via Git SCM. There are simplified version of how they look like:
// name: my_upstream_job.groovy
// just triggers some downstream build
thebuild = build job: 'my_downstream_job',
propagate: false,
parameters: [
string(name: "my_str_param", value: "foo")
]
// name: my_downstream_job.groovy
// occasionally fails due to java.lang.NullPointerException: Cannot invoke method contains() on null object
properties([
parameters([
string(
defaultValue: '',
description: 'Some parameter for demo',
name: 'my_str_param')
])
])
// if we're using something like this outside of node() step
// build can occasionally fail
if (env.my_str_param.contains("foo")) {
println
[JIRA] (JENKINS-55818) Extend REST API to enable navigation by modules, issue types, priority etc.
Title: Message Title
Stefan Schletterer created an issue
Jenkins / JENKINS-55818
Extend REST API to enable navigation by modules, issue types, priority etc.
Issue Type:
Improvement
Assignee:
Ulli Hafner
Components:
warnings-ng-plugin
Created:
2019-01-28 18:03
Priority:
Minor
Reporter:
Stefan Schletterer
The web gui of the static analysis plugin allows me to navigate and sort the data by modules, issue types and filter by severity. However, the io.jenkins.plugins.analysis.core.restapi.AnalysisResultApi }}doesn't return the required information to navigate e.g. to a specific module. Currently the only navigation path is for {{./new, ./fixed and ./all. However, when using the web gui, and navigating to a specific module, then a URL is generated for this module, and this can be used to get the data RESTful for the module (like cppcheck/moduleName.192380630/api/json). In our specific case we want to display say top 5 modules in a web dashboard, and allow the user to jump to the Jenkins warnings-ng UI, eg. job/cppCheck/14/cppcheck/moduleName.1853593734/type.1844850586/ Perhaps the tree query syntax enable sorting and paging like on the web ui.
Add Comment
[JIRA] (JENKINS-55816) Publish over FTP fails on multi-module project when modules skipped
Title: Message Title Alex Earl commented on JENKINS-55816 Re: Publish over FTP fails on multi-module project when modules skipped That option is not part of the plugin itself, and the plugin is used in more than just Maven builds, so I can't really remove it. I am not very familiar with Maven jobs, so I am not sure what will need to be done here. I will need to look into it further. 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-55781) When selecting Git in Source Code Management and updating http://user:passw...@bitbucket.com/.git. It gives an authentication error.
Title: Message Title
Mark Waite edited a comment on JENKINS-55781
Re: When selecting Git in Source Code Management and updating http://user:passw...@bitbucket.com/.git. It gives an authentication error.
The bitbucket message says:{quote}Your Bitbucket account has been locked. To unlock it and log in again you mustsolve a CAPTCHA. This is typically caused by too many attempts to login with anincorrect password. The account lock prevents your SCM client from accessingBitbucket and its mirrors until it is solved, even if you enter your passwordcorrectly.If you are currently logged in to Bitbucket via a browser you may need tologout and then log back in in order to solve the CAPTCHA.{quote}Have you connected to that bitbucket account from a web browser, logged out, then logged in again? If so, did it require that you solve the CAPTCHA as stated in that message?When you say that you {quote}tried the workaround and it didn't help{quote} , does that mean that you defined a credential and then used that credential, or something else?
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-55738) NodeMonitor out of disk space message is wrong for master
Title: Message Title Nisarg Shah commented on JENKINS-55738 Re: NodeMonitor out of disk space message is wrong for master I just need to verify the changes done by doing tests as I had a look on code once again and thought that the changes done in the pr looks fine just needed to get verify. Are there any specific tests needed for this through which I can get to know that whether it works or not? 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-48258) git client plugin occasionally fails with "text file busy" error
Title: Message Title Mark Waite edited a comment on JENKINS-48258 Re: git client plugin occasionally fails with "text file busy" error [~pavenova] I provided the status update in a [preceding comment|https://issues.jenkins-ci.org/browse/JENKINS-48258?focusedCommentId=341685=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-341685]. That status report is still correct. The change that is intended to fix this problem is included in the current git client plugin 3.0.0 beta releases.I can't duplicate the problem and have never been able to duplicate the problem.Could you please provide a status report of your experiences using the git client plugin 3.0.0 beta release and the git plugin 4.0.0 beta release?If you haven't installed the beta release of the plugin, when can I expect that you will install the beta release of the plugin?How long will you run the beta release in your environment to assure that the issue is resolved?While I'm happy to hear that you're interested in the fix, I'm much more interested in test results from users that can duplicate the problem. The fix that has been included in the beta release for multiple months. 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-48258) git client plugin occasionally fails with "text file busy" error
Title: Message Title Mark Waite commented on JENKINS-48258 Re: git client plugin occasionally fails with "text file busy" error Pavel Novak I provided the status update in a preceding comment. That status report is still correct. The change that is intended to fix this problem is included in the current git client plugin 3.0.0 beta releases. I can't duplicate the problem and have never been able to duplicate the problem. Could you please provide a status report of your experiences using the git client plugin 3.0.0 beta release and the git plugin 4.0.0 beta release? If you haven't installed the beta release of the plugin, when can I expect that you will install the beta release of the plugin? How long will you run the beta release in your environment to assure that the issue is resolved? While I'm happy to hear that you're interested in the fix, I'm much more interested in test results from users that can duplicate the problem. The fix that has been included in the beta release for multiple months. 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-55816) Publish over FTP fails on multi-module project when modules skipped
Title: Message Title Metin Savignano commented on JENKINS-55816 Re: Publish over FTP fails on multi-module project when modules skipped Thanks. Does not give me any more insight, though. It works okay when building snapshots, but fails on releases. Does it refer to the release build only somehow? However, I wonder why the plugin checks the build result, because when configuring the FTP step in the build, the user selects between "Run only if build succeeds", "Run only if build succeeds or is unstable", "Run regardless of build result". The fact that the plugin tries to act according to the build result is actually confusing. For example, I tried it with "Run regardless of build result", but the plugin insists on making its own decision and ignores my wish. I think the plugin itself should not check the build result at all. 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-55816) Publish over FTP fails on multi-module project when modules skipped
Title: Message Title Metin Savignano edited a comment on JENKINS-55816 Re: Publish over FTP fails on multi-module project when modules skipped Thanks. Does not give me any more insight, though. It works okay when building snapshots, but fails on releases. Does it refer to the release snapshot build only somehow?However, I wonder why the plugin checks the build result, because when configuring the FTP step in the build, the user selects between "Run only if build succeeds", "Run only if build succeeds or is unstable", "Run regardless of build result". The fact that the plugin tries to act according to the build result is actually confusing. For example, I tried it with "Run regardless of build result", but the plugin insists on making its own decision and ignores my wish.I think the plugin itself should not check the build result at all. 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-55781) When selecting Git in Source Code Management and updating http://user:passw...@bitbucket.com/.git. It gives an authentication error.
Title: Message Title Mark Waite commented on JENKINS-55781 Re: When selecting Git in Source Code Management and updating http://user:passw...@bitbucket.com/.git. It gives an authentication error. The bitbucket message says: Your Bitbucket account has been locked. To unlock it and log in again you must solve a CAPTCHA. This is typically caused by too many attempts to login with an incorrect password. The account lock prevents your SCM client from accessing Bitbucket and its mirrors until it is solved, even if you enter your password correctly. If you are currently logged in to Bitbucket via a browser you may need to logout and then log back in in order to solve the CAPTCHA. Have you connected to that bitbucket account from a web browser, logged out, then logged in again? If so, did it require that you solve the CAPTCHA as stated in that message? When you say that you tried the workaround and it didn't help , does that mean that you defined a credential and then used that credential, or something else? 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-55361) DescriptorExtensionList not locking correctly, leading to deadlocks
Title: Message Title Oleg Nenashev commented on JENKINS-55361 Re: DescriptorExtensionList not locking correctly, leading to deadlocks https://github.com/jenkinsci/jenkins/pull/3828 from Arnaud TAMAILLON addresses this issue 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-32402) Credentials binding fails to find creds when using a Parameterized Expression, but only for timed jobs
Title: Message Title
Christopher Sullivan edited a comment on JENKINS-32402
Re: Credentials binding fails to find creds when using a Parameterized _expression_, but only for timed jobs
I worked around this issue by using the [Authorize Project plugin|https://wiki.jenkins.io/display/JENKINS/Authorize+Project+plugin]. Instead of passing the credentials from the upstream job, I set the {{defaultValue}} of the parameter instead to globally scoped credentials.For build "Authorization" (enabled by Authorize Project), I set the job to run as a user with access to the global credentials (I would have used credentials scoped to the user only, but you can't use these as default values). When selecting "Build with Parameters" as any other user, only the user scoped credentials are available.Other users can still pass parameters to the job and successfully run it if they have the correct credentials. - If they try to run the job without specifying their own credentials, they can not access the default credentials and the job fails as desired. - (still working on restricting access to the credentials) When initiated by timer, it uses the default globally scoped credentials and successfully runs.
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-55816) Publish over FTP fails on multi-module project when modules skipped
Title: Message Title Alex Earl commented on JENKINS-55816 Re: Publish over FTP fails on multi-module project when modules skipped This method is used to determine when to build: https://github.com/jenkinsci/publish-over-plugin/blob/3669f32d0a3d13d140fa353d95390b6547b76b02/src/main/java/jenkins/plugins/publish_over/BPPlugin.java#L143 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-55816) Publish over FTP fails on multi-module project when modules skipped
Title: Message Title Metin Savignano edited a comment on JENKINS-55816 Re: Publish over FTP fails on multi-module project when modules skipped According to the very similar issue described in JENKINS-16240, it may not actually happen always when modules are skipped. In fact, I have another Jenkins build with skipped modules, and there, the FTP takes place as expected.How 's the NOT_BUILT determined? 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-55816) Publish over FTP fails on multi-module project when modules skipped
Title: Message Title Metin Savignano edited a comment on JENKINS-55816 Re: Publish over FTP fails on multi-module project when modules skipped According to the very similar issue described in JENKINS-16240, it may not actually happen always when modules are skipped. In fact, I have another Jenkins build with skipped modules, and there, the FTP takes place as expected.How the NOT_BUILT determined? 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-55816) Publish over FTP fails on multi-module project when modules skipped
Title: Message Title Metin Savignano commented on JENKINS-55816 Re: Publish over FTP fails on multi-module project when modules skipped According to the very similar issue described in JENKINS-16240, it may not actually happen always when modules are skipped. In fact, I have another Jenkins build with skipped modules, and the FTP takes place as expected. How the NOT_BUILT determined? 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-55815) Allow API access with Google Login Plugin
Title: Message Title Ryan Campbell closed an issue as Won't Do Please reopen with details on why the Jenkins API key is insufficient Jenkins / JENKINS-55815 Allow API access with Google Login Plugin Change By: Ryan Campbell Status: Open Closed Resolution: Won't Do 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-55815) Allow API access with Google Login Plugin
Title: Message Title Ryan Campbell commented on JENKINS-55815 Re: Allow API access with Google Login Plugin This is already possible by setting an API key for your user. https://support.cloudbees.com/hc/en-us/articles/115003090592-How-to-re-generate-my-Jenkins-user-token There isn't a way to authenticate with your Google password via API that I'm aware of anyway. But the above should work fine. 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-32402) Credentials binding fails to find creds when using a Parameterized Expression, but only for timed jobs
Title: Message Title Christopher Sullivan commented on JENKINS-32402 Re: Credentials binding fails to find creds when using a Parameterized _expression_, but only for timed jobs I worked around this issue by using the Authorize Project plugin. Instead of passing the credentials from the upstream job, I set the defaultValue of the parameter instead to globally scoped credentials. For build "Authorization" (enabled by Authorize Project), I set the job to run as a user with access to the global credentials (I would have used credentials scoped to the user only, but you can't use these as default values). When selecting "Build with Parameters" as any other user, only the user scoped credentials are available. Other users can still pass parameters to the job and successfully run it if they have the correct credentials. If they try to run the job without specifying their own credentials, they can not access the default credentials and the job fails as desired. When initiated by timer, it uses the default globally scoped credentials and successfully runs. 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-18884) Seperate Permission for People View to close Security Hole with AD Plugin
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-18884 Seperate Permission for People View to close Security Hole with AD Plugin Change By: Oleg Nenashev Labels: configuration permissions security security-hardening 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-8618) would like to use one instance per build
Title: Message Title Matt Sicker updated JENKINS-8618 PR merged to master: https://github.com/jenkinsci/ec2-plugin/pull/323 Jenkins / JENKINS-8618 would like to use one instance per build Change By: Matt Sicker Status: Open Fixed but Unreleased Resolution: Fixed 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-55738) NodeMonitor out of disk space message is wrong for master
Title: Message Title Nisarg Shah edited a comment on JENKINS-55738 Re: NodeMonitor out of disk space message is wrong for master In my pull request yesterday testing was being done and it passed all the tests. And a green tick was given that all tests cases passed and this commit can be build. But today tests were running once again and one error occurred which is different from the errors occurred in earlier test. Error is of Remote call on jenkinsinfra-highmem8ca11 failed 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-55738) NodeMonitor out of disk space message is wrong for master
Title: Message Title Nisarg Shah commented on JENKINS-55738 Re: NodeMonitor out of disk space message is wrong for master In my pull request yesterday testing was being done and it passed all the tests. And a green tick was given that all tests cases passed and this commit can be build. But today tests were running once again and one error occurred which is different from the errors occurred in earlier test. 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-46006) image.inside leaks volumes
Title: Message Title Julien Leroy commented on JENKINS-46006 Re: image.inside leaks volumes I'm actually having the same issue. I use a container for test database (so it's forgotten after usage), and so I would like the volume to be deleted when the container is removed. 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-55248) workspace mixup when 2 jobs running on 2 diff nodes at the same time
Title: Message Title Karl Wirth commented on JENKINS-55248 Re: workspace mixup when 2 jobs running on 2 diff nodes at the same time Hi Frederico Pratas. I have just sent you a private email so I can request more information. Please let me know if you don't receive it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55813) Improve AD/LDAP attribute analysis for locked accounts
Title: Message Title Wadeck Follonier commented on JENKINS-55813 Re: Improve AD/LDAP attribute analysis for locked accounts The PRs in ldap and active-directory uses the Microsoft's standard for the attribute names/values. I am not sure that's sufficient to cover most of the usage. 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-55817) Support Credentials store for SSH Steps
Title: Message Title Naresh Rayapati created an issue Jenkins / JENKINS-55817 Support Credentials store for SSH Steps Issue Type: Improvement Assignee: Naresh Rayapati Components: ssh-steps-plugin Created: 2019-01-28 15:42 Priority: Minor Reporter: Naresh Rayapati Currently we need to use `withCredentials` to map the credentials to all the steps, it would nice to have credentials store integrated to read the credentials from store. Add Comment This message was sent by Atlassian Jira
