[JIRA] [cppcheck] (JENKINS-21927) Redesign of build summary page
Michal Turek created JENKINS-21927 Redesign of build summary page Issue Type: Improvement Affects Versions: current Assignee: Michal Turek Attachments: exception.txt, summary_after.png, summary_before.png Components: cppcheck Created: 23/Feb/14 11:46 AM Description: Redesign Cppcheck summary on the build page to contain a sortable table with the same information that will be better readable. The current implementation displays "(nb/new)" legend in the middle of each line, zero new value is displayed as "+0" and resolved issues are not present at all (negative values not implemented). There is also NullPointerException in CppcheckSummary.createReportSummaryDetails() if the first build is displayed (attached). Environment: All, plugin version 1.14 Project: Jenkins Priority: Major Reporter: Michal Turek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cppcheck] (JENKINS-21927) Redesign of build summary page
Michal Turek started work on JENKINS-21927 Redesign of build summary page Change By: Michal Turek (23/Feb/14 11:56 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/groups/opt_out.
[JIRA] [cppcheck] (JENKINS-21927) Redesign of build summary page
Michal Turek commented on JENKINS-21927 Redesign of build summary page Implemented in https://github.com/mixalturek/cppcheck-plugin/commit/8edec09b5c49d22fdb8519e66827fe2abce81b64. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [plot] (JENKINS-21493) NullPointerException in Publisher
Nikolaus Krismer commented on JENKINS-21493 NullPointerException in Publisher Same problem here. I am using jenkins v. 1.546 and Plot 1.6 with a xml file (type: nodeset). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-19345) NoClassDefFoundError on project build
Konrad Windszus commented on JENKINS-19345 NoClassDefFoundError on project build We are running exactly into that issue with the git-plugin 2.0.3. But it works with 2.0.1. So there must be a regression bug in 2.0.3. The weird thing is, that we indeed have the mailer plugin installed and still run into that error with git-plugin 2.0.3 FATAL: hudson/tasks/Mailer$UserProperty java.lang.NoClassDefFoundError: hudson/tasks/Mailer$UserProperty at hudson.plugins.git.GitChangeLogParser.parseCommit(GitChangeLogParser.java:80) at hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:74) at hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:51) at hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:29) at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:903) at hudson.model.AbstractBuild.getChangeSet(AbstractBuild.java:877) at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:413) at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:410) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:710) at hudson.model.Run.execute(Run.java:1690) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:246) Caused by: java.lang.ClassNotFoundException: hudson.tasks.Mailer$UserProperty at org.apache.tools.ant.AntClassLoader.findClassInComponents(AntClassLoader.java:1365) at org.apache.tools.ant.AntClassLoader.findClass(AntClassLoader.java:1315) at org.apache.tools.ant.AntClassLoader.loadClass(AntClassLoader.java:1068) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) ... 13 more This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ownership] (JENKINS-21838) Allow to authenticate as a job's owner during the build
ikedam updated JENKINS-21838 Allow to authenticate as a jobs owner during the build I cannot get what you point. You mean I should update the minor version of authorize-project plugin, not the incremental version as a new API is added? Change By: ikedam (23/Feb/14 1:49 PM) Component/s: authorize-project This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ownership] (JENKINS-21838) Allow to authenticate as a job's owner during the build
Oleg Nenashev commented on JENKINS-21838 Allow to authenticate as a jobs owner during the build Yes, I think so. BTW, it is just a proposal for future. Please feel free to accept or decline it. I'll appreciate a new functionality in any case This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-14539) Incorrectly Using Committer User Full Name in resolving Committer Email Address
Alex Earl commented on JENKINS-14539 Incorrectly Using Committer User Full Name in resolving Committer Email Address Try setting the "Create new accounts base on author/committer's email" option in the global config. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mailer] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
Alex Earl commented on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification I submitted a pull request for "fixing" this. https://github.com/jenkinsci/mailer-plugin/pull/11 I'm also planning on making a pull request for the Mercurial plugin that would create user accounts a little differently. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21168) Git core.symlinks option not correctly auto-detected on Windows
Mark Waite commented on JENKINS-21168 Git core.symlinks option not correctly auto-detected on Windows The git-client-plugin creates a new repository differently than a typical git command line client. It initializes a repository using JGit (creating the .git directory, etc.), and then uses a "git fetch" to bring in the contents from the remote repository. The specific details of the "git fetch" command will need more time for me to extract them from the source code. I assume that must be the source of the differences between what you observe from the command line and from within Jenkins. The "git fetch" command is used as a way to reduce the number of cases where a "git" command will hang waiting for interactive authentication. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mailer] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
Jesse Glick commented on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification Your test case is reproducible but it does not really tell us anything, because the malformed culprits are simply being copied from earlier builds (#2 #5). What is needed is a test case which demonstrates fresh additions to the culprits list with the malformed names; specifically the call stack of User.init with an incorrect fullName. Note that the Mercurial changelog.xml in these builds show the correct text. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mailer] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
Alex Earl commented on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification @Jesse, I agree it should be calling it with the 's, but I think because of this code in AbstractBuild.java, it will call it with the _'s https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/AbstractBuild.java#L729 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mailer] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
Jesse Glick commented on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification Still working on reproducing from scratch. I think I may see what the issue is. If I am right, it is a bug in core as I suspected on Dec 19. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21861) option to include attachment with console.txt from failed slaves
Alex Earl commented on JENKINS-21861 option to include attachment with console.txt from failed slaves @Mike, my jobs run on slave machines. I can set it up so that they don't run on master at all and I still get the full log output from the 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/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21861) option to include attachment with console.txt from failed slaves
Alex Earl commented on JENKINS-21861 option to include attachment with console.txt from failed slaves I'll dig into this a bit more and see what I can find. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cppcheck] (JENKINS-21928) Redesign of results page
Michal Turek created JENKINS-21928 Redesign of results page Issue Type: Improvement Affects Versions: current Assignee: Michal Turek Attachments: details_after.png, results_before.png Components: cppcheck Created: 23/Feb/14 6:14 PM Description: There are several issues on the results page: All tables have 100% width of the page. It would be better if summary table has rows instead of columns. Errors trend is not necessary, it can be part of summary table (footer). Column headers in details table look more like identifiers than words. Text in details table is not wrapping, so the page contains unnecessary horizontal scroll bar. Environment: All, plugin version 1.14 Project: Jenkins Priority: Major Reporter: Michal Turek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cppcheck] (JENKINS-21928) Redesign of results page
Michal Turek started work on JENKINS-21928 Redesign of results page Change By: Michal Turek (23/Feb/14 6:14 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
Jesse Glick updated JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification Change By: Jesse Glick (23/Feb/14 6:23 PM) Status: Reopened Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
Jesse Glick updated JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification Change By: Jesse Glick (23/Feb/14 6:23 PM) Labels: user Assignee: JesseGlick Component/s: core Component/s: mailer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
Jesse Glick started work on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification Change By: Jesse Glick (23/Feb/14 6:23 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
Jesse Glick commented on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification OK, finally reproduced. The mentioned line 729 is innocent, and really AbstractBuild as a whole is doing nothing wrong; nor, as far as I can tell, are the Mailer or Mercurial plugins. The problem (as I surmised on Sep 16) is in User itself. When you run a build that fails, and it has a changelog mentioning at least one user with full name email address who does not yet have any permanent record in $JENKINS_HOME/users/$id/config.xml, the build stores a culprits field listing the user’s ID, which correctly includes underscores. So long as Jenkins remains running, the loaded User object is fine, and mailing would work. However if you restart Jenkins, and then run a new build that again fails, but with no changelog this time, getCulprits inherits the culprits list from the previous build. This time User.get(id) is called and since there is no persistent record for that user, there is no way of reconstructing the proper fullName—we only have the sanitized ID. Therefore the User is constructed with a bogus fullName and mailing fails. Looking into a 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/groups/opt_out.
[JIRA] [core] (JENKINS-20965) SSH CLI -v (console output) option causes high master CPU utilization
SCM/JIRA link daemon commented on JENKINS-20965 SSH CLI -v (console output) option causes high master CPU utilization Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/Run.java http://jenkins-ci.org/commit/jenkins/5d91ed77f7402133fd7c9e77b1a6676c6695ec5a Log: Merge branch 'JENKINS-20965' of github.com:christ66/jenkins This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20965) SSH CLI -v (console output) option causes high master CPU utilization
SCM/JIRA link daemon commented on JENKINS-20965 SSH CLI -v (console output) option causes high master CPU utilization Code changed in jenkins User: christ66 Path: core/src/main/java/hudson/model/Run.java http://jenkins-ci.org/commit/jenkins/82e94e5e738c988c36181d8c0ff6b9ffed846bcc Log: FIXED JENKINS-20965 Run.writeWholeLogTo causes high CPU usage. Wait one second before writing to log files. Switched to while loop to prevent extra one second delay. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20965) SSH CLI -v (console output) option causes high master CPU utilization
SCM/JIRA link daemon resolved JENKINS-20965 as Fixed SSH CLI -v (console output) option causes high master CPU utilization Change By: SCM/JIRA link daemon (23/Feb/14 6:31 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/groups/opt_out.
[JIRA] [core] (JENKINS-20965) SSH CLI -v (console output) option causes high master CPU utilization
Jesse Glick updated JENKINS-20965 SSH CLI -v (console output) option causes high master CPU utilization Change By: Jesse Glick (23/Feb/14 6:31 PM) Labels: cli lts-candidate performance This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20965) SSH CLI -v (console output) option causes high master CPU utilization
SCM/JIRA link daemon commented on JENKINS-20965 SSH CLI -v (console output) option causes high master CPU utilization Code changed in jenkins User: Jesse Glick Path: changelog.html http://jenkins-ci.org/commit/jenkins/0d77f1795cf97a5e7dbd43f066ab5f97753b464b Log: JENKINS-20965 Noting merge of #1137. Compare: https://github.com/jenkinsci/jenkins/compare/761af2d2dbd2...0d77f1795cf9 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21861) option to include attachment with console.txt from failed slaves
Mike Dubman commented on JENKINS-21861 option to include attachment with console.txt from failed slaves hmmm.. interesting, we have tens projects (multi-configuration projects) and mail sent from master always look like this: hpc-ompi-shmem - Build # 2217 - Still Failing: Git: origin/master 368c6bb3261e77d1c12f473ed692ca21bf28c7d3 Check console output at http://hpc-master.lab.mtl.com:8080/job/hpc-ompi-shmem/2217/ to view the results. Build log: ... Started by an SCM change EnvInject - Loading node environment variables. Building on master in workspace /scrap/jenkins/workspace/hpc-ompi-shmem-2 Deleting project workspace... done Checkout:hpc-ompi-shmem-2 / /scrap/jenkins/workspace/hpc-ompi-shmem-2 - hudson.remoting.LocalChannel@7fd2c81d Using strategy: Default Last Built Revision: Revision 9fe0dd82ba28da9e918d0c8495c42d04dac628ac (origin/master, origin/HEAD) Cloning the remote Git repository Cloning repository http://bgate.mellanox.com:8080/git/ompi-vendor.git git --version git version 1.8.4.3 Fetching upstream changes from origin Seen branch in repository origin/HEAD Seen branch in repository origin/master Seen branch in repository origin/mellanox-master Seen branch in repository origin/mellanox-shmem-from-v1.6 Seen branch in repository origin/mellanox-test_branch Seen branch in repository origin/mellanox-v1.6 Seen branch in repository origin/mellanox-v1.7 Seen branch in repository origin/ompi-hcoll-datatype Seen branch in repository origin/test_branch Seen branch in repository origin/v1.6 Seen branch in repository origin/v1.7 Seen 11 remote branches Multiple candidate revisions Scheduling another build to catch up with hpc-ompi-shmem Commencing build of Revision 368c6bb3261e77d1c12f473ed692ca21bf28c7d3 (origin/master, origin/HEAD) Checking out Revision 368c6bb3261e77d1c12f473ed692ca21bf28c7d3 (origin/master, origin/HEAD) Warning : There are multiple branch changesets here No emails were triggered. Triggering r-vmb-rhel6-u3-x86-64 Triggering r-vmb-fedora14-x86-64 Triggering r-vmb-rhel5-u10-x86-64 Triggering r-vmb-rhel6-u2-x86-64 Triggering r-vmb-rhel6-u4-x86-64 Triggering hpc-test-node Triggering r-vmb-sles11-sp3-x86-64 Triggering r-vmb-rhel5-u9-x86-64 Triggering r-vmb-centos5-u7-x86-64 Triggering r-vmb-sles11-sp1-x86-64 Triggering r-vmb-fedora16-x86-64 Triggering r-vmb-fedora17-x86-64 Triggering r-vmb-rhel5-u8-x86-64 Triggering r-vmb-ubuntu13-u10-x86-64 Triggering r-vmb-rhel7-u0-beta-x86-64 Triggering r-vmb-rhel6-u5-x86-64 Triggering r-vmb-sles11-sp2-x86-64 Triggering r-vmb-ole6-u2-x86-64 Triggering r-vmb-centos6-u0-x86-64 Triggering r-vmb-rhel6-u1-x86-64 Triggering r-vmb-ubuntu12-u4-x86-64 Triggering r-vmb-sles11-sp0-x86-64 r-vmb-rhel6-u3-x86-64 completed with result SUCCESS r-vmb-fedora14-x86-64 completed with result SUCCESS r-vmb-rhel5-u10-x86-64 completed with result SUCCESS r-vmb-rhel6-u2-x86-64 completed with result SUCCESS r-vmb-rhel6-u4-x86-64 completed with result SUCCESS hpc-test-node completed with result FAILURE r-vmb-sles11-sp3-x86-64 completed with result SUCCESS r-vmb-rhel5-u9-x86-64 completed with result SUCCESS r-vmb-centos5-u7-x86-64 completed with result SUCCESS r-vmb-sles11-sp1-x86-64 completed with result SUCCESS r-vmb-fedora16-x86-64 completed with result SUCCESS r-vmb-fedora17-x86-64 completed with result SUCCESS r-vmb-rhel5-u8-x86-64 completed with result SUCCESS r-vmb-ubuntu13-u10-x86-64 completed with result SUCCESS r-vmb-rhel7-u0-beta-x86-64 completed with result SUCCESS r-vmb-rhel6-u5-x86-64 completed with result SUCCESS r-vmb-sles11-sp2-x86-64 completed with result SUCCESS r-vmb-ole6-u2-x86-64 completed with result SUCCESS r-vmb-centos6-u0-x86-64 completed with result SUCCESS r-vmb-rhel6-u1-x86-64 completed with result SUCCESS r-vmb-ubuntu12-u4-x86-64 completed with result SUCCESS r-vmb-sles11-sp0-x86-64 completed with result SUCCESS Email was triggered for: Failure Sending email for trigger: Failure This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send
[JIRA] [cppcheck] (JENKINS-21928) Redesign of results page
Michal Turek commented on JENKINS-21928 Redesign of results page Implemented in https://github.com/mixalturek/cppcheck-plugin/commit/9335f6c706ef9afc2887411320bc306fe4d32a32. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [throttle-concurrents] (JENKINS-21044) Throttle Concurrent Builds blocking Jenkins queue
Jesse Glick commented on JENKINS-21044 Throttle Concurrent Builds blocking Jenkins queue While that PR may work, I think it would be better to just make the cache be transient. I never had any intention of its being persisted to disk, so if that is what is happening, that was purely an accident (XStream automagically finding stuff and saving it). The cache would just need to be recreated if and when a job category is changed or the cache is requested, but that is pretty simple synchronization. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21861) option to include attachment with console.txt from failed slaves
Alex Earl commented on JENKINS-21861 option to include attachment with console.txt from failed slaves What is "Trigger for matrix projects" set to in the job configuration? There are three options there, Only Parent, Only Configurations or Both. I believe the default is only for the parent, you may want to try either Only Configurations, or Both. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [extra-columns] (JENKINS-21740) Columns with value of a variable from script
Fred G commented on JENKINS-21740 Columns with value of a variable from script Hi, I was pretty sure that it would be either a string or a number. What I meant was rather the meaning of the value, for example a certain build parameter or return value of a script. = Can you give a practical use case? Regards, Fred This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [throttle-concurrents] (JENKINS-21044) Throttle Concurrent Builds blocking Jenkins queue
Oleg Nenashev commented on JENKINS-21044 Throttle Concurrent Builds blocking Jenkins queue @Jesse I've made the cache transient. All other changes just provide the safe migration procedure if there is any cache data on the disk. The load procedure is synchronized to avoid concurrency. After that, the code just re-saves the configuration in order to purge wrong data from configs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
Alex Earl commented on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification Jesse, I just like to poke at these until you come up with the correct solution This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21168) Git core.symlinks option not correctly auto-detected on Windows
Sebastian Schuberth commented on JENKINS-21168 Git core.symlinks option not correctly auto-detected on Windows That's interesting to known, so the plugin does not solely use the configured command line client, but will always use JGit (in parts) even if you have explicitly not configured JGit. I don't think that "git fetch" is the culprit here, but rather "git checkout" (or whatever the plugin is doing to get a working tree). I'd appreciate if you could shed any light on this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21168) Git core.symlinks option not correctly auto-detected on Windows
Sebastian Schuberth edited a comment on JENKINS-21168 Git core.symlinks option not correctly auto-detected on Windows Thanks for your explanations about the JGit implementation, I got it now. I did some more tests and realized the issue is somehow related to the custom version of Git for Windows that I'm using (mingwGitDevEnv, see 1). I can confirm that everything is fine if I clone the sandbox repository at 2 (which contains several Linux links) with msysgit 1.8.4 as the plugin's client 3. But if I configure the plugin to use mingwGitDevEnv it fails cloning like at 4. However, here comes the funny part: If I just create a build step where I clone the sandbox repository using mingwGitDevEnv manually, i.e. by directly invoking the mingwGitDevEnv Git executable instead of the Jenkins Git plugin doing it, it works again (see 5). So there must be something that the plugin is doing different than I when calling git.exe for cloning. Any idea what that could be? 1 https://github.com/sschuberth/mingwGitDevEnv 2 https://github.com/sschuberth/sandbox 3 http://mingwgitdevenv.cloudapp.net/view/Playground/job/sandbox/7/console 4 http://mingwgitdevenv.cloudapp.net/view/Playground/job/sandbox/8/console 5 http://mingwgitdevenv.cloudapp.net/view/Playground/job/sandbox/9/console This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ownership] (JENKINS-21838) Allow to authenticate as a job's owner during the build
Oleg Nenashev commented on JENKINS-21838 Allow to authenticate as a jobs owner during the build https://github.com/jenkinsci/ownership-plugin/pull/20 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ownership] (JENKINS-21838) Allow to authenticate as a job's owner during the build
Oleg Nenashev started work on JENKINS-21838 Allow to authenticate as a jobs owner during the build Change By: Oleg Nenashev (23/Feb/14 7:41 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21168) Git core.symlinks option not correctly auto-detected on Windows
Sebastian Schuberth commented on JENKINS-21168 Git core.symlinks option not correctly auto-detected on Windows FYI, I was looking at CliGitAPIImpl.java to see what the plugin is doing and tried to resemble its actions as closely as possible. Here are the steps that I think the plugin is doing, and they work fine if I use them in a shell build step: mkdir sandbox2 git init sandbox2 cd sandbox2 git remote add origin https://github.com/sschuberth/sandbox.git git fetch git checkout -f 809ea43fece46bf4995e61ddd9440193db8814fd git checkout -b master 809ea43fece46bf4995e61ddd9440193db8814fd This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xcode] (JENKINS-12153) Setting bundle identifier and app display name from build settings
Nathaniel Irons
commented on JENKINS-12153
Setting bundle identifier and app display name from build settings
If you want to use different bundle IDs or app display names in different circumstances, update Info.plist directly. For example, create a user-defined "APP_BUNDLE_ID" build setting, and then set your target's CFBundleIdentifier to ${APP_BUNDLE_ID}, which you can then choose to define differently in your Debug vs Release build configs. You can create as many build configurations as you need to.
Once you've made CFBundleIdentifier or CFBundleDisplayName dependent on your build configuration, you could even override them at runtime as arguments to xcodebuild, but to do so would be foolish. It's pathological to put your build server in charge of determining essential metadata like your bundle ID or displayed bundle name, because it means the project can't build correctly anywhere else.
In my opinion, this feature request should be closed without action.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mailer] (JENKINS-19433) ownership plugin does not find owner's email - although it's defined in his/her profile
SCM/JIRA link daemon commented on JENKINS-19433 ownership plugin does not find owners email - although its defined in his/her profile Code changed in jenkins User: Oleg Nenashev Path: src/main/java/hudson/tasks/MailAddressResolver.java src/main/java/hudson/tasks/Mailer.java src/test/java/hudson/tasks/MailAddressResolverTest.java http://jenkins-ci.org/commit/mailer-plugin/0a8d52ac7d06a774b0a94cf4c2d7e8826a5c3d25 Log: JENKINS-19433 - Added handling of user-defined e-mail addresses in FastEmailResolver. This change adds a new routine for fast email resolution. If a user has defined his own e-mail on the profile page, it will be resolved in the Mailer plugin with a highest priority. Resolves https://issues.jenkins-ci.org/browse/JENKINS-19433 Signed-off-by: Oleg Nenashev o.v.nenas...@gmail.com This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mailer] (JENKINS-19433) ownership plugin does not find owner's email - although it's defined in his/her profile
Oleg Nenashev commented on JENKINS-19433 ownership plugin does not find owners email - although its defined in his/her profile https://github.com/jenkinsci/mailer-plugin/pull/12 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mailer] (JENKINS-19433) ownership plugin does not find owner's email - although it's defined in his/her profile
Oleg Nenashev started work on JENKINS-19433 ownership plugin does not find owners email - although its defined in his/her profile Change By: Oleg Nenashev (23/Feb/14 8:49 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mailer] (JENKINS-19433) ownership plugin does not find owner's email - although it's defined in his/her profile
SCM/JIRA link daemon commented on JENKINS-19433 ownership plugin does not find owners email - although its defined in his/her profile Code changed in jenkins User: Oleg Nenashev Path: src/main/java/hudson/tasks/MailAddressResolver.java src/main/java/hudson/tasks/Mailer.java http://jenkins-ci.org/commit/mailer-plugin/fe2d408c71dfe66820fc66d835b2d6082b4730ff Log: JENKINS-19433 - Fixed comments from @jglick Signed-off-by: Oleg Nenashev o.v.nenas...@gmail.com This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
Jesse Glick updated JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification Change By: Jesse Glick (23/Feb/14 10:45 PM) Labels: lts-candidate 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/groups/opt_out.
[JIRA] [batch-task] (JENKINS-13682) Setenv Plugin and Batch Task Plugin no longer compatible?
evernat resolved JENKINS-13682 as Incomplete Setenv Plugin and Batch Task Plugin no longer compatible? No response from the reporter, so resolving as incomplete. Change By: evernat (23/Feb/14 11:25 PM) Status: InProgress 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/groups/opt_out.
[JIRA] [core] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
SCM/JIRA link daemon resolved JENKINS-16332 as Fixed Leading and trailing underscores are added to commiters email address, unable to send build notification Change By: SCM/JIRA link daemon (24/Feb/14 12:10 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/groups/opt_out.
[JIRA] [core] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
SCM/JIRA link daemon commented on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/model/User.java test/src/test/java/hudson/model/UserTest.java http://jenkins-ci.org/commit/jenkins/fdda9ca65689423794a8378c1f28faca7dffddf0 Log: FIXED JENKINS-16332 Ensure that User records are saved when the fullName is not recoverable from the id. Otherwise User.get(id).getFullName() after restarting Jenkins will produce the wrong result. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21861) option to include attachment with console.txt from failed slaves
Mike Dubman updated JENKINS-21861 option to include attachment with console.txt from failed slaves Change By: Mike Dubman (24/Feb/14 5:40 AM) Attachment: matrixCap.PNG This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21861) option to include attachment with console.txt from failed slaves
Mike Dubman commented on JENKINS-21861 option to include attachment with console.txt from failed slaves tried all options - same result. matrix projects - this is a plugin to create jenkins job: we use: Build multi-configuration project wizard and it contains "matrix setup" to define run dimensions (per OS, per lib version, ...) - see attached This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [promoted-builds] (JENKINS-20492) Re-Execute promotion button is gone
Clecio Varjao commented on JENKINS-20492 Re-Execute promotion button is gone The manually approved "re-execute" button just moved into the Badge: https://github.com/jenkinsci/promoted-builds-plugin/blob/9395ed5d781ac93fcd6baf629e99a2f0048a05aa/src/main/resources/hudson/plugins/promoted_builds/conditions/ManualCondition/Badge/index.jelly#L12 The previous re-execute should was preserved for the non-manual promotion (as you pointed out). Can you provide with more details of the job? what conditions do you have? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21159) buildTimeTrend only shows last day of builds
Dominik Bartholdi commented on JENKINS-21159 buildTimeTrend only shows last day of builds I don't think we can close this... If the comment on the change changelog is correct, then the most 20 builds are shown only. In our environment we use this view quite a lot for audit purposes - means: we would need it a lot This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [extra-columns] (JENKINS-21740) Columns with value of a variable from script
dor cohen commented on JENKINS-21740 Columns with value of a variable from script hehe yeah that's pretty obvious =D At first I thought of maybe setting one of the environment variables, but probably Jenkins can't read it when the script ends. So now I'm thinking of taking a value that is actually the contents of a file, who's path will be decided in the job's parameters. For example, maybe it could be taken from "./workspace/reports/buildParameterName.txt" and later that file would be transferred to the archive directory. The path to the file should be either absolute or relative. The value of "buildParameterName" would be set in the "Edit view" page, as part of the absolute/relative path. When clicking on the button "Add column", an option of "Contents of file" should be displayed and it will determine the path of the file. I'm yet to have a complete familiarity with Jenkins, so maybe you'll see a better approach. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [extra-columns] (JENKINS-21929) Configurations of latest build parameters won't save
dor cohen created JENKINS-21929 Configurations of latest build parameters wont save Issue Type: Bug Assignee: Fred G Components: extra-columns Created: 24/Feb/14 7:05 AM Description: I've noticed a bug that the configurations won't save: After setting a single parameter name and clicking "OK" (to save configurations), the text field "Parameter name" and checkbox "Show single parameter" won't save their values when returning to the "Edit view" page. Project: Jenkins Priority: Minor Reporter: dor cohen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [extra-columns] (JENKINS-21929) Configurations of latest build parameters won't save
dor cohen updated JENKINS-21929 Configurations of latest build parameters wont save Change By: dor cohen (24/Feb/14 7:11 AM) Description: Ivenoticedabugthattheconfigurationswontsave:AftersettingasingleparameternameandclickingOK(tosaveconfigurations),thetextfieldParameternameandcheckboxShowsingleparameterwontsavetheirvalueswhenreturningtotheEditviewpage. Relevanttoissue20910:https://issues.jenkins-ci.org/browse/JENKINS-20910 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [performance-plugin] (JENKINS-16627) Fail to parse jmeter report
Simon Schlachter updated JENKINS-16627 Fail to parse jmeter report See the File EXAMPLE-OUTPUT.jtl Change By: Simon Schlachter (24/Feb/14 7:45 AM) Attachment: EXAMPLE-OUTPUT.jtl This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
