[JIRA] (JENKINS-49894) Active Choices Reactive Reference Parameter triggering the groovy script twice
Title: Message Title Bruno P. Kinoshita commented on JENKINS-49894 Re: Active Choices Reactive Reference Parameter triggering the groovy script twice Have just spent some minutes debugging it, and I believe I now understand what's causing the issue. Can't fix it right now due to limited bandwidth to develop, but the below is a short explanation of the problem (and also a note to myself in the future, when working on this issue again). I only reproduced it on the first time the page is loaded. Debugging, it is possible to see the first call comes from Jelly tags being evaluated. And the second call comes from _javascript_ code. The issue appears to be that when we put the elements on the UI, we also intentionally call the update method on the server side, to get the right values. Then once everything is loaded, there is a JS call to refresh the elements' values. The ideal approach would be to have Jelly creating the elements, then using JS to start the execution. But that's not easy to implement without breaking other things. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49894) Active Choices Reactive Reference Parameter triggering the groovy script twice
Title: Message Title
Bruno P. Kinoshita updated an issue
Jenkins / JENKINS-49894
Active Choices Reactive Reference Parameter triggering the groovy script twice
Change By:
Bruno P. Kinoshita
I am trying to fetch a list of branches from git in the active choice reactive reference parameter.I am using the run *groovy script* option.But the script is ran twice when I check the tomcat logs.Because of which the drop down is rendered twice.Please find the below script{code: java groovy }def html= ''' Select... ''' def cmd = ["/bin/bash", "-c","sudo sh /home/centos/JenkinScripts/dynamicChoices/getBranchesFromGit.sh https://kgjenk...@bitbucket.org/vtakru/escloudadmin.git"] def sout = new StringBuffer() def serr = new StringBuffer() // Run the command println "running "+cmd def proc = cmd.execute() proc.consumeProcessOutput ( sout, serr ) proc.waitFor() def options="" sout.tokenize().each{ branch-> if(branch.contains("refs/heads/")){ branch=branch.minus("refs/heads/") println "Branch "+branch options+="$branch" } } html+=options return html{code} Please help me with this issue
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-49894) Active Choices Reactive Reference Parameter triggering the groovy script twice
Title: Message Title
Bruno P. Kinoshita updated an issue
Jenkins / JENKINS-49894
Active Choices Reactive Reference Parameter triggering the groovy script twice
Change By:
Bruno P. Kinoshita
I am trying to fetch a list of branches from git in the active choice reactive reference parameter.I am using the run *groovy script* option.But the script is ran twice when I check the tomcat logs.Because of which the drop down is rendered twice.Please find the below script html= {code:java} def html= '''Select... {code} ''' {code:java} def cmd = ["/bin/bash", "-c","sudo sh /home/centos/JenkinScripts/dynamicChoices/getBranchesFromGit.sh https://kgjenk...@bitbucket.org/vtakru/escloudadmin.git"] def sout = new StringBuffer() def serr = new StringBuffer() // Run the command println "running "+cmd def proc = cmd.execute() proc.consumeProcessOutput ( sout, serr ) proc.waitFor() def options="" sout.tokenize().each{ branch-> if(branch.contains("refs/heads/")){ branch=branch.minus("refs/heads/") println "Branch "+branch options+="$branch" } } html+=options return html {code} Please help me with this issue
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-49894) Active Choices Reactive Reference Parameter triggering the groovy script twice
Title: Message Title
Bruno P. Kinoshita updated an issue
Jenkins / JENKINS-49894
Active Choices Reactive Reference Parameter triggering the groovy script twice
Change By:
Bruno P. Kinoshita
I am trying to fetch a list of branches from git in the active choice reactive reference parameter.I am using the run *groovy script* option.But the script is ran twice when I check the tomcat logs.Because of which the drop down is rendered twice.Please find the below scripthtml= ''' {code:java} Select... {code} ''' {code:java} def cmd = ["/bin/bash", "-c","sudo sh /home/centos/JenkinScripts/dynamicChoices/getBranchesFromGit.sh https://kgjenk...@bitbucket.org/vtakru/escloudadmin.git"]def sout = new StringBuffer()def serr = new StringBuffer()// Run the commandprintln "running "+cmddef proc = cmd.execute()proc.consumeProcessOutput ( sout, serr )proc.waitFor() def options=""sout.tokenize().each \ { branch->if(branch.contains("refs/heads/")) \ {branch=branch.minus("refs/heads/")println "Branch "+branchoptions+="$branch"}}html+=optionsreturn html {code} Please help me with this issue
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-50366) I would like to add "--first-parent" to git log command
Title: Message Title Ben Sluis updated an issue Jenkins / JENKINS-50366 I would like to add "--first-parent" to git log command Change By: Ben Sluis Comment: I can see that the git-client-plugin has support for the --first-parent argument being passed to 'git rev-list', [https://github.com/jenkinsci/git-client-plugin/blob/master/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L2838|https://github.com/jenkinsci/git-client-plugin/blob/master/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L2838.]I've spent a little time trying to figure out if or how this is used by this repo, git-plugin, but I haven't succeeded. Can you share any pointers or places to look to understand this code and how the git-plugin uses the git-client-plugin to fetch change sets from Git? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50366) I would like to add "--first-parent" to git log command
Title: Message Title Ben Sluis updated an issue Jenkins / JENKINS-50366 I would like to add "--first-parent" to git log command Change By: Ben Sluis Comment: I found the place to add the changes, [https://github.com/jenkinsci/git-plugin/blob/master/src/main/java/hudson/plugins/git/GitSCM.java#L1285.] I think it also requires changes to the git-client-plugin at [https://github.com/jenkinsci/git-client-plugin/blob/master/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L1029] to add --first-parent arg.The challenge I have is testing out my local modification to git-client-plugin at the same time as a local modification to git-plugin. I'm trying to figure out how to get Maven to allow me to use the locally built (mvn package) git-client-plugin when doing 'mvn hpi:run' on the git-plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50366) I would like to add "--first-parent" to git log command
Title: Message Title Ben Sluis commented on JENKINS-50366 Re: I would like to add "--first-parent" to git log command I found the place to add the changes, https://github.com/jenkinsci/git-plugin/blob/master/src/main/java/hudson/plugins/git/GitSCM.java#L1285. I think it also requires changes to the git-client-plugin at https://github.com/jenkinsci/git-client-plugin/blob/master/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L1029 to add --first-parent arg. The challenge I have is testing out my local modification to git-client-plugin at the same time as a local modification to git-plugin. I'm trying to figure out how to get Maven to allow me to use the locally built (mvn package) git-client-plugin when doing 'mvn hpi:run' on the git-plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51094) Custom WAR Packager - Support building with LATEST versions from Incrementals repo
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-51094 Custom WAR Packager - Support building with LATEST versions from Incrementals repo Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55327) Job restrictions can be skipped if no node block in Jenkinsfile
Title: Message Title Oleg Nenashev commented on JENKINS-55327 Re: Job restrictions can be skipped if no node block in Jenkinsfile Actually this particular case is not related to JENKINS-46652, sorry for confusion. Likely the plugin's extension point impls are not longer being invoked for the Pipeline flyweight master. Anyway, execution of Pipeline root task should always happen on the master. It just won't be able to be really executed on any other machine due to the current Pipeline system design Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51109) Allow incremental releases in Stapler
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-51109 Allow incremental releases in Stapler Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54233) Pipeline Script textarea missing
Title: Message Title Kevin Wilson commented on JENKINS-54233 Re: Pipeline Script textarea missing Ok, that was strange. It worked only once after the change. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54233) Pipeline Script textarea missing
Title: Message Title
Kevin Wilson commented on JENKINS-54233
Re: Pipeline Script textarea missing
I was using AJP for my HTTPD-Tomcat connection. I switched to HTTP, and the script editor came back. Directories, IP addresses and port numbers were removed. The tip off was this error in my logs: 27-Dec-2018 14:19:35.166 WARNING [Handling GET /cloudbees/configure from xxx.xxx.xxx.xxx : ajp-apr-yyy.yyy.yyy.yyy--exec-1] hudson.init.impl.InstallUncaughtExceptionHandler.lambda$init$0 null {{ javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:.../tomcat8/webapps/cloudbees/WEB-INF/lib/jenkins-core-2.138.4-cb-2.jar!/lib/form/dropdownListBlock.jelly:51:59: java.io.IOException: Failed to send AJP message}} {{ at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:111)}} {{ at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739)}} {{ at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870)}} {{ at org.kohsuke.stapler.Stapler.invoke(Stapler.java:668)}} {{ at org.kohsuke.stapler.Stapler.service(Stapler.java:238)}} {{ at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)}}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55194) Excessive logging
Title: Message Title Vlad Uros commented on JENKINS-55194 Re: Excessive logging Thanks Naresh. If possible, please add as well option to hide server name before command output, for example: server-name|command_output Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55369) Background step that passed is displayed as undefined
Title: Message Title Damian Szczepanik updated JENKINS-55369 Jenkins / JENKINS-55369 Background step that passed is displayed as undefined Change By: Damian Szczepanik Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55369) Background step that passed is displayed as undefined
Title: Message Title Damian Szczepanik commented on JENKINS-55369 Re: Background step that passed is displayed as undefined Report this issue https://github.com/damianszczepanik/cucumber-reporting with the JSON file for the reference Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55369) Background step that passed is displayed as undefined
Title: Message Title Damian Szczepanik updated JENKINS-55369 Jenkins / JENKINS-55369 Background step that passed is displayed as undefined Change By: Damian Szczepanik Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55370) Exception during the Jenkins startup
Title: Message Title Naresh Rayapati commented on JENKINS-55370 Re: Exception during the Jenkins startup In fact we don't have a sequence, we have a single script called main.groovy which invokes other groovy scripts. jenkinshost.groovy is the one which sets the jenkins url Running initialisation script : jenkinshost.groovy` https://gist.github.com/nrayapati/15f9fe62adf2e3430e694b4c456c115d Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55370) Exception during the Jenkins startup
Title: Message Title Cyrille Le Clerc commented on JENKINS-55370 Re: Exception during the Jenkins startup I mean the logs of your initialisation sequence Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55370) Exception during the Jenkins startup
Title: Message Title Naresh Rayapati commented on JENKINS-55370 Re: Exception during the Jenkins startup Initialization is not failing, what I am saying we are using init script to set the Jenkins URL, but before that init script starts we are seeing the exception mentioned above. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55370) Exception during the Jenkins startup
Title: Message Title Naresh Rayapati edited a comment on JENKINS-55370 Re: Exception during the Jenkins startup Initialization is not failing, what I am was saying is we are using init script to set the Jenkins URL, but before that init script starts we are seeing the exception mentioned above. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55370) Exception during the Jenkins startup
Title: Message Title Cyrille Le Clerc commented on JENKINS-55370 Re: Exception during the Jenkins startup Can you gist the initialisation sequence? I don't catch what's specific in your use case that makes the initialisation fail Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55257) Timestamper break builds on Windows agents
Title: Message Title Mark Waite commented on JENKINS-55257 Re: Timestamper break builds on Windows agents I can't duplicate the problem as described on Windows 10. I'm surprised if it is truly specific to Windows Server 2016 and not visible on Windows 10. The repository where I've tried various permutations of the bug duplication instructions is the JENKINS-55257 branch of my jenkins-bugs repository. My Java versions are JDK 8 on agents and on master, with all the agents running at least 1.8.0 151. The master is running JDK 8 162 from my my docker image. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55372) ArgumentsActionImpl.sanitizeObjectAndRecordMutation can fail
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-55372 ArgumentsActionImpl.sanitizeObjectAndRecordMutation can fail Issue Type: Bug Assignee: Unassigned Components: workflow-cps-plugin Created: 2018-12-31 19:50 Labels: robustness Priority: Minor Reporter: Jesse Glick See JENKINS-55239 for an example and a proposed fix. For testing, I bet a @TestExtension public class X extends GlobalVariable creating, say, a databinding-unaware Builder you can pass as an arg to step would do the trick, in combination with LoggerRule.capture. Add Comment
[JIRA] (JENKINS-55239) FilesystemSCM is not annotated properly in JFR
Title: Message Title Jesse Glick commented on JENKINS-55239 Re: FilesystemSCM is not annotated properly in JFR Filed JENKINS-55372 for the more general issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55239) FilesystemSCM is not annotated properly in JFR
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-55239 FilesystemSCM is not annotated properly in JFR Change By: Jesse Glick Component/s: workflow-cps-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55370) Exception during the Jenkins startup
Title: Message Title Naresh Rayapati commented on JENKINS-55370 Re: Exception during the Jenkins startup Yes, we are using the same init.groovy.d file but still this exception thrown before the actual init script is initiated. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55370) Exception during the Jenkins startup
Title: Message Title Cyrille Le Clerc commented on JENKINS-55370 Re: Exception during the Jenkins startup You can use a Jenkins initialisation groovy script to set Jenkins.location.url Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55370) Exception during the Jenkins startup
Title: Message Title Naresh Rayapati edited a comment on JENKINS-55370 Re: Exception during the Jenkins startup We use startup script to do that job set the url , which happens after the jenkins is up. Thank you. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55370) Exception during the Jenkins startup
Title: Message Title Naresh Rayapati commented on JENKINS-55370 Re: Exception during the Jenkins startup We use startup script to do that job, which happens after the jenkins is up. Thank you. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55370) Exception during the Jenkins startup
Title: Message Title Cyrille Le Clerc assigned an issue to Cyrille Le Clerc Jenkins / JENKINS-55370 Exception during the Jenkins startup Change By: Cyrille Le Clerc Assignee: Alvaro Lobato Cyrille Le Clerc Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55370) Exception during the Jenkins startup
Title: Message Title Cyrille Le Clerc commented on JENKINS-55370 Re: Exception during the Jenkins startup Could you have not yet defined the URL of your Jenkins server in the "manage Jenkins" page? We will make the code more robust Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49894) Active Choices Reactive Reference Parameter triggering the groovy script twice
Title: Message Title Adam vonNieda commented on JENKINS-49894 Re: Active Choices Reactive Reference Parameter triggering the groovy script twice Hello, I've got the same issue, using Active Choices 2.1 (Jenkins LTS 2.150.1) Here's the code I'm executing. def sout = new StringBuilder(), serr = new StringBuilder() def proc = ["sudo", "-u", "oragen", "/home/oragen/automation/scripts/git/pull.sh"].execute() proc.consumeProcessOutput(sout, serr) proc.waitForOrKill(5000) return "Cloning the Git repository to local" + sout + "" + serr.text() If there's any sort of workaround I'd really appreciate it Let me know if there's anything additional I can provide. Thanks, -Adam Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19892) TOOL_HOME doesn't work in PATH
Title: Message Title Alex Taylor updated JENKINS-19892 Jenkins / JENKINS-19892 TOOL_HOME doesn't work in PATH Change By: Alex Taylor Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19892) TOOL_HOME doesn't work in PATH
Title: Message Title Alex Taylor commented on JENKINS-19892 Re: TOOL_HOME doesn't work in PATH This should be fixed with the update in https://issues.jenkins-ci.org/browse/JENKINS-53146 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19892) TOOL_HOME doesn't work in PATH
Title: Message Title Alex Taylor started work on JENKINS-19892 Change By: Alex Taylor Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19892) TOOL_HOME doesn't work in PATH
Title: Message Title Alex Taylor assigned an issue to Alex Taylor Jenkins / JENKINS-19892 TOOL_HOME doesn't work in PATH Change By: Alex Taylor Assignee: Alex Taylor Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53146) TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step
Title: Message Title Alex Taylor started work on JENKINS-53146 Change By: Alex Taylor Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53146) TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step
Title: Message Title Alex Taylor commented on JENKINS-53146 Re: TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step I am pretty sure I fixed this issue with the new PR. If anyone has time to test it out for themselves locally that would be great Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53146) TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step
Title: Message Title Alex Taylor updated JENKINS-53146 Jenkins / JENKINS-53146 TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step Change By: Alex Taylor Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55371) Ability to reset password using email address
Title: Message Title cowwoc created an issue Jenkins / JENKINS-55371 Ability to reset password using email address Issue Type: New Feature Assignee: Unassigned Components: core Created: 2018-12-31 18:26 Priority: Minor Reporter: cowwoc A user that forgets their username or password should be able to reset their password by providing their email address. If an account is associated with that address, an email will be sent containing a link. Upon clicking on that link, the user will be able to set the password to a value of their choosing. Add Comment
[JIRA] (JENKINS-54743) Contribute JIRA_URL environment variable
Title: Message Title
Naresh Rayapati edited a comment on JENKINS-54743
Re: Contribute JIRA_URL environment variable
[~falcon] If that is the case, I would use the script to get the site url from the config. You would need to approve some signatures (script security) to use the below methods, and fine tune it a bit as it can throw null pointer exception for those when site those are not not available for given name . Let me know if you still need it as an environment variable.{code:java}import org.thoughtslive.jenkins.plugins.jira.Config;import org.thoughtslive.jenkins.plugins.jira.Site;println getJIRASiteURL("Test")def getJIRASiteURL(siteName) {Site[] sites = Config.DESCRIPTOR.getSites()return sites.find { it.name == siteName }.url.toString()}{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29142) look for MSVC 15.x toolchain
Title: Message Title Martin Weber commented on JENKINS-29142 Re: look for MSVC 15.x toolchain One possible solution would be to change the plugin to run a sub-shell (cmd.exe) which first runs the environment-setter-script (vcvarsall) and then runs cmake. There would be an input field in the UI that allows users to specify the path to the environment-setter-script. Let me know if this could be a better solution than the workaround. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54743) Contribute JIRA_URL environment variable
Title: Message Title
Naresh Rayapati commented on JENKINS-54743
Re: Contribute JIRA_URL environment variable
benoit guerin If that is the case, I would use the script to get the site url from the config. You would need to approve some signatures to use the below methods, and fine tune it a bit as it can throw null pointer exception for those site those are not available. Let me know if you still need it as an environment variable.
import org.thoughtslive.jenkins.plugins.jira.Config;
import org.thoughtslive.jenkins.plugins.jira.Site;
println getJIRASiteURL("Test")
def getJIRASiteURL(siteName) {
Site[] sites = Config.DESCRIPTOR.getSites()
return sites.find { it.name == siteName }.url.toString()
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54743) Contribute JIRA_URL environment variable
Title: Message Title
Naresh Rayapati edited a comment on JENKINS-54743
Re: Contribute JIRA_URL environment variable
[~falcon] If that is the case, I would use the script to get the site url from the config. You would need to approve some signatures (script security) to use the below methods, and fine tune it a bit as it can throw null pointer exception for those site those are not available. Let me know if you still need it as an environment variable.{code :java }import org.thoughtslive.jenkins.plugins.jira.Config;import org.thoughtslive.jenkins.plugins.jira.Site;println getJIRASiteURL("Test")def getJIRASiteURL(siteName) {Site[] sites = Config.DESCRIPTOR.getSites()return sites.find { it.name == siteName }.url.toString()}{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54743) Contribute JIRA_URL environment variable
Title: Message Title benoit guerin commented on JENKINS-54743 Re: Contribute JIRA_URL environment variable My use case is on the description : build links to issues, using configuration instead of a remote call to obtain the root URL of the Jira site. To preserve multi sites runs, we can limit this change to the case where the JIRA_SITE env var is set. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55327) Job restrictions can be skipped if no node block in Jenkinsfile
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-55327 Job restrictions can be skipped if no node block in Jenkinsfile Change By: Oleg Nenashev Labels: regression Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55327) Job restrictions can be skipped if no node block in Jenkinsfile
Title: Message Title Oleg Nenashev edited a comment on JENKINS-55327 Re: Job restrictions can be skipped if no node block in Jenkinsfile It is a deliberate imorivement/ regression due to the changes in 2.111 - JENKINS-46652. I cannot fix it on the plugin side. CC [~jglick] [~danielbeck] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55327) Job restrictions can be skipped if no node block in Jenkinsfile
Title: Message Title Oleg Nenashev edited a comment on JENKINS-55327 Re: Job restrictions can be skipped if no node block in Jenkinsfile It is a deliberate imorivement improvement /regression due to the changes in 2.111 - JENKINS-46652. I cannot fix it on the plugin side. CC [~jglick] [~danielbeck] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55327) Job restrictions can be skipped if no node block in Jenkinsfile
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-55327 Job restrictions can be skipped if no node block in Jenkinsfile Change By: Oleg Nenashev Component/s: core Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55327) Job restrictions can be skipped if no node block in Jenkinsfile
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-55327 Job restrictions can be skipped if no node block in Jenkinsfile Change By: Oleg Nenashev Labels: regression Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55327) Job restrictions can be skipped if no node block in Jenkinsfile
Title: Message Title Oleg Nenashev commented on JENKINS-55327 Re: Job restrictions can be skipped if no node block in Jenkinsfile It is a regression due to the changes in 2.111 - JENKINS-46652. I cannot fix it on the plugin side. CC Jesse Glick Daniel Beck < /td> Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55360) language bug
Title: Message Title Oleg Nenashev commented on JENKINS-55360 Re: language bug suren pi Please take a look. Is it the recent recovery of localizations in the core in https://github.com/jenkinsci/jenkins/pull/3814 ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55360) language bug
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-55360 language bug Change By: Oleg Nenashev Component/s: localization-zh-cn-plugin Component/s: locale-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55360) language bug
Title: Message Title Oleg Nenashev assigned an issue to suren pi Jenkins / JENKINS-55360 language bug Change By: Oleg Nenashev Assignee: lockheed qi suren pi Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53816) [Blue Ocean] Completed stages appear to be skipped instead of finished
Title: Message Title boris ivan edited a comment on JENKINS-53816 Re: [Blue Ocean] Completed stages appear to be skipped instead of finished slight correction: my pipeline is still running, but otherwise is as described above at this point. The downstream steps that were complete are now completely missing in the visualization. The parallel-sequential step updated to show all complete (they were all complete ~ 40 minutes earlier, in reality). When the UI update occurred for that, that's when the downstream sequential steps that had previously run and completed (and were shown) disappeared. The pipeline is now on a step further downstream and it's running, though it's not shown _anywhere_. I suspect that when the entire pipeline is complete, it will all reappear, as I think I saw that occur before. update: as suspected. The entire pipeline shows upon completion, including the steps that had shown before that went away mid pipeline as described above. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53816) [Blue Ocean] Completed stages appear to be skipped instead of finished
Title: Message Title boris ivan commented on JENKINS-53816 Re: [Blue Ocean] Completed stages appear to be skipped instead of finished slight correction: my pipeline is still running, but otherwise is as described above at this point. The downstream steps that were complete are now completely missing in the visualization. The parallel-sequential step updated to show all complete (they were all complete ~ 40 minutes earlier, in reality). When the UI update occurred for that, that's when the downstream sequential steps that had previously run and completed (and were shown) disappeared. The pipeline is now on a step further downstream and it's running, though it's not shown anywhere. I suspect that when the entire pipeline is complete, it will all reappear, as I think I saw that occur before. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53816) [Blue Ocean] Completed stages appear to be skipped instead of finished
Title: Message Title boris ivan updated an issue Jenkins / JENKINS-53816 [Blue Ocean] Completed stages appear to be skipped instead of finished Change By: boris ivan Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53816) [Blue Ocean] Completed stages appear to be skipped instead of finished
Title: Message Title boris ivan commented on JENKINS-53816 Re: [Blue Ocean] Completed stages appear to be skipped instead of finished I'm seeing similar but even worse – the 'parallel sequential' stage that I have (similar to the picture attached) is in the beginning of my pipeline, and there are other steps afterwards. My build is currently executing those 'later' steps, showing blank circles for some of the steps that I know were finished earlier, in the 'parallel sequential' step that has been long finished ~ 40 minutes ago. Ack – even worse! It literally just finished my build and updated the visualization: the 'parallel sequential' step now shows all steps inside it complete, but all the downstream steps (which were executing earlier, and had shown as complete...) are now gone – not displayed at all. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55370) Exception during the Jenkins startup
Title: Message Title
Naresh Rayapati created an issue
Jenkins / JENKINS-55370
Exception during the Jenkins startup
Issue Type:
Bug
Assignee:
Alvaro Lobato
Components:
pipeline-maven-plugin
Created:
2018-12-31 15:21
Environment:
Jenkins 1.156 pipeline-maven:3.6.5
Priority:
Major
Reporter:
Naresh Rayapati
With latest plugin the following exception is thrown upon each time Jenkins starts. I think we are not yet ready to try the dependencies feature, so we haven't configured any database. is there any way that we can avoid this exception to keep the logs clean? Thank you.
Dec 31, 2018 3:15:15 PM org.jenkinsci.plugins.pipeline.maven.GlobalPipelineMavenConfig getDao
INFO: Connect to database jdbc:h2:file:/var/jenkins/jenkins-jobs/jenkins-jobs;AUTO_SERVER=TRUE;MULTI_THREADED=1;QUERY_CACHE_SIZE=25;JMX=TRUE with username sa and properties {}
Dec 31, 2018 3:15:15 PM com.zaxxer.hikari.HikariDataSource
INFO: HikariPool-1 - Starting...
Dec 31, 2018 3:15:16 PM com.zaxxer.hikari.HikariDataSource
INFO: HikariPool-1 - Start completed.
Dec 31, 2018 3:15:17 PM org.jenkinsci.plugins.pipeline.maven.GlobalPipelineMavenConfig getDao
WARNING: Exception creating database dao, skip
java.sql.SQLException: Exception connecting to 'null' with credentials 'null' (sa/***) and DAO PipelineMavenPluginH2Dao
at org.jenkinsci.plugins.pipeline.maven.GlobalPipelineMavenConfig.getDao(GlobalPipelineMavenConfig.java:346)
at org.jenkinsci.plugins.pipeline.maven.NonProductionGradeDatabaseWarningAdministrativeMonitor.isActivated(NonProductionGradeDatabaseWarningAdministrativeMonitor.java:19)
at
[JIRA] (JENKINS-49979) Showing only Jenkinsusers in Assignee Selectbox
Title: Message Title Arnaud TAMAILLON edited a comment on JENKINS-49979 Re: Showing only Jenkinsusers in Assignee Selectbox Hello, There AFAIK, there is no real way to know which users are actually real users, and which ones were created by some other ways (like for ex, git commit users).I proposed a change in git plugin to handle git use case (which might not be the only one), for JENKINS-9016, https://github.com/jenkinsci/git-plugin/pull/553 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49979) Showing only Jenkinsusers in Assignee Selectbox
Title: Message Title Arnaud TAMAILLON commented on JENKINS-49979 Re: Showing only Jenkinsusers in Assignee Selectbox Hello, There is no real way to know which users are actually real users, and which ones were created by some other ways (like for ex, git commit users). I proposed a change in git plugin to handle git use case (which might not be the only one), for JENKINS-9016, https://github.com/jenkinsci/git-plugin/pull/553 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52451) Stack Trace is printed when saving the smtp settings in jenkins
Title: Message Title Arnaud TAMAILLON commented on JENKINS-52451 Re: Stack Trace is printed when saving the smtp settings in jenkins Avinash Deva: Were you in the process of updating the plugin when this error occured? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55351) docker.build().inside() not run "inside" in Jenkins within Docker
Title: Message Title Attila Szeremi closed an issue as Duplicate Jenkins / JENKINS-55351 docker.build().inside() not run "inside" in Jenkins within Docker Change By: Attila Szeremi Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55351) docker.build().inside() not run "inside" in Jenkins within Docker
Title: Message Title Attila Szeremi commented on JENKINS-55351 Re: docker.build().inside() not run "inside" in Jenkins within Docker Closing this issue in favor of JENKINS-33510. It turns out that I only thought that that the commands were run on the host, but what I didn't know was that Jenkins mounted the exact same folder for the job into the container and cd'd into it for me (which I didn't expect nor want). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55369) Background step that passed is displayed as undefined
Title: Message Title Lawrence Ajayi created an issue Jenkins / JENKINS-55369 Background step that passed is displayed as undefined Issue Type: Bug Assignee: Damian Szczepanik Attachments: Screen Shot 2018-12-31 at 13.54.30.png Components: cucumber-reports-plugin Created: 2018-12-31 14:03 Priority: Major Reporter: Lawrence Ajayi Background steps that passed are being displayed as undefined and the overall status of the feature is displayed as failed despite that all the scenario and background steps are passed. Attached is the screenshot. Add Comment
[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title
Attila Szeremi commented on JENKINS-33510
Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
This ticket is supposedly resolved... but then what do I need to write to make sure the `sh` commands are run in the correct working directory?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55356) Some workflow jobs fail after restart on Java 11 server
Title: Message Title Mark Waite commented on JENKINS-55356 Re: Some workflow jobs fail after restart on Java 11 server Baptiste Mathus thanks for asking! The details in this report are using the incremental build from the pull request that Devin Nusbaum had provided. The results with that pull request are much better than without it. Without that pull request I see null pointer exception messages in the Jenkins logs on restart. The null pointer exceptions cause the jobs to fail and are described in JENKINS-55338. JENKINS-55338 is a duplicate of JENKINS-55174. There are no additional entries in the Jenkins log related to the problem as far as I can tell. I think PR-86 should be merged into the workflow support plugin for Java 11. It improves the results by removing the null pointer exception and moves the code onto a newer JBoss marshalling release. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55241) sshagent + sshCommand: connector is not available
Title: Message Title Naresh Rayapati edited a comment on JENKINS-55241 Re: sshagent + sshCommand: connector is not available ssh-steps using the *jsch* library which supports only *nc*/*jna* user sockets only, from the exception about above it was able to find the SSH_AUTH_SOCK but it is not doesn't look like it is either *nc or jna*.May I know more details about your environment? like what OS and so on..And also I am wondering about use case to wrap sshCommand with sshagent? I don't think so we need that.Note: I was away for vacation, sorry for the late response. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54474) Variables not resolving in SSH Steps plugin
Title: Message Title Naresh Rayapati commented on JENKINS-54474 Re: Variables not resolving in SSH Steps plugin Dan Caldarola is this still an issue? I am going to close this please don't hesitate to reopen if you are still facing any issues. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55194) Excessive logging
Title: Message Title Naresh Rayapati commented on JENKINS-55194 Re: Excessive logging Vlad Uros Sure, let me make it as a param, so that we can alter it based on the use case. Thank you for reporting. https://github.com/jenkinsci/ssh-steps-plugin/blob/master/src/main/groovy/org/jenkinsci/plugins/sshsteps/SSHService.groovy#L86 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54743) Contribute JIRA_URL environment variable
Title: Message Title Naresh Rayapati commented on JENKINS-54743 Re: Contribute JIRA_URL environment variable benoit guerin I am wondering about the real use case here, not sure if this change really is going to behave as expected especially when using multiple sites with in a single run, the environment variable would change consistently based on the site. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55241) sshagent + sshCommand: connector is not available
Title: Message Title Naresh Rayapati commented on JENKINS-55241 Re: sshagent + sshCommand: connector is not available ssh-steps using the jsch library which supports only nc/jna user sockets only, from the exception about it was able to find the SSH_AUTH_SOCK but it is not either nc or jna. May I know more details about your environment? like what OS and so on.. And also I am wondering about use case to wrap sshCommand with sshagent? I don't think so we need that. Note: I was away for vacation, sorry for the late response. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44398) Add few more steps around Issues
Title: Message Title Naresh Rayapati commented on JENKINS-44398 Re: Add few more steps around Issues for changelog, not sure if I will get to this soon, please don't mind to issue a pull request if you are interested in. Thank you for the feedback Viviana Terceros Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55368) No issues found when parsing Eclipse ECJ output from console log during maven build
Title: Message Title
Piotrek Zygielo updated an issue
Jenkins / JENKINS-55368
No issues found when parsing Eclipse ECJ output from console log during maven build
Change By:
Piotrek Zygielo
Maven build using ECJ completes with:{noformat}channel stopped[Eclipse ECJ] Sleeping for 5 seconds due to JENKINS-32191...[Eclipse ECJ] Parsing console log (workspace: '/home/jenkins-agent/agent-1/workspace/xxx')[Eclipse ECJ] Attaching ResultAction with ID 'eclipse' to run 'xxx #10'.[Eclipse ECJ] Using reference build 'xxx #9' to compute new, fixed, and outstanding issues[Eclipse ECJ] Issues delta (vs. reference build): outstanding: 0, new: 0, fixed: 0[Eclipse ECJ] No quality gates have been set - skipping[Eclipse ECJ] Health report is disabled - skipping[Eclipse ECJ] Created analysis result for 0 issues (found 0 new issues, fixed 0 issues)Finished: SUCCESS{noformat}Parser - indeed has *ANT*_ECLIPSE_WARNING_PATTERN in [EclipseParser.java|https://github.com/jenkinsci/analysis-model/blob/0c53a83b491b1dc32e57ff73a3f5751175448c7c/src/main/java/edu/hm/hafner/analysis/parser/EclipseParser.java#L26], not MAVEN in name, yet [Documentation|https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md] promises Maven Project to be supported type.Inspection of job's log with {{less}} shows colorised entries with control sequences like below:{noformat}ESC[8mha: 4NPzfsCHJFyEqbHt1tyu83RhpB1NXTka2OpStZBOt27 4ABzfsCHJFyEqbHt1tyu83RhpB1NXTka2OpStZBOt27 / Yx AACAYx + LCP9b85aBtbiIQSWjNKU4P0 LCAAcAWZAAP9ba5aBtbi1QSWjNKU4P0 + vJLE4u1gvPjexLDVPzxdEhicW5WXmpfvll6S2fNly5fzGzauYGBgqihikoFqS8 vJLE4u1gvPjexLDVPzxdEhicW5WXmpfvWl6S2eNly5fzGzaurGBgqihikoFqS8 / OK83NS9ZwhNEghAwQwghQWAACwxA OK83NS9ZwhlkghAwQwghQWAA14xA + XYg XYgAbAA ==ESC[0m[WARNING] /home/jenkins-agent/agent-1/workspace/xxx/.../Y.java:[167,6363] Unqualified access to the field Y.w{noformat}but I don't know if they are also transferred to {{ReportScanningTool}}. If project is executed with modified plexus-compiler (as the currently released one does not support specifying log file [plexus-compiler#55|https://github.com/codehaus-plexus/plexus-compiler/issues/55]) - with log files preserved and fed to warnings-ng - the same build results in{noformat}...channel stopped[Eclipse ECJ] Searching for all files in '/home/jenkins-agent/agent-2/workspace/xxx' that match the pattern '**/target/ecjerr-*.xml'[Eclipse ECJ] -> found 10 files[Eclipse ECJ] Successfully parsed file /home/jenkins-agent/agent-2/workspace/xxx/target/ecjerr-1737547503980039210.xml[Eclipse ECJ] -> found 7 issues (skipped 0 duplicates)...[Eclipse ECJ] Post processing issues on 'phobos-agent-2' with encoding 'UTF-8'[Eclipse ECJ] Resolving absolute file names for all issues[Eclipse ECJ] -> 0 resolved, 0 unresolved, 55 already resolved[Eclipse ECJ] Copying affected files to Jenkins' build folder /home/yyy/.jenkins/jobs/xxx/builds/11[Eclipse ECJ] -> 55 copied, 0 not in workspace, 0 not-found, 0 with I/O error[Eclipse ECJ] Resolving module names from module definitions
[JIRA] (JENKINS-55368) No issues found when parsing Eclipse ECJ output from console log during maven build
Title: Message Title
Piotrek Zygielo updated an issue
Jenkins / JENKINS-55368
No issues found when parsing Eclipse ECJ output from console log during maven build
Change By:
Piotrek Zygielo
Maven build using ECJ completes with:{noformat}channel stopped[Eclipse ECJ] Sleeping for 5 seconds due to JENKINS-32191...[Eclipse ECJ] Parsing console log (workspace: '/home/jenkins-agent/agent-1/workspace/xxx')[Eclipse ECJ] Attaching ResultAction with ID 'eclipse' to run 'xxx #10'.[Eclipse ECJ] Using reference build 'xxx #9' to compute new, fixed, and outstanding issues[Eclipse ECJ] Issues delta (vs. reference build): outstanding: 0, new: 0, fixed: 0[Eclipse ECJ] No quality gates have been set - skipping[Eclipse ECJ] Health report is disabled - skipping[Eclipse ECJ] Created analysis result for 0 issues (found 0 new issues, fixed 0 issues)Finished: SUCCESS{noformat}Parser - indeed has *ANT*_ECLIPSE_WARNING_PATTERN in [EclipseParser.java|https://github.com/jenkinsci/analysis-model/blob/0c53a83b491b1dc32e57ff73a3f5751175448c7c/src/main/java/edu/hm/hafner/analysis/parser/EclipseParser.java#L26], not MAVEN in name, yet [Documentation|https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md] promises Maven Project to be supported type. Inspection of job's log with {{less}} shows colorised entries with control sequences like below: {noformat}ESC[8mha:4NPzfsCHJFyEqbHt1tyu83RhpB1NXTka2OpStZBOt27/Yx+LCP9b85aBtbiIQSWjNKU4P0+vJLE4u1gvPjexLDVPzxdEhicW5WXmpfvll6S2fNly5fzGzauYGBgqihikoFqS8/OK83NS9ZwhNEghAwQwghQWAACwxA+XYg==ESC[0m[WARNING] /home/jenkins - agent/agent - 1/workspace/xxx/.../Y.java:[167,6363] Unqualified access to the field Y.w{noformat}but I don't know if they are also transferred to {{ReportScanningTool}}. -- -- If project is executed with modified plexus-compiler (as the currently released one does not support specifying log file [plexus-compiler#55|https://github.com/codehaus-plexus/plexus-compiler/issues/55]) - with log files preserved and fed to warnings-ng - the same build results in{noformat}...channel stopped[Eclipse ECJ] Searching for all files in '/home/jenkins-agent/agent-2/workspace/xxx' that match the pattern '**/target/ecjerr-*.xml'[Eclipse ECJ] -> found 10 files[Eclipse ECJ] Successfully parsed file /home/jenkins-agent/agent-2/workspace/xxx/target/ecjerr-1737547503980039210.xml[Eclipse ECJ] -> found 7 issues (skipped 0 duplicates)...[Eclipse ECJ] Post processing issues on 'phobos-agent-2' with encoding 'UTF-8'[Eclipse ECJ] Resolving absolute file names for all issues[Eclipse ECJ] -> 0 resolved, 0 unresolved, 55 already resolved[Eclipse ECJ] Copying affected files to Jenkins' build folder /home/yyy/.jenkins/jobs/xxx/builds/11[Eclipse ECJ] -> 55 copied, 0 not in workspace, 0 not-found, 0 with I/O error[Eclipse ECJ] Resolving module names from module definitions (build.xml, pom.xml, or Manifest.mf files)[Eclipse ECJ] -> resolved module names for 381 issues[Eclipse ECJ] Resolving package names (or namespaces) by parsing the affected files[Eclipse
[JIRA] (JENKINS-51751) When claiming Test or build, only send mail if claiming for someone else
Title: Message Title Arnaud TAMAILLON updated JENKINS-51751 Jenkins / JENKINS-51751 When claiming Test or build, only send mail if claiming for someone else Change By: Arnaud TAMAILLON Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51751) When claiming Test or build, only send mail if claiming for someone else
Title: Message Title Arnaud TAMAILLON assigned an issue to Arnaud TAMAILLON Jenkins / JENKINS-51751 When claiming Test or build, only send mail if claiming for someone else Change By: Arnaud TAMAILLON Assignee: florian gouze Arnaud TAMAILLON Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51751) When claiming Test or build, only send mail if claiming for someone else
Title: Message Title Arnaud TAMAILLON started work on JENKINS-51751 Change By: Arnaud TAMAILLON Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55368) No issues found when parsing Eclipse ECJ output from console log during maven build
Title: Message Title Piotrek Zygielo updated an issue Jenkins / JENKINS-55368 No issues found when parsing Eclipse ECJ output from console log during maven build Change By: Piotrek Zygielo Environment: ||SW||Version||| Jenkins | : 2.156 | | warnings-ng-plugin | : 1.0.1 | | ecj | : 3.16.0, 3.15.1 | | plexus-compiler | : 2.8.5 | | maven | : 3.6.0 | | java | : 1.8.0_191 | Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55368) No issues found when parsing Eclipse ECJ output from console log during maven build
Title: Message Title Piotrek Zygielo created an issue Jenkins / JENKINS-55368 No issues found when parsing Eclipse ECJ output from console log during maven build Issue Type: Bug Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2018-12-31 11:37 Environment: ||SW||Version|| |Jenkins|2.156| |warnings-ng-plugin|1.0.1| |ecj|3.16.0, 3.15.1| |plexus-compiler|2.8.5| |maven|3.6.0| |java|1.8.0_191| Priority: Minor Reporter: Piotrek Zygielo Maven build using ECJ completes with: channel stopped [Eclipse ECJ] Sleeping for 5 seconds due to JENKINS-32191... [Eclipse ECJ] Parsing console log (workspace: '/home/jenkins-agent/agent-1/workspace/xxx') [Eclipse ECJ] Attaching ResultAction with ID 'eclipse' to run 'xxx #10'. [Eclipse ECJ] Using reference build 'xxx #9' to compute new, fixed, and outstanding issues [Eclipse ECJ] Issues delta (vs. reference build): outstanding: 0, new: 0, fixed: 0 [Eclipse ECJ] No quality gates have been set - skipping [Eclipse ECJ] Health report is disabled - skipping [Eclipse ECJ] Created analysis result for 0 issues (found 0 new issues, fixed 0 issues) Finished: SUCCESS Parser - indeed has ANT_ECLIPSE_WARNING_PATTERN in EclipseParser.java, not MAVEN in name, yet Documentation promises Maven Project to be supported type. If project is executed with modified plexus-compiler (as the currently released one does not support specifying log file plexus-compiler#55) - with log files
[JIRA] (JENKINS-55262) Missing content-type on serverStatuses REST API
Title: Message Title Florian Ramillien commented on JENKINS-55262 Re: Missing content-type on serverStatuses REST API Linked pull request : https://github.com/jenkinsci/gerrit-trigger-plugin/pull/388 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55367) Uft discovery job is not working correctly in Jenkins 2.107.1+ because of Security hardening
Title: Message Title Radi Berkovich created an issue Jenkins / JENKINS-55367 Uft discovery job is not working correctly in Jenkins 2.107.1+ because of Security hardening Issue Type: Bug Assignee: Radi Berkovich Components: hp-application-automation-tools-plugin Created: 2018-12-31 10:56 Priority: Critical Reporter: Radi Berkovich Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54746) Can't connect via SSH on 1.29.1
Title: Message Title Torsten Landschoff commented on JENKINS-54746 Re: Can't connect via SSH on 1.29.1 Never mind, in my case somebody else changed the credentials - Jenkins now uses a new node key to authenticate, which was not in the authorized_keys of this particular host. The sshd logs didn't help in this case though - Jenkins claims that the key was rejected while the sshd reports that the connection was closed on client request - probably, because it has run out of keys to try... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55122) Evaluate flaky tests
Title: Message Title Baptiste Mathus assigned an issue to Unassigned Jenkins / JENKINS-55122 Evaluate flaky tests Change By: Baptiste Mathus Assignee: Baptiste Mathus Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
