[JIRA] [core] (JENKINS-22311) Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history
Daniel Beck assigned JENKINS-22311 to Daniel Beck Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history Change By: Daniel Beck (20/Dec/14 12:38 PM) Assignee: DanielBeck This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-12379) Archive the artifacts should allow specifying the target artifacts path
Daniel Beck commented on JENKINS-12379 Archive the artifacts should allow specifying the target artifacts path As I need this feature now, implementing as proposed above. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-12379) Archive the artifacts should allow specifying the target artifacts path
Daniel Beck assigned JENKINS-12379 to Daniel Beck Archive the artifacts should allow specifying the target artifacts path Change By: Daniel Beck (20/Dec/14 12:40 PM) Assignee: DanielBeck This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-21861) option to include attachment with console.txt from failed slaves
Mike Dubman commented on JENKINS-21861 option to include attachment with console.txt from failed slaves it does not for matrix projects This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26185) Reusing workspaces between stages and nodes
Nikita Salnikov-Tarnovski created JENKINS-26185 Reusing workspaces between stages and nodes Issue Type: Improvement Assignee: Jesse Glick Components: workflow-plugin Created: 20/Dec/14 4:07 PM Description: Imagine I have a workflow with 2 stages. For different reasons these two stages should run on different slaves. Now I do not want to checkout the whole repo on the second slave during second stage, when that was already done on first slave during first stage. Is it possible to just copy whole workspace between slaves and stages? Project: Jenkins Priority: Minor Reporter: Nikita Salnikov-Tarnovski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [svnmerge-plugin] (JENKINS-25769) Rebase build action cannot be triggered from Promoted Builds
SCM/JIRA link daemon commented on JENKINS-25769 Rebase build action cannot be triggered from Promoted Builds Code changed in jenkins User: Hugues Chabot Path: src/main/java/jenkins/plugins/svnmerge/IntegrationPublisher.java src/main/java/jenkins/plugins/svnmerge/RebaseBuilder.java src/main/java/jenkins/plugins/svnmerge/Utility.java http://jenkins-ci.org/commit/svnmerge-plugin/556ce5ee0bb4c45ba43d466f260508cc43e8dbbc Log: Merge pull request #25 from jenkinsci/JENKINS-25769 FIX JENKINS-25769 Use root build on a promotion build Compare: https://github.com/jenkinsci/svnmerge-plugin/compare/283ad16abf1f...556ce5ee0bb4 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [svnmerge-plugin] (JENKINS-25769) Rebase build action cannot be triggered from Promoted Builds
SCM/JIRA link daemon commented on JENKINS-25769 Rebase build action cannot be triggered from Promoted Builds Code changed in jenkins User: Hugues Chabot Path: src/main/java/jenkins/plugins/svnmerge/IntegrationPublisher.java src/main/java/jenkins/plugins/svnmerge/RebaseBuilder.java src/main/java/jenkins/plugins/svnmerge/Utility.java http://jenkins-ci.org/commit/svnmerge-plugin/ac8ccf875f024a7871b69626bb125617c341f871 Log: FIX JENKINS-25769 Use root build on a promotion build This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [buildtriggerbadge-plugin] (JENKINS-26186) Last Build Trigger Column does not print author name
J John created JENKINS-26186 Last Build Trigger Column does not print author name Issue Type: Bug Assignee: Baptiste Mathus Attachments: Issue.JPG Components: buildtriggerbadge-plugin Created: 20/Dec/14 6:21 PM Description: Last Build Trigger Column does not print author name in the trigger column as shown in the plugin webpage. Attached screenshot. Environment: Jenkins Version 1.593 Build Trigger Plugin 1.3 Windows Server 2012 Project: Jenkins Labels: buildtriggerplugin Priority: Minor Reporter: J John This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26184) jenkins user in jobs not inheriting linux groups
Daniel Beck commented on JENKINS-26184 jenkins user in jobs not inheriting linux groups When did you add Jenkins to that group? Did you restart Jenkins (or possibly the machine) since? What happens when you run groups jenkins (assuming the user is called jenkins)? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20148) Misleading description of the 'workspace' permission
Daniel Beck started work on JENKINS-20148 Misleading description of the workspace permission Change By: Daniel Beck (20/Dec/14 11:35 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-25970) Use proxy from http.proxy{Host|Port} JVM properties
Mark Waite resolved JENKINS-25970 as Fixed Use proxy from http.proxy{Host|Port} JVM properties The call to CliGitAPIImpl.checkCredentials() has been removed. I don't have a proxy available to test. Can you build and test a version of the plugin for yourself to confirm that your proxy use case works? If you can't easily build it yourself, I'm happy to build you a pre-release version for testing. Based on my test results, I suspect git-client-plugin 1.13.1 will be released within the next 1-2 weeks and will include the fix. Change By: Mark Waite (21/Dec/14 12:57 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-24879) Git Plugin env variable resolution not working in Git Publisher
Mark Waite closed JENKINS-24879 as Duplicate Git Plugin env variable resolution not working in Git Publisher Change By: Mark Waite (21/Dec/14 1:09 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-23188) Tag List Empty
Mark Waite commented on JENKINS-23188 Tag List Empty The call to checkCredentials has been removed from the git client plugin. Once git client plugin 1.13.1 releases, could you check again to see if the problem is still visible? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-22119) Fail to update git repository with stored credential
Mark Waite commented on JENKINS-22119 Fail to update git repository with stored credential The call to checkCredentials() has been removed in git-client-plugin from 1.13.1 and beyond. Would you be willing to test a pre-release of git-client-plugin 1.13.1 for this case? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-20533) Git2 plugin and HTTP-authentication fails
Mark Waite commented on JENKINS-20533 Git2 plugin and HTTP-authentication fails The call to checkCredentials() has been removed in git-client-plugin from 1.13.1 and beyond. Would you be willing to test a pre-release of git-client-plugin 1.13.1 for this case? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-23050) Slave unable to clone from Git over HTTPS due to self signed certificate
Mark Waite commented on JENKINS-23050 Slave unable to clone from Git over HTTPS due to self signed certificate The call to checkCredentials() has been removed in git-client-plugin from 1.13.1 and beyond. Would you be willing to test a pre-release of git-client-plugin 1.13.1 for this case? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-19726) JGIT Error in combination with self signed certificate and https repo
Mark Waite commented on JENKINS-19726 JGIT Error in combination with self signed certificate and https repo The call to checkCredentials() has been removed in git-client-plugin from 1.13.1 and beyond. Would you be willing to test a pre-release of git-client-plugin 1.13.1 for this case? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-22909) Jenkins SSH connection to a Git server is not working using username/password
Mark Waite commented on JENKINS-22909 Jenkins SSH connection to a Git server is not working using username/password The more I look at this report, the less confident I am that I understand what is requested. I'm able to clone with a username / password credential without using public / private keys with the following steps: Configure a global username / password credential (through "Manage Credentials") with appropriate user name and password (no public key, no private key) Create a new freestyle job - JENKINS-22909-username-password-credentials Use git as the SCM for the job Use an ssh URL for the repository. I used ssh://mwa...@mark-pc1.markwaite.net/var/lib/git/mwaite/bin.git Use the previously defined username / password credential as the credential for that ssh URL Run the job, confirm it succeeds Are there more steps you're taking to show the problem? Have you used a more recent git client plugin and a more recent git plugin? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-24304) Enable/Disable verbose Git command logging in Jenkins build log
Mark Waite commented on JENKINS-24304 Enable/Disable verbose Git command logging in Jenkins build log You might check if defining the property org.jenkinsci.plugins.gitclient.GitClient.quietRemoteBranches=true on the java command line which starts the Jenkins server. If the line you're trying to avoid is "Seen branch xyzzy", then the conditional in the code seems to only display that if quietRemoteBranches is the default value of false. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-22675) Jenkins GIT Plugin unable to access repository using HTTPS with self-signed certificate
Mark Waite commented on JENKINS-22675 Jenkins GIT Plugin unable to access repository using HTTPS with self-signed certificate The call to checkCredentials() has been removed in git-client-plugin from 1.13.1 and beyond. Would you be willing to test a pre-release of git-client-plugin 1.13.1 for this case? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22311) Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history
Daniel Beck started work on JENKINS-22311 Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history Change By: Daniel Beck (21/Dec/14 2:22 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25989) No wrap up(not in multiple lines) of too long list of slaves at label page
Daniel Beck started work on JENKINS-25989 No wrap up(not in multiple lines) of too long list of slaves at label page Change By: Daniel Beck (21/Dec/14 2:31 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25174) Run parameters should display in human readable form rather than build numbers
Daniel Beck started work on JENKINS-25174 Run parameters should display in human readable form rather than build numbers Change By: Daniel Beck (21/Dec/14 2:51 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-25338) list-jobs cli
Daniel Beck started work on JENKINS-25338 list-jobs cli Change By: Daniel Beck (21/Dec/14 3:01 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25910) Nodes are not sorted on label overview page
Daniel Beck started work on JENKINS-25910 Nodes are not sorted on label overview page Change By: Daniel Beck (21/Dec/14 3:19 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25601) JDK9 with jigsaw file layer is not detected as valid JDK
Daniel Beck started work on JENKINS-25601 JDK9 with jigsaw file layer is not detected as valid JDK Change By: Daniel Beck (21/Dec/14 3:24 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25601) JDK9 with jigsaw file layer is not detected as valid JDK
Daniel Beck commented on JENKINS-25601 JDK9 with jigsaw file layer is not detected as valid JDK Please see comment above for build with proposed fix. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24895) An existing connection was forcibly closed by the remote host
Leslie Klein commented on JENKINS-24895 An existing connection was forcibly closed by the remote host Hi Graziano/anynoe, can you contribute some insight to our findings? 1. We run the Jenkins job after the slave has been activated as a slave-agent launched from browser - result, the job runs to completion with successful termination. 2.We run the slave using the batch command that you attached above - result, the job runs for 7 minutes and then terminates on the server with the "SocketException: connection reset" error below (the actual job on the slave continues to run and completes successfully after about another 3 minutes). 3.If we run the slave as a Service, we receive the connection reset error after about 2-3 minutes. 4.There are no error messages in the Jenkins Server Event Viewer coinciding with the connection reset error under any of the above cases. 5.We did notice a peak on Jenkins CPU usage when the connection was reset. Error trace --- FATAL: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset hudson.remoting.RequestAbortedExcepton: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset at hudson.remoting.RequestAbortedExcepton.wrapForRethrow(RequestAbortedException.java:41) at hudson.remoting.RequestAbortedExcepton.wrapForRethrow(RequestAbortedException.java:34) at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Request.call(Request.java:722) and so on This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.