丰满媚娘
丰满媚娘 删除字 --向 tzdyo.hioe向m.c向om?3r3l -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22758) Jenkins >=1.560 breaks Jenkins slave handling / NIO JNLP related (using swarm plugin)
Vivekanand SV commented on JENKINS-22758 Jenkins >=1.560 breaks Jenkins slave handling / NIO JNLP related (using swarm plugin) I updated to 1.575 and used the latest salve.jar, things are working fine till now. Will update if there are any issues. Vivek. 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] (JENKINS-24261) Assembla browser breaks config page
Mark Waite resolved JENKINS-24261 as Fixed Assembla browser breaks config page Fixed in git client plugin 2.2.5 released 15 Aug 2014 Change By: Mark Waite (16/Aug/14 2:54 AM) Status: In Progress 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] (JENKINS-24261) Assembla browser breaks config page
Mark Waite closed JENKINS-24261 as Fixed Assembla browser breaks config page Change By: Mark Waite (16/Aug/14 2:54 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] (JENKINS-23179) git pre-merge fails with matrix project
Mark Waite closed JENKINS-23179 as Fixed git pre-merge fails with matrix project Fixed in git client plugin 2.2.5, released 15 Aug 2014. Change By: Mark Waite (16/Aug/14 2:31 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] (JENKINS-22009) Git Polling Keeps Detecting Changes When Variables in refspec
Mark Waite closed JENKINS-22009 as Fixed Git Polling Keeps Detecting Changes When Variables in refspec Fixed in git client plugin 2.2.5, released 15 Aug 2014. Change By: Mark Waite (16/Aug/14 2:30 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] [msbuild] (JENKINS-22451) Backslash is stripped from MSBuild command line argument
Gregory Boissinot edited a comment on JENKINS-22451 Backslash is stripped from MSBuild command line argument '\' is an escaped character. In your use case, for having 'trunk\' in the command line, use double backslash character 'trunk\\\'. 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-24014) Jenkins wrongly(?) warns that "reverse proxy set up is broken" when using autorefresh link.
Daniel Beck started work on JENKINS-24014 Jenkins wrongly(?) warns that "reverse proxy set up is broken" when using autorefresh link. Change By: Daniel Beck (15/Aug/14 10:12 PM) Status: Open In Progress 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] [msbuild] (JENKINS-22451) Backslash is stripped from MSBuild command line argument
Gregory Boissinot commented on JENKINS-22451 Backslash is stripped from MSBuild command line argument Sorry I fixed with an alternative 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] (JENKINS-19994) Unable to delete workspace
Gregory Boissinot updated JENKINS-19994 Unable to delete workspace Change By: Gregory Boissinot (15/Aug/14 10:49 PM) Component/s: msbuild 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] [claim] (JENKINS-23046) Failed msbuild does not appear in claims report
Gregory Boissinot updated JENKINS-23046 Failed msbuild does not appear in claims report Change By: Gregory Boissinot (15/Aug/14 9:59 PM) Component/s: msbuild 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] [msbuild] (JENKINS-18652) Handling of Configuration and Platform parameters
Gregory Boissinot commented on JENKINS-18652 Handling of Configuration and Platform parameters Does this issue persists with the latest version? 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] [msbuild] (JENKINS-22451) Backslash is stripped from MSBuild command line argument
Gregory Boissinot edited a comment on JENKINS-22451 Backslash is stripped from MSBuild command line argument '\' is an escaped character. In your use case, for having 'trunk\' in the command line, use double backslash character. 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] [msbuild] (JENKINS-22461) New MSBuild release has a space in the installation path; causes msbuild plugin to fail
Gregory Boissinot resolved JENKINS-22461 as Fixed New MSBuild release has a space in the installation path; causes msbuild plugin to fail Change By: Gregory Boissinot (15/Aug/14 10:00 PM) 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] [msbuild] (JENKINS-22344) Command Line Arguments: /p:PublishFolder does not work with UNC format to publish to remote server
SCM/JIRA link daemon commented on JENKINS-22344 Command Line Arguments: /p:PublishFolder does not work with UNC format to publish to remote server Code changed in jenkins User: Gregory Boissinot Path: src/main/java/hudson/plugins/msbuild/MsBuildBuilder.java src/test/java/hudson/plugins/msbuild/MsBuildBuilderTest.java http://jenkins-ci.org/commit/msbuild-plugin/bdec2dfe089d62a80fd0371db605ee9c3ebbe41b Log: Fix JENKINS-22344 and JENKINS-22451 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] [msbuild] (JENKINS-22344) Command Line Arguments: /p:PublishFolder does not work with UNC format to publish to remote server
Gregory Boissinot resolved JENKINS-22344 as Fixed Command Line Arguments: /p:PublishFolder does not work with UNC format to publish to remote server Change By: Gregory Boissinot (15/Aug/14 10:50 PM) 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] [msbuild] (JENKINS-22451) Backslash is stripped from MSBuild command line argument
Gregory Boissinot resolved JENKINS-22451 as Fixed Backslash is stripped from MSBuild command line argument '\' is an escaped character. In your use case, for having 'trunk\' in the command line, use double backslash character 'trunk'. Change By: Gregory Boissinot (15/Aug/14 10:10 PM) 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] [vss] (JENKINS-19868) Jenkins windows service terminates unexpectedly
Gregory Boissinot updated JENKINS-19868 Jenkins windows service terminates unexpectedly Change By: Gregory Boissinot (15/Aug/14 10:54 PM) Component/s: msbuild 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] [msbuild] (JENKINS-22451) Backslash is stripped from MSBuild command line argument
SCM/JIRA link daemon commented on JENKINS-22451 Backslash is stripped from MSBuild command line argument Code changed in jenkins User: Gregory Boissinot Path: src/main/java/hudson/plugins/msbuild/MsBuildBuilder.java src/test/java/hudson/plugins/msbuild/MsBuildBuilderTest.java http://jenkins-ci.org/commit/msbuild-plugin/bdec2dfe089d62a80fd0371db605ee9c3ebbe41b Log: Fix JENKINS-22344 and JENKINS-22451 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] [docker-build-step] (JENKINS-22985) Fork of docker-java under jenkins namespace?
vjuranek resolved JENKINS-22985 as Fixed Fork of docker-java under jenkins namespace? Plugin has already switched to docker-java, closing. Change By: vjuranek (15/Aug/14 8:49 PM) 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] [matrix-auth] (JENKINS-17764) 'Trigger Builds Remotely' with ?token not working when Matrix Authorization Strategy is used
Matthaus Owens edited a comment on JENKINS-17764 'Trigger Builds Remotely' with ?token not working when Matrix Authorization Strategy is used Is there a ticket for the component fix? In what version was the fixed component released? Oh, you meant you set the component to the correct element. Never mind. 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] [matrix-auth] (JENKINS-17764) 'Trigger Builds Remotely' with ?token not working when Matrix Authorization Strategy is used
Matthaus Owens commented on JENKINS-17764 'Trigger Builds Remotely' with ?token not working when Matrix Authorization Strategy is used Is there a ticket for the component fix? In what version was the fixed component released? 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] [postbuildscript] (JENKINS-24216) executeOn is created even for non-matrix jobs when updating config with REST API
Gregory Boissinot commented on JENKINS-24216 executeOn is created even for non-matrix jobs when updating config with REST API Could you give me a reproductible sample? 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] [github] (JENKINS-24291) GitHub plugin to make parameters from webhook data
Rob Richardson created JENKINS-24291 GitHub plugin to make parameters from webhook data Issue Type: Improvement Assignee: Unassigned Components: github, plugin Created: 15/Aug/14 8:54 PM Description: I'm trying to build the git hash / branch that just got pushed. GitHub passes the correct webhook, and https://JENKINSURLHERE/log/webhooks/?auto_refresh=true shows me the correct data, but the build notes "After filtering out what's already been built: []\nNothing seems worth building, so falling back to the previously built revision:" then lists the git hash of the previous build. Most of the time the new code is the most recent code, but not always. Consider the case where different branch names yield different build steps – e.g. git-flow deploys release/* branches to the test server and dev to the dev server. In this case, I want to push a new branch name on a previously built git hash, and have it build again with different results. Here's steps to reproduce the problem: 1. Given a repository on GitHub or GitHub Enterprise with some history (2 or 3 commits is enough) 2. Given a build that listens to GitHub (or GitHub Enterprise) via webhook 3. Given that the build has run a few times already 4. Create a new branch on an old commit (not a tip), for example "initial commit" 5. Push the new branch 6. Note that the github webhook log shows the specified git hash and branch 7. Note that it builds the tip, not the specified commit Failure cause: GitHub plugin only gets the repository url and committer name from the webhook data (see https://github.com/jenkinsci/github-plugin/blob/master/src/main/java/com/cloudbees/jenkins/GitHubWebHook.java#L175), it does not get the other details. Proposed solution: GitHub plugin creates parameters of relevant webhook data that other plugins / parameterized builds could leverage such as GIT_HASH, GIT_BRANCH, etc, etc. Plugins such as http://www.sourceprojects.org/jenkins-and-the-git-branch-selection could leverage these as parameterized build sources, or parameterized builds could consume these variables directly. Alternate solution: GitHub plugin could skip over `getCandidateRevisions` call completely and trigger the build with the webhook's specified git hash / branch Project: Jenkins Labels: github plugin Priority: Major Reporter: Rob Richardson 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] [docker-build-step] (JENKINS-24154) Cannot ping REST endpoint (after upgrade)
vjuranek resolved JENKINS-24154 as Fixed Cannot ping REST endpoint (after upgrade) JENKINS-24156 is implemented and will be in the next release, closing. Change By: vjuranek (15/Aug/14 8:47 PM) 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] [msbuild] (JENKINS-24276) MSBuild targeting both Debug and Release configurations fails
Gregory Boissinot commented on JENKINS-24276 MSBuild targeting both Debug and Release configurations fails Please could you give me the actual command line and the expected command line? 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-24253) Add JOB_LABELS environment variable
David Ruhmann commented on JENKINS-24253 Add JOB_LABELS environment variable That looks great Daniel! Exactly my goal, to have no config and always run. Probably going to just build it as is and throw it up on my box for the time being so that I can start to use the variable. Will modify it as I go. Glad to see that my implementation was not to far off. I was mainly just missing the logging and the validation of the object type for AbstractProject. 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-24272) jnlp slaves fail to reconnect when master is restarted
Richard Mortimer started work on JENKINS-24272 jnlp slaves fail to reconnect when master is restarted Change By: Richard Mortimer (15/Aug/14 7:33 PM) Status: Open In Progress 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-24272) jnlp slaves fail to reconnect when master is restarted
Richard Mortimer assigned JENKINS-24272 to Richard Mortimer jnlp slaves fail to reconnect when master is restarted Change By: Richard Mortimer (15/Aug/14 7:33 PM) Assignee: Kohsuke Kawaguchi Richard Mortimer 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] [ssh-credentials] (JENKINS-24273) Presence of ECDSA SSH keys breaks SSH credentials plugin
SCM/JIRA link daemon resolved JENKINS-24273 as Fixed Presence of ECDSA SSH keys breaks SSH credentials plugin Change By: SCM/JIRA link daemon (15/Aug/14 7:46 PM) 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] [ssh-credentials] (JENKINS-24273) Presence of ECDSA SSH keys breaks SSH credentials plugin
SCM/JIRA link daemon commented on JENKINS-24273 Presence of ECDSA SSH keys breaks SSH credentials plugin Code changed in jenkins User: Stephen Connolly Path: src/main/java/com/cloudbees/jenkins/plugins/sshcredentials/impl/TrileadSSHPublicKeyAuthenticator.java http://jenkins-ci.org/commit/ssh-credentials-plugin/a5fb4045c3e50d651e32593a789310d01a31648a Log: [FIXED JENKINS-24273] Thrilead SSH throws IOE when passed an unknown keytype 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] [gerrit-trigger] (JENKINS-23871) Play-back Gerrit events which happened during a Jenkins downtime
Ivelin Bratanov commented on JENKINS-23871 Play-back Gerrit events which happened during a Jenkins downtime I'm not able to make this feature work with the latest release, version 2.11.1. I've ticked off the “Check non-reviewed patchsets” checkbox in the job. The builds are triggering fine while the connection between Jenkins and Gerrit is established, but no attempt is made to look for unreviewed patchsets in either of the following test cases: a) Shut down Jenkins, create a new patchset on Gerrit, and reboot from war file. b) Stop the connection from the server config page, create a new patchset on Gerrit, and start connection again. Any suggestions would be appreciated. Also, I've updated the issue description to include the limitations with regards to our requirement. 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] (JENKINS-22706) git fetching fails after switching from HTTPS to SSH
Mark Waite edited a comment on JENKINS-22706 git fetching fails after switching from HTTPS to SSH Thanks Emil Styrke for detecting that unexpected dependency which msysgit has on a temporary directory path which does not include spaces. I've confirmed the same behavior. If I set TEMP=C:\has a space\tmp and have that in the environment when I run my windows slave, then this exact failure appears when cloning from an ssh git URL. I'll consider what alternatives are available to at least inform the user from the git client plugin when such a problem happens. The work around is straightforward, but the messages in the failure do not give any hint that is the work around. 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-24272) jnlp slaves fail to reconnect when master is restarted
Richard Mortimer commented on JENKINS-24272 jnlp slaves fail to reconnect when master is restarted https://github.com/jenkinsci/remoting/pull/25 https://github.com/jenkinsci/jenkins/pull/1372 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-24272) jnlp slaves fail to reconnect when master is restarted
Richard Mortimer commented on JENKINS-24272 jnlp slaves fail to reconnect when master is restarted I propose to add a onReconnect() callback to the EngineListener interface in remoting. That gets called after the slave has detected that the master has recovered. The master then hooks into the new onReconnect() callback instead of onDisconnect() and restarts the slave at that point. I've tested this on my setup with both linux and windows slaves using old slave.jar; new slave.jar with old onDisconnect() restart callback and new slave.jar with new onReconnect() restart callback. All combinations interacted properly and the fix was observed to reconnect properly with the onReconnect() hooked up in the master. 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] (JENKINS-22706) git fetching fails after switching from HTTPS to SSH
Mark Waite assigned JENKINS-22706 to Mark Waite git fetching fails after switching from HTTPS to SSH Change By: Mark Waite (15/Aug/14 6:48 PM) Assignee: Nicolas De Loof Mark Waite 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] (JENKINS-22706) git fetching fails after switching from HTTPS to SSH
Mark Waite commented on JENKINS-22706 git fetching fails after switching from HTTPS to SSH Thanks Emil Styrke for detecting that unexpected dependency which msysgit has on a temporary directory path which does not include spaces. I'll consider what alternatives are available to at least inform the user from the git client plugin when such a problem happens. The work around is straightforward, but the messages in the failure do not give any hint that is the work around. 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-24253) Add JOB_LABELS environment variable
David Ruhmann commented on JENKINS-24253 Add JOB_LABELS environment variable Sure, I would enjoy that. I have read through the wiki about creating a plugin and have begun modifying a skeleton to implement a EnvironmentContributor, but the more examples the better 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] [findbugs] (JENKINS-24289) FindBugs Plugin does not honor setting "Only use stable builds as reference" being off
Ulli Hafner commented on JENKINS-24289 FindBugs Plugin does not honor setting "Only use stable builds as reference" being off Can you please add more details what you tried? 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-24253) Add JOB_LABELS environment variable
Daniel Beck commented on JENKINS-24253 Add JOB_LABELS environment variable https://github.com/daniel-beck/jenkins-joblabel-environment-plugin Very basic (no config, just always runs), and the exact behavior is up for discussion (e.g. set an empty value when not applicable). 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-24290) [ComputerListener] - Add the per-node onChanged callback
Oleg Nenashev assigned JENKINS-24290 to Oleg Nenashev [ComputerListener] - Add the per-node onChanged callback Change By: Oleg Nenashev (15/Aug/14 6:24 PM) Assignee: Oleg Nenashev 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] [delivery-pipeline] (JENKINS-24019) Absolute URLs in delivery pipeline break reverse proxy setups
Patrik Boström commented on JENKINS-24019 Absolute URLs in delivery pipeline break reverse proxy setups Have open a PR containing fixes where all absolute urls has been replaced by relative ones. https://github.com/Diabol/delivery-pipeline-plugin/pull/80 Will do some more testing and then merge to master and release. 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-24290) [ComputerListener] - Add the per-node onChanged callback
Oleg Nenashev started work on JENKINS-24290 [ComputerListener] - Add the per-node onChanged callback Change By: Oleg Nenashev (15/Aug/14 6:25 PM) Status: Open In Progress 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] [gerrit-trigger] (JENKINS-23871) Play-back Gerrit events which happened during a Jenkins downtime
Ivelin Bratanov updated JENKINS-23871 Play-back Gerrit events which happened during a Jenkins downtime Change By: Ivelin Bratanov (15/Aug/14 6:01 PM) Description: Use case: Jenkins become unavailable. In the meantime, there are a number of Gerrit events occurring which are missed. When Jenkins restarts, these missed events should be replayed.E.g. a designer submits a patch set during a Jenkins outage. Since Gerrit trigger is not firing, the patch will never be verified and merged, or will need to be done manually. There is a facility in Gerrit trigger to "manually" query events during a given period, but this will not scale as need to be done for each job.The requirement would be:1. It shall be possible to replay all "missing" Gerrit events for a given Jenkins master following a downtime of the master2. It shall be possible to have #1 trigger automatically i.e. that when Jenkins restart, all events that happened since last time it ran will be replayed.3. It shall be possible to trigger #1 manually. This capability shall be available only to the administrator role Limitations of current feature with regards to our requirement:- Only "patchset created" events are supported. Events such as "change merged," "comment added," or "ref updated" will be missed.- Gerrit projects specified via path or regular _expression_ will be ignored.- If a user submits a review to a patchset during the downtime, the build will not be triggered because the feature only looks at unreviewed patchsets.- It is not possible to trigger this feature manually. 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] (JENKINS-21861) option to include attachment with console.txt from failed slaves
Alex Earl commented on JENKINS-21861 option to include attachment with console.txt from failed slaves My IT department blocks most things, so I couldn't do it doing "work" hours. 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] [build-name-setter] (JENKINS-24277) BUILD_USER_ID not available for build-name-setter plugin.
Damien Nozay
commented on JENKINS-24277
BUILD_USER_ID not available for build-name-setter plugin.
the var is available in the environment in a shell build step.
Started by user damien
[EnvInject] - Loading node environment variables.
Building on master in workspace /jenkins_data/jenkins/jobs/playground/jobs/test-user/workspace
Unrecognized macro 'BUILD_USER_ID' in '#${BUILD_NUMBER} - by ${BUILD_USER_ID}'
[workspace] $ /bin/sh -xe /tmp/hudson4283431871309031896.sh
+ env
BUILD_CAUSE_MANUALTRIGGER=true
JOB_NAME=playground/test-user
BUILD_USER_ID=damien
BUILD_DISPLAY_NAME=#2
BUILD_CAUSE=MANUALTRIGGER
BUILD_ID=2014-08-15_11-01-01
...
BUILD_USER_FIRST_NAME=damien
BUILD_USER=damien
Unrecognized macro 'BUILD_USER_ID' in '#${BUILD_NUMBER} - by ${BUILD_USER_ID}'
Finished: SUCCESS
other issues:
job doesn't fail even though macro expansion failed.
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-24253) Add JOB_LABELS environment variable
Daniel Beck commented on JENKINS-24253 Add JOB_LABELS environment variable If you're interested I'm currently hacking something together as sample code/exercise. 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-24290) [ComputerListener] - Add the per-node onChanged callback
Oleg Nenashev created JENKINS-24290 [ComputerListener] - Add the per-node onChanged callback Issue Type: New Feature Assignee: Unassigned Components: core Created: 15/Aug/14 6:24 PM Description: The current implementation allows to track new changes only. BTW, the callback would be useful for mail-watcher plugin Project: Jenkins Priority: Major Reporter: Oleg Nenashev 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] [robot-plugin] (JENKINS-24281) Add option to move files during test result publishing
azam alias created JENKINS-24281 Add option to move files during test result publishing Issue Type: New Feature Assignee: jpiironen Attachments: move.png Components: robot-plugin Created: 15/Aug/14 7:08 AM Project: Jenkins Priority: Minor Reporter: azam alias 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] [xunit] (JENKINS-23564) PHPUnit test results from dataProvider tests are not parsed by xUnit
Gregory Boissinot commented on JENKINS-23564 PHPUnit test results from dataProvider tests are not parsed by xUnit By giving your test result file to xUnit it is OK. Could you attach a complete reproductible sample with the problem? 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-24282) Use noun phrases for new items
Tom FENNELLY commented on JENKINS-24282 Use noun phrases for new items strawboss-plugin: N/A tikal-multijob-plugin: Already OK jenkins.py: N/A jenkow-plugin: Couldn't install or build... looks dead drools-plugin: Deprecated - not in update center template-workflows-plugin: Already OK DotCi: N/A item-forwarder-plugin: N/A (and doesn't seem to be in the update center) jprt-plugin: Already OK external-monitor-job-plugin: Already OK literate-plugin: https://github.com/jenkinsci/literate-plugin/pull/5 branch-api-plugin: N/A ?? categorized-view-plugin: Already OK jobgenerator-plugin: Already OK matrix-project-plugin: https://github.com/jenkinsci/matrix-project-plugin/pull/6 maven-plugin: https://github.com/jenkinsci/maven-plugin/pull/27 maven-release-cascade-plugin: Already OK (was not able to build this though) build-flow-plugin: Already OK ivy-plugin: https://github.com/jenkinsci/ivy-plugin/pull/15 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] [nodelabelparameter] (JENKINS-24280) Environment variables get corrupted when using Node parameter
Andreas Kleber
updated JENKINS-24280
Environment variables get corrupted when using Node parameter
Change By:
Andreas Kleber
(15/Aug/14 6:46 AM)
Description:
When I use a Node parameter at my jobs, it is not possible for jenkins anymore to start a windows batch script on a windows slave, because cmd.exe can not be found
anymore
.If I use the Label parameter with that nodes name, everything works as expected.I do not kno if it is relevant but I also use the Environment Injector Plugin.
Running Jenkins: 1.554.3, Node and Label parameter plugin: 1.5.1, Environment Injector Plugin 1.89
{code}Started by user Andreas Kleber[EnvInject] - Loading node environment variables.Building remotely on basstu01 (puppet vdp vdk windows) in workspace c:\j\workspace\test-env[test-env] $ cmd /c call C:\Users\XXX\AppData\Local\Temp\hudson4333783914616487877.batThe parameter is incorrectFATAL: command execution failedjava.io.IOException: Cannot run program "cmd" (in directory "c:\j\workspace\test-env"): CreateProcess error=87, The parameter is incorrect at java.lang.ProcessBuilder.start(Unknown Source) at hudson.Proc$LocalProc.(Proc.java:244) at hudson.Proc$LocalProc.(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:773) at hudson.Launcher$ProcStarter.start(Launcher.java:353) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1023) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:990) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Unknown Source)Caused by: java.io.IOException: CreateProcess error=87, The parameter is incorrect at java.lang.ProcessImpl.create(Native Method) at java.lang.ProcessImpl.(Unknown Source) at java.lang.ProcessImpl.start(Unknown Source) ... 17 moreBuild step 'Execute Windows batch command' marked build as failureFinished: FAILURE{code}
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] [pretested-integration] (JENKINS-24285) Improve commit message
Andrius Ordojan created JENKINS-24285 Improve commit message Issue Type: New Feature Assignee: Praqma Support Components: pretested-integration Created: 15/Aug/14 10:56 AM Description: The commit messages from the most recent commit in the accumulated change set should be reused - concatenated with the name of the branch that has been integrated. Project: Jenkins Priority: Major Reporter: Andrius Ordojan 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] [envinject] (JENKINS-24287) EnvInject exposes password hashes
Walter Kacynski created JENKINS-24287 EnvInject exposes password hashes Issue Type: Bug Assignee: Gregory Boissinot Components: envinject Created: 15/Aug/14 1:36 PM Description: Currently, if a user without configuration access to a job can read the job they have access to the link "Environment variables". This allows the non-privileged user to see the password hashes. If they have Config access to a difference folder on the same master, they can use this password hash to expose the password and take control of the account. I propose that this link or at least the password hashes be restricted to only users with job config access. Project: Jenkins Priority: Critical Reporter: Walter Kacynski 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] [pretested-integration] (JENKINS-24284) In the commit message - don't write "origin"
Mads Nielsen assigned JENKINS-24284 to Praqma Support In the commit message - don't write "origin" Change By: Mads Nielsen (15/Aug/14 10:48 AM) Assignee: Alexander Uldall Praqma Support 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-24282) Use noun phrases for new items
Tom FENNELLY updated JENKINS-24282 Use noun phrases for new items Change By: Tom FENNELLY (15/Aug/14 8:11 AM) Attachment: target.png Attachment: current.png 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] [rqm] (JENKINS-24264) Better logging when execute fails (case 11732)
Mads Nielsen resolved JENKINS-24264 as Fixed Better logging when execute fails (case 11732) Change By: Mads Nielsen (15/Aug/14 6:40 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] [job-dsl-plugin] (JENKINS-24258) Broken Build Timeout Plugin implementation
Daniel Spilker resolved JENKINS-24258 as Fixed Broken Build Timeout Plugin implementation 1.25 will contain the fix. Change By: Daniel Spilker (15/Aug/14 9:18 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] [core] (JENKINS-24259) Unable to use custom update center as primary and jenkinsCI update center as secondary to install new plugins
Scott Hebert commented on JENKINS-24259 Unable to use custom update center as primary and jenkinsCI update center as secondary to install new plugins I believe I was initially swayed by the fact that there are a couple of places in the core where the default site is forced to be first site in the UpdatSite list: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/PluginManager.java#L767 This actually has the effect of putting the jenkinsci default site as the first one in the UI even though it is not the first in the config file. Updating the URL from UI alters the URL in the persisted config file but does not change its site order. Seems a bit confusing. In any event, Daniel, you are right! If I use the update center's self-reported ID as its ID in Jenkins, as follows: company-default https://update-center.company.com/update-center.json default http://updates.jenkins-ci.org/stable/update-center.json Then as long as https://update-center.company.com/update-center.json uses company-default as its ID, the corporate blessed plugin scenario works! I will resolve this issue. 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] [openid] (JENKINS-24288) Noclassdef found in openID plugin
Daniel Beck updated JENKINS-24288 Noclassdef found in openID plugin Seems unrelated to Plugin Usage Plugin (components, with few exceptions, are plugin names). Change By: Daniel Beck (15/Aug/14 3:18 PM) Component/s: openid Component/s: plugin-usage 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] [cobertura] (JENKINS-20706) Make Cobertura plug-in support multi-configuration (matrix) jobs
James Talton commented on JENKINS-20706 Make Cobertura plug-in support multi-configuration (matrix) jobs I pulled the latest code and merged in the changes from https://github.com/jenkinsci/cobertura-plugin/pull/26. The code coverage is indeed aggregated up and looks good on the matrix job. What is not working for us is that the code coverage thresholds are still being applied at each matrix run and not on the aggregated results. This causes a matrix run to fail even though the aggregated coverage is 100%. 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-24282) Use noun phrases for new items
Tom FENNELLY commented on JENKINS-24282 Use noun phrases for new items Freestyle Projects (english only): https://github.com/jenkinsci/jenkins/pull/1369 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-24259) Unable to use custom update center as primary and jenkinsCI update center as secondary to install new plugins
Scott Hebert edited a comment on JENKINS-24259 Unable to use custom update center as primary and jenkinsCI update center as secondary to install new plugins I believe I was initially swayed by the fact that there are a couple of places in the core where the default site is forced to be first site in the UpdateSite list: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/PluginManager.java#L767 This actually has the effect of putting the jenkinsci default site as the first one in the UI even though it is not the first in the config file. Updating the URL from UI alters the URL in the persisted config file but does not change its site order. Seems a bit confusing. In any event, Daniel, you are right! If I use the update center's self-reported ID as its ID in Jenkins, as follows: company-default https://update-center.company.com/update-center.json default http://updates.jenkins-ci.org/stable/update-center.json Then as long as https://update-center.company.com/update-center.json uses company-default as its ID, the corporate blessed plugin scenario works! I will resolve this issue. 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] [tap] (JENKINS-24245) Broken links on Tap Extended test results
Laurent Mazuel commented on JENKINS-24245 Broken links on Tap Extended test results In http://10.128.4.199:8180/jenkins/configure The "Jenkins Location" tab, the "Jenkins URL" is: http://10.128.4.199:8180/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-14583) Improve validation of 'builds dir' global setting
Maitrey Mishra commented on JENKINS-14583 Improve validation of 'builds dir' global setting Hi Bruce, I face the same issue of dead executors with jenkins-1.532.3. Coudl you please provide insights: Here is the log: Exception in thread "Executor #0 for master" java.lang.ClassCastException: hudson.model.FreeStyleBuild cannot be cast to hudson.model.Action at hudson.model.Run.onLoad(Run.java:331) at hudson.model.RunMap.retrieve(RunMap.java:223) at hudson.model.RunMap.retrieve(RunMap.java:59) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:688) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:671) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:470) at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:219) at hudson.tasks.Fingerprinter$FingerprintAction.compact(Fingerprinter.java:361) at hudson.tasks.Fingerprinter$FingerprintAction.onLoad(Fingerprinter.java:350) at hudson.model.Run.onLoad(Run.java:333) at hudson.model.RunMap.retrieve(RunMap.java:223) at hudson.model.RunMap.retrieve(RunMap.java:59) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:688) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:650) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:382) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:547) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:393) at jenkins.model.lazy.AbstractLazyLoadRunMap.newestBuild(AbstractLazyLoadRunMap.java:335) at hudson.model.AbstractProject.getLastBuild(AbstractProject.java:1089) at hudson.model.AbstractProject.getLastBuild(AbstractProject.java:152) at hudson.model.Job.isLogUpdated(Job.java:293) at hudson.model.AbstractProject.getCauseOfBlockage(AbstractProject.java:1285) at hudson.model.AbstractProject.isBuildBlocked(AbstractProject.java:1222) at hudson.model.Queue.isBuildBlocked(Queue.java:1021) at hudson.model.Queue.maintain(Queue.java:1080) at hudson.model.Queue.pop(Queue.java:935) at hudson.model.Executor.grabJob(Executor.java:297) at hudson.model.Executor.run(Executor.java:211) 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] [clearcase-ucm] (JENKINS-23920) The '&' Special character not handled with describe (case 11500)
Mads Nielsen resolved JENKINS-23920 as Fixed The '&' Special character not handled with describe (case 11500) Change By: Mads Nielsen (15/Aug/14 11:36 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] [unity3d-plugin] (JENKINS-24265) Wrong auto-detected editor.log PATH on system user on Windows
lacostej commented on JENKINS-24265 Wrong auto-detected editor.log PATH on system user on Windows I made a test and installed a Windows 2008 SP2 64 bits server on EC2. Installed java 64 bits on it (JDK7). I started the slave as JNLP and ran it as a service. Connected that server to my master, and sent it a simple job that runs a Windows batch command that does contains set java -version Here's the relevant output: ALLUSERSPROFILE=C:\ProgramData APPDATA=C:\Windows\system32\config\systemprofile\AppData\Roaming BASE=C:\Jenkins BUILD_CAUSE=MANUALTRIGGER BUILD_CAUSE_MANUALTRIGGER=true BUILD_DISPLAY_NAME=#3 BUILD_ID=2014-08-15_15-38-57 BUILD_NUMBER=3 BUILD_TAG=jenkins-unity3d-sample-project-lite-3 CommonProgramFiles=C:\Program Files\Common Files CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files ComSpec=C:\Windows\system32\cmd.exe DFSTRACINGON=FALSE EXECUTOR_NUMBER=0 FP_NO_HOST_CHECK=NO HUDSON_HOME=/Users/Shared/Jenkins/Home HUDSON_SERVER_COOKIE=6fd210b99c2cb227 JAVA_HOME=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home JENKINS_HOME=/Users/Shared/Jenkins/Home JOB_NAME=unity3d-sample-project-lite LOCALAPPDATA=C:\Windows\system32\config\systemprofile\AppData\Local NODE_LABELS=ec2-windows2008 windows2008 NODE_NAME=ec2-windows2008 OS=Windows_NT Path=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Amazon\cfn-bootstrap\ PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC PROCESSOR_ARCHITECTURE=AMD64 PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 62 Stepping 4, GenuineIntel PROCESSOR_LEVEL=6 PROCESSOR_REVISION=3e04 ProgramData=C:\ProgramData ProgramFiles=C:\Program Files ProgramFiles(x86)=C:\Program Files (x86) PROMPT=$P$G PSModulePath=C:\Windows\system32\WindowsPowerShell\v1.0\Modules\;C:\Program Files (x86)\AWS Tools\PowerShell\ PUBLIC=C:\Users\Public SystemDrive=C: SystemRoot=C:\Windows TEMP=C:\Windows\TEMP TMP=C:\Windows\TEMP TRACE_FORMAT_SEARCH_PATH=\\winseqfe\release\Windows6.0\lh_sp2rtm\6002.18005.090410-1830\amd64fre\symbols.pri\TraceFormat USERDOMAIN=WORKGROUP USERNAME=WIN-I4XX USERPROFILE=C:\Windows\system32\config\systemprofile windir=C:\Windows WORKSPACE=C:\Jenkins\workspace\unity3d-sample-project-lite C:\Jenkins\workspace\unity3d-sample-project-lite>java -version java version "1.7.0_67" Java(TM) SE Runtime Environment (build 1.7.0_67-b01) Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode) I also tried starting unity from the same job and indeed, unity uses the SysWOW64 directory to store the Editor.log So either a documentation bug, missunderstanding on how LOCALAPPDATA can be identified or bug in unity. Anyway, I highly suggest you to override the -logFile in the meantime. I suspect that in the future I will even override the -logFile argument for all jobs and replace it with the plugin's one. This in order to solve other problems, including complexity in the plugin code and piping issues. 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-22346) jenkins cli command with key fails with - java.io.EOFException
Daniel Christophis commented on JENKINS-22346 jenkins cli command with key fails with - java.io.EOFException Also broken in LTS Version 1.565.1. I get the following LDAP error when trying to use CLI commands: Exception in thread "Thread-XX" org.acegisecurity.userdetails.UsernameNotFoundException: User X not found in directory. at org.acegisecurity.ldap.search.FilterBasedLdapUserSearch.searchForUser(FilterBasedLdapUserSearch.java:126) at hudson.security.LDAPSecurityRealm$LDAPUserDetailsService.loadUserByUsername(LDAPSecurityRealm.java:787) at hudson.security.LDAPSecurityRealm$LDAPUserDetailsService.loadUserByUsername(LDAPSecurityRealm.java:738) at jenkins.security.ImpersonatingUserDetailsService.loadUserByUsername(ImpersonatingUserDetailsService.java:32) at hudson.model.User.impersonate(User.java:266) at org.jenkinsci.main.modules.cli.auth.ssh.SshCliAuthenticator.authenticate(SshCliAuthenticator.java:44) at hudson.cli.CliManagerImpl$2.run(CliManagerImpl.java:109) And of course related with this: Exception in thread "main" java.io.EOFException at java.io.DataInputStream.readBoolean(DataInputStream.java:244) at hudson.cli.Connection.readBoolean(Connection.java:95) at hudson.cli.CLI.authenticate(CLI.java:634) at hudson.cli.CLI._main(CLI.java:474) at hudson.cli.CLI.main(CLI.java:384) Any suggestions for temporary workarounds? 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] [job-dsl-plugin] (JENKINS-24258) Broken Build Timeout Plugin implementation
Daniel Spilker commented on JENKINS-24258 Broken Build Timeout Plugin implementation D'oh! Actually the fix was quite trivial. The plugin stores the value in milliseconds and we were generating the XML with seconds. https://github.com/jenkinsci/job-dsl-plugin/pull/262 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] [pretested-integration] (JENKINS-24286) Plugin tries to delete origin/master
Andrius Ordojan created JENKINS-24286 Plugin tries to delete origin/master Issue Type: Bug Assignee: Praqma Support Components: pretested-integration Created: 15/Aug/14 11:27 AM Description: The post build step should not execute if the plugin is disabled. Project: Jenkins Priority: Major Reporter: Andrius Ordojan 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] [envinject] (JENKINS-24283) Empty environment variables are deleted
Magnus Jacobsson updated JENKINS-24283 Empty environment variables are deleted Change By: Magnus Jacobsson (15/Aug/14 10:04 AM) Description: Empty environment variables are deleted. Three methods tried:1. Parameter2. Generate environment variables from script3. Inject environment variables to the build processAs can be seen from the log below, the non-empty variables MYVAR1, MYVAR3 & MYVAR5 works as expected, but the empty variables MYVAR2, MYVAR4 & MYVAR6 are not present in the environment when the job executes.When looking at the enviroment through the left hand menu "Environment Variables" on the build page , all variables are present. You can actually also see that an implicit environment varable variable TEST_NODE are is also deleted.I'm not sure that the problem is in EnvInject. Feel free to move it to some other component.Looks similar to JENKINS-15146.log:Started by user magjac[EnvInject] - Loading node environment variables.Building on master in workspace /srv/lhome/jenkins/jobs/empty_env_var_test/workspace[workspace] $ /bin/sh -xe /tmp/empty_env_var_test6599764777552559363.sh+ echo MYVAR3=world+ echo MYVAR4=[environment-script] Adding variable 'MYVAR4' with value ''[environment-script] Adding variable 'MYVAR3' with value 'world'[EnvInject] - Executing scripts and injecting environment variables after the SCM step.[EnvInject] - Injecting as environment variables the properties content MYVAR5=fooMYVAR6=[EnvInject] - Variables injected successfully.[workspace] $ /bin/sh -xe /tmp/hudson101371634758484537.sh+ envJENKINS_HOME=/srv/lhome/jenkinsMAIL=/var/mail/smokerUSER=smokerLC_TIME=en_DK.UTF-8MYVAR1=helloSHLVL=1NODE_LABELS=master master_label nullHUDSON_URL=http://smoketest.netinsight.se/jenkins/LD_LIBRARY_PATH=/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64/server:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64:/usr/lib/jvm/java-6-openjdk-amd64/jre/../lib/amd64MYVAR3=worldHOME=/home/smokerBUILD_URL=http://smoketest.netinsight.se/jenkins/job/empty_env_var_test/6/MYVAR5=fooJENKINS_SERVER_COOKIE=dad1862e4df27e29HUDSON_COOKIE=0cebdd7b-7b7f-4962-a07c-c1dc9a842ca6LC_CTYPE=sv_SE.UTF-8WORKSPACE=/srv/lhome/jenkins/jobs/empty_env_var_test/workspaceLOGNAME=smokerBUILD_CAUSE=MANUALTRIGGER_=/usr/bin/daemonEXECUTOR_NUMBER=380TERM=rxvtBUILD_DISPLAY_NAME=#6LC_COLLATE=sv_SE.UTF-8HUDSON_HOME=/srv/lhome/jenkinsPATH=/home/smoker/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/gamesBUILD_ID=2014-08-15_11-35-11BUILD_TAG=jenkins-empty_env_var_test-6DISPLAY=worabu.netinsight.se:0.0JENKINS_URL=http://smoketest.netinsight.se/jenkins/PYTHONUSERBASE=/home/smoker/.localLANG=CJOB_URL=http://smoketest.netinsight.se/jenkins/job/empty_env_var_test/BUILD_NUMBER=6NODE_PATH=/usr/lib/nodejs:/usr/lib/node_modules:/usr/share/_javascript_SHELL=/bin/bashHUDSON_SERVER_COOKIE=dad1862e4df27e29LC_MEASUREMENT=sv_SE.UTF-8JOB_NAME=empty_env_var_testPWD=/srv/lhome/jenkins/jobs/empty_env_var_test/workspaceLC_NUMERIC=sv_SE.UTF-8LC_PAPER=sv_SE.UTF-8BUILD_CAUSE_MANUALTRIGGER=trueFinished: SUCCESSmenu "Environment Variables":-_ /usr/bin/daemonBUILD_CAUSE MANUALTRIGGERBUILD_CAUSE_MANUALTRIGGER trueBUILD_DISPLAY_NAME #4BUILD_ID 2014-08-15_10-40-44BUILD_NUMBER 4BUILD_TAG jenkins-magjac-999-dev-smoke-fw025-nosa3-4BUILD_URL http://smoketest.netinsight.se/jenkins/job/magjac-999-dev-smoke-fw025-nosa3/4/BUILD_USER magjacBUILD_USER_FIRST_NAME magjacBUILD_USER_ID magjacCONFIG_FILE fw025.rcDISPLAY worabu.netinsight.se:0.0DO_COPY trueDO_INSTALL falseDO_PUBLISH falseDO_TEST trueEXECUTOR_NUMBER 324EXIT_ON_FAILURE falseGIT_ROOT /home/magjac/git_repos2HOME /home/smokerHUDSON_HOME /srv/lhome/jenkinsHUDSON_SERVER_COOKIE dad1862e4df27e29HUDSON_URL http://smoketest.netinsight.se/jenkins/JENKINS_HOME /srv/lhome/jenkinsJENKINS_SERVER_COOKIE dad1862e4df27e29JENKINS_URL http://smoketest.netinsight.se/jenkins/JOB_NAME magjac-999-dev-smoke-fw025-nosa3JOB_URL http://smoketest.netinsight.se/jenkins/job/magjac-999-dev-smoke-fw025-nosa3/LANG CLC_COLLATE sv_SE.UTF-8LC_CTYPE sv_SE.UTF-8LC_MEASUREMENT sv_SE.UTF-8LC_NUMERIC sv_SE.UTF-8LC_PAPER sv_SE.UTF-8LC_TIME en_DK.UTF-8LD_LIBRARY_PATH /usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64/server:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64:/usr/lib/jvm/j
[JIRA] [tap] (JENKINS-24245) Broken links on Tap Extended test results
Laurent Mazuel commented on JENKINS-24245 Broken links on Tap Extended test results Jenkins version 1.559 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-24282) Use noun phrases for new items
Tom FENNELLY
edited a comment on JENKINS-24282
Use noun phrases for new items
The following are trimmed down greps of what I think might need to be looked at (across all repos in the jenkinsci github org).
TopLevelItemDescriptor:
./repos/strawboss-plugin/src/main/java/captmorgan/ExternalProject.java: public static final class DescriptorImpl extends TopLevelItemDescriptor {
./repos/tikal-multijob-plugin/src/main/java/com/tikal/jenkins/plugins/multijob/views/AbstractWrapper.java: public TopLevelItemDescriptor getDescriptor() {
./repos/jenkins.py/python-wrapper/src/main/java/jenkins/python/descriptor/TopLevelItemDescriptorPW.java:public abstract class TopLevelItemDescriptorPW extends TopLevelItemDescriptor {
./repos/jenkow-plugin/jenkow-plugin/src/main/java/com/cisco/step/jenkins/plugins/jenkow/JenkowWorkflowJob.java://public static class DescriptorImpl extends TopLevelItemDescriptor {
./repos/drools-plugin/drools/src/main/java/hudson/drools/DroolsProject.java:public static final class DescriptorImpl extends TopLevelItemDescriptor {
./repos/template-workflows-plugin/src/main/java/org/jenkins/plugin/templateWorkflows/TemplatesWorkflowJob.java:public TopLevelItemDescriptor getDescriptor() {
./repos/DotCi/src/main/java/com/groupon/jenkins/dynamic/organizationcontainer/OrganizationContainer.java: public static class DescriptorImpl extends TopLevelItemDescriptor {
./repos/item-forwarder-plugin/src/main/java/org/jenkinsci/plugins/item_forwarding/ForwardingItem.java:public static class DescriptorImpl extends TopLevelItemDescriptor {
./repos/jprt-plugin/src/main/java/hudson/plugins/jprt/JPRTJob.java:public TopLevelItemDescriptor getDescriptor() {
./repos/external-monitor-job-plugin/src/main/java/hudson/model/ExternalJob.java:public static final class DescriptorImpl extends TopLevelItemDescriptor {
./repos/literate-plugin/src/main/java/org/cloudbees/literate/jenkins/LiterateBranchProject.java:public TopLevelItemDescriptor getDescriptor() {
./repos/branch-api-plugin/src/main/java/jenkins/branch/MultiBranchProjectDescriptor.java:public abstract class MultiBranchProjectDescriptor extends TopLevelItemDescriptor {
./repos/categorized-view-plugin/src/main/java/org/jenkinsci/plugins/categorizedview/GroupTopLevelItem.java: public TopLevelItemDescriptor getDescriptor() {
AbstractProjectDescriptor:
./repos/tikal-multijob-plugin/src/main/java/com/tikal/jenkins/plugins/multijob/MultiJobProject.java: public static final class DescriptorImpl extends AbstractProjectDescriptor {
./repos/jobgenerator-plugin/src/main/java/org/jenkinsci/plugins/jobgenerator/JobGenerator.java: extends AbstractProjectDescriptor {
./repos/matrix-project-plugin/src/main/java/hudson/matrix/MatrixProject.java:public static final class DescriptorImpl extends AbstractProjectDescriptor {
./repos/template-workflows-plugin/src/main/java/org/jenkins/plugin/templateWorkflows/TemplatesWorkflowJob.java:public static final class DescriptorImpl extends AbstractProjectDescriptor {
./repos/DotCi/src/main/java/com/groupon/jenkins/dynamic/build/DynamicProject.java: public static final class DescriptorImpl extends AbstractProjectDescriptor {
./repos/maven-plugin/src/main/java/hudson/maven/MavenModuleSet.java:public static final class DescriptorImpl extends AbstractProjectDescriptor {
./repos/maven-release-cascade-plugin/src/main/java/com/barchart/jenkins/cascade/CascadeProject.java: public static class TheDescriptor extends AbstractProjectDescriptor {
./repos/build-flow-plugin/src/main/java/com/cloudbees/plugins/flow/BuildFlow.java:public static class BuildFlowDescriptor extends AbstractProjectDescriptor {
./repos/literate-plugin/src/main/java/org/cloudbees/literate/jenkins/LiterateBranchProject.java:public static class DescriptorImpl extends AbstractProjectDescriptor {
./repos/ivy-plugin/src/main/java/hudson/ivy/IvyModuleSet.java:public static final class DescriptorImpl extends AbstractProjectDescriptor {
What else should I search for?
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
[JIRA] [envinject] (JENKINS-24283) Empty environment variables are deleted
Magnus Jacobsson created JENKINS-24283 Empty environment variables are deleted Issue Type: Bug Assignee: Gregory Boissinot Components: envinject Created: 15/Aug/14 10:01 AM Description: Empty environment variables are deleted. Three methods tried: 1. Parameter 2. Generate environment variables from script 3. Inject environment variables to the build process As can be seen from the log below, the non-empty variables MYVAR1, MYVAR3 & MYVAR5 works as expected, but the empty variables MYVAR2, MYVAR4 & MYVAR6 are not present in the environment when the job executes. When looking at the enviroment through the left hand menu "Environment Variables" on the build page all variables are present. You can actually also see that an implicit environment varable TEST_NODE are also deleted. I'm not that the problem is in EnvInject. Feel free to move it to some other component. Looks similar to JENKINS-15146. log: Started by user magjac [EnvInject] - Loading node environment variables. Building on master in workspace /srv/lhome/jenkins/jobs/empty_env_var_test/workspace [workspace] $ /bin/sh -xe /tmp/empty_env_var_test6599764777552559363.sh + echo MYVAR3=world + echo MYVAR4= [environment-script] Adding variable 'MYVAR4' with value '' [environment-script] Adding variable 'MYVAR3' with value 'world' [EnvInject] - Executing scripts and injecting environment variables after the SCM step. [EnvInject] - Injecting as environment variables the properties content MYVAR5=foo MYVAR6= [EnvInject] - Variables injected successfully. [workspace] $ /bin/sh -xe /tmp/hudson101371634758484537.sh + env JENKINS_HOME=/srv/lhome/jenkins MAIL=/var/mail/smoker USER=smoker LC_TIME=en_DK.UTF-8 MYVAR1=hello SHLVL=1 NODE_LABELS=master master_label null HUDSON_URL=http://smoketest.netinsight.se/jenkins/ LD_LIBRARY_PATH=/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64/server:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64:/usr/lib/jvm/java-6-openjdk-amd64/jre/../lib/amd64 MYVAR3=world HOME=/home/smoker BUILD_URL=http://smoketest.netinsight.se/jenkins/job/empty_env_var_test/6/ MYVAR5=foo JENKINS_SERVER_COOKIE=dad1862e4df27e29 HUDSON_COOKIE=0cebdd7b-7b7f-4962-a07c-c1dc9a842ca6 LC_CTYPE=sv_SE.UTF-8 WORKSPACE=/srv/lhome/jenkins/jobs/empty_env_var_test/workspace LOGNAME=smoker BUILD_CAUSE=MANUALTRIGGER _=/usr/bin/daemon EXECUTOR_NUMBER=380 TERM=rxvt BUILD_DISPLAY_NAME=#6 LC_COLLATE=sv_SE.UTF-8 HUDSON_HOME=/srv/lhome/jenkins PATH=/home/smoker/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games BUILD_ID=2014-08-15_11-35-11 BUILD_TAG=jenkins-empty_env_var_test-6 DISPLAY=worabu.netinsight.se:0.0 JENKINS_URL=http://smoketest.netinsight.se/jenkins/ PYTHONUSERBASE=/home/smoker/.local LANG=C JOB_URL=http://smoketest.netinsight.se/jenkins/job/empty_env_var_test/ BUILD_NUMBER=6 NODE_PATH=/usr/lib/nodejs:/usr/lib/node_modules:/usr/share/_javascript_ SHELL=/bin/bash HUDSON_SERVER_COOKIE=dad1862e4df27e29 LC_MEASUREMENT=sv_SE.UTF-8 JOB_NAME=empty_env_var_test PWD=/srv/lhome/jenkins/jobs/empty_env_var_test/workspace LC_NUMERIC=sv_SE.UTF-8 LC_PAPER=sv_SE.UTF-8 BUILD_CAUSE_MANUALTRIGGER=true Finished: SUCCESS menu "Environment Variables": - _ /usr/bin/daemon BUILD_CAUSE MANUALTRIGGER BUILD_CAUSE_MANUALTRIGGER true BUILD_DISPLAY_NAME #4 BUILD_ID 2014-08-15_10-40-44 BUILD_NUMBER 4 BUILD_TAG jenkins-magjac-999-dev-smoke-fw025-nosa3-4 BUILD_URL http://smoketest.netinsight.se/jenkins/job/magjac-999-dev-smoke-fw025-nosa3/4/ BUILD_USER magjac BUILD_USER_FIRST_NAME magjac BUILD_USER_ID magjac CONFIG_FILE fw025.rc DISPLAY worabu.netinsight.se:0.0 DO_COPY true DO_INSTALL false DO_PUBLISH false DO_TEST true EXECUTOR_NUMBER 324 EXIT_ON_FAILURE false GIT_ROOT /home/magjac/git_repos2 HOME /home/smoker HUDSON_HOME /srv/lhome/jenkins HUDSON_SERVER_COOKIE dad1862e4df27e29 HUDSON_URL http://smoketest.netinsight.se/jenkins/ JENKINS_HOME /srv/lhome/jenkins JENKINS_SERVER_COOKIE dad1862e4df27e29 JENKINS_URL http://smoketest.netinsight.se/jenkins/ JOB_NAME magjac-999-dev-smoke-fw025-nosa3 JOB_URL http://smoketest.netinsight.se/jenkins/job/magjac-999-dev-smoke-f
[JIRA] [build-name-setter] (JENKINS-24277) BUILD_USER_ID not available for build-name-setter plugin.
Daniel Beck commented on JENKINS-24277 BUILD_USER_ID not available for build-name-setter plugin. Does the variable exist when you run env (in a Shell build step) or set (in a Batch build step)? 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] [config-rotator] (JENKINS-23653) Improve performance while establishing view (case 11425)
Mads Nielsen resolved JENKINS-23653 as Fixed Improve performance while establishing view (case 11425) Change By: Mads Nielsen (15/Aug/14 12:09 PM) 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] [core] (JENKINS-24282) Use noun phrases for new items
SCM/JIRA link daemon commented on JENKINS-24282 Use noun phrases for new items Code changed in jenkins User: Kevin Formsma Path: src/main/resources/hudson/ivy/Messages.properties http://jenkins-ci.org/commit/ivy-plugin/a0f6060f61592ae39d667389e22f6f1f4b6693bc Log: Merge pull request #15 from jenkinsci/JENKINS-24282 Use noun phrases for new items JENKINS-24282 Compare: https://github.com/jenkinsci/ivy-plugin/compare/e2394a70c8cd...a0f6060f6159 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] (JENKINS-24261) Assembla browser breaks config page
Mark Waite started work on JENKINS-24261 Assembla browser breaks config page Change By: Mark Waite (15/Aug/14 11:07 AM) Status: Open In Progress 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] [maven2] (JENKINS-6763) Hudson does not set JAVA_HOME for Maven Builds
Damon Overboe edited a comment on JENKINS-6763 Hudson does not set JAVA_HOME for Maven Builds On Jenkins 1.575, working against Windows Server 2012, setting the JDK in Jenkins provides the option to input the JAVA_HOME variable, and that worked around the issue for me. This might be what you were referring to as having it set twice, but given that it seems to completely ignore JAVA_HOME on the clients (even though it reports that correctly with the script console) it doesn't seem to cause any issues. Here were my steps: Manage Jenkins Configure System Scroll to JDK installations Add JDK Installation Provide JAVA_HOME path to the JDK folder on the client/slave such as `C:\Progra~2\Java\jdk1.7.0_67` where Proga~2 is Program Files (x86) 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] [nodelabelparameter] (JENKINS-24280) Environment variables get corrupted when using Node parameter
Andreas Kleber created JENKINS-24280 Environment variables get corrupted when using Node parameter Issue Type: Bug Assignee: Dominik Bartholdi Components: nodelabelparameter Created: 15/Aug/14 6:45 AM Description: When I use a Node parameter at my jobs, it is not possible for jenkins anymore to start a windows batch script on a windows slave, because cmd.exe can not be found anymore. If I use the Label parameter with that nodes name, everything works as expected. I do not kno if it is relevant but I also use the Environment Injector Plugin. Running Jenkins: 1.554.3, Node and Label parameter plugin: 1.5.1, Environment Injector Plugin 1.89 Started by user Andreas Kleber [EnvInject] - Loading node environment variables. Building remotely on basstu01 (puppet vdp vdk windows) in workspace c:\j\workspace\test-env [test-env] $ cmd /c call C:\Users\XXX\AppData\Local\Temp\hudson4333783914616487877.bat The parameter is incorrect FATAL: command execution failed java.io.IOException: Cannot run program "cmd" (in directory "c:\j\workspace\test-env"): CreateProcess error=87, The parameter is incorrect at java.lang.ProcessBuilder.start(Unknown Source) at hudson.Proc$LocalProc.(Proc.java:244) at hudson.Proc$LocalProc.(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:773) at hudson.Launcher$ProcStarter.start(Launcher.java:353) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1023) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:990) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Unknown Source) Caused by: java.io.IOException: CreateProcess error=87, The parameter is incorrect at java.lang.ProcessImpl.create(Native Method) at java.lang.ProcessImpl.(Unknown Source) at java.lang.ProcessImpl.start(Unknown Source) ... 17 more Build step 'Execute Windows batch command' marked build as failure Finished: FAILURE Project: Jenkins Priority: Major Reporter: Andreas Kleber 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] [ssh-credentials] (JENKINS-24273) Presence of ECDSA SSH keys breaks SSH credentials plugin
Hendrik Halkow updated JENKINS-24273 Presence of ECDSA SSH keys breaks SSH credentials plugin Change By: Hendrik Halkow (14/Aug/14 6:52 PM) Summary: Presence of ECDSA SSH keys break breaks SSH credentials 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] [cli] (JENKINS-18824) Build Causer doesn't resolve CLI based usernames
dogfood commented on JENKINS-18824 Build Causer doesn't resolve CLI based usernames Integrated in jenkins_main_trunk #3620 JENKINS-18824 prevent failure when startedBy is ‘unknown’ (Revision 3efe07f563d30a38cf405a20c9145c3ea88e5051) Result = SUCCESS Nicolas De Loof : 3efe07f563d30a38cf405a20c9145c3ea88e5051 Files : core/src/main/java/hudson/cli/BuildCommand.java 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] [recipe] (JENKINS-22241) Recipe export does not properly quote non-ASCII characters in the job description field
Steven Christou assigned JENKINS-22241 to Steven Christou Recipe export does not properly quote non-ASCII characters in the job description field Change By: Steven Christou (15/Aug/14 10:02 AM) Assignee: Steven Christou 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-14191) Load Statistics: Exponential Moving Average artifacts make interpretation difficult
Daniel Beck commented on JENKINS-14191 Load Statistics: Exponential Moving Average artifacts make interpretation difficult Martina Oefelein Do you think you'll have time to test these soon? 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-24259) Unable to use custom update center as primary and jenkinsCI update center as secondary to install new plugins
Scott Hebert resolved JENKINS-24259 as Not A Defect Unable to use custom update center as primary and jenkinsCI update center as secondary to install new plugins Change By: Scott Hebert (15/Aug/14 3:51 PM) Status: Open Resolved Resolution: Not A Defect 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] [clearcase-ucm] (JENKINS-23246) Performance improvement, use generated load rule to swipe workspace (case 11387)
Mads Nielsen resolved JENKINS-23246 as Fixed Performance improvement, use generated load rule to swipe workspace (case 11387) Change By: Mads Nielsen (15/Aug/14 11:38 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] [core] (JENKINS-24253) Add JOB_LABELS environment variable
David Ruhmann commented on JENKINS-24253 Add JOB_LABELS environment variable @Daniel, Thanks for your input. I will look into creating a 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] [github] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
Rich Schumacher commented on JENKINS-23641 Builds are failing due to GitHubCommitNotifier exception Just wanted to throw my name into the ring as someone who is also hung up on this bug. 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] [valgrind] (JENKINS-24256) Fail build for missing / erroneous valgrind publisher XMLs
Johannes Ohlemacher commented on JENKINS-24256 Fail build for missing / erroneous valgrind publisher XMLs Sounds reasonable and should be easy to integrate. I am pretty busy right now, but i will try to look into it within the next couple of days. 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] [cygpath] (JENKINS-20364) Failed to locate cygwin installation
Greg Warner
commented on JENKINS-20364
Failed to locate cygwin installation
I'm seeing this bug too. I ran the failing line using the jython console. I tried both "SOFTWARECygwin" and "SOFTWARE\\Wow6432NodeCygwin" and they both failed. It does, however, find plain ol' "SOFTWARE". Also, I try other keys such as "SOFTWARE[Motorola,Intel,TrendMicro" and it finds all of them. So this seems to be a cygwin-specific problem.
>>> RegistryKey.LOCAL_MACHINE.openReadonly("SOFTWARECygwin")
Traceback (most recent call last):
File "", line 1, in
at hudson.util.jna.RegistryKey.check(RegistryKey.java:124)
at hudson.util.jna.RegistryKey.open(RegistryKey.java:223)
at hudson.util.jna.RegistryKey.openReadonly(RegistryKey.java:218)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
hudson.util.jna.JnaException: hudson.util.jna.JnaException: Win32 error: 2 - The
system cannot find the file specified
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] [unity3d-plugin] (JENKINS-23958) Pipe Broken
lacostej commented on JENKINS-23958 Pipe Broken Note I've posted on the dev list for a bit of help: https://groups.google.com/d/msg/jenkinsci-dev/LjHaBd6yUW8/LstWtVCaOHwJ "Troubleshooting remoting related input/output stream piping issues" 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] [clearcase] (JENKINS-17096) Differences in config spec detected when config spec is read from file
Vincent Latombe commented on JENKINS-17096 Differences in config spec detected when config spec is read from file According to the commit information, this has been included since release 1.4 but I forgot to update the issue. 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] [active-directory] (JENKINS-20064) Cannot use CLI or URL with API token with Active Directory as the access control security realm
Daniel Christophis commented on JENKINS-20064 Cannot use CLI or URL with API token with Active Directory as the access control security realm Also broken in LTS Version 1.565.1. I get the following LDAP error when trying to use CLI commands: Exception in thread "Thread-XX" org.acegisecurity.userdetails.UsernameNotFoundException: User X not found in directory. at org.acegisecurity.ldap.search.FilterBasedLdapUserSearch.searchForUser(FilterBasedLdapUserSearch.java:126) at hudson.security.LDAPSecurityRealm$LDAPUserDetailsService.loadUserByUsername(LDAPSecurityRealm.java:787) at hudson.security.LDAPSecurityRealm$LDAPUserDetailsService.loadUserByUsername(LDAPSecurityRealm.java:738) at jenkins.security.ImpersonatingUserDetailsService.loadUserByUsername(ImpersonatingUserDetailsService.java:32) at hudson.model.User.impersonate(User.java:266) at org.jenkinsci.main.modules.cli.auth.ssh.SshCliAuthenticator.authenticate(SshCliAuthenticator.java:44) at hudson.cli.CliManagerImpl$2.run(CliManagerImpl.java:109) And of course this: Exception in thread "main" java.io.EOFException at java.io.DataInputStream.readBoolean(DataInputStream.java:244) at hudson.cli.Connection.readBoolean(Connection.java:95) at hudson.cli.CLI.authenticate(CLI.java:634) at hudson.cli.CLI._main(CLI.java:474) at hudson.cli.CLI.main(CLI.java:384) Any suggestions for temporary workarounds? 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] [unity3d-plugin] (JENKINS-24265) Wrong auto-detected editor.log PATH on system user on Windows
lacostej commented on JENKINS-24265 Wrong auto-detected editor.log PATH on system user on Windows I reported issue #626407 @ unity 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] [build-timeout] (JENKINS-24279) run custom shell script on Build timeout as pre-on-timeout hook
Mike Dubman created JENKINS-24279 run custom shell script on Build timeout as pre-on-timeout hook Issue Type: Improvement Affects Versions: current Assignee: Kohsuke Kawaguchi Components: build-timeout Created: 15/Aug/14 5:52 AM Description: Hi, Is that possible to allow running shell script command before taking action when timeout occures (action like fail/abort). The use-case for this request is to extract stacktraces with "gstack" or "gdb" from hanging job before build-timeout aborts it? Also, as addition pre-ontimeout action, plugin can send email to specific address and wait for some sentinel file to be removed by user. This will allow developer to connect to the hanging job, examine/debug hang, remove sentinel file and job will resume abort/fail routine. Thanks Environment: linux Project: Jenkins Labels: build-tmeout Priority: Major Reporter: Mike Dubman 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] [active-directory] (JENKINS-20064) Cannot use CLI or URL with API token with Active Directory as the access control security realm
Daniel Christophis edited a comment on JENKINS-20064 Cannot use CLI or URL with API token with Active Directory as the access control security realm Also broken in LTS Version 1.565.1. I get the following LDAP error when trying to use CLI commands: Exception in thread "Thread-XX" org.acegisecurity.userdetails.UsernameNotFoundException: User X not found in directory. at org.acegisecurity.ldap.search.FilterBasedLdapUserSearch.searchForUser(FilterBasedLdapUserSearch.java:126) at hudson.security.LDAPSecurityRealm$LDAPUserDetailsService.loadUserByUsername(LDAPSecurityRealm.java:787) at hudson.security.LDAPSecurityRealm$LDAPUserDetailsService.loadUserByUsername(LDAPSecurityRealm.java:738) at jenkins.security.ImpersonatingUserDetailsService.loadUserByUsername(ImpersonatingUserDetailsService.java:32) at hudson.model.User.impersonate(User.java:266) at org.jenkinsci.main.modules.cli.auth.ssh.SshCliAuthenticator.authenticate(SshCliAuthenticator.java:44) at hudson.cli.CliManagerImpl$2.run(CliManagerImpl.java:109) And of course related with this: Exception in thread "main" java.io.EOFException at java.io.DataInputStream.readBoolean(DataInputStream.java:244) at hudson.cli.Connection.readBoolean(Connection.java:95) at hudson.cli.CLI.authenticate(CLI.java:634) at hudson.cli.CLI._main(CLI.java:474) at hudson.cli.CLI.main(CLI.java:384) Any suggestions for temporary workarounds? 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] [envinject] (JENKINS-24287) EnvInject exposes password hashes
Daniel Beck commented on JENKINS-24287 EnvInject exposes password hashes they can use this password hash to expose the password and take control of the account Could you provide steps to reproduce this? 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-24282) Use noun phrases for new items
SCM/JIRA link daemon commented on JENKINS-24282 Use noun phrases for new items Code changed in jenkins User: tfennelly Path: src/main/resources/hudson/maven/Messages.properties http://jenkins-ci.org/commit/maven-plugin/354a762b3250c8a92edc640151fb1f48083c14a1 Log: Use noun phrases for new items JENKINS-24282 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] [build-timeout] (JENKINS-24279) run custom shell script on Build timeout as pre-on-timeout hook
Mike Dubman updated JENKINS-24279 run custom shell script on Build timeout as pre-on-timeout hook Change By: Mike Dubman (15/Aug/14 5:53 AM) Description: Hi,Is that possible to allow running shell script /inline command before taking action when timeout occures (action like fail/abort).The use-case for this request is to extract stacktraces with "gstack" or "gdb" from hanging job before build-timeout aborts it?Also, as addition pre-ontimeout action, plugin can send email to specific address and wait for some sentinel file to be removed by user. This will allow developer to connect to the hanging job, examine/debug hang, remove sentinel file and job will resume abort/fail routine.Thanks 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] [ssh-slaves] (JENKINS-20108) SSH slaves can block for a long time in NativePRNG
Jesse Glick assigned JENKINS-20108 to Unassigned SSH slaves can block for a long time in NativePRNG Change By: Jesse Glick (15/Aug/14 2:22 PM) Assignee: Kohsuke Kawaguchi 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.
