[JIRA] (JENKINS-52994) Pipeline Syntax Generator for specifying browsers missing
Title: Message Title Andrew Gray created an issue Jenkins / JENKINS-52994 Pipeline Syntax Generator for specifying browsers missing Issue Type: Bug Assignee: Yeh Fang Components: sauce-ondemand-plugin Created: 2018-08-11 05:26 Environment: All Priority: Major Reporter: Andrew Gray The Pipeline Syntax generator for the Sauce On Demand plugin does not provide a means to specify which browsers to test on (like the controls provided in a freestyle build). I want to be able to specify browsers in the same way as under a freestyle build and generate the code that needs to go in my Jenkinsfile to correctly call the Sauce OnDemand plugin. I do not want to use Nightwatch.js. I am using C# and NUnit Add Comment
[JIRA] (JENKINS-52993) JGit 5.02 logs failure to delete a pruned branch
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-52993
JGit 5.02 logs failure to delete a pruned branch
Change By:
Mark Waite
The JGitAPIImpl prune implementation logs a message that it is unable to remove path. Possible behavioral change in the transition from JGit 4.5.4 to JGIt 5.0.2. Stack trace indicates it is happening in the caches directory used by a multi-branch project. The referenced directory is not empty. The message is correct, but if deletion is not expected to succeed and is harmless, the exception should be accepted and suppressed. {noformat}Aug 10, 2018 11:04:46 PM org.eclipse.jgit.internal.storage.file.RefDirectory deleteWARNING: Unable to remove path /var/jenkins_home/caches/git-c3acd33583448548d14667df83b93ee1/.git/logs/refs/remotes/originjava.nio.file.DirectoryNotEmptyException: /var/jenkins_home/caches/git-c3acd33583448548d14667df83b93ee1/.git/logs/refs/remotes/originat sun.nio.fs.UnixFileSystemProvider.implDelete(UnixFileSystemProvider.java:242)at sun.nio.fs.AbstractFileSystemProvider.delete(AbstractFileSystemProvider.java:103)at java.nio.file.Files.delete(Files.java:1126)at org.eclipse.jgit.internal.storage.file.RefDirectory.delete(RefDirectory.java:1289)at org.eclipse.jgit.internal.storage.file.RefDirectory.delete(RefDirectory.java:1273)at org.eclipse.jgit.internal.storage.file.RefDirectory.delete(RefDirectory.java:694)at org.eclipse.jgit.internal.storage.file.RefDirectoryUpdate.doDelete(RefDirectoryUpdate.java:153)at org.eclipse.jgit.lib.RefUpdate$2.execute(RefUpdate.java:680)at org.eclipse.jgit.lib.RefUpdate.updateImpl(RefUpdate.java:774)at org.eclipse.jgit.lib.RefUpdate.delete(RefUpdate.java:677)at org.eclipse.jgit.lib.RefUpdate.delete(RefUpdate.java:649)at org.eclipse.jgit.api.DeleteBranchCommand.call(DeleteBranchCommand.java:144)at org.jenkinsci.plugins.gitclient.JGitAPIImpl$2.execute(JGitAPIImpl.java:635)at jenkins.plugins.git.AbstractGitSCMSource.doRetrieve(AbstractGitSCMSource.java:356)at jenkins.plugins.git.AbstractGitSCMSource.retrieve(AbstractGitSCMSource.java:544)at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:357)at jenkins.scm.api.SCMSource.fetch(SCMSource.java:267)at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:633)at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:276)at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:165)at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:1024)at hudson.model.ResourceController.execute(ResourceController.java:97)at hudson.model.Executor.run(Executor.java:429){noformat}
[JIRA] (JENKINS-52993) JGit 5.02 logs failure to delete a pruned branch
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-52993 JGit 5.02 logs failure to delete a pruned branch Issue Type: Improvement Assignee: Unassigned Components: git-client-plugin Created: 2018-08-11 05:15 Environment: Git client plugin 3.0.0-beta5 Git plugin 4.0.0-beta pre-release Jenkins 2.121.2 My lts-with-plugins repo, in the caches directory Priority: Minor Reporter: Mark Waite The JGitAPIImpl prune implementation logs a message that it is unable to remove path. Possible behavioral change in the transition from JGit 4.5.4 to JGIt 5.0.2. Aug 10, 2018 11:04:46 PM org.eclipse.jgit.internal.storage.file.RefDirectory delete WARNING: Unable to remove path /var/jenkins_home/caches/git-c3acd33583448548d14667df83b93ee1/.git/logs/refs/remotes/origin java.nio.file.DirectoryNotEmptyException: /var/jenkins_home/caches/git-c3acd33583448548d14667df83b93ee1/.git/logs/refs/remotes/origin at sun.nio.fs.UnixFileSystemProvider.implDelete(UnixFileSystemProvider.java:242) at sun.nio.fs.AbstractFileSystemProvider.delete(AbstractFileSystemProvider.java:103) at java.nio.file.Files.delete(Files.java:1126) at org.eclipse.jgit.internal.storage.file.RefDirectory.delete(RefDirectory.java:1289) at org.eclipse.jgit.internal.storage.file.RefDirectory.delete(RefDirectory.java:1273) at org.eclipse.jgit.internal.storage.file.RefDirectory.delete(RefDirectory.java:694) at org.eclipse.jgit.internal.storage.file.RefDirectoryUpdate.doDelete(RefDirectoryUpdate.java:153) at org.eclipse.jgit.lib.RefUpdate$2.execute(RefUpdate.java:680)
[JIRA] (JENKINS-44824) "minimum" of f:repeatableProperty is inherit from ancestors
Title: Message Title ikedam assigned an issue to Unassigned Really interesting issue. I found that this occurs for the implementation of Jenkins core. Changed component/s. Jenkins / JENKINS-44824 "minimum" of f:repeatableProperty is inherit from ancestors Change By: ikedam Summary: Exception when saving job config due to empty Classpath entry "minimum" of f:repeatableProperty is inherit from ancestors Issue Type: Improvement Bug Component/s: core Component/s: groovy-postbuild-plugin Assignee: Stefan Wolf Add Comment
[JIRA] (JENKINS-47761) Unable to view parameters created in post build to pass them as part of promote build plugin
Title: Message Title
ikedam updated JENKINS-47761
I can't get the point or what you expect at all. The groovy interpolation ("$RES_DIR ...") works for the groovy variables, not for the build parameters. So your code should never work. And it looks to me that you already succeeded to capture and display outputs with manager.listener.logger.println "${resDir}". Please reopen the ticket if you missed explaining the actual point.
Jenkins / JENKINS-47761
Unable to view parameters created in post build to pass them as part of promote build plugin
Change By:
ikedam
Status:
Open Fixed but Unreleased
Assignee:
Stefan Wolf Amith Arangi
Resolution:
Not A Defect
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message
[JIRA] (JENKINS-52043) manager.removeBadge(index) throws UnsupportedOperationException
Title: Message Title ikedam updated JENKINS-52043 Thanks for the fix! Please let me have some more time to make a new release. Jenkins / JENKINS-52043 manager.removeBadge(index) throws UnsupportedOperationException Change By: ikedam Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52043) manager.removeBadge(index) throws UnsupportedOperationException
Title: Message Title ikedam assigned an issue to ikedam Jenkins / JENKINS-52043 manager.removeBadge(index) throws UnsupportedOperationException Change By: ikedam Assignee: Stefan Wolf ikedam Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51370) Error on using Groovy Postbuild plugin
Title: Message Title ikedam assigned an issue to Shalhoob Manatheykad Shalhoob Manatheykad Let me know more about the situation. When and where is the stacktrace displayed? In build logs (when a build runs) or on web pages (when opening the build configuration etc.) Jenkins / JENKINS-51370 Error on using Groovy Postbuild plugin Change By: ikedam Assignee: Stefan Wolf Shalhoob Manatheykad Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51370) Error on using Groovy Postbuild plugin
Title: Message Title ikedam commented on JENKINS-51370 Re: Error on using Groovy Postbuild plugin This looks rather an issue of script-security for this part of the stacktrace: Caused by: java.lang.IllegalStateException: maybe need to rebuild plugin? at org.jenkinsci.plugins.scriptsecurity.scripts.ScriptApproval.get(ScriptApproval.java:99) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SecureGroovyScript$DescriptorImpl.doCheckScript(SecureGroovyScript.java:410) Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41930) manager.addShortText requires protection of characters '<' and '>'
Title: Message Title ikedam updated JENKINS-41930 Fixed in groovy-postbuild-2.4. Jenkins / JENKINS-41930 manager.addShortText requires protection of characters '<' and '>' Change By: ikedam Status: Open Fixed but Unreleased Assignee: Stefan Wolf Alexander Samoylov Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41930) manager.addShortText requires protection of characters '<' and '>'
Title: Message Title ikedam updated JENKINS-41930 Please try groovy-postbuild-2.4. Jenkins / JENKINS-41930 manager.addShortText requires protection of characters '<' and '>' Change By: ikedam Status: Fixed but Unreleased Resolved Released As: groovy-postbuild-2.4. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50420) Class-exception in Build Monitor Plugin with Groovy Postbuild Plugin 2.4
Title: Message Title ikedam updated JENKINS-50420 Please try build-monitor 1.11. Jenkins / JENKINS-50420 Class-exception in Build Monitor Plugin with Groovy Postbuild Plugin 2.4 Change By: ikedam Status: Fixed but Unreleased Resolved Assignee: Jan Molak GMC Software Development B Corporate Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50420) Class-exception in Build Monitor Plugin with Groovy Postbuild Plugin 2.4
Title: Message Title ikedam updated JENKINS-50420 Should be fixed in build-monitor-1.11. Jenkins / JENKINS-50420 Class-exception in Build Monitor Plugin with Groovy Postbuild Plugin 2.4 Change By: ikedam Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52879) Explore testcontainers for test automation
Title: Message Title Pham Vu Tuan updated JENKINS-52879 Jenkins / JENKINS-52879 Explore testcontainers for test automation Change By: Pham Vu Tuan Status: In Review Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52992) Provide a configuration for a mirror URL for jsrepository.json
Title: Message Title Steve Springett assigned an issue to Steve Springett Jenkins / JENKINS-52992 Provide a configuration for a mirror URL for jsrepository.json Change By: Steve Springett Assignee: Steve Springett Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52969) java.lang.InterruptedException: sleep interrupted
Title: Message Title Swathi Gangisetty commented on JENKINS-52969 Re: java.lang.InterruptedException: sleep interrupted You are right about the anchore stage failing. Anchore plugin logs indicate that the plugin received an interrupt signal and bailed. I'm trying to figure out what/who triggered this interrupt signal in the first place. It sounds like you've ruled out another stage failing and triggering the interrupt. Another potential for termination would be a timeout if its enforced on the anchore plugin stage. I would need to look through the build console logs to investigate this further Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52992) Provide a configuration for a mirror URL for jsrepository.json
Title: Message Title Gusti Benawi created an issue Jenkins / JENKINS-52992 Provide a configuration for a mirror URL for jsrepository.json Issue Type: Improvement Assignee: Unassigned Components: dependency-check-jenkins-plugin Created: 2018-08-10 22:05 Priority: Minor Reporter: Gusti Benawi Currently the URL for the jsrepository.json is hardcoded in the Dependency Core in the dependency-check.properties file. Unlike the CLI counterpart, where it is possible to overwrite the URL, it is not possible to do this using the Jenkins Plugin. In a restricted environment, where the internet connection to that hardcoded URL is, not allowed, retirejs analyzer will fail. It would be good if we can provide a way (for eg. in the Jenkins Global Configuration for Dependency Check Plugin) to overwrite this URL Add Comment
[JIRA] (JENKINS-50097) MavenConsole parser skips duplicate lines
Title: Message Title Ulli Hafner started work on JENKINS-50097 Change By: Ulli Hafner Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51444) Maven Parser creates errors during affectedFilesResolving
Title: Message Title Ulli Hafner started work on JENKINS-51444 Change By: Ulli Hafner Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46044) ec2 plugin doesn't work it has same label with other slaves
Title: Message Title Travis Neal commented on JENKINS-46044 Re: ec2 plugin doesn't work it has same label with other slaves I have this problem too, we created a single jenkins system to be used by our entire company, but because of this queue build up on common labels like "ubuntu" and "windows" there's an exponential queue time of waiting for executors and eventually creating a new instance. Was hoping the One-Shot Executor Plugin would fix this, however that only supplies an API to be used by other plugins and the Amazon EC2 plugin doesn't implement this API. Working on creating a custom plugin to tie these 2 community plugins together. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23697) IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276)
Title: Message Title Devin Nusbaum commented on JENKINS-23697 Re: IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276) Another way I recent saw this issue was with a ModelHyperlinkNote where the model object's display name contained newlines. When the log was being annotated, only the text up to the first newline was considered, so the lengths did not match. I am going to file a change to ModelHyperlinkNote to replace newlines with spaces to prevent that class of errors. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52904) Clean up Error Telemetry tests to use expect and make sure they're testing the hook methods correctly
Title: Message Title Mandie Smith updated JENKINS-52904 Jenkins / JENKINS-52904 Clean up Error Telemetry tests to use expect and make sure they're testing the hook methods correctly Change By: Mandie Smith Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title Paul Kramer updated an issue Jenkins / JENKINS-41662 Proceed button fails (investigate) Change By: Paul Kramer Attachment: image-2018-08-10-13-33-42-164.png Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title Paul Kramer edited a comment on JENKINS-41662 Re: Proceed button fails (investigate) We see the same behavior.!image-2018-08-10-13-35-50-968.png! We expect that pressing the Run button should take us to the page i show in the second part of this picture. We should see the input page. But we don't. We have to press refresh.Is there any thought on what we should investigate? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title Paul Kramer updated an issue Jenkins / JENKINS-41662 Proceed button fails (investigate) Change By: Paul Kramer Attachment: image-2018-08-10-13-35-50-968.png Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title Paul Kramer commented on JENKINS-41662 Re: Proceed button fails (investigate) We see the same behavior. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title Paul Kramer updated an issue Jenkins / JENKINS-41662 Proceed button fails (investigate) Change By: Paul Kramer Comment: HowdyWe see this too.!image-2018-08-10-13-33-42-164.png! Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title Paul Kramer commented on JENKINS-41662 Re: Proceed button fails (investigate) Howdy We see this too. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title Paul Kramer updated an issue Jenkins / JENKINS-41662 Proceed button fails (investigate) Change By: Paul Kramer Attachment: image-2018-08-10-13-33-42-164.png Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52969) java.lang.InterruptedException: sleep interrupted
Title: Message Title Ben Mathews commented on JENKINS-52969 Re: java.lang.InterruptedException: sleep interrupted No, it is definitely anchore that is failing. The other parallel sections will have a message like this. Sending interrupt signal to process sh: line 1: 25850 Terminated Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52991) withDockerRegistry([...]) fails with "Email: EOF" on older docker versions
Title: Message Title
Matt Evans updated an issue
Jenkins / JENKINS-52991
withDockerRegistry([...]) fails with "Email: EOF" on older docker versions
Change By:
Matt Evans
Recently upgraded from Jenkins 1.x to 2.x and now I'm receiving errors during the pipeline{code:java}[Pipeline] withDockerRegistry $ docker login -u anonymous -p https://registry:5000 Email: EOF{code}I'm using an old version of docker {{1.10}} that still requires the email option when using {{docker login}}. I was using version {{1.12}} of the [ Docker Pipeline Plugin|[ https://wiki.jenkins.io/display/JENKINS/Docker+Pipeline+Plugin] ] and now I'm on the most recent \ {{1.17}}
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52991) withDockerRegistry([...]) fails with "Email: EOF" on older docker versions
Title: Message Title
Matt Evans updated an issue
Jenkins / JENKINS-52991
withDockerRegistry([...]) fails with "Email: EOF" on older docker versions
Change By:
Matt Evans
Recently upgraded from Jenkins 1.x to 2.x and now I'm receiving errors during the pipeline{code:java}[Pipeline] withDockerRegistry $ docker login -u anonymous -p https://registry:5000 Email: EOF{code}I'm using an old version of docker {{1.10}} that still requires the email option when using {{docker login}}. I was using version ` {{ 1.12 ` }} of the [Docker Pipeline Plugin ]( |[ https://wiki.jenkins.io/display/JENKINS/Docker+Pipeline+Plugin ) ]] and now I'm on the most recent ` \{{ 1.17 ` }}
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52991) withDockerRegistry([...]) fails with "Email: EOF" on older docker versions
Title: Message Title Matt Evans created an issue Jenkins / JENKINS-52991 withDockerRegistry([...]) fails with "Email: EOF" on older docker versions Issue Type: Bug Assignee: Unassigned Components: docker-workflow-plugin Created: 2018-08-10 20:13 Labels: regression Priority: Blocker Reporter: Matt Evans Recently upgraded from Jenkins 1.x to 2.x and now I'm receiving errors during the pipeline [Pipeline] withDockerRegistry $ docker login -u anonymous -p https://registry:5000 Email: EOF I'm using an old version of docker 1.10 that still requires the email option when using docker login. I was using version `1.12` of the [Docker Pipeline Plugin](https://wiki.jenkins.io/display/JENKINS/Docker+Pipeline+Plugin) and now I'm on the most recent `1.17`
[JIRA] (JENKINS-52969) java.lang.InterruptedException: sleep interrupted
Title: Message Title Swathi Gangisetty commented on JENKINS-52969 Re: java.lang.InterruptedException: sleep interrupted I think failFast aborts all parallel stages when one of them reports a failure. Is there any chance a different stage has failed for some reason and caused the in-progress anchore-verification stage to abort? Console log for the pipeline build (not the anchore plugin) will probably contain more information about stage interrupts and the extraneous cause if any. Look for something like "Sending interrupt signal to process" and the logs around that. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34222) Zephyr for JIRA hangs while recording results, and throws NPE while stopping the hanged job
Title: Message Title Vinod Kumar commented on JENKINS-34222 Re: Zephyr for JIRA hangs while recording results, and throws NPE while stopping the hanged job I have same issue and it stuck at below message. Recording test results [ZapiTestResultReporter] [INFO] Examining test results... Build result is SUCCESS JIRA v7.2.7 Zephyr for JIRA 3.6.4 ZAPI for JIRA 2.6.0 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51852) Since 0.10 the glob matching broken/incompatible
Title: Message Title Alex Earl commented on JENKINS-51852 Re: Since 0.10 the glob matching broken/incompatible When I try and do that I just get errors like this: master53668|SEVERE: Failed to install Publish Over CIFS master53668|java.io.IOException: Downloaded file /home/ath-user/ath-sources/target/jenkins3939363797066647269home/plugins/publish-over-cifs.jpi.tmp does not match expected SHA-256, expected 'nBOpBcYoY/KfajQw8AQ2XTL3BYPw5xA2onk+w05WFR0=', actual '40fakNRWazpJHrwg3eaW44QFqCMVFhNmV1pJL9SqSYM=' I've tried with running an "mvn install" so that the snapshot is in .m2 and using VERSION_OVERRIDES as well as with LOCAL_JARS. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46136) Nexus Platform plugin fail to connect to the Nexus 3 repository Server
Title: Message Title Justin Young updated JENKINS-46136 Released in 3.2.20180724-142843.2f5144d Jenkins / JENKINS-46136 Nexus Platform plugin fail to connect to the Nexus 3 repository Server Change By: Justin Young Status: In Review Resolved Resolution: Fixed Released As: https://plugins.jenkins.io/nexus-jenkins-plugin#3.2.20180724-142843.2f5144d Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46136) Nexus Platform plugin fail to connect to the Nexus 3 repository Server
Title: Message Title Justin Young started work on JENKINS-46136 Change By: Justin Young Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46136) Nexus Platform plugin fail to connect to the Nexus 3 repository Server
Title: Message Title Justin Young updated JENKINS-46136 Jenkins / JENKINS-46136 Nexus Platform plugin fail to connect to the Nexus 3 repository Server Change By: Justin Young Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46136) Nexus Platform plugin fail to connect to the Nexus 3 repository Server
Title: Message Title Justin Young commented on JENKINS-46136 Re: Nexus Platform plugin fail to connect to the Nexus 3 repository Server Nexus Platform Plugin 3.2.20180724-142843.2f5144d adds support of Nexus Repository Manager 3.13.0-01 servers for Maven component uploads, and new staging features (for Pro versions): tags, move, and delete. See more on the Wiki: https://plugins.jenkins.io/nexus-jenkins-plugin Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52990) Allow setting priority per category
Title: Message Title Simon Richter created an issue Jenkins / JENKINS-52990 Allow setting priority per category Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-plugin Created: 2018-08-10 17:25 Priority: Minor Reporter: Simon Richter It would be nice if there was a way to alter the priority for a warning by category. I'd like to treat certain warnings as high priority (e.g. "tautological const_cast") because they are indicative of problems with the codebase and have no false positives, while others (e.g. "suggest using a smart pointer here") I'd like to treat as low priority. Add Comment
[JIRA] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title Craig Rodrigues commented on JENKINS-33412 Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors @olamy do you know if your change https://github.com/jenkinsci/winstone/pull/44 has impacts on this ticket? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51852) Since 0.10 the glob matching broken/incompatible
Title: Message Title Oliver Gondža commented on JENKINS-51852 Re: Since 0.10 the glob matching broken/incompatible Alex Earl, the ATH? sure: https://github.com/jenkinsci/acceptance-test-harness/blob/master/docs/SUT-VERSIONS.md#use-custom-plugin-file Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51852) Since 0.10 the glob matching broken/incompatible
Title: Message Title Alex Earl commented on JENKINS-51852 Re: Since 0.10 the glob matching broken/incompatible Is there a way to run with a non-released version of the plugin? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52989) Test LDAP Setting throws Exceptions
Title: Message Title
yongyuth visestamkul created an issue
Jenkins / JENKINS-52989
Test LDAP Setting throws Exceptions
Issue Type:
Bug
Assignee:
Unassigned
Components:
ldap-plugin
Created:
2018-08-10 16:20
Environment:
PROD
Priority:
Major
Reporter:
yongyuth visestamkul
Hello, I'm using Jenkins Version Jenkins ver. 2.135. The LDAP configuration is: User search base: DC=internal,DC=vodafone,DC=com User search filter: mail={0} When trying to do "Test LDAP Setting" in the Global Security Configuration, I'm getting this exception: Stack-Trace org.springframework.dao.IncorrectResultSizeDataAccessException: Incorrect result size: expected 1, actual 2 at org.acegisecurity.ldap.LdapTemplate$3.doInDirContext(LdapTemplate.java:259) at org.acegisecurity.ldap.LdapTemplate.execute(LdapTemplate.java:126) at org.acegisecurity.ldap.LdapTemplate.searchForSingleEntry(LdapTemplate.java:246) at org.acegisecurity.ldap.search.FilterBasedLdapUserSearch.searchForUser(FilterBasedLdapUserSearch.java:119) at hudson.security.LDAPSecurityRealm$LDAPUserDetailsService.loadUserByUsername(LDAPSecurityRealm.java:1314) at hudson.security.LDAPSecurityRealm$LDAPUserDetailsService.loadUserByUsername(LDAPSecurityRealm.java:1251) at hudson.security.LDAPSecurityRealm$DescriptorImpl.validate(LDAPSecurityRealm.java:1725) at hudson.security.LDAPSecurityRealm$DescriptorImpl.doValidate(LDAPSecurityRealm.java:1595) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at
[JIRA] (JENKINS-52983) Missing root URL in the generated link to build while using groovy-html.template
Title: Message Title
Hari Dara commented on JENKINS-52983
Re: Missing root URL in the generated link to build while using groovy-html.template
By comparing the config with another Jenkins instance where this is working, I noticed that the jenkins.model.JenkinsLocationConfiguration.xml file is missing on this environment. When I used the below code, the file got created:
import jenkins.model.JenkinsLocationConfiguration
config = JenkinsLocationConfiguration.get();
config.setUrl("***")
config.setAdminAddress("***");
config.save()
May be this gets created only when the corresponding field(s) in /configure are updated, but I didn't know that and the fact that correct URL gets shown on that page made me think that it is all good. Actually, this environment got fully created via Ansible scripts, which modify specific parts of the configuration using Groovy scripts, so Save button on the /configure page was never hit, which may be why the location config never got created, and if this is the expected behavior, I will have to add the above to the existing Groovy scripts. I can now confirm that the emails have the right links, so this issue can be closed.
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52969) java.lang.InterruptedException: sleep interrupted
Title: Message Title
Ben Mathews commented on JENKINS-52969
Re: java.lang.InterruptedException: sleep interrupted
Most of the time the scan works. I'd hesitate to give a percentage, but say 90-95% of the time it works. The plugin is called from a Jenkinsfile that looks like this. Lots of stuff cut out, but hopefully this is the pertinant parts.
#!groovy
timestamps { stage('build images')
Unknown macro: { //build stuff }
stage('unit tests, rpm building, check for upgrades') { builders = [:] builders['unit-tests'] =
Unknown macro: { node(vivdocker.build_node()) Unknown macro}
}
builders['rpms'] =
Unknown macro: { node(vivdocker.build_node()) Unknown macro}
}
builders['upgrades'] =
Unknown macro: { node(vivdocker.build_node()) Unknown macro}
}
builders['anchore-verification'] = { node(vivdocker.build_node())
Unknown macro: { try Unknown macro}
catch (e) Unknown macro: { notifyBuildFailure() throw e } } }
builders['failFast'] = true
parallel builders } }
Add Comment
[JIRA] (JENKINS-51404) processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method"
Title: Message Title Alex Taylor commented on JENKINS-51404 Re: processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method" Cyrille Le Clerc Did you get the chance to look at this further? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52897) Service account token not used on slaves
Title: Message Title Carlos Sanchez resolved as Not A Defect Jenkins / JENKINS-52897 Service account token not used on slaves Change By: Carlos Sanchez Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52985) Job DSL multibranchPipelineJob branchSources does not have `svn`
Title: Message Title
James Femia updated an issue
Jenkins / JENKINS-52985
Job DSL multibranchPipelineJob branchSources does not have `svn`
Change By:
James Femia
When attempting to use a Scripted Pipeline to execute some Job DSL to create a Multibranch Pipeline, I am unable to specify my branch sources in SVN. The [documentation|https://jenkinsci.github.io/job-dsl-plugin/#path/multibranchPipelineJob-branchSources] and [source code|https://github.com/jenkinsci/job-dsl-plugin/blob/a10a66e3dcc4294deb5177acb7afa50f0b178c81/job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/workflow/BranchSourcesContext.groovy] indicate that this is simply not implemented. I would expect the following to work:{noformat}node {jobDsl failOnMissingPlugin: true, ignoreExisting: true, sandbox: true, scriptText: '''multibranchPipelineJob("test-generated") {branchSources {svn { location remoteBase ("http://svn/svn/test_repo/trunk") credentials credentialsId ("svn")}}}}'''} {noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop
[JIRA] (JENKINS-52985) Job DSL multibranchPipelineJob branchSources does not have `svn`
Title: Message Title James Femia commented on JENKINS-52985 Re: Job DSL multibranchPipelineJob branchSources does not have `svn` note: Submitted PR https://github.com/jenkinsci/job-dsl-plugin/pull/1139 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37589) Replay link does not show up if Jenkinsfile had a syntax error
Title: Message Title Enrique Canales commented on JENKINS-37589 Re: Replay link does not show up if Jenkinsfile had a syntax error I had tested this with workflow-cps 2.54 and workflow-job 2.21 and it looks like the Replay link shows up, but the ` Main Script` portion does not when there was a syntax error. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52711) JUnit Results Trend graph doesn't show all build results if builds have been deleted
Title: Message Title Greg Hester commented on JENKINS-52711 Re: JUnit Results Trend graph doesn't show all build results if builds have been deleted Thanks for input. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52986) Investigate on mac OSX for DOCKERHOST
Title: Message Title Pham Vu Tuan updated an issue Jenkins / JENKINS-52986 Investigate on mac OSX for DOCKERHOST Change By: Pham Vu Tuan We have SSL handshake problem on Devin's machine Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52908) Newlines get ignored in failure message and possibly stack trace when uploading xUnitDotNet xml results
Title: Message Title Edgars Batna commented on JENKINS-52908 Re: Newlines get ignored in failure message and possibly stack trace when uploading xUnitDotNet xml results Glad it's fixed so quickly. Though, test result formatting is not purely cosmetic. If you can't read them, you can't fix them. I'm not talking exception messages, but formatted tables with a thousand lines and over 10 columns. Thanks for looking into this in any case! Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52988) Release 1.1 version
Title: Message Title Pham Vu Tuan created an issue Jenkins / JENKINS-52988 Release 1.1 version Issue Type: Improvement Assignee: Pham Vu Tuan Components: remoting-kafka-plugin Created: 2018-08-10 15:06 Priority: Minor Reporter: Pham Vu Tuan Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52987) Update demo instruction to use the plugin without Kafka-enabled SSL
Title: Message Title Pham Vu Tuan created an issue Jenkins / JENKINS-52987 Update demo instruction to use the plugin without Kafka-enabled SSL Issue Type: Improvement Assignee: Pham Vu Tuan Components: remoting-kafka-plugin Created: 2018-08-10 14:52 Priority: Minor Reporter: Pham Vu Tuan Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52897) Service account token not used on slaves
Title: Message Title Markus Spanier commented on JENKINS-52897 Re: Service account token not used on slaves Hi Carlos, Thanks for pointing to that configuration. Providing the service account name (without the system:serviceaccount:: prefix) worked like a charm . Sorry that I missed it before. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51048) Setting workspace type to 'READONLY' doesn't work with servers running < 2017.1
Title: Message Title Paul Allen started work on JENKINS-51048 Change By: Paul Allen Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52986) Investigate on mac OSX for DOCKERHOST
Title: Message Title Pham Vu Tuan created an issue Jenkins / JENKINS-52986 Investigate on mac OSX for DOCKERHOST Issue Type: Improvement Assignee: Pham Vu Tuan Components: remoting-kafka-plugin Created: 2018-08-10 14:32 Priority: Minor Reporter: Pham Vu Tuan Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52852) Refactor ClientViewMappingGenerator
Title: Message Title Paul Allen closed an issue as Fixed Ready for release. Jenkins / JENKINS-52852 Refactor ClientViewMappingGenerator Change By: Paul Allen Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52941) Simple Pull Request Builder plugin needs to be updated to the new JCasC release candidate
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-52941 Simple Pull Request Builder plugin needs to be updated to the new JCasC release candidate Change By: Oleg Nenashev Summary: Simple Pull Request Builder plugin needs to be updated to the new JCasC alpha release candidate Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52941) Simple Pull Request Builder plugin needs to be updated to the new JCasC release candidate
Title: Message Title Oleg Nenashev commented on JENKINS-52941 Re: Simple Pull Request Builder plugin needs to be updated to the new JCasC release candidate Now it is Release Candidate Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52957) Workspace not cleaned up when using skipDefaultCheckout option
Title: Message Title Andrew Bayer updated JENKINS-52957 Jenkins / JENKINS-52957 Workspace not cleaned up when using skipDefaultCheckout option Change By: Andrew Bayer Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52957) Workspace not cleaned up when using skipDefaultCheckout option
Title: Message Title Andrew Bayer commented on JENKINS-52957 Re: Workspace not cleaned up when using skipDefaultCheckout option skipDefaultCheckout() just skips the checkout - it doesn't do anything to the workspace. In general, there's no guarantee that a workspace will or will not be reused from a previous build. If you need to ensure a clean workspace at the beginning of your build or stage, I'd recommend using the deleteDir() step as the first step in your stage. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52935) Git LFS failing clone
Title: Message Title Mark Waite edited a comment on JENKINS-52935 Re: Git LFS failing clone The https based failure to clone from github.com likely indicates that your company has a proxy configured and the proxy configuration was not used for the git clone command. A timeout trying to reach port 443 on the public internet most often means that the command line git program is unable to connect to the https port of the remote server and some network infrastructure (proxy, etc.) is intentionally blocking that connection.The ssh based failure might indicate that you didn't configure the job to use an ssh credential, or the ssh credential you configured is not registered with github.com, or the same network configuration that is blocking access to https on the public internet is also blocking ssh access to the public internet.The Jenkins git plugin supports two forms of credentials:# username/password for https and http connections# private key for ssh connections (g...@example.com:dir/repo.git and ssh://example.com/dir/repo.git)I assume when you say that you're required to use a token, that you mean you are using a private key. At least that is the format of the URL that is mentioned in the logs. If you're not using a private key and are instead using a GitHub deploy key or some other form of key, then the ssh-based URL like g...@example.com:organization/repo.git is not what you want.I believe that I've used GitHub keys in the username/password case by creating a credential with MarkEWaite as the username and the deploy key as the password. You might try the same thing. Using the git plugin with a typical secured git server without using credentials is quite difficult. It requires that every agent be configured to login to the secured git server by default. It is possible to do that, but it tends to make the management of Jenkins agents much more difficult. I assumed you are using Jenkins credentials rather than attempting to configure each agent so that it can login to the secured git server without credentials. Are you using Jenkins credentials? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
[JIRA] (JENKINS-52966) Two sequential stages in a parallel stage in a declarative pipeline making use of the same agent can cause a StackOverflowError
Title: Message Title
Andrew Bayer commented on JENKINS-52966
Re: Two sequential stages in a parallel stage in a declarative pipeline making use of the same agent can cause a StackOverflowError
Oh, and does it always fail at the same point, i.e., right after [Pipeline] [p1] { (p1s2)?
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52966) Two sequential stages in a parallel stage in a declarative pipeline making use of the same agent can cause a StackOverflowError
Title: Message Title Andrew Bayer commented on JENKINS-52966 Re: Two sequential stages in a parallel stage in a declarative pipeline making use of the same agent can cause a StackOverflowError Huh - does this happen consistently? I can't get it to reproduce so far. The underlying issue is, obviously, something in the serialization that gets self-referential. My rough guess is that the second error is a side effect of the stack overflow, but I can't be sure. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52985) Job DSL multibranchPipelineJob branchSources does not have `svn`
Title: Message Title
James Femia created an issue
Jenkins / JENKINS-52985
Job DSL multibranchPipelineJob branchSources does not have `svn`
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
2018-08-10 13:48
Environment:
Jenkins LTS 2.121.2 Docker container Job DSL Plugin 1.70
Priority:
Minor
Reporter:
James Femia
When attempting to use a Scripted Pipeline to execute some Job DSL to create a Multibranch Pipeline, I am unable to specify my branch sources in SVN. The documentation and source code indicate that this is simply not implemented. I would expect the following to work:
node {
jobDsl failOnMissingPlugin: true,
ignoreExisting: true,
sandbox: true,
scriptText: '''multibranchPipelineJob("test-generated") {
branchSources {
svn {
location("http://svn/svn/test_repo/trunk")
credentials("svn")
}
}
}
}'''
}
[JIRA] (JENKINS-52966) Two sequential stages in a parallel stage in a declarative pipeline making use of the same agent can cause a StackOverflowError
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-52966 Two sequential stages in a parallel stage in a declarative pipeline making use of the same agent can cause a StackOverflowError Change By: Andrew Bayer Component/s: pipeline-model-definition-plugin Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title Thomas Werner updated an issue Jenkins / JENKINS-33412 Jenkins locks when started in HTTPS mode on a host with 37+ processors Change By: Thomas Werner Priority: Major Blocker Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52983) Missing root URL in the generated link to build while using groovy-html.template
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-52983 Missing root URL in the generated link to build while using groovy-html.template Change By: Andrew Bayer Component/s: email-ext-plugin Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52908) Newlines get ignored in failure message and possibly stack trace when uploading xUnitDotNet xml results
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-52908 Newlines get ignored in failure message and possibly stack trace when uploading xUnitDotNet xml results Change By: Nikolas Falco Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52908) Newlines get ignored in failure message and possibly stack trace when uploading xUnitDotNet xml results
Title: Message Title Nikolas Falco resolved as Fixed Down to minor because it's cospetic and does not prevent functionality of the build Jenkins / JENKINS-52908 Newlines get ignored in failure message and possibly stack trace when uploading xUnitDotNet xml results Change By: Nikolas Falco Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52974) Refusing to marshal java.io.PrintStream for security reasons; exception while disabling the project
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-52974 Refusing to marshal java.io.PrintStream for security reasons; exception while disabling the project Change By: Oleg Nenashev Summary: Refusing to marshal java.io.PrintStream for security reasons; wxception exception while disabling the project Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52980) Scripted pipeline aborts for unknown reasons
Title: Message Title Markus Uckelmann closed an issue as Not A Defect Customer mixed declarative and scripted pipeline syntax. Jenkins / JENKINS-52980 Scripted pipeline aborts for unknown reasons Change By: Markus Uckelmann Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52980) Scripted pipeline aborts for unknown reasons
Title: Message Title Markus Uckelmann commented on JENKINS-52980 Re: Scripted pipeline aborts for unknown reasons Closed. My stupidity. Removed the "declarative" pipeline block and it worked. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52983) Missing root URL in the generated link to build while using groovy-html.template
Title: Message Title Hari Dara commented on JENKINS-52983 Re: Missing root URL in the generated link to build while using groovy-html.template To answer my own question on the difference in context, in the case when Jenkins.getRootUrl() works (i.e., from Script Console), though location config returns null, the URL is being extracted from the http request. In case of job execution, there is no such request, so it returns null. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48930) Add new way to publish shared libraries
Title: Message Title Fabrice Pipart commented on JENKINS-48930 Re: Add new way to publish shared libraries We started working on the implementation of this plugin internally. We'll see later how to make it open source. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52983) Missing root URL in the generated link to build while using groovy-html.template
Title: Message Title
Hari Dara commented on JENKINS-52983
Re: Missing root URL in the generated link to build while using groovy-html.template
The url gets computed from here:
public @Nullable String getRootUrl() throws IllegalStateException {
final JenkinsLocationConfiguration config = JenkinsLocationConfiguration.get();
if (config == null) {
// Try to get standard message if possible
final Jenkins j = Jenkins.getInstance();
throw new IllegalStateException("Jenkins instance " + j + " has been successfully initialized, but JenkinsLocationConfiguration is undefined.");
}
String url = ""
if(url!=null) {
return Util.ensureEndsWith(url,"/");
}
StaplerRequest req = Stapler.getCurrentRequest();
if(req!=null)
return getRootUrlFromRequest();
return null;
}
I tried running the below code in Script Console and got null:
import jenkins.model.JenkinsLocationConfiguration
config = JenkinsLocationConfiguration.get();
print(config.getUrl())
However, I do have Jenkins URL configured under Jenkins Location. Why is this coming back as null ?
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it,
[JIRA] (JENKINS-52983) Missing root URL in the generated link to build while using groovy-html.template
Title: Message Title David van Laatum updated an issue Jenkins / JENKINS-52983 Missing root URL in the generated link to build while using groovy-html.template Change By: David van Laatum Component/s: pipeline Component/s: email-ext-plugin Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52983) Missing root URL in the generated link to build while using groovy-html.template
Title: Message Title David van Laatum assigned an issue to Unassigned Jenkins / JENKINS-52983 Missing root URL in the generated link to build while using groovy-html.template Change By: David van Laatum Assignee: David van Laatum Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52984) Hide/Show Installed Plugins That Can't Be Disabled
Title: Message Title K S created an issue Jenkins / JENKINS-52984 Hide/Show Installed Plugins That Can't Be Disabled Issue Type: New Feature Assignee: Unassigned Components: core Created: 2018-08-10 12:46 Labels: jenkins user-experience Priority: Minor Reporter: K S Being able to hide/show plugins that cannot be disabled would declutter the already long list of installed plugins. Add Comment
[JIRA] (JENKINS-52935) Git LFS failing clone
Title: Message Title Mark Waite commented on JENKINS-52935 Re: Git LFS failing clone The https based failure to clone from github.com likely indicates that your company has a proxy configured and the proxy configuration was not used for the git clone command. A timeout trying to reach port 443 on the public internet most often means that the command line git program is unable to connect to the https port of the remote server and some network infrastructure (proxy, etc.) is intentionally blocking that connection. The ssh based failure might indicate that you didn't configure the job to use an ssh credential, or the ssh credential you configured is not registered with github.com, or the same network configuration that is blocking access to https on the public internet is also blocking ssh access to the public internet. The Jenkins git plugin supports two forms of credentials: username/password for https and http connections private key for ssh connections (g...@example.com:dir/repo.git and ssh://example.com/dir/repo.git) I believe that I've used GitHub keys in the username/password case by creating a credential with MarkEWaite as the username and the deploy key as the password. You might try the same thing. Using the git plugin with a typical secured git server without using credentials is quite difficult. It requires that every agent be configured to login to the secured git server by default. It is possible to do that, but it tends to make the management of Jenkins agents much more difficult. I assumed you are using Jenkins credentials rather than attempting to configure each agent so that it can login to the secured git server without credentials. Are you using Jenkins credentials? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You
[JIRA] (JENKINS-52983) Missing root URL in the generated link to build while using groovy-html.template
Title: Message Title
Hari Dara commented on JENKINS-52983
Re: Missing root URL in the generated link to build while using groovy-html.template
Using the below pipeline script (I had to disable Groovy Sandbox), I am seeing null values for url:
import hudson.plugins.emailext.ExtendedEmailPublisherDescriptor;pipeline {
agent any
stages {
stage("Init") {
steps {
sh "exit 1"
}
}
}
post {
failure {
script {
def descriptor = Jenkins.getActiveInstance().getDescriptorByType(ExtendedEmailPublisherDescriptor.class)
echo "getHudsonUrl: ${descriptor.getHudsonUrl()}"
echo "getRootUrl: ${Jenkins.getActiveInstance().getRootUrl()}"
}
}
}
}
Here is the console output:
Started by user Hari Krishna Dara
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] node
...
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Declarative: Post Actions)
[Pipeline] script
[Pipeline] {
[Pipeline] echo
getHudsonUrl: null
[Pipeline] echo
getRootUrl: null
[Pipeline] }
[Pipeline] // script
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
ERROR: script returned exit code 1
Finished: FAILURE
What could be different about this context? Now it appears to be even unrelated to email-ext plugin.
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
[JIRA] (JENKINS-52983) Missing root URL in the generated link to build while using groovy-html.template
Title: Message Title
Hari Dara commented on JENKINS-52983
Re: Missing root URL in the generated link to build while using groovy-html.template
Adding to the puzzle, tried the below script in Script Console and it gave the right URL:
import hudson.plugins.emailext.ExtendedEmailPublisherDescriptor
descriptor = Jenkins.getActiveInstance().getDescriptorByType(ExtendedEmailPublisherDescriptor.class)
print("getHudsonUrl: ${descriptor.getHudsonUrl()}")
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52983) Missing root URL in the generated link to build while using groovy-html.template
Title: Message Title
Hari Dara commented on JENKINS-52983
Re: Missing root URL in the generated link to build while using groovy-html.template
One may use this simple pipeline script to reproduce the issue:
pipeline {
agent any
stages {
stage("Init") {
steps {
sh "exit 1"
}
}
}
post {
failure {
emailext subject: "Pipeline failed: ${currentBuild.fullDisplayName}",
body: '''${SCRIPT, template="groovy-html.template"}''',
mimeType: 'text/html',
recipientProviders: [requestor()],
replyTo: 'nore...@salesforce.com'
}
}
}
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52983) Missing root URL in the generated link to build while using groovy-html.template
Title: Message Title
Hari Dara created an issue
Jenkins / JENKINS-52983
Missing root URL in the generated link to build while using groovy-html.template
Issue Type:
Bug
Assignee:
David van Laatum
Components:
email-ext-plugin
Created:
2018-08-10 12:20
Environment:
Jenkins ver. 2.73.3 Email-ext vers. 2.62
Priority:
Major
Reporter:
Hari Dara
I am using the groovy-html.template which generates a link to the build and it is coming up as something like: nulljob/test/2 where test is the name of the job and 2 is the build number. The nulljob part is coming from the concatenation of null root URL and the job URL as can be seen from here:
${rooturl}${build.url}
The rooturl property is coming from ExtendedEmailPublisherDescriptor.java.getHudsonUrl() as seen here
binding.put("rooturl", descriptor.getHudsonUrl());
This method internally just calls Jenkins.getActiveInstance().getRootUrl() as seen here:
public String getHudsonUrl() {
return
[JIRA] (JENKINS-51436) Hardcoded id's for Html-Components within loops
Title: Message Title Ulli Hafner updated JENKINS-51436 Jenkins / JENKINS-51436 Hardcoded id's for Html-Components within loops Change By: Ulli Hafner Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50867) SAX2 driver class org.apache.xerces.parsers.SAXParser not found
Title: Message Title
Amir Barkal edited a comment on JENKINS-50867
Re: SAX2 driver class org.apache.xerces.parsers.SAXParser not found
Suffering from the same issue with s3FindFiles pipeline step. After an plugin upgrade (email-ext) + Jenkins restart, problem solved.Why update email-ext? Because it depends on "analysis-core-plugin" which was found to be using the org.xml.sax.driver, so I though I'd give it a refresh. I have a feeling that just a Jenkins restart is enough. By anyway this is not acceptable and very non-deterministic behavior. {code :java }java.lang.ClassNotFoundException: org.apache.xerces.parsers.SAXParser at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:565) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at org.xml.sax.helpers.NewInstance.newInstance(NewInstance.java:82) at org.xml.sax.helpers.XMLReaderFactory.loadClass(XMLReaderFactory.java:228)Caused: org.xml.sax.SAXException: SAX2 driver class org.apache.xerces.parsers.SAXParser not foundjava.lang.ClassNotFoundException: org.apache.xerces.parsers.SAXParser at org.xml.sax.helpers.XMLReaderFactory.loadClass(XMLReaderFactory.java:230) at org.xml.sax.helpers.XMLReaderFactory.createXMLReader(XMLReaderFactory.java:191) at com.amazonaws.services.s3.model.transform.XmlResponsesSaxParser.(XmlResponsesSaxParser.java:115)Caused: com.amazonaws.SdkClientException: Couldn't initialize a SAX driver to create an XMLReader at com.amazonaws.services.s3.model.transform.XmlResponsesSaxParser.(XmlResponsesSaxParser.java:118) at com.amazonaws.services.s3.model.transform.Unmarshallers$ListObjectsUnmarshaller.unmarshall(Unmarshallers.java:69) at com.amazonaws.services.s3.model.transform.Unmarshallers$ListObjectsUnmarshaller.unmarshall(Unmarshallers.java:59) at com.amazonaws.services.s3.internal.S3XmlResponseHandler.handle(S3XmlResponseHandler.java:62) at com.amazonaws.services.s3.internal.S3XmlResponseHandler.handle(S3XmlResponseHandler.java:31) at com.amazonaws.http.response.AwsResponseHandlerAdapter.handle(AwsResponseHandlerAdapter.java:70) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleResponse(AmazonHttpClient.java:1554) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1272) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1056) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:743) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:717) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:699) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:667) at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:649) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:513) at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:4325) at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:4272) at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:4266) at com.amazonaws.services.s3.AmazonS3Client.listObjects(AmazonS3Client.java:834) at de.taimos.pipeline.aws.S3FindFilesStep$Execution.run(S3FindFilesStep.java:216) at de.taimos.pipeline.aws.S3FindFilesStep$Execution.run(S3FindFilesStep.java:148) at
[JIRA] (JENKINS-50867) SAX2 driver class org.apache.xerces.parsers.SAXParser not found
Title: Message Title
Amir Barkal edited a comment on JENKINS-50867
Re: SAX2 driver class org.apache.xerces.parsers.SAXParser not found
Suffering from the same issue with s3FindFiles pipeline step.After an plugin upgrade (email-ext) + Jenkins restart, problem solved.Why update email-ext? Because it depends on "analysis-core-plugin" which was found to be using the org.xml.sax.driver, so I though I'd give it a refresh. I have a feeling that just a Jenkins restart is enough. By anyway In any case this is not acceptable and very non-deterministic behavior. {code:java}java.lang.ClassNotFoundException: org.apache.xerces.parsers.SAXParser at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:565) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at org.xml.sax.helpers.NewInstance.newInstance(NewInstance.java:82) at org.xml.sax.helpers.XMLReaderFactory.loadClass(XMLReaderFactory.java:228)Caused: org.xml.sax.SAXException: SAX2 driver class org.apache.xerces.parsers.SAXParser not foundjava.lang.ClassNotFoundException: org.apache.xerces.parsers.SAXParser at org.xml.sax.helpers.XMLReaderFactory.loadClass(XMLReaderFactory.java:230) at org.xml.sax.helpers.XMLReaderFactory.createXMLReader(XMLReaderFactory.java:191) at com.amazonaws.services.s3.model.transform.XmlResponsesSaxParser.(XmlResponsesSaxParser.java:115)Caused: com.amazonaws.SdkClientException: Couldn't initialize a SAX driver to create an XMLReader at com.amazonaws.services.s3.model.transform.XmlResponsesSaxParser.(XmlResponsesSaxParser.java:118) at com.amazonaws.services.s3.model.transform.Unmarshallers$ListObjectsUnmarshaller.unmarshall(Unmarshallers.java:69) at com.amazonaws.services.s3.model.transform.Unmarshallers$ListObjectsUnmarshaller.unmarshall(Unmarshallers.java:59) at com.amazonaws.services.s3.internal.S3XmlResponseHandler.handle(S3XmlResponseHandler.java:62) at com.amazonaws.services.s3.internal.S3XmlResponseHandler.handle(S3XmlResponseHandler.java:31) at com.amazonaws.http.response.AwsResponseHandlerAdapter.handle(AwsResponseHandlerAdapter.java:70) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleResponse(AmazonHttpClient.java:1554) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1272) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1056) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:743) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:717) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:699) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:667) at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:649) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:513) at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:4325) at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:4272) at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:4266) at com.amazonaws.services.s3.AmazonS3Client.listObjects(AmazonS3Client.java:834) at de.taimos.pipeline.aws.S3FindFilesStep$Execution.run(S3FindFilesStep.java:216) at de.taimos.pipeline.aws.S3FindFilesStep$Execution.run(S3FindFilesStep.java:148) at
[JIRA] (JENKINS-52982) Improve parsing performance
Title: Message Title Share Cheng created an issue Jenkins / JENKINS-52982 Improve parsing performance Issue Type: Improvement Assignee: Share Cheng Components: code-coverage-api-plugin Created: 2018-08-10 12:08 Priority: Minor Reporter: Share Cheng Change XML parsing method to SAX and JSON parsing method to Stream Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
[JIRA] (JENKINS-51443) Wrong mount point spec for Windows Containers in Docker
Title: Message Title Besik Tsitelashvili commented on JENKINS-51443 Re: Wrong mount point spec for Windows Containers in Docker ,z and -u as well, does not supported... Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52962) Tests failing with the new Login page introduced in 2.128
Title: Message Title Romain Verduci updated JENKINS-52962 Jenkins / JENKINS-52962 Tests failing with the new Login page introduced in 2.128 Change By: Romain Verduci Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52981) Pipeline: success after checkout error
Title: Message Title
Christoph Vogtländer updated an issue
Jenkins / JENKINS-52981
Pipeline: success after checkout error
Change By:
Christoph Vogtländer
When trying to checkout from a non existing location there the pipeline script simply resumes operation without setting the build result to FAILURE.My checkout step: {code:java}checkout changelog: false, poll: false, scm: [$class: 'SubversionSCM', additionalCredentials: [[credentialsId: 'id', realm: ' VisualSVN Server']], excludedCommitMessages: '', excludedRegions: '', excludedRevprop: '', excludedUsers: '', filterChangelog: false, ignoreDirPropChanges: false, includedRegions: '', locations: [[cancelProcessOnExternalsFail: true, credentialsId: 'id', depthOption: 'infinity', ignoreExternalsOption: false, local: nonexisting, remote: https://server/path/nonexisting]], workspaceUpdater: [$class: 'UpdateWithRevertUpdater']]{code}Running the code will result in: {code:java}[Pipeline] [Checkout nonexisting] checkout[Checkout nonexisting] Location 'https://server/path/nonexisting' does not exist[Checkout nonexisting] ERROR: Failed to parse svn info forhttps://server/path/nonexisting[Checkout nonexisting] org.tmatesoft.svn.core.SVNException: svn: E155007: '/var/jenkins/workspace/System/trunk/Test/nonexisting' is not a working copy[Checkout nonexisting] at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:70)[Checkout nonexisting] at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:57)[Checkout nonexisting] at org.tmatesoft.svn.core.internal.wc17.db.SVNWCDb.parseDir(SVNWCDb.java:1955)[Checkout nonexisting] at org.tmatesoft.svn.core.internal.wc17.db.SVNWCDb.parseDir(SVNWCDb.java:1846)[Checkout nonexisting] at org.tmatesoft.svn.core.internal.wc17.db.SVNWCDb.readConflicts(SVNWCDb.java:3382)[Checkout nonexisting] at org.tmatesoft.svn.core.internal.wc17.db.SVNWCDb.readConflicts(SVNWCDb.java:3355)[Checkout nonexisting] at org.tmatesoft.svn.core.internal.wc17.db.SVNWCDb.opReadTreeConflict(SVNWCDb.java:2797)[Checkout nonexisting] at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgGetInfo.run(SvnNgGetInfo.java:74)[Checkout nonexisting] at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgGetInfo.run(SvnNgGetInfo.java:45)[Checkout nonexisting] at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.run(SvnNgOperationRunner.java:20)[Checkout nonexisting] at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21)[Checkout nonexisting] at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1239)[Checkout nonexisting] at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294)[Checkout nonexisting] at org.tmatesoft.svn.core.wc.SVNWCClient.doInfo(SVNWCClient.java:2497)[Checkout nonexisting] at hudson.scm.SubversionSCM$BuildRevisionMapTask.invoke(SubversionSCM.java:1325)[Checkout nonexisting] at hudson.scm.SubversionSCM$BuildRevisionMapTask.invoke(SubversionSCM.java:1289)[Checkout nonexisting] at
[JIRA] (JENKINS-52981) Pipeline: success after checkout error
Title: Message Title Christoph Vogtländer created an issue Jenkins / JENKINS-52981 Pipeline: success after checkout error Issue Type: Bug Assignee: Ivan Fernandez Calvo Components: pipeline, subversion-plugin Created: 2018-08-10 11:38 Environment: Jenkins ver. 2.121.2 Windows Server 2012 Priority: Minor Reporter: Christoph Vogtländer When trying to checkout from a non existing location there the pipeline script simply resumes operation without setting the build result to FAILURE. My checkout step: checkout changelog: false, poll: false, scm: [$class: 'SubversionSCM', additionalCredentials: [[credentialsId: 'id', realm: '//server:443> VisualSVN Server']], excludedCommitMessages: '', excludedRegions: '', excludedRevprop: '', excludedUsers: '', filterChangelog: false, ignoreDirPropChanges: false, includedRegions: '', locations: [[cancelProcessOnExternalsFail: true, credentialsId: 'id', depthOption: 'infinity', ignoreExternalsOption: false, local: nonexisting, remote: https://server/path/nonexisting]], workspaceUpdater: [$class: 'UpdateWithRevertUpdater']] Running the code will result in: [Pipeline] [Checkout nonexisting] checkout [Checkout nonexisting] Location 'https://server/path/nonexisting' does not exist [Checkout nonexisting] ERROR: Failed to parse svn info
[JIRA] (JENKINS-24224) improve xunit plugin with test-stability plugin
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-24224 improve xunit plugin with test-stability plugin Change By: Nikolas Falco Assignee: Gregory Boissinot Nikolas Falco Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24224) improve xunit plugin with test-stability plugin
Title: Message Title Nikolas Falco resolved as Duplicate Add support for TestDataPublisher Jenkins / JENKINS-24224 improve xunit plugin with test-stability plugin Change By: Nikolas Falco Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52980) Scripted pipeline aborts for unknown reasons
Title: Message Title
Markus Uckelmann created an issue
Jenkins / JENKINS-52980
Scripted pipeline aborts for unknown reasons
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
error, Jenkinsfile.issue
Components:
core
Created:
2018-08-10 11:08
Environment:
Jenkins 2.121.2
Priority:
Minor
Reporter:
Markus Uckelmann
Hello all, I'm trying to dynamically create parallel jobs. My code works as expected but the job still fails with:
hudson.remoting.ProxyException: org.codehaus.groovy.runtime.typehandling.GroovyCastException: Cannot cast object '{test-qucli=null, test-composer=null}' with class 'java.util.HashMap' to class 'org.jenkinsci.plugins.pipeline.modeldefinition.model.Root' due to: groovy.lang.GroovyRuntimeException: Could not find matching constructor for: org.jenkinsci.plugins.pipeline.modeldefinition.model.Root(java.util.HashMap)
The error does not appear when I comment out the last block ("Clean") in the runPipeline method. I'm quite certain that this isn't a bug. But I hit a wall and neither IRC nor mailing list responded. So, sorry about that. Also I'm not familiar with Groovy and the code looks accordingly. If I am at the wrong place, could you please point me somewhere where I might find help? Jenkinsfile and the complete error is attached.
[JIRA] (JENKINS-52979) User-specified changelog size limit
Title: Message Title Kim Randell created an issue Jenkins / JENKINS-52979 User-specified changelog size limit Issue Type: New Feature Assignee: Unassigned Components: mercurial-plugin Created: 2018-08-10 11:01 Priority: Minor Reporter: Kim Randell We have a similar problem to the one that celltestr reported in JENKINS-16654. However, we would prefer to retain changelogs when the builds are incremental, while disabling them when switching branch or building after a long gap. Therefore, it would be useful if we could specify a size limit on the changelog (for instance, maximum number of changesets). When the size limit is reached, the changelog would be truncated (perhaps with a summary noting the total original size). Add Comment
