[JIRA] [ghprb-plugin] (JENKINS-22253) Problems Parsing
Kanstantsin Shautsou
edited a comment on JENKINS-22253
Problems Parsing
GitHub pull request #2043 of commit ef734b7d25172541d671f1ab5c032a2f8a0caa2b automatically merged.
[EnvInject] - Loading node environment variables.
[EnvInject] - Preparing an environment for the build.
[EnvInject] - Keeping Jenkins system variables.
[EnvInject] - Keeping Jenkins build variables.
[EnvInject] - Injecting as environment variables the properties content
[EnvInject] - Variables injected successfully.
[EnvInject] - Injecting contributions.
Building remotely on Node1 in workspace /var/lib/jenkins/workspace/PR-builder
Wiping out workspace first.
Cloning the remote Git repository
Cloning repository g...@github.com:project/repo.git
> git init /var/lib/jenkins/workspace/PR-builder # timeout=10
Fetching upstream changes from g...@github.com:project/repo.git
> git --version # timeout=10
> git fetch --tags --progress g...@github.com:project/repo.git +refs/heads/*:refs/remotes/origin/*
> git config remote.origin.url g...@github.com:project/repo.git # timeout=10
> git config remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
> git config remote.origin.url g...@github.com:project/repo.git # timeout=10
Fetching upstream changes from g...@github.com:project/repo.git
> git fetch --tags --progress g...@github.com:project/repo.git +refs/pull/*:refs/remotes/origin/pr/*
> git rev-parse origin/pr/2043/merge^{commit} # timeout=10
FATAL: Command "git rev-parse origin/pr/2043/merge^{commit}" returned status code 128:
stdout: origin/pr/2043/merge^{commit}
stderr: fatal: ambiguous argument 'origin/pr/2043/merge^{commit}': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions
hudson.plugins.git.GitException: Command "git rev-parse origin/pr/2043/merge^{commit}" returned status code 128:
stdout: origin/pr/2043/merge^{commit}
stderr: fatal: ambiguous argument 'origin/pr/2043/merge^{commit}': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1435)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1411)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1407)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1110)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1120)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.revParse(CliGitAPIImpl.java:516)
at hudson.plugins.git.GitAPI.revParse(GitAPI.java:257)
at sun.reflect.GeneratedMethodAccessor52.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:310)
at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:290)
at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:249)
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.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
GitHub Pull Request Builder 1.16-5
GitHub plugin 1.9.1
GIT plugin 2.2.7
Jenkins GIT client plugin 1.11.0
Can this issue be caused because of closed/merged PR?
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
[JIRA] [ghprb-plugin] (JENKINS-22253) Problems Parsing
Kanstantsin Shautsou
commented on JENKINS-22253
Problems Parsing
GitHub pull request #2043 of commit ef734b7d25172541d671f1ab5c032a2f8a0caa2b automatically merged.
[EnvInject] - Loading node environment variables.
[EnvInject] - Preparing an environment for the build.
[EnvInject] - Keeping Jenkins system variables.
[EnvInject] - Keeping Jenkins build variables.
[EnvInject] - Injecting as environment variables the properties content
[EnvInject] - Variables injected successfully.
[EnvInject] - Injecting contributions.
Building remotely on Node1 in workspace /var/lib/jenkins/workspace/PR-builder
Wiping out workspace first.
Cloning the remote Git repository
Cloning repository g...@github.com:project/repo.git
> git init /var/lib/jenkins/workspace/PR-builder # timeout=10
Fetching upstream changes from g...@github.com:project/repo.git
> git --version # timeout=10
> git fetch --tags --progress g...@github.com:project/repo.git +refs/heads/*:refs/remotes/origin/*
> git config remote.origin.url g...@github.com:project/repo.git # timeout=10
> git config remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
> git config remote.origin.url g...@github.com:project/repo.git # timeout=10
Fetching upstream changes from g...@github.com:project/repo.git
> git fetch --tags --progress g...@github.com:project/repo.git +refs/pull/*:refs/remotes/origin/pr/*
> git rev-parse origin/pr/2043/merge^{commit} # timeout=10
FATAL: Command "git rev-parse origin/pr/2043/merge^{commit}" returned status code 128:
stdout: origin/pr/2043/merge^{commit}
stderr: fatal: ambiguous argument 'origin/pr/2043/merge^{commit}': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions
hudson.plugins.git.GitException: Command "git rev-parse origin/pr/2043/merge^{commit}" returned status code 128:
stdout: origin/pr/2043/merge^{commit}
stderr: fatal: ambiguous argument 'origin/pr/2043/merge^{commit}': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1435)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1411)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1407)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1110)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1120)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.revParse(CliGitAPIImpl.java:516)
at hudson.plugins.git.GitAPI.revParse(GitAPI.java:257)
at sun.reflect.GeneratedMethodAccessor52.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:310)
at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:290)
at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:249)
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.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
GitHub Pull Request Builder 1.16-5
GitHub plugin 1.9.1
GIT plugin 2.2.7
Jenkins GIT client plugin 1.11.0
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] [ghprb-plugin] (JENKINS-25235) NPE on run()
Kanstantsin Shautsou commented on JENKINS-25235 NPE on run() Yes, many, for the same job. 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] [junit-plugin] (JENKINS-25340) lost trend history after skipping build
Kanstantsin Shautsou commented on JENKINS-25340 lost trend history after skipping build FreeStyle. When new success/unstable jobs appeared - only new jobs appeared in Trend. Then i deleted skipped builds and graph is still without not full. 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] [junit-plugin] (JENKINS-25340) lost trend history after skipping build
Kanstantsin Shautsou edited a comment on JENKINS-25340 lost trend history after skipping build FreeStyle. When new success/unstable jobs appeared - only new jobs appeared in Trend. Then i deleted skipped builds and graph is still not full. 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] [junit-plugin] (JENKINS-25340) lost trend history after skipping build
Kanstantsin Shautsou commented on JENKINS-25340 lost trend history after skipping build Hm... afair AbstractProject.getNewBuilds() is limited with 100 jobs... isn't this limit enough for showing default trend without performance degradation? 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] [cucumber-testresult-plugin] (JENKINS-25340) lost trend history after skipping build
Kanstantsin Shautsou reopened JENKINS-25340 lost trend history after skipping build This is blocker for me. I'm limiting number of jobs to what i want see in trend - it's near 30, not sure what performance issues it may cause and what you want expect from core. Also we can't use Jenkins test results now. Do you have core issue that maybe linked to this issue? Change By: Kanstantsin Shautsou (28/Oct/14 4:48 PM) Resolution: Won't Fix Status: Resolved Reopened 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] [cucumber-testresult-plugin] (JENKINS-25340) lost trend history after skipping build
Kanstantsin Shautsou created JENKINS-25340 lost trend history after skipping build Issue Type: Bug Assignee: teilo Components: cucumber-testresult-plugin Created: 28/Oct/14 1:58 PM Description: I had trend history, then aborted two builds (run job and press abort), after it trend history graph become clear. After 2 builds graph filled back with 2 results (but before abort results still doesn't appeared). Environment: core: 1.565.3 LTS plugin: 0.6.0 Project: Jenkins Priority: Major Reporter: Kanstantsin Shautsou 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] [maven-metadata-plugin] (JENKINS-18138) Value is not stored as parameter for later use
Kanstantsin Shautsou updated JENKINS-18138 Value is not stored as parameter for later use Change By: Kanstantsin Shautsou (17/Oct/14 11:34 AM) Priority: Blocker Minor 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] [maven-metadata-plugin] (JENKINS-18138) Value is not stored as parameter for later use
Kanstantsin Shautsou edited a comment on JENKINS-18138 Value is not stored as parameter for later use This plugin is injecting variables in form of artifactname+tail. If i'm entering input value name as KEY then it must be a KEY, no magic substitution. 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] [maven-metadata-plugin] (JENKINS-18138) Value is not stored as parameter for later use
Kanstantsin Shautsou commented on JENKINS-18138 Value is not stored as parameter for later use This plugin is injecting variables in form of artifactname+tail, so when artifactname has dash this variable become unusuable for shell. If i'm entering input value name as KEY then it must be a KEY, no magic substitution. 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] [maven-metadata-plugin] (JENKINS-18138) Value is not stored as parameter for later use
Kanstantsin Shautsou reopened JENKINS-18138 Value is not stored as parameter for later use Entered value must be stored without modification Change By: Kanstantsin Shautsou (17/Oct/14 6:58 AM) Resolution: Not A Defect Status: Closed Reopened 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] [crowd2] (JENKINS-16703) Too many periodic requests to Crowd server
Kanstantsin Shautsou commented on JENKINS-16703 Too many periodic requests to Crowd server Try remove group restriction... 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] [cucumber-testresult-plugin] (JENKINS-21835) Cucumber Test Result Plugin does not correctly parse Scenario Outline results
Kanstantsin Shautsou commented on JENKINS-21835 Cucumber Test Result Plugin does not correctly parse Scenario Outline results Is there any news? 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-17170) Jenkins auto install tools feature floods Nexus of HTTP request
Kanstantsin Shautsou commented on JENKINS-17170 Jenkins auto install tools feature floods Nexus of HTTP request So we need have some checkbox to control this behavior. 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-15063) support for multiple security realms with failover
Kanstantsin Shautsou commented on JENKINS-15063 support for multiple security realms with failover I'm not specialist on Atlassian products, but probably Crowd may do this, have you looked on it? 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] [maven-plugin] (JENKINS-23846) Jenkins Maven support doesn't handle version ranges in parent definitions
Kanstantsin Shautsou commented on JENKINS-23846 Jenkins Maven support doesn't handle version ranges in parent definitions Current maven-plugin based on 3.1.0 ... 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-17170) Jenkins auto install tools feature floods Nexus of HTTP request
Kanstantsin Shautsou commented on JENKINS-17170 Jenkins auto install tools feature floods Nexus of HTTP request Weird. https://github.com/jenkinsci/jenkins/blob/70f5968160b0a1cf81dc451fd2aacf1e0f9201ea/core/src/main/java/hudson/tools/DownloadFromUrlInstaller.java#L67 has check before. Both DownloadFromUrlInstaller and ZipExtractionInstaller do the same: "download and extract". JDKInstaller also has such check https://github.com/jenkinsci/jenkins/blob/70f5968160b0a1cf81dc451fd2aacf1e0f9201ea/core/src/main/java/hudson/tools/JDKInstaller.java#L126 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-24932) Build fails if mirror of "unpack archive" Maven installation procedure is unreachable
Kanstantsin Shautsou commented on JENKINS-24932 Build fails if mirror of "unpack archive" Maven installation procedure is unreachable Do you have /home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.2.3 path on lab76 ? 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-14193) EnvInject doesn't pass variables defined in prebuild step if maven project is used
Kanstantsin Shautsou edited a comment on JENKINS-14193 EnvInject doesn't pass variables defined in prebuild step if maven project is used Fixed in 2.7 maven-plugin version. Details: JENKINS-20884 2.7 will appear in update center when INFRA-178 will be resolved. Markus Meisterernst, if it solves your issue you may donate based on this info https://wiki.jenkins-ci.org/display/JENKINS/Donation 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-14193) EnvInject doesn't pass variables defined in prebuild step if maven project is used
Kanstantsin Shautsou resolved JENKINS-14193 as Fixed EnvInject doesn't pass variables defined in prebuild step if maven project is used Fixed in 2.7 maven-plugin version. Details: JENKINS-20884 Change By: Kanstantsin Shautsou (12/Oct/14 4:42 PM) 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] [gerrit-trigger] (JENKINS-24948) Git/Gerrit environment Variables are not available in Maven projects
Kanstantsin Shautsou commented on JENKINS-24948 Git/Gerrit environment Variables are not available in Maven projects Update center temporary broken INFRA-178 you may update it directly 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-24948) Git/Gerrit environment Variables are not available in Maven projects
Kanstantsin Shautsou commented on JENKINS-24948 Git/Gerrit environment Variables are not available in Maven projects Then wait or directly download https://updates.jenkins-ci.org/download/plugins/maven-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] [gerrit-trigger] (JENKINS-24948) Git/Gerrit environment Variables are not available in Maven projects
Kanstantsin Shautsou edited a comment on JENKINS-24948 Git/Gerrit environment Variables are not available in Maven projects Please try with maven-plugin-2.7 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-24948) Git/Gerrit environment Variables are not available in Maven projects
Kanstantsin Shautsou commented on JENKINS-24948 Git/Gerrit environment Variables are not available in Maven projects Please try wih maven-plugin-2.7 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] [maven-plugin] (JENKINS-10700) Maven3 builder is swallowing exceptions in reporters
Kanstantsin Shautsou commented on JENKINS-10700 Maven3 builder is swallowing exceptions in reporters Reviewed many latest commits... is it still actual? How i can reproduce? 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] [maven-plugin] (JENKINS-20884) Variable expansion in maven goals
Kanstantsin Shautsou commented on JENKINS-20884 Variable expansion in maven goals Tested with groovy injection - works fine. 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] [maven-plugin] (JENKINS-11385) Parameter value with '<', '>' are not properly escaped when launching mvn
Kanstantsin Shautsou commented on JENKINS-11385 Parameter value with '<', '>' are not properly escaped when launching mvn Is it still actual? have you tried escape variables? Jenkins and shell may do expansions and you need prepare right values. 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] [maven-plugin] (JENKINS-4424) Configuration fails to apply for deployment
Kanstantsin Shautsou commented on JENKINS-4424 Configuration fails to apply for deployment Is it still actual? 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] [maven-plugin] (JENKINS-3747) maven from scm, please
Kanstantsin Shautsou updated JENKINS-3747 maven from scm, please Change By: Kanstantsin Shautsou (09/Oct/14 5:54 PM) Priority: Critical Minor 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] [maven-plugin] (JENKINS-3747) maven from scm, please
Kanstantsin Shautsou commented on JENKINS-3747 maven from scm, please I think nobody will do it because it has no sense. Do you still need this weird feature? 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] [maven-plugin] (JENKINS-17796) Maven 2/3 _-Project Job Unable to commit files svn: E155004
Kanstantsin Shautsou resolved JENKINS-17796 as Not A Defect Maven 2/3 _-Project Job Unable to commit files svn: E155004 10:56:09 svn: E155004: 'D:\KQVWork\hudson1t\workspace\cosa-scm-k1-win175_trunk_release_branch\cosa-scm-k1-win175' is already locked. 10:56:09 svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details) Not jenkins issue, because maven-release-plugin calls svn client that doesn't belong to jenkins plugins. http://stackoverflow.com/questions/16433933/svn-e155004-path-of-resouce-is-already-locked Change By: Kanstantsin Shautsou (09/Oct/14 5: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] [maven-plugin] (JENKINS-7985) In Maven2 jobs, parsing POM is done *after* calling pre-build steps (using M2-extra-steps-plugin)
Kanstantsin Shautsou commented on JENKINS-7985 In Maven2 jobs, parsing POM is done *after* calling pre-build steps (using M2-extra-steps-plugin) Is it still actual? Is it related to "maven-plugin" or to some other? 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] [maven-plugin] (JENKINS-23039) [MAVEN] java.net.SocketException: Connection reset
Kanstantsin Shautsou commented on JENKINS-23039 [MAVEN] java.net.SocketException: Connection reset https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue#Howtoreportanissue-WhatinformationtoprovideforEnvironmentandDescription 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] [maven-plugin] (JENKINS-21372) NPE when parsing emails for notification when build is unstable and email field does not contain any email
Kanstantsin Shautsou commented on JENKINS-21372 NPE when parsing emails for notification when build is unstable and email field does not contain any email Jenkins version? Maven version? What plugin for email? What configuration? How reproduce? 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-14193) EnvInject doesn't pass variables defined in prebuild step if maven project is used
Kanstantsin Shautsou commented on JENKINS-14193 EnvInject doesn't pass variables defined in prebuild step if maven project is used Hi, i think this not EnvInject plugin issue, because i injected env and parameter variables with groovy and they are not available in Maven build step. #JENKINS-20884 seems the root of 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] [envinject] (JENKINS-14193) EnvInject doesn't pass variables defined in prebuild step if maven project is used
Kanstantsin Shautsou updated JENKINS-14193 EnvInject doesn't pass variables defined in prebuild step if maven project is used Change By: Kanstantsin Shautsou (08/Oct/14 3:29 PM) Component/s: maven-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] [crowd2] (JENKINS-24884) Unable to use SSO with Jenkins + Crowd
Kanstantsin Shautsou edited a comment on JENKINS-24884 Unable to use SSO with Jenkins + Crowd I checked code it calls the same getAuthoritiesForUser(). What groups specified in crowd server settings for jenkins application? PS provide logs for classes that i mentioned (at least for de.theit.jenkins.crowd). 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] [crowd2] (JENKINS-24884) Unable to use SSO with Jenkins + Crowd
Kanstantsin Shautsou commented on JENKINS-24884 Unable to use SSO with Jenkins + Crowd I checked code it calls the same getAuthoritiesForUser(). What groups specified in crowd server settings for jenkins application? 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] [crowd2] (JENKINS-24884) Unable to use SSO with Jenkins + Crowd
Kanstantsin Shautsou commented on JENKINS-24884 Unable to use SSO with Jenkins + Crowd Hi, could you check closed issues? There was some issues before but they are all were closed by requestor after setting right proxy and other settings. Plus add in jenkins configuration logger for crowd and jenkins/hudson.security, acegi classes to collect debug info. And open in chrome debug console and check in network connection requested/accepted "cookies" tab. 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-24761) Jenkin job fails with hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown
Kanstantsin Shautsou commented on JENKINS-24761 Jenkin job fails with hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown Hi, this project called "Jenkins", not "junkins" or "junking". 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] [core] (JENKINS-24745) hundson failed to create symlink cause incorrect function
Kanstantsin Shautsou commented on JENKINS-24745 hundson failed to create symlink cause incorrect function What is "Oracle IRE"? What version? Where is other info? "jenkins acces through localhost:8080" is irrelevant info. @ayfer , please read again https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue#Howtoreportanissue-WhatinformationtoprovideforEnvironmentandDescription 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] [disk-usage] (JENKINS-14872) disk-usage-plugin: Calculating disk usage is causing very high I/O
Kanstantsin Shautsou commented on JENKINS-14872 disk-usage-plugin: Calculating disk usage is causing very high I/O Deadlock maybe the separate issue. This was related to old plugin version, so reporter should try new version and reply. 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] [perforce] (JENKINS-24740) Expose duration of sync in ENV
Kanstantsin Shautsou commented on JENKINS-24740 Expose duration of sync in ENV Additionally, you can create separate tool that will just analyze build logs with existed timestamps and then provide any info you want for your it. 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] [disk-usage] (JENKINS-14872) disk-usage-plugin: Calculating disk usage is causing very high I/O
Kanstantsin Shautsou commented on JENKINS-14872 disk-usage-plugin: Calculating disk usage is causing very high I/O Is it still actual with new plugin versions? 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] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Kanstantsin Shautsou commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 Please, stop flooding. Everybody may send PR with fixed 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] [emailext-template] (JENKINS-22613) email-ext-template plugin has many names
Kanstantsin Shautsou reopened JENKINS-22613 email-ext-template plugin has many names Remove old component in jira. https://issues.jenkins-ci.org/browse/JENKINS/component/18763 ? Change By: Kanstantsin Shautsou (20/Aug/14 6:58 PM) Resolution: Fixed Status: Resolved Reopened 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] [crowd2] (JENKINS-17957) Crowd plugin - "remember me" doesn't work
Kanstantsin Shautsou edited a comment on JENKINS-17957 Crowd plugin - "remember me" doesn't work Next week I will add SSO part and then provide new version for testing. 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] [crowd2] (JENKINS-17957) Crowd plugin - "remember me" doesn't work
Kanstantsin Shautsou commented on JENKINS-17957 Crowd plugin - "remember me" doesn't work Next week I will add SSO part and then provide new 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] [crowd2] (JENKINS-17957) Crowd plugin - "remember me" doesn't work
Kanstantsin Shautsou commented on JENKINS-17957 Crowd plugin - "remember me" doesn't work Results of testing refactored plugin: remember me works, need implement SSO auth part and test it. 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] [crowd2] (JENKINS-17957) Crowd plugin - "remember me" doesn't work
Kanstantsin Shautsou started work on JENKINS-17957 Crowd plugin - "remember me" doesn't work Change By: Kanstantsin Shautsou (18/Aug/14 5:03 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] [crowd2] (JENKINS-22136) Jenkins Crowd2 plugin Project-based Matrix Authorization Strategy functionally issue - application permissions override the project-based security
Kanstantsin Shautsou resolved JENKINS-22136 as Not A Defect Jenkins Crowd2 plugin Project-based Matrix Authorization Strategy functionally issue - application permissions override the project-based security Change By: Kanstantsin Shautsou (18/Aug/14 5:02 PM) Status: Open Resolved Assignee: Thorsten Heit Kanstantsin Shautsou 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] [crowd2] (JENKINS-22775) Crowd2 seems to destroy user session when using SSO
Kanstantsin Shautsou assigned JENKINS-22775 to Kanstantsin Shautsou Crowd2 seems to destroy user session when using SSO Change By: Kanstantsin Shautsou (18/Aug/14 4:59 PM) Assignee: Thorsten Heit Kanstantsin Shautsou 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] [crowd2] (JENKINS-16703) Too many periodic requests to Crowd server
Kanstantsin Shautsou assigned JENKINS-16703 to Kanstantsin Shautsou Too many periodic requests to Crowd server Change By: Kanstantsin Shautsou (18/Aug/14 4:59 PM) Assignee: Thorsten Heit Kanstantsin Shautsou 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] [security] (JENKINS-17060) Jenkins errors when 'Remember me on this computer' is checked.
Kanstantsin Shautsou updated JENKINS-17060 Jenkins errors when 'Remember me on this computer' is checked. Change By: Kanstantsin Shautsou (18/Aug/14 4:53 PM) Description: Jenkins > 1.500 requires principal to be UserDetails. Status Code: 500Exception: Stacktrace:java.lang.IllegalArgumentException: Object of class [java.lang.String] must be an instance of interface org.acegisecurity.userdetails.UserDetails at org.springframework.util.Assert.isInstanceOf(Assert.java:337) at org.springframework.util.Assert.isInstanceOf(Assert.java:319) at hudson.security.TokenBasedRememberMeServices2.loginSuccess(TokenBasedRememberMeServices2.java:76) at org.acegisecurity.ui.AbstractProcessingFilter.successfulAuthentication(AbstractProcessingFilter.java:488) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:266) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.plugins.pwauth.PWauthFilter.doFilter(PWauthFilter.java:50) at hudson.plugins.pwauth.PWauthFilter.doFilter(PWauthFilter.java:37) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:227) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722)Generated by Winstone Servlet Engine v0.9.10 at Mon Mar 04 16:59:54 EST 2013 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] [security] (JENKINS-17060) Jenkins errors when 'Remember me on this computer' is checked.
Kanstantsin Shautsou commented on JENKINS-17060 Jenkins errors when 'Remember me on this computer' is checked. Resolved what? PWAuth? 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] [security] (JENKINS-17060) Jenkins errors when 'Remember me on this computer' is checked.
Kanstantsin Shautsou edited a comment on JENKINS-17060 Jenkins errors when 'Remember me on this computer' is checked. PWAuth-plugin is not fixed as i see, part about crowd2-plugin is resolved. I can look at PWAuth if somebody will test changes. 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] [security] (JENKINS-17060) Jenkins errors when 'Remember me on this computer' is checked.
Kanstantsin Shautsou commented on JENKINS-17060 Jenkins errors when 'Remember me on this computer' is checked. PWAuth-plugin is not fixed as i see, part about crowd2-plugin is resolved. I can look on PWAuth if somebody will test changes. 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] [mail] (JENKINS-279) Modular email notification
Kanstantsin Shautsou resolved JENKINS-279 as Fixed Modular email notification email-ext plugin is solving this issue. Change By: Kanstantsin Shautsou (08/Aug/14 1:41 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] [other] (JENKINS-1682) Pre-tested commit feature
Kanstantsin Shautsou commented on JENKINS-1682 Pre-tested commit feature What is the status? 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-7882) Console log can throw OutOfMemoryError if it contains a malformed ConsoleNote
Kanstantsin Shautsou resolved JENKINS-7882 as Cannot Reproduce Console log can throw OutOfMemoryError if it contains a malformed ConsoleNote atm can't reproduce on linux and Jenkins-1.566-snapshot. Please reopen if you still see this issue. Change By: Kanstantsin Shautsou (04/Aug/14 10:24 PM) Status: Open Resolved Resolution: Cannot Reproduce 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-5316) X connection to localhost after maven site site:deploy
Kanstantsin Shautsou resolved JENKINS-5316 as Incomplete X connection to localhost after maven site site:deploy Change By: Kanstantsin Shautsou (04/Aug/14 10:11 PM) Status: Open Resolved Resolution: Incomplete 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-16634) Failed to connect slave due to missing folder on the master
Kanstantsin Shautsou commented on JENKINS-16634 Failed to connect slave due to missing folder on the master AFAIR various logs were moved from JENKINS_HOME to subdirectory. Is it still reproducible? 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] [crowd2] (JENKINS-17957) Crowd plugin - "remember me" doesn't work
Kanstantsin Shautsou commented on JENKINS-17957 Crowd plugin - "remember me" doesn't work Could you join to IRC freenode.net on #jenkins channel it will be easier for me to compare configurations? And again, crash was only when you checked "remember me" auth was working. 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] [crowd2] (JENKINS-17957) Crowd plugin - "remember me" doesn't work
Kanstantsin Shautsou edited a comment on JENKINS-17957 Crowd plugin - "remember me" doesn't work 1) List cookies for your jenkins. I have ACEGI_SECURITY_HASHED_REMEMBER_ME_COOKIE that marked as Expired on +14 days 2) add org.acegisecurity.ui.rememberme to jenkins logging (in "manage jenkins"->"System logging") 3) close browser 4) open browser and go to jenkins, without loggin check what cookies exist (at firefox ACEGI_SECURITY_HASHED_REMEMBER_ME_COOKIE disappeared) 5) navigate to jenkins log and check messages... And again, what browser do you use? 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] [crowd2] (JENKINS-17957) Crowd plugin - "remember me" doesn't work
Kanstantsin Shautsou commented on JENKINS-17957 Crowd plugin - "remember me" doesn't work 1) List cookies for your jenkins. I have ACEGI_SECURITY_HASHED_REMEMBER_ME_COOKIE that marked as Expired on +14 days 2) add org.acegisecurity.ui.rememberme to jenkins logging (in "manage jenkins"->"System logging") 3) close browser 4) open browser and go to jenkins, without loggin check what cookies exist (at firefox ACEGI_SECURITY_HASHED_REMEMBER_ME_COOKIE disappeared) And again, what browser do you use? 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] [crowd2] (JENKINS-17957) Crowd plugin - "remember me" doesn't work
Kanstantsin Shautsou commented on JENKINS-17957 Crowd plugin - "remember me" doesn't work Could you try new 1.8 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] [crowd2] (JENKINS-22136) Jenkins Crowd2 plugin Project-based Matrix Authorization Strategy functionally issue - application permissions override the project-based security
Kanstantsin Shautsou edited a comment on JENKINS-22136 Jenkins Crowd2 plugin Project-based Matrix Authorization Strategy functionally issue - application permissions override the project-based security Page not found. Crowd doesn't do anything with authorization. It provides groups that belong to user for other jenkins routines. Crowd works perfect with role-based 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] [crowd2] (JENKINS-22136) Jenkins Crowd2 plugin Project-based Matrix Authorization Strategy functionally issue - application permissions override the project-based security
Kanstantsin Shautsou commented on JENKINS-22136 Jenkins Crowd2 plugin Project-based Matrix Authorization Strategy functionally issue - application permissions override the project-based security Page not found. Crowd doesn't do anything with authorization. Crowd works perfect with role-based 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] [crowd2] (JENKINS-16703) Too many periodic requests to Crowd server
Kanstantsin Shautsou commented on JENKINS-16703 Too many periodic requests to Crowd server Is it still reproducible with 1.8 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] [crowd2] (JENKINS-16978) NoHttpResponseException with working Crowd2-Plugin
Kanstantsin Shautsou resolved JENKINS-16978 as Cannot Reproduce NoHttpResponseException with working Crowd2-Plugin Check your network and crowd as java application latency for replies. Check new connection options available from 1.7 version. Change By: Kanstantsin Shautsou (01/Aug/14 4:22 PM) Status: Open Resolved Assignee: Thorsten Heit Kanstantsin Shautsou Resolution: Cannot Reproduce 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] [crowd] (JENKINS-18731) crowd authentication suddenly stopped working after chaning the domain of jenkins
Kanstantsin Shautsou resolved JENKINS-18731 as Cannot Reproduce crowd authentication suddenly stopped working after chaning the domain of jenkins Try latest 1.8 version and try reproduce. Change By: Kanstantsin Shautsou (01/Aug/14 4:19 PM) Status: Open Resolved Resolution: Cannot Reproduce 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] [crowd2] (JENKINS-22774) Crowd2 does not honor Crowd's Session Timeout
Kanstantsin Shautsou resolved JENKINS-22774 as Incomplete Crowd2 does not honor Crowd's Session Timeout Change By: Kanstantsin Shautsou (01/Aug/14 4:16 PM) Status: Open Resolved Assignee: Thorsten Heit Kanstantsin Shautsou Resolution: Incomplete 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] [crowd2] (JENKINS-21852) Allow configuration of HTTPS proxy for connection to Crowd
Kanstantsin Shautsou resolved JENKINS-21852 as Fixed Allow configuration of HTTPS proxy for connection to Crowd Change By: Kanstantsin Shautsou (01/Aug/14 4:17 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] [crowd2] (JENKINS-22775) Crowd2 seems to destroy user session when using SSO
Kanstantsin Shautsou commented on JENKINS-22775 Crowd2 seems to destroy user session when using SSO Does this comment solves issue? Why plugin and jenkins version is not 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] [crowd2] (JENKINS-23208) Backtrace when trying to use 'remember me' with latest crowd auth plugin
Kanstantsin Shautsou commented on JENKINS-23208 Backtrace when trying to use 'remember me' with latest crowd auth plugin Added one more fix, please test this https://jenkins.ci.cloudbees.com/job/plugins/job/crowd2-plugin/20/org.jenkins-ci.plugins$crowd2/ hpi build and reply wether you use sso and what jenkins version you have. If everything ok i will release new 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] [crowd2] (JENKINS-23208) Backtrace when trying to use 'remember me' with latest crowd auth plugin
Kanstantsin Shautsou commented on JENKINS-23208 Backtrace when trying to use 'remember me' with latest crowd auth plugin And please try this https://jenkins.ci.cloudbees.com/job/plugins/job/crowd2-plugin/17/org.jenkins-ci.plugins$crowd2/artifact/org.jenkins-ci.plugins/crowd2/1.8-SNAPSHOT/crowd2-1.8-SNAPSHOT.hpi i added fast patch but have no time to check it... 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-23248) CLI: get-job calls are causing file descriptor leaks.
Kanstantsin Shautsou commented on JENKINS-23248 CLI: get-job calls are causing file descriptor leaks. It maybe useful to wrote a test case and run automated bisect http://java.dzone.com/articles/automated-bug-finding-git ... 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] [crowd2] (JENKINS-23208) Backtrace when trying to use 'remember me' with latest crowd auth plugin
Kanstantsin Shautsou commented on JENKINS-23208 Backtrace when trying to use 'remember me' with latest crowd auth plugin Try disable this button. SSO should work. 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] [crowd2] (JENKINS-23208) Backtrace when trying to use 'remember me' with latest crowd auth plugin
Kanstantsin Shautsou commented on JENKINS-23208 Backtrace when trying to use 'remember me' with latest crowd auth plugin Have you tried to disable "remember me" button in security configuration? 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] [subversion] (JENKINS-23628) case-insensitive hostname
Kanstantsin Shautsou commented on JENKINS-23628 case-insensitive hostname Do you have "no revision error?" I think not the same. 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] [subversion] (JENKINS-22190) Changelog only shows changes in externals
Kanstantsin Shautsou commented on JENKINS-22190 Changelog only shows changes in externals What do you mean under "main" and "external" projects? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-23628) case-insensitive hostname
Kanstantsin Shautsou updated JENKINS-23628 case-insensitive hostname Change By: Kanstantsin Shautsou (16/Jul/14 3:52 PM) Assignee: Kanstantsin Shautsou 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] [subversion] (JENKINS-23628) case-insensitive hostname
Kanstantsin Shautsou created JENKINS-23628 case-insensitive hostname Issue Type: Improvement Assignee: Kanstantsin Shautsou Components: subversion Created: 30/Jun/14 4:46 PM Description: based on http://stackoverflow.com/questions/19051709/envvar-svn-revision-and-svn-url-not-set WARNING: no revision found corresponding to http://SERVERNAME/svn/Project/trunk; known: [http://servername/svn/Project/trunk] Probably String type should be changed to java.net.URI Project: Jenkins Priority: Major Reporter: Kanstantsin Shautsou 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] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Kanstantsin Shautsou commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 Please, don't spam with +1 messages, there is a vote button. @aristedes community can do PR with fixes and open separate bug with linking issues to this root 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] [core] (JENKINS-5336) Users are automatically created when going thru HUDSON_URL/user/[anything]
Kanstantsin Shautsou commented on JENKINS-5336 Users are automatically created when going thru HUDSON_URL/user/[anything] Well, this is not a good behavior for UI. When i tested it still allowed create users. Maybe something changed. If such action ends to 404 for non admin users now, then bug priority maybe decreased. 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] [crowd2] (JENKINS-11912) SSO not working
Kanstantsin Shautsou resolved JENKINS-11912 as Not A Defect SSO not working Change By: Kanstantsin Shautsou (03/Jun/14 9:30 AM) Status: Reopened 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] [crowd2] (JENKINS-11912) SSO not working
Kanstantsin Shautsou edited a comment on JENKINS-11912 SSO not working Plus add com.atlassian.crowd to logger Filter routine checks auth at https://github.com/jenkinsci/crowd2-plugin/blob/master/src/main/java/de/theit/jenkins/crowd/CrowdServletFilter.java#L139 Check that SSO domain configured right plus check errors from com.atlassian.crowd library. 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] [crowd2] (JENKINS-11912) SSO not working
Kanstantsin Shautsou commented on JENKINS-11912 SSO not working Plus add com.atlassian.crowd to logger Filter routine tries to extract token, here it fails. Check that SSO domain configured right plus check errors from com.atlassian.crowd library. 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] [crowd2] (JENKINS-11912) SSO not working
Kanstantsin Shautsou reopened JENKINS-11912 SSO not working Change By: Kanstantsin Shautsou (02/Jun/14 4:04 PM) Resolution: Not A Defect Status: Closed Reopened Assignee: Thorsten Heit Kanstantsin Shautsou 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] [crowd2] (JENKINS-11912) SSO not working
Kanstantsin Shautsou commented on JENKINS-11912 SSO not working Add jenkins.security, hudson.security, de.theit.jenkins.crowd to logger. 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-16227) ProjectNamingStrategy: remove Default Strategy from the UI
Kanstantsin Shautsou commented on JENKINS-16227 ProjectNamingStrategy: remove Default Strategy from the UI +1 for show always, because jenkins always checks job name using ProjectNamingStrategy. "Default maybe renamed to "Allow all" 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-16227) ProjectNamingStrategy: remove Default Strategy from the UI
Kanstantsin Shautsou edited a comment on JENKINS-16227 ProjectNamingStrategy: remove Default Strategy from the UI +1 for show always, because jenkins always checks job name using ProjectNamingStrategy. "Default" maybe renamed to "Allow all" 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-23218) hetero-list for ProjectNamingStrategy
Kanstantsin Shautsou assigned JENKINS-23218 to Kanstantsin Shautsou hetero-list for ProjectNamingStrategy Change By: Kanstantsin Shautsou (28/May/14 1:20 PM) Assignee: Kanstantsin Shautsou 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-23218) hetero-list for ProjectNamingStrategy
Kanstantsin Shautsou started work on JENKINS-23218 hetero-list for ProjectNamingStrategy Change By: Kanstantsin Shautsou (28/May/14 1:20 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-16228) ProjectNamingStrategy/UI: move "force existing" option to feature level
Kanstantsin Shautsou assigned JENKINS-16228 to Kanstantsin Shautsou ProjectNamingStrategy/UI: move "force existing" option to feature level Change By: Kanstantsin Shautsou (28/May/14 12:12 PM) Assignee: Kanstantsin Shautsou 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-23218) hetero-list for ProjectNamingStrategy
Kanstantsin Shautsou created JENKINS-23218 hetero-list for ProjectNamingStrategy Issue Type: Improvement Assignee: Unassigned Components: core Created: 28/May/14 12:07 PM Description: I have cases when i want to have more then one enabled ProjectNamingStrategy. Current radio-list need to be changed to hetero-list. Order of checkName() and isForceExistingJobs() should be the same as order of plugins (for example from top to bottom). Project: Jenkins Priority: Major Reporter: Kanstantsin Shautsou 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] [crowd2] (JENKINS-13279) Interface with Crowd embedded that runs in Jira
Kanstantsin Shautsou resolved JENKINS-13279 as Fixed Interface with Crowd embedded that runs in Jira Change By: Kanstantsin Shautsou (28/May/14 11:51 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] [crowd2] (JENKINS-23208) Backtrace when trying to use 'remember me' with latest crowd auth plugin
Kanstantsin Shautsou commented on JENKINS-23208 Backtrace when trying to use 'remember me' with latest crowd auth plugin 1) Initial plugin author implemented SSO using rememberme. 2) See this JENKINS-17060 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] [role-strategy] (JENKINS-19934) Add "Job Create" permission to project roles
Kanstantsin Shautsou edited a comment on JENKINS-19934 Add "Job Create" permission to project roles After fix JENKINS-23127 it will be possible to have "role based project naming" extension, but it will require new core or someway to have it optionally. Or assign roles may have "create" checkboxes that will work only on new core and with enabled "project naming". So checkbox tip will say "only with project naming strategy", project naming will say "only on core >". 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.
