[JIRA] [robot-plugin] (JENKINS-22546) Add REST API to robot framework plugin
jpiironen commented on JENKINS-22546 Add REST API to robot framework plugin I think this could be really useful feature in for many users! What would be the most important data for you that you would like to obtain from the API? 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-21509) Create new item fails: NumberFormatException: for InputString
Philip Helger edited a comment on JENKINS-21509 Create new item fails: NumberFormatException: for InputString Thanks for responding. After uninstalling green balls the same result. Is there any configuration I can paste here to help searching? This seems to be the source of the problem: at jenkins.model.PeepholePermalink.resolve(PeepholePermalink.java:87) at hudson.model.Job.getLastSuccessfulBuild(Job.java:836) at hudson.maven.AbstractMavenProject.createTransientActions(AbstractMavenProject.java:185) 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] [testlink] (JENKINS-22220) TestLink Plugin is not executing testng method and showing Not Run in jenkins excution report
subbu m commented on JENKINS-0 TestLink Plugin is not executing testng method and showing Not Run in jenkins excution report hi, i also having this issue, any workaround please i think I also noted if i just place a some testNg-result.xml file in working folder of the Item/Project , its not reading either please let us know the stable version to roll back thanks in advance subbu This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-8642) Defaults for unstable, still unstable, failing and still failing are a bit harsh :-)
Mirko Friedenhagen closed JENKINS-8642 as Fixed Defaults for unstable, still unstable, failing and still failing are a bit harsh :-) Change By: Mirko Friedenhagen (11/Apr/14 7:15 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21509) Create new item fails: NumberFormatException: for InputString
Philip Helger resolved JENKINS-21509 as Wont Fix Create new item fails: NumberFormatException: for InputString I investigated the file system and found that the project I wanted to create was already there, but could not be loaded, because "lastStable" and "lastSuccessful" were file links, and not directory links as in the other projects - whysoever. After manually deleting the project from disk and creating a new one, everything worked out fine! Change By: Philip Helger (11/Apr/14 7:16 AM) Status: Open Resolved Resolution: WontFix 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] [publish-over-ssh] (JENKINS-16240) Problem with NOT_BUILT build result
Mahmoud AllamehAmiri commented on JENKINS-16240 Problem with NOT_BUILT build result I solved this problem by setting build result to success manually! I defined post build script (groovy) and in that I set build result to success. 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] [publish-over-ssh] (JENKINS-16240) Problem with NOT_BUILT build result
Isaac Cruz commented on JENKINS-16240 Problem with NOT_BUILT build result Can you post that groovy script? In any case, that's a workaround but the bug is still there... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-22561) publish-over-cifs should be able to use Jenkins session credentials - including domain when Jenkins Active Directory authentication is used
Sam Liddicott commented on JENKINS-22561 publish-over-cifs should be able to use Jenkins session credentials - including domain when Jenkins Active Directory authentication is used $25 currently offered for a fix at https://freedomsponsors.org/core/issue/483/publish-over-cifs-should-be-able-to-use-jenkins-session-credentials-including-domain-when-jenkins-active-directory-authentication-is-used?alert=SPONSOR# This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-20767) Git plugin 2.0: Git polling causes builds even if no changes
alexanderlink commented on JENKINS-20767 Git plugin 2.0: Git polling causes builds even if no changes Hello Mark, (Pull Request coming in a second) I tested git-client 1.7.0 together with git 2.1.0 (I assume newer versions are also affected, but I'll check). I obviously missed something during tests. We have the same issue we had with namespace branches again with the "master" branch. The CI job is triggered again and again. The problem is that "master" still matches for "refs/heads/master", "refs/heads/abc/master", "refs/heads/xyz/master", etc. Since git ls-remote lists the refs alphabetically the first entry might be the correct one by chance - or not. I extended the test GitAPITestCase.test_getHeadRev_namespaces(). When I tried to fix this issue I recognized that there are several additional problems with the "Branch Specifier" handling! First of all you have to be aware that it is possible to create weird branch names containing words which should be reserved by Git but are not. E.g. you can create a branch "refs/heads/master" (being refs/heads/refs/heads/master) or a branch "origin/master" (being refs/heads/origin/master), etc. A remote name also can contain weird stuff and slashes! E.g. a remote can be called "origin/master"! Even without this knowledge it was quite hard to definitely "guess" what is meant by a configured "Branch Specifier". Even git itself has problems with ambiguous specs. Try the following in a repo having a remote "origin" and branch "master": git branch origin/master git checkout origin/master - warning: refname 'origin/master' is ambiguous. Therefore it is necessary to specify concrete rules which (from my perspective) did not exist yet. >From my perspective several potential variations have to be checked and depending on if it makes sense in the current repo and a rev could be identified the matching result is taken. In org.jenkinsci.plugins.gitclient.LegacyCompatibleGitAPIImpl.normalizeBranchSpec(String) you can see how the proposed rules look like: If a branch spec starts with "refs/" try to get the revision for exactly this String. If a branch spec starts with "remote/" check if a remote with this name exists and build String "refs/heads/branchName" definite for ls-remote If both was not the case check again if the branch spec starts with a valid remote (e.g. "origin/master") As ultimate fallbacks try "refs/heads/branchSpec" to check if a branch named like this exists (remember the weird possible names - we should not spend too much thoughts, just try) ... "refs/headsbranchSpec" if wildcards are used (e.g. "/master" - "refs/heads/master". "refs/heads/*/master" would not match the "master" branch) ... and simply "branchSpec" as final fallback. The patterns are tried starting with the upper one. Ther first one which results in a definite result is considered to be the correct one. Furthermore I now throw an AmbiguousResultException in case the result is ambiguous. Until now simply the first entry of "git ls-remote" is taken which is way too randomly considering the alphabetical sorting. I hope you see my points. I spent over a week now to understand and fix those issues Maybe the tests and changes in the Pull Request show what I mean. Thanks a lot and kind regards, Alex This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-20767) Git plugin 2.0: Git polling causes builds even if no changes
alexanderlink edited a comment on JENKINS-20767 Git plugin 2.0: Git polling causes builds even if no changes Hello Mark, (Pull Request coming in a second) I tested git-client 1.7.0 together with git 2.1.0 (I assume newer versions are also affected, but I'll check). I obviously missed something during tests. We have the same issue we had with namespace branches again with the "master" branch. The CI job is triggered again and again. The problem is that "master" still matches for "refs/heads/master", "refs/heads/abc/master", "refs/heads/xyz/master", etc. Since git ls-remote lists the refs alphabetically the first entry might be the correct one by chance - or not. I extended the test GitAPITestCase.test_getHeadRev_namespaces(). When I tried to fix this issue I recognized that there are several additional problems with the "Branch Specifier" handling! First of all you have to be aware that it is possible to create weird branch names containing words which should be reserved by Git but are not. E.g. you can create a branch "refs/heads/master" (being refs/heads/refs/heads/master) or a branch "origin/master" (being refs/heads/origin/master), etc. A remote name also can contain weird stuff and slashes! E.g. a remote can be called "origin/master"! Even without this knowledge it was quite hard to definitely "guess" what is meant by a configured "Branch Specifier". Even git itself has problems with ambiguous specs. Try the following in a repo having a remote "origin" and branch "master": git branch origin/master git checkout origin/master - warning: refname 'origin/master' is ambiguous. Therefore it is necessary to specify concrete rules which (from my perspective) did not exist yet. >From my perspective several potential variations have to be checked and depending on if it makes sense in the current repo and a rev could be identified the matching result is taken. In org.jenkinsci.plugins.gitclient.LegacyCompatibleGitAPIImpl.normalizeBranchSpec(String) you can see how the proposed rules look like: If a branch spec starts with "refs/" try to get the revision for exactly this String. If a branch spec starts with "remote/" check if a remote with this name exists and build String "refs/heads/branchName" definite for ls-remote If both was not the case check again if the branch spec starts with a valid remote (e.g. "origin/master") As ultimate fallbacks try "refs/heads/branchSpec" to check if a branch named like this exists (remember the weird possible names - we should not spend too much thoughts, just try) ... "refs/headsbranchSpec" if wildcards are used (e.g. "/master" - "refs/heads/master". "refs/heads//master" would not match the "master" branch) ... and simply "branchSpec" as final fallback. The patterns are tried starting with the upper one. Ther first one which results in a definite result is considered to be the correct one. Furthermore I now throw an AmbiguousResultException in case the result is ambiguous. Until now simply the first entry of "git ls-remote" is taken which is way too randomly considering the alphabetical sorting. I hope you see my points. I spent over a week now to understand and fix those issues Maybe the tests and changes in the Pull Request show what I mean. Thanks a lot and kind regards, Alex This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-20767) Git plugin 2.0: Git polling causes builds even if no changes
alexanderlink edited a comment on JENKINS-20767 Git plugin 2.0: Git polling causes builds even if no changes Hello Mark, (Pull Request https://github.com/jenkinsci/git-client-plugin/pull/129) I tested git-client 1.7.0 together with git 2.1.0 (I assume newer versions are also affected, but I'll check). I obviously missed something during tests. We have the same issue we had with namespace branches again with the "master" branch. The CI job is triggered again and again. The problem is that "master" still matches for "refs/heads/master", "refs/heads/abc/master", "refs/heads/xyz/master", etc. Since git ls-remote lists the refs alphabetically the first entry might be the correct one by chance - or not. I extended the test GitAPITestCase.test_getHeadRev_namespaces(). When I tried to fix this issue I recognized that there are several additional problems with the "Branch Specifier" handling! First of all you have to be aware that it is possible to create weird branch names containing words which should be reserved by Git but are not. E.g. you can create a branch "refs/heads/master" (being refs/heads/refs/heads/master) or a branch "origin/master" (being refs/heads/origin/master), etc. A remote name also can contain weird stuff and slashes! E.g. a remote can be called "origin/master"! Even without this knowledge it was quite hard to definitely "guess" what is meant by a configured "Branch Specifier". Even git itself has problems with ambiguous specs. Try the following in a repo having a remote "origin" and branch "master": git branch origin/master git checkout origin/master - warning: refname 'origin/master' is ambiguous. Therefore it is necessary to specify concrete rules which (from my perspective) did not exist yet. >From my perspective several potential variations have to be checked and depending on if it makes sense in the current repo and a rev could be identified the matching result is taken. In org.jenkinsci.plugins.gitclient.LegacyCompatibleGitAPIImpl.normalizeBranchSpec(String) you can see how the proposed rules look like: If a branch spec starts with "refs/" try to get the revision for exactly this String. If a branch spec starts with "remote/" check if a remote with this name exists and build String "refs/heads/branchName" definite for ls-remote If both was not the case check again if the branch spec starts with a valid remote (e.g. "origin/master") As ultimate fallbacks try "refs/heads/branchSpec" to check if a branch named like this exists (remember the weird possible names - we should not spend too much thoughts, just try) ... "refs/headsbranchSpec" if wildcards are used (e.g. "/master" - "refs/heads/master". "refs/heads//master" would not match the "master" branch) ... and simply "branchSpec" as final fallback. The patterns are tried starting with the upper one. Ther first one which results in a definite result is considered to be the correct one. Furthermore I now throw an AmbiguousResultException in case the result is ambiguous. Until now simply the first entry of "git ls-remote" is taken which is way too randomly considering the alphabetical sorting. I hope you see my points. I spent over a week now to understand and fix those issues Maybe the tests and changes in the Pull Request show what I mean. Thanks a lot and kind regards, Alex 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] [master-slave] (JENKINS-11992) Win7 x64: x86 Java runtime creates bad PATH on x64 OS causing ' \Java\jre6\bin was unexpected at this time.' error
Robert Grampp edited a comment on JENKINS-11992 Win7 x64: x86 Java runtime creates bad PATH on x64 OS causing \Java\jre6\bin was unexpected at this time. error I would like to see this bug raised to level MAJOR since a command line build with Microsoft Studio 11 is impossible with this Jenkins behaviour. It crashes when calling Microsofts script vcvarsall.bat! Job log: C:\Users\plossys\workspace\Test_Slave_Windows_VC_Buildpath PATH=C:\Program Files (x86)\Java\jdk1.6.0_37_32b/bin;C:\Program Files (x86)\Java\jdk1.6.0_37_32b/bin;C:\Program Files (x86)\Java\jre6\bin;C:\Program Files (x86)\Mozilla Firefox;C:\Program Files (x86)\Java\jre6\bin;C:\ruby200\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\TortoiseGit\bin;C:\Program Files\TortoiseSVN\bin;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\VisualSVN\bin;C:\strawberry\c\bin;C:\strawberry\perl\site\bin;C:\strawberry\perl\bin;C:\Chocolatey\bin;C:\sysinternals;"C:\Program Files (x86)\Java\jre6\bin" C:\Users\plossys\workspace\Test_Slave_Windows_VC_Build"C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\vcvarsall.bat" amd64 \Java\jre6\bin"" was unexpected at this time. Build step 'Windows Batch-Datei ausführen' marked build as failure Jenkins slave is connected via JNLP launcher (Java Applet), not via Windows service cause that raised too much hassle with firewall/group policy issues. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [master-slave] (JENKINS-11992) Win7 x64: x86 Java runtime creates bad PATH on x64 OS causing ' \Java\jre6\bin was unexpected at this time.' error
Robert Grampp commented on JENKINS-11992 Win7 x64: x86 Java runtime creates bad PATH on x64 OS causing \Java\jre6\bin was unexpected at this time. error I would like to see this bug raised to level MAJOR since a command line build with Microsoft Studio 11 is impossible with this Jenkins behaviour. It crashes when calling Microsofts script vcvarsall.bat! Job log: C:\Users\plossys\workspace\Test_Slave_Windows_VC_Buildpath PATH=C:\Program Files (x86)\Java\jdk1.6.0_37_32b/bin;C:\Program Files (x86)\Java\jdk1.6.0_37_32b/bin;C:\Program Files (x86)\Java\jre6\bin;C:\Program Files (x86)\Mozilla Firefox;C:\Program Files (x86)\Java\jre6\bin;C:\ruby200\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\TortoiseGit\bin;C:\Program Files\TortoiseSVN\bin;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\VisualSVN\bin;C:\strawberry\c\bin;C:\strawberry\perl\site\bin;C:\strawberry\perl\bin;C:\Chocolatey\bin;C:\sysinternals;"C:\Program Files (x86)\Java\jre6\bin" C:\Users\plossys\workspace\Test_Slave_Windows_VC_Build"C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\vcvarsall.bat" amd64 \Java\jre6\bin"" was unexpected at this time. Build step 'Windows Batch-Datei ausführen' marked build as failure Jenkins slave is connected via JNLP launcher (Java Applet), not via Windows service cause that raised too much hassle with firewall/group policy issues. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clearcase-ucm] (JENKINS-13234) Option to specify the view storage location - our case 8516
Jens Brejner
commented on JENKINS-13234
Option to specify the view storage location - our case 8516
Hi Iosif.
The original idea behind this case was to offer the ability to specify a name which is different from view. This would be implemented as a global configuration option for snapshot view folder name. Today the option is not available, any view CCUCM creates are located in the a job's workspace as ${workspace}\view\ As said, we can make a global configuration option with default value 'view', but whichever string is in the global configuration, will be used by all CCUCM jobs.
Your need is a bit different and as I understand it, it has nothing to do with the use of string 'view' for the local data representation. You need an option, where we change our use of the mkview command so we use -vws UNC-path instead of -stgloc -auto.
Do you see this as a global configuration option or as a per job option ? From my point of view I think we should arrange an online meeting and talk this through.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22342) Gitweb URL can be mangled (if it doesn't contain a path?)
Alan Clucas commented on JENKINS-22342 Gitweb URL can be mangled (if it doesnt contain a path?) Sent a pull request with a fix. Tested against Github and Gitweb. Now understand more than I want to about java serialization. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [robot-plugin] (JENKINS-22546) Add REST API to robot framework plugin
Jose Sa commented on JENKINS-22546 Add REST API to robot framework plugin Primarily we are interested in the “failed test cases” table content as shown in robot reports page, the “all test suites” may also be useful but that is secondary. 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] [groovy] (JENKINS-22582) Cannot submit configuration after removing groovy step
wolfs created JENKINS-22582 Cannot submit configuration after removing groovy step Issue Type: Bug Assignee: wolfs Components: groovy Created: 11/Apr/14 12:46 PM Description: After adding a groovy buildstep and removing it, clicking submit on the configuration page has no effect. The culprit seems to be the codemirror js plugin. Project: Jenkins Priority: Major Reporter: wolfs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22342) Gitweb URL can be mangled (if it doesn't contain a path?)
Mark Waite commented on JENKINS-22342 Gitweb URL can be mangled (if it doesnt contain a path?) Thanks. I've started the automated evaluation of the fix in my various environments. Would you consider modifying your changes to minimize your diffs from git-2.2.0? I've submitted a pull request to your repository with my proposed changes for you to evaluate. 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] [master-slave] (JENKINS-11992) Win7 x64: x86 Java runtime creates bad PATH on x64 OS causing ' \Java\jre6\bin was unexpected at this time.' error
Robert Grampp edited a comment on JENKINS-11992 Win7 x64: x86 Java runtime creates bad PATH on x64 OS causing \Java\jre6\bin was unexpected at this time. error I would like to see this bug raised to level MAJOR since a command line build with Microsoft Visual Studio 11 is impossible with this Jenkins behaviour. It crashes when calling Microsofts script vcvarsall.bat! Job log: C:\Users\plossys\workspace\Test_Slave_Windows_VC_Buildpath PATH=C:\Program Files (x86)\Java\jdk1.6.0_37_32b/bin;C:\Program Files (x86)\Java\jdk1.6.0_37_32b/bin;C:\Program Files (x86)\Java\jre6\bin;C:\Program Files (x86)\Mozilla Firefox;C:\Program Files (x86)\Java\jre6\bin;C:\ruby200\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\TortoiseGit\bin;C:\Program Files\TortoiseSVN\bin;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\VisualSVN\bin;C:\strawberry\c\bin;C:\strawberry\perl\site\bin;C:\strawberry\perl\bin;C:\Chocolatey\bin;C:\sysinternals;"C:\Program Files (x86)\Java\jre6\bin" C:\Users\plossys\workspace\Test_Slave_Windows_VC_Build"C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\vcvarsall.bat" amd64 \Java\jre6\bin"" was unexpected at this time. Build step 'Windows Batch-Datei ausführen' marked build as failure Jenkins slave is connected via JNLP launcher (Java Applet), not via Windows service cause that raised too much hassle with firewall/group policy issues. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22583) hetero-radio should work with multiple instances of the same ui
wolfs created JENKINS-22583 hetero-radio should work with multiple instances of the same ui Issue Type: Bug Assignee: wolfs Components: core Created: 11/Apr/14 1:20 PM Description: If there are multiple instances of the same page include (e.g. Build-Steps), then only the last one is opened (see https://github.com/wolfs/groovy-plugin/commit/68fb0018f602d55e04a332e240489b0761f6 where I fixed it for the groovy plugin). Adding a unique identifier solves the problem. Project: Jenkins Priority: Major Reporter: wolfs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22342) Gitweb URL can be mangled (if it doesn't contain a path?)
Alan Clucas commented on JENKINS-22342 Gitweb URL can be mangled (if it doesnt contain a path?) I think I've done the right thing to accept them. 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-20858) Images missing from Jenkins UI
Richard Mortimer commented on JENKINS-20858 Images missing from Jenkins UI The fix went into 1.558. I have that running here and it is now unpacking the WAR file into /var/cache/jenkins/war as per the --webroot setting. 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-22442) Jetty exploding war to /tmp is a bad idea
Richard Mortimer commented on JENKINS-22442 Jetty exploding war to /tmp is a bad idea The fix went into 1.558. I have that running here and it is now unpacking the WAR file into /var/cache/jenkins/war as per the --webroot setting. 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-17526) Broken CSS when reloading Jenkins after a time of inactivity
Richard Mortimer commented on JENKINS-17526 Broken CSS when reloading Jenkins after a time of inactivity The fix for JENKINS-22442 restores the previous behaviour and 1.558 now honours the --webroot commandline argument again. 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-20682) Starting Jenkins with defined --webroot or JETTY_HOME not working.
Richard Mortimer resolved JENKINS-20682 as Duplicate Starting Jenkins with defined --webroot or JETTY_HOME not working. Duplicate of JENKINS-22442 Change By: Richard Mortimer (11/Apr/14 1:45 PM) Status: Open Resolved Resolution: Duplicate 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] [htmlpublisher] (JENKINS-7139) HtmlPublisher should be able to handle wildcard paths to find multiple html files
Grégory Joseph commented on JENKINS-7139 HtmlPublisher should be able to handle wildcard paths to find multiple html files Having the option to list matching files would also be valuable in some cases; if I have 80 reports, I don't really want 80 tabs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-user-vars] (JENKINS-19187) User variables are not set to Maven3 build
SCM/JIRA link daemon commented on JENKINS-19187 User variables are not set to Maven3 build Code changed in jenkins User: Clifford Sanders Path: src/main/java/org/jenkinsci/plugins/builduser/BuildUser.java http://jenkins-ci.org/commit/build-user-vars-plugin/1984212a790660bfde9410f27394ce359077eb76 Log: FIXED JENKINS-19187 User variables are not set to Maven3 build This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-user-vars] (JENKINS-19187) User variables are not set to Maven3 build
SCM/JIRA link daemon commented on JENKINS-19187 User variables are not set to Maven3 build Code changed in jenkins User: Clifford Sanders Path: src/main/java/org/jenkinsci/plugins/builduser/BuildUser.java http://jenkins-ci.org/commit/build-user-vars-plugin/61450e9337aaf55ecd280f03bc6473e076baf729 Log: Merge pull request #3 from clifford-github/master FIXED JENKINS-19187 User variables are not set to Maven3 build Compare: https://github.com/jenkinsci/build-user-vars-plugin/compare/0a44831b76cc...61450e9337aa This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-user-vars] (JENKINS-19187) User variables are not set to Maven3 build
SCM/JIRA link daemon resolved JENKINS-19187 as Fixed User variables are not set to Maven3 build Change By: SCM/JIRA link daemon (11/Apr/14 2:43 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] [git] (JENKINS-22342) Gitweb URL can be mangled (if it doesn't contain a path?)
Alan Clucas commented on JENKINS-22342 Gitweb URL can be mangled (if it doesnt contain a path?) Just wondered if you wanted them squashing down? 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] [ldap] (JENKINS-21475) Multiple LDAP OU support
Jesse Glick updated JENKINS-21475 Multiple LDAP OU support Change By: Jesse Glick (11/Apr/14 3:01 PM) Assignee: KohsukeKawaguchi Component/s: 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.
[JIRA] [changelog-history] (JENKINS-22560) Deadlocked executors on slaves since 1.556
Dirk Kuypers commented on JENKINS-22560 Deadlocked executors on slaves since 1.556 Just a short feedback: Jenkins ver. 1.560-SNAPSHOT (private-04/10/2014 15:41 GMT-jenkins) is running since about 8 hours now without a deadlock, so I think the bug is gone. Thanks a lot for the fast fix! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hudsontrayapp] (JENKINS-22584) Tray app appears to not update properly under latest JRE
Phil Rutherford created JENKINS-22584 Tray app appears to not update properly under latest JRE Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: hudsontrayapp Created: 11/Apr/14 3:28 PM Description: On JRE 7 and latest Jenkins it appears that this app stops updating from the server after a short while, until launched again. Project: Jenkins Priority: Major Reporter: Phil Rutherford This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22342) Gitweb URL can be mangled (if it doesn't contain a path?)
Mark Waite commented on JENKINS-22342 Gitweb URL can be mangled (if it doesnt contain a path?) I would prefer if you squashed them down so that there isn't an intermediate state where the constructor is missing. 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-15331) Workaround Windows unpredictable file locking in Util.deleteContentsRecursive
pjdarton updated JENKINS-15331 Workaround Windows unpredictable file locking in Util.deleteContentsRecursive I've just attached a new patch file "0001-Proposed-solution-to-JENKINS-15331.patch" This one is based on the current Jenkins master trunk (at the time of writing, that's aimed at 1.560-SNAPSHOT). This is slightly different than the earlier patch: 1) The configuration for garbage-collection when deletes fail now defaults to "false" on all platforms. 2) The garbage-collection should now get called if it's enabled (the previous version had a bug). Change By: pjdarton (11/Apr/14 4:03 PM) Attachment: 0001-Proposed-solution-to-JENKINS-15331.patch 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] [analysis-core] (JENKINS-20185) Long pause after end of run
Joe Hansche updated JENKINS-20185 Long pause after end of run Change By: Joe Hansche (11/Apr/14 4:35 PM) Component/s: analysis-core Component/s: checkstyle 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-18537) ArrayIndexOutOfBoundsException during Jenkins.doConfigSubmit; need XStream 1.4.6
Pedro Lopez commented on JENKINS-18537 ArrayIndexOutOfBoundsException during Jenkins.doConfigSubmit; need XStream 1.4.6 If for the same operation, now we have a core dump... For me it seems that the fix not solve completely the problem. Did you try the fix on a AIX machine ? For your information I have same problem on 1.558 version. Why did you said probably unrelated ? Thank's for your feedback. 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] [analysis-core] (JENKINS-20185) Long pause after end of run
Joe Hansche assigned JENKINS-20185 to Ulli Hafner Long pause after end of run Change By: Joe Hansche (11/Apr/14 4:38 PM) Assignee: UlliHafner 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] [analysis-core] (JENKINS-20185) Long pause after end of run
Joe Hansche
commented on JENKINS-20185
Long pause after end of run
I'm seeing this as well, long pause on "Computing warning deltas". The job has already been updated to SUCCESS, and the build time has already been recorded (as ~30-45 seconds). But the job continues to spin for about another 2-3 minutes, which blocks the executors, and blocks pending builds of the same job in the queue ("Build #1234 is already in progress ..."). There does not appear to be a way to disable the computation of deltas, only option is to disable the collection of the checkstyle stats.
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] [analysis-core] (JENKINS-20185) Long pause after end of run
Joe Hansche assigned JENKINS-20185 to Unassigned Long pause after end of run Change By: Joe Hansche (11/Apr/14 5:02 PM) Assignee: UlliHafner 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] [analysis-core] (JENKINS-20185) Long pause after end of run
Joe Hansche
edited a comment on JENKINS-20185
Long pause after end of run
I'm seeing this as well, long pause on "Computing warning deltas". The job has already been updated to SUCCESS, and the build time has already been recorded (as ~30-45 seconds). But the job continues to spin for about another 2-3 minutes, which blocks the executors, and blocks pending builds of the same job in the queue ("Build #1234 is already in progress ..."). There does not appear to be a way to disable the computation of deltas, only option is to disable the collection of the checkstyle stats.
EDIT: spoke too soon... I disabled the checkstyle plugin for this build, and the build continues to spin even after setting the build status and duration, and without the CHECKSTYLE entries in the log. I have no other post-build actions, so I'm not sure what it's doing in the meantime...
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] [categorized-view] (JENKINS-22585) Reconfiguration of categorized-view overrides previous configuration
Maciej Gregorczyk updated JENKINS-22585 Reconfiguration of categorized-view overrides previous configuration Change By: Maciej Gregorczyk (11/Apr/14 5:46 PM) Description: Aftercreatinganinitialconfigurationofcategorizedview(att.1.png) !1.png! theviewiscreatedcorrectly(withonegroupbasedonregular_expression_)(att.2.png)NowItriedtoaddnewregular_expression_fornextgroup.Inoticedthatinselectedjobssectionjobsfromthelastregexgrouparedissabled(att3.png).Addingadditionalgroupbasedonregex(att3.png)dissablespreviouslyconfiguration.Groupfromtheinitialconfigurationisnotvisibleintheview.Visibleisonlynewllycreated.(att.4.png)Itisimmposibletore-selectallissueseachtimeIaddnewcategory.(Ihavenearly300jobs). 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] [categorized-view] (JENKINS-22585) Reconfiguration of categorized-view overrides previous configuration
Maciej Gregorczyk updated JENKINS-22585 Reconfiguration of categorized-view overrides previous configuration Change By: Maciej Gregorczyk (11/Apr/14 5:47 PM) Description: Aftercreatinganinitialconfigurationofcategorizedview(att.1.png)!1.png!theviewiscreatedcorrectly(withonegroupbasedonregular_expression_)(att.2.png) !2.png! NowItriedtoaddnewregular_expression_fornextgroup.Inoticedthatinselectedjobssectionjobsfromthelastregexgrouparedissabled(att3.png). !3.png! Addingadditionalgroupbasedonregex(att3.png)dissablespreviouslyconfiguration.Groupfromtheinitialconfigurationisnotvisibleintheview.Visibleisonlynewllycreated.(att.4.png) !4.png! Itisimmposibletore-selectallissueseachtimeIaddnewcategory.(Ihavenearly300jobs). 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] [categorized-view] (JENKINS-22585) Reconfiguration of categorized-view overrides previous configuration
Maciej Gregorczyk assigned JENKINS-22585 to taksan Reconfiguration of categorized-view overrides previous configuration Change By: Maciej Gregorczyk (11/Apr/14 5:50 PM) Assignee: taksan 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] [categorized-view] (JENKINS-22585) Reconfiguration of categorized-view overrides previous configuration
Maciej Gregorczyk created JENKINS-22585 Reconfiguration of categorized-view overrides previous configuration Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: 1.png, 2.png, 3.png, 4.png Components: categorized-view Created: 11/Apr/14 5:45 PM Description: After creating an initial configuration of categorized view (att. 1.png) the view is created correctly (with one group based on regular _expression_) (att. 2.png) Now I tried to add new regular _expression_ for next group. I noticed that in selected jobs section jobs from the last regex group are dissabled (att 3.png). Adding additional group based on regex (att 3.png) dissables previously configuration. Group from the initial configuration is not visible in the view. Visible is only newlly created. (att. 4.png) It is immposible to re-select all issues each time I add new category. (I have nearly 300 jobs). Environment: Jenkins ver. 1.558 Categorized view ver. 1.4 Project: Jenkins Priority: Critical Reporter: Maciej Gregorczyk 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] (JENKINS-10234) Junit result archiver getting stuck for a long time in concurrent builds
Jesse Glick reopened JENKINS-10234 Junit result archiver getting stuck for a long time in concurrent builds Since JENKINS-9913 is covering only the reporting of checkpoints, this should be reopened: JUnitResultArchiver.CHECKPOINT still exists, and probably should not. Needs to be determined if anything needs to be done to replace it, in case a build with a higher number in fact finishes before one with a lower number, so calculation of test regressions cannot be done accurately when the result is published (in case anyone even cares about build-to-build diffs for a concurrent-capable job). Until the earlier build finishes, will the later build’s test result display show any “regressions” (against the last completed build), or show no regressions ever, or throw exceptions? After the earlier build finishes, will the later’s result display show regressions against the earlier build, or against the last completed build at the time of this build’s completion, or do something else? In other words, are calls to getPreviousResult made on demand whenever a build-to-build diff is requested (great)? Or made once when the build completes (not great but adequate)? Or does something really break? My casual inspection of the code suggests that there is some improper caching (CaseResult.failedSince) but that code generally defends against a prior build having no test result action, meaning that simply deleting CHECKPOINT would cause little harm. Change By: Jesse Glick (11/Apr/14 5:54 PM) Resolution: Duplicate 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] [timestamper] (JENKINS-22586) System Time ignores the TimeZone
Christian Höltje created JENKINS-22586 System Time ignores the TimeZone Issue Type: Bug Assignee: stevengbrown Components: timestamper Created: 11/Apr/14 6:33 PM Description: I have Jenkins started with -Dorg.apache.commons.jelly.tags.fmt.timeZone="America/Los_Angeles" The server's TZ is EDT (it's in Pittsburgh). However, the "System Clock" setting for the TimeStamper is showing EDT time, not PDT. It should be using the passed in TimeZone. Project: Jenkins Priority: Major Reporter: Christian Höltje 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] [categorized-view] (JENKINS-22585) Reconfiguration of categorized-view overrides previous configuration
taksan commented on JENKINS-22585 Reconfiguration of categorized-view overrides previous configuration I will see into it as soon as possible! Thanks for reporting 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-18537) ArrayIndexOutOfBoundsException during Jenkins.doConfigSubmit; need XStream 1.4.6
Jesse Glick commented on JENKINS-18537 ArrayIndexOutOfBoundsException during Jenkins.doConfigSubmit; need XStream 1.4.6 now we have a core dump Possibly a bug in your JRE. May or may not have anything to do with XStream. This fix may simply have allowed Jenkins to proceed past the error reported here, on to some unrelated code which triggers a Java crash. Did you try the fix on a AIX machine? No, I do not know of any core Jenkins developers with access to an AIX machine 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] [core] (JENKINS-22583) hetero-radio should work with multiple instances of the same ui
Jesse Glick updated JENKINS-22583 hetero-radio should work with multiple instances of the same ui Change By: Jesse Glick (11/Apr/14 7:04 PM) Labels: form-datajelly 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-22583) hetero-radio should work with multiple instances of the same ui
Jesse Glick updated JENKINS-22583 hetero-radio should work with multiple instances of the same ui Change By: Jesse Glick (11/Apr/14 7:07 PM) URL: https://github.com/jenkinsci/jenkins/pull/1182 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] [jclouds-jenkins] (JENKINS-22587) JClouds does not honor security group against OpenStack
Andrew Grimberg created JENKINS-22587 JClouds does not honor security group against OpenStack Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: jclouds-jenkins Created: 11/Apr/14 7:50 PM Description: Version 2.5.1 of the JClouds plugin added the ability to define Security Groups that VMs should launch under. I've seen in the logs that it is setting something related to it but VMs are still being forcibly created in the jclouds-instance_name security group which eventually gets deleted when no more slaves are in it and not recreated on the next slave creation. Environment: CentOS 6.5 OpenJDK 1.7.0 Jenkins 1.558 JClouds plugin 2.5.1 OpenStack (Havanna) Project: Jenkins Labels: jclouds Priority: Major Reporter: Andrew Grimberg 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] [ui-changes] (JENKINS-22588) No description or tool tip of what a promotion is on the job/job/id/promotion/ page
Michael Martinez created JENKINS-22588 No description or tool tip of what a promotion is on the job/job/id/promotion/ page Issue Type: Bug Assignee: Unassigned Components: ui-changes Created: 11/Apr/14 8:53 PM Description: As an engineer who has used Jenkins, Bamboo and many other Continuous Integration services, when I see a "Promotions" page attached to a build with buttons like "Reexecute Promotions", it would be helpful to know what specifically, a "promotion" is by reading about it on the page via tool tips or help text. Project: Jenkins Priority: Major Reporter: Michael Martinez 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] [vs-code-metrics] (JENKINS-22589) Command line field entries do not undergo variable substitution before metrics program is launched
Jon Starbird created JENKINS-22589 Command line field entries do not undergo variable substitution before metrics program is launched Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: vs-code-metrics Created: 11/Apr/14 9:49 PM Description: If using Jenkins variables in the command line parameters they will not be substituted before run time. Workaround - use Windows command line method of using Environment variables, %varname%, instead of the Jenkins variables. Environment: Jenkins 1.532.2 VS Code Metrics plugin - 1.7 Project: Jenkins Priority: Minor Reporter: Jon Starbird This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-22590) Promotion permalinks not offered when job name is parameterized
Jesse Glick created JENKINS-22590 Promotion permalinks not offered when job name is parameterized Issue Type: Bug Assignee: Unassigned Components: copyartifact Created: 11/Apr/14 9:59 PM Description: If you specify an upstream job with a promotion process, and select the permalink option, you are able to request a permalink corresponding to the last promotion. (Eventually—for some reason the pulldown does not refresh very reliably so you have to click around a few times to get it to appear.) But if the upstream job is defined as $SOME_PARAMETER, the pulldown only shows standard permalinks, so there is no apparent way to request the promotion from the UI.(Presumably you could edit config.xml directly.) Environment: 1.532.x Project: Jenkins Labels: promoted-builds Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-22590) Promotion permalinks not offered when job name is parameterized
Jesse Glick commented on JENKINS-22590 Promotion permalinks not offered when job name is parameterized Should this pulldown just be made into an editable combo box? Or text field with completion? 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-22485) Cannot save job configuration after deleting a parameter
Townsend Duong commented on JENKINS-22485 Cannot save job configuration after deleting a parameter I've noticed the same issue on Jenkins 1.558 in Google Chrome 33/34. As a workaround, I am able to delete the parameter and then save using Internet Explorer (IE8). 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-22485) Cannot save job configuration after deleting a parameter
Jeremy Kissell commented on JENKINS-22485 Cannot save job configuration after deleting a parameter Oh, good to know. I didn't try that, I'm a Mac user, so I tried from Safari and Chrome and neither 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] [categorized-view] (JENKINS-22585) Reconfiguration of categorized-view overrides previous configuration
taksan started work on JENKINS-22585 Reconfiguration of categorized-view overrides previous configuration Change By: taksan (12/Apr/14 12:41 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-13502) Editing any job removes inaccessible downstream jobs from all accessible jobs
SCM/JIRA link daemon commented on JENKINS-13502 Editing any job removes inaccessible downstream jobs from all accessible jobs Code changed in jenkins User: Jesse Glick Path: test/src/test/groovy/hudson/model/AbstractProjectTest.groovy http://jenkins-ci.org/commit/jenkins/b53139e0db15d1a9b8f6b8eac5b08c33ea40566b Log: Test of JENKINS-13502 fix is obsolete since we no longer check permissions when configuring triggers. 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-16956) Require authentication for build triggers
SCM/JIRA link daemon commented on JENKINS-16956 Require authentication for build triggers Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/tasks/BuildTrigger.java core/src/main/resources/hudson/tasks/Messages.properties test/src/test/java/hudson/tasks/BuildTriggerTest.java http://jenkins-ci.org/commit/jenkins/d31ff2fed352cc15d808cb8aa91eba6576ed13ae Log: JENKINS-16956 More compatible behavior: if no QIA’s are configured yet, fall back to running as SYSTEM. Also make a best effort to issue a warning in the log if downstream builds might skipped due to lack of authentication; or if downstream build permissions might not be checked due to legacy 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-16956) Require authentication for build triggers
SCM/JIRA link daemon resolved JENKINS-16956 as Fixed Require authentication for build triggers Change By: SCM/JIRA link daemon (12/Apr/14 1:14 AM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-16956) Require authentication for build triggers
SCM/JIRA link daemon commented on JENKINS-16956 Require authentication for build triggers Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/AbstractProject.java core/src/main/java/hudson/tasks/BuildTrigger.java test/src/test/java/hudson/tasks/BuildTriggerTest.java http://jenkins-ci.org/commit/jenkins/48e92efaed7d48d6bd515a7844f9c055a8e27f6b Log: JENKINS-16956 Make BuildTrigger.execute pay attention to build permissions, rather than checking the configuring user. 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-16956) Require authentication for build triggers
SCM/JIRA link daemon commented on JENKINS-16956 Require authentication for build triggers Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/model/queue/Tasks.java core/src/main/java/jenkins/security/QueueItemAuthenticator.java core/src/main/java/jenkins/triggers/ReverseBuildTrigger.java http://jenkins-ci.org/commit/jenkins/7f76a93dd947cb0180a36d2ce54b1e3c2ddaf3bc Log: FIXED JENKINS-16956 Noting merge of #1172. Compare: https://github.com/jenkinsci/jenkins/compare/a1cd49b948ab...7f76a93dd947 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] [categorized-view] (JENKINS-22585) Reconfiguration of categorized-view overrides previous configuration
taksan commented on JENKINS-22585 Reconfiguration of categorized-view overrides previous configuration https://github.com/jenkinsci/categorized-view-plugin/commit/4c0a5bf6204910fd4f4e2bb1e4021b0e01683ff3 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] [categorized-view] (JENKINS-22585) Reconfiguration of categorized-view overrides previous configuration
taksan edited a comment on JENKINS-22585 Reconfiguration of categorized-view overrides previous configuration Fixed on version 1.6 https://github.com/jenkinsci/categorized-view-plugin/commit/4c0a5bf6204910fd4f4e2bb1e4021b0e01683ff3 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] [categorized-view] (JENKINS-19466) View sorting breaks categorized groups.
taksan edited a comment on JENKINS-19466 View sorting breaks categorized groups. Fixed on 1.4 https://github.com/jenkinsci/categorized-view-plugin/commit/826ce0556c347d2cc188ac6a8239810f8822ad96 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] [categorized-view] (JENKINS-22580) NullPointerException flooding logs
taksan resolved JENKINS-22580 as Fixed NullPointerException flooding logs Fixed on version 1.5 https://github.com/jenkinsci/categorized-view-plugin/commit/52f19a2a573bb0771ba378c7ec27f0d0b97c90c0 Change By: taksan (12/Apr/14 1:32 AM) Status: InProgress 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] [categorized-view] (JENKINS-19466) View sorting breaks categorized groups.
taksan edited a comment on JENKINS-19466 View sorting breaks categorized groups. Fixed on 1.4 https://github.com/jenkinsci/categorized-view-plugin/commit/826ce0556c347d2cc188ac6a8239810f8822ad96 https://github.com/jenkinsci/categorized-view-plugin/commit/a1f9890b8ae293470997d6c884bbe3d561bcb31a https://github.com/jenkinsci/categorized-view-plugin/commit/3da36ae0196151d174498d7c6424484676e4da66 https://github.com/jenkinsci/categorized-view-plugin/commit/2e5a10503dd656cb4c9b2894e8347a792967c172 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-16956) Require authentication for build triggers
dogfood commented on JENKINS-16956 Require authentication for build triggers Integrated in jenkins_main_trunk #3296 JENKINS-16956 Make BuildTrigger.execute pay attention to build permissions, rather than checking the configuring user. (Revision 48e92efaed7d48d6bd515a7844f9c055a8e27f6b) JENKINS-16956 More compatible behavior: if no QIA’s are configured yet, fall back to running as SYSTEM. (Revision d31ff2fed352cc15d808cb8aa91eba6576ed13ae) FIXED JENKINS-16956 Noting merge of #1172. (Revision 7f76a93dd947cb0180a36d2ce54b1e3c2ddaf3bc) Result = SUCCESS Jesse Glick : 48e92efaed7d48d6bd515a7844f9c055a8e27f6b Files : test/src/test/java/hudson/tasks/BuildTriggerTest.java core/src/main/java/hudson/model/AbstractProject.java core/src/main/java/hudson/tasks/BuildTrigger.java Jesse Glick : d31ff2fed352cc15d808cb8aa91eba6576ed13ae Files : test/src/test/java/hudson/tasks/BuildTriggerTest.java core/src/main/resources/hudson/tasks/Messages.properties core/src/main/java/hudson/tasks/BuildTrigger.java Jesse Glick : 7f76a93dd947cb0180a36d2ce54b1e3c2ddaf3bc Files : core/src/main/java/hudson/model/queue/Tasks.java changelog.html core/src/main/java/jenkins/triggers/ReverseBuildTrigger.java core/src/main/java/jenkins/security/QueueItemAuthenticator.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [selenium] (JENKINS-15721) Cannot add browsers due to template include exception
Richard Lavoie resolved JENKINS-15721 as Fixed Cannot add browsers due to template include exception 2.4 has just been released and solves the issue Change By: Richard Lavoie (12/Apr/14 3:48 AM) Status: InProgress 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] [selenium] (JENKINS-18638) Selenium Plugin New Configuration error: 'config.jelly' for class hudson.plugins.selenium.configuration.browser.selenium.IEBrowser
Richard Lavoie resolved JENKINS-18638 as Fixed Selenium Plugin New Configuration error: config.jelly for class hudson.plugins.selenium.configuration.browser.selenium.IEBrowser 2.4 has just been released and solves the issue Change By: Richard Lavoie (12/Apr/14 3:47 AM) Status: Reopened 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] [selenium] (JENKINS-12805) Let Jenkins user to stop/start/restart Selenium grid server (hub)
Richard Lavoie resolved JENKINS-12805 as Fixed Let Jenkins user to stop/start/restart Selenium grid server (hub) Hub can be restarted now in 2.4 Change By: Richard Lavoie (12/Apr/14 3:50 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] [selenium] (JENKINS-12754) selenium-grid .for( :remote, :desired_capabilities = :chrome ) should work, but doesn't
Richard Lavoie resolved JENKINS-12754 as Fixed selenium-grid .for( :remote, :desired_capabilities = :chrome ) should work, but doesnt Works now when you specify the path to the chromedriver executable Change By: Richard Lavoie (12/Apr/14 3: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] [selenium] (JENKINS-22069) Client can not register to Selenium grid if jenkins is served via a proxy
Richard Lavoie resolved JENKINS-22069 as Fixed Client can not register to Selenium grid if jenkins is served via a proxy Version 2.4 now has a way to define which host you want the slaves to connect to. It can either be to use the default jenkins URL or another user defined static ip/host Change By: Richard Lavoie (12/Apr/14 3:52 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] [selenium] (JENKINS-18102) Grid Hub version needs to match latest version at Selenium HQ
Richard Lavoie resolved JENKINS-18102 as Fixed Grid Hub version needs to match latest version at Selenium HQ Version 2.4 has now 2.41.0 bundled in it along with IEServerDriver executables Change By: Richard Lavoie (12/Apr/14 3:54 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] [selenium] (JENKINS-12675) Add an option to install specific selenium version on the running nodes
Richard Lavoie resolved JENKINS-12675 as Fixed Add an option to install specific selenium version on the running nodes Change By: Richard Lavoie (12/Apr/14 3:55 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] [selenium] (JENKINS-12675) Add an option to install specific selenium version on the running nodes
Richard Lavoie commented on JENKINS-12675 Add an option to install specific selenium version on the running nodes It is unfortunately not that easy because when new versions of selenium gets out, sometimes it comes with new servers binaries (IE driver server) which is hard to decouple from the main plugin. Version 2.4 has been released today and includes 2.41.0 which was just released. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [chromedriver] (JENKINS-21473) Selenium plugin Custom RC node configuration produces config lacking JVM options and starred browser names
Richard Lavoie resolved JENKINS-21473 as Fixed Selenium plugin Custom RC node configuration produces config lacking JVM options and starred browser names Binary path should be solved in 2.4 which was just released. Change By: Richard Lavoie (12/Apr/14 3:58 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] [htmlpublisher] (JENKINS-7139) HtmlPublisher should be able to handle wildcard paths to find multiple html files
mcrooney commented on JENKINS-7139 HtmlPublisher should be able to handle wildcard paths to find multiple html files If anyone wants to give this a stab, there was a pull request at https://github.com/jenkinsci/htmlpublisher-plugin/pull/5 that had to be reverted as it caused https://issues.jenkins-ci.org/browse/JENKINS-16083. So it probably isn't a huge amount of work to fix the pull request and solve its regression. 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.
