[JIRA] [s3] (JENKINS-23432) S3 publisher fails with String index out of range error
Maxim Kopeyka commented on JENKINS-23432 S3 publisher fails with String index out of range error same problem This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23965) Discard Old Builds does not work properly with Execute concurrent builds if necessary enabled. Not all builds are completely removed.
Maxim Strygin created JENKINS-23965 Discard Old Builds does not work properly with Execute concurrent builds if necessary enabled. Not all builds are completely removed. Issue Type: Bug Assignee: Unassigned Components: core Created: 24/Jul/14 7:23 AM Description: Despite the fact that Discard Old Builds is enabled and Max # of builds to keep is set to 10, there are many old builds remain in job_name/builds directory. It should be noted that at the same time those not deleted builds are not visible via web GUI of Jenkins. This problem arise for jobs that have Execute concurrent builds if necessary option enabled. How to reproduce The job (let's call it jobA), beside Discard Old Builds, should have Execute concurrent builds if necessary option enabled. Make some of the nodes busy by running another job (e.g.: jobC) on them. Launch jobA a few times via Jenkins web interface. The number of running jobA should be bigger than number set in Max # of builds to keep. When jobC completes, all instances of running jobA will be able to complete. Check jobA/builds/ directory at Jenkins, there are not discarded builds. Version of Jenkins this bug is occurring Jenkins ver. 1.572 How we are running Jenkins /usr/java/latest/bin/java -XX:MaxPermSize=1024M -Dhudson.Functions.autoRefreshSeconds=60 -Dhudson.tasks.Fingerprinter.enableFingerprintsInDependencyGraph=true -Dhudson.upstreamCulprits=true -Xmx3000M -Dhudson.scm.SubversionSCM.pollFromMaster=true -Djava.util.logging.ConsoleHandler.level=FINE -jar lib/jenkins.war --httpPort=18080 --webroot=mst/war --ajp13Port=-1 Environment we are using System Properties Name ? Value awt.toolkit sun.awt.X11.XToolkit executable-war /data/ci/lib/jenkins-1.572.war file.encoding UTF-8 file.encoding.pkg sun.io file.separator / hudson.diyChunking true hudson.Functions.autoRefreshSeconds 60 hudson.scm.SubversionSCM.pollFromMaster true hudson.tasks.Fingerprinter.enableFingerprintsInDependencyGraph true hudson.upstreamCulprits true java.awt.graphicsenv sun.awt.X11GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.print.PSPrinterJob java.class.path lib/jenkins.war java.class.version 51.0 java.endorsed.dirs /usr/java/jdk1.7.0_60/jre/lib/endorsed java.ext.dirs /usr/java/jdk1.7.0_60/jre/lib/ext:/usr/java/packages/lib/ext java.home /usr/java/jdk1.7.0_60/jre java.io.tmpdir /tmp java.library.path /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib java.runtime.name Java(TM) SE Runtime Environment java.runtime.version 1.7.0_60-b19 java.specification.name Java Platform API Specification java.specification.vendor Oracle Corporation java.specification.version 1.7 java.util.logging.ConsoleHandler.level FINE java.vendor Oracle Corporation java.vendor.url http://java.oracle.com/ java.vendor.url.bug http://bugreport.sun.com/bugreport/ java.version 1.7.0_60 java.vm.info mixed mode java.vm.name Java HotSpot(TM) 64-Bit Server VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendor Oracle Corporation java.vm.specification.version 1.7 java.vm.vendor Oracle Corporation java.vm.version 24.60-b09 jna.platform.library.path /usr/lib64:/lib64:/usr/lib:/lib line.separator mail.smtp.sendpartial true mail.smtps.sendpartial true os.arch amd64 os.name Linux os.version 2.6.18-308.el5 path.separator : sun.arch.data.model 64 sun.boot.class.path /usr/java/jdk1.7.0_60/jre/lib/resources.jar:/usr/java/jdk1.7.0_60/jre/lib/rt.jar:/usr/java/jdk1.7.0_60/jre/lib/sunrsasign.jar:/usr/java/jdk1.7.0_60/jre/lib/jsse.jar:/usr/java/jdk1.7.0_60/jre/lib/jce.jar:/usr/java/jdk1.7.0_60/jre/lib/charsets.jar:/usr/java/jdk1.7.0_60/jre/lib/jfr.jar:/usr/java/jdk1.7.0_60/jre/classes sun.boot.library.path /usr/java/jdk1.7.0_60/jre/lib/amd64 sun.cpu.endian little sun.cpu.isalist sun.font.fontmanager sun.awt.X11FontManager sun.io.unicode.encoding UnicodeLittle sun.java.command lib/jenkins.war --httpPort=18080 --webroot=mst/war --ajp13Port=-1 sun.java.launcher SUN_STANDARD sun.jnu.encoding UTF-8 sun.management.compiler HotSpot 64-Bit Tiered Compilers sun.os.patch.level unknown svnkit.http.methods
[JIRA] [dynamicparameter] (JENKINS-18972) About class loader of Dynamic Choice Parameter (Scriptler) (Version 0.2.0)
Dirk Haun commented on JENKINS-18972 About class loader of Dynamic Choice Parameter (Scriptler) (Version 0.2.0) Looks like we ran into the same problem: Jul 23, 2014 10:24:17 AM SEVERE com.seitenbau.jenkins.plugins.dynamicparameter.BaseParameterDefinition executeScript Error during executing script for parameter 'CPLIB_REVISION' hudson.remoting.ProxyException: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: Script1.groovy: 52: unable to resolve class hudson.scm.SubversionSCM @ line 52, column 18. def newscm = new hudson.scm.SubversionSCM(newSvnPaths, job.scm.workspaceUpdater, job.scm.browser, job.scm.excludedRegions, ^ 1 error Any chance the pull request from Nicolas De Loof could make it into the plugin? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-23275) ScmSyncConfiguration NullPointerException on postCredential
Maxim Kopeyka commented on JENKINS-23275 ScmSyncConfiguration NullPointerException on postCredential Same problem on Windows 8 x64 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-23872) Jenkins users disappeared!
stephenconnolly updated JENKINS-23872 Jenkins users disappeared! This is nothing to do with the credentials plugin Change By: stephenconnolly (24/Jul/14 8:48 AM) Assignee: stephenconnolly Component/s: core Component/s: credentials This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-23867) Incompatibility with Jenkins 1.572 or later
Dirk Kuypers reopened JENKINS-23867 Incompatibility with Jenkins 1.572 or later Sorry Steven, the problem is not fixed for me. I am still getting no progress in console output even when using Ctrl + F5. We are now using 1.574 and timestamper 1.5.13, I am using Chrome 36. Please note that my first description mentioned that my problem went away when downgrading to 1.5.11. Must be something else that has nothing to do with the UI enhancements after 1.572. Change By: Dirk Kuypers (24/Jul/14 9:10 AM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23868) Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported
Daniel Beck commented on JENKINS-23868 Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported What happens when you download the artifact using different tools, e.g. other browser, command line tools like wget, curl (may need authentication if Jenkins is secured, but that's possible)? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-20941) Stored git credentials not used when submodule is updated
Ido Ran
commented on JENKINS-20941
Stored git credentials not used when submodule is updated
I also see this issue, I can use ssh credentials to fetch git repository from BitBucket but when it tries to fetch the submodule repository, which is on the same account, I get permission exception.
Fetching upstream changes from g...@bitbucket.org:mycomp/at.git
C:\CI\Git\bin\git.exe --version
using GIT_SSH to set credentials Bitbucket key
C:\CI\Git\bin\git.exe fetch --tags --progress g...@bitbucket.org:mycomp/at.git +refs/heads/:refs/remotes/origin/
C:\CI\Git\bin\git.exe rev-parse "origin/ci^{commit}"
Checking out Revision a079842300ba7fc9e6f4e7182c94af2cfc3af0ba (origin/ci)
C:\CI\Git\bin\git.exe config core.sparsecheckout
C:\CI\Git\bin\git.exe checkout -f a079842300ba7fc9e6f4e7182c94af2cfc3af0ba
C:\CI\Git\bin\git.exe rev-list a079842300ba7fc9e6f4e7182c94af2cfc3af0ba
C:\CI\Git\bin\git.exe remote
C:\CI\Git\bin\git.exe submodule init
C:\CI\Git\bin\git.exe submodule sync
C:\CI\Git\bin\git.exe config --get remote.origin.url
C:\CI\Git\bin\git.exe submodule update
FATAL: Command "C:\CI\Git\bin\git.exe submodule update" returned status code 1:
stdout:
stderr: Cloning into 'include/portal_air'...
Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Clone of 'g...@bitbucket.org:mycomp/portal_air.git' into submodule path 'include/portal_air' failed
hudson.plugins.git.GitException: Command "C:\CI\Git\bin\git.exe submodule update" returned status code 1:
stdout:
stderr: Cloning into 'include/portal_air'...
Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Clone of 'g...@bitbucket.org:mycomp/portal_air.git' into submodule path 'include/portal_air' failed
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1406)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:87)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$6.execute(CliGitAPIImpl.java:741)
at hudson.plugins.git.extensions.impl.SubmoduleOption.onCheckoutCompleted(SubmoduleOption.java:77)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:908)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1414)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:671)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:580)
at hudson.model.Run.execute(Run.java:1684)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:231)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-23868) Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported
sharon xia commented on JENKINS-23868 Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported it happends on all artifacts. No warning in the log This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [label-verifier] (JENKINS-23966) Master labels is disappeared in case system configuration has been changed
Maxim Kopeyka created JENKINS-23966 Master labels is disappeared in case system configuration has been changed Issue Type: Bug Affects Versions: current Assignee: Oleg Nenashev Components: label-verifier Created: 24/Jul/14 9:18 AM Description: Steps to reproduce Assign some labels to master node Got to Manage Jenkins - Configure System - click save button Check master node settings, labels is disappeared Environment: Windows 8 x64, jenkins 1.573 Project: Jenkins Priority: Major Reporter: Maxim Kopeyka This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-23275) ScmSyncConfiguration NullPointerException on postCredential
Maxim Kopeyka edited a comment on JENKINS-23275 ScmSyncConfiguration NullPointerException on postCredential Same problem on Windows 8 x64, jenkins 1.573 I've tried also SCM Sync Configuration Plugin: 0.0.7.3 and 0.0.6.1, result is the same. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22685) Jenkins cannot restart Windows service
Paul Adams edited a comment on JENKINS-22685 Jenkins cannot restart Windows service I have a similar problem with the 1.554.3 LTS release using the Windows Service, whereby Jenkins does not restart. It just sits there with the message "Please wait while Jenkins is restarting...". I have to manually restart using the Windows Services Manager. Note that I am using Windows 2008 R2 Server O/S. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-21640) scm-sync-configuration plugin doesn't work anymore with Subversion Plugin =2.0
Frédéric Camblor updated JENKINS-21640 scm-sync-configuration plugin doesnt work anymore with Subversion Plugin =2.0 Change By: Frédéric Camblor (24/Jul/14 10:46 AM) Summary: scm-sync-configurationplugindoesntworkanymorewithSubversionPlugin = 2.0 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodenamecolumn] (JENKINS-12207) get warnings in log
Steven Christou commented on JENKINS-12207 get warnings in log Fix for this issue can be found: https://github.com/jenkinsci/nodenamecolumn-plugin/pull/1. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-17265) Builds disappearing from history
Alex Ouzounis commented on JENKINS-17265 Builds disappearing from history Problem no longer present in the latest versions ie 1.570 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xunit] (JENKINS-23413) xunit plugin does not work with XML produced by QTestlib
Gregory Boissinot edited a comment on JENKINS-23413 xunit plugin does not work with XML produced by QTestlib QTtestLib XSL file can be overridden in the user content directory. However, the file is located in the plugin. You can find it here https://github.com/jenkinsci/xunit-plugin/blob/master/src/main/resources/org/jenkinsci/plugins/xunit/types/qtestlib-to-junit-5.xsl Feel free to try to fix the xsl file. In addition, please upload your QTtest result file. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xunit] (JENKINS-23413) xunit plugin does not work with XML produced by QTestlib
Gregory Boissinot commented on JENKINS-23413 xunit plugin does not work with XML produced by QTestlib QTtest XSL file can be overridden in the user content directory. However, the file is located in the plugin. You can find it here https://github.com/jenkinsci/xunit-plugin/blob/master/src/main/resources/org/jenkinsci/plugins/xunit/types/qtestlib-to-junit-5.xsl Feel free to try to fix the xsl file. In addition, please upload your QTtest result file. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nunit] (JENKINS-14864) NUnit Plugin 0.14 - won't merge multiple xmls
SCM/JIRA link daemon commented on JENKINS-14864 NUnit Plugin 0.14 - wont merge multiple xmls Code changed in jenkins User: David Churchill Path: src/main/java/hudson/plugins/nunit/NUnitReportTransformer.java http://jenkins-ci.org/commit/nunit-plugin/792cb7da50a5b1afa30790300ce24d6a02cd98eb Log: FIXED JENKINS-14864 Merge multiple XMLs Applied patch provided by David Churchill in the Jenkins issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nunit] (JENKINS-14864) NUnit Plugin 0.14 - won't merge multiple xmls
SCM/JIRA link daemon resolved JENKINS-14864 as Fixed NUnit Plugin 0.14 - wont merge multiple xmls Change By: SCM/JIRA link daemon (24/Jul/14 12:40 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] [nunit] (JENKINS-14864) NUnit Plugin 0.14 - won't merge multiple xmls
SCM/JIRA link daemon commented on JENKINS-14864 NUnit Plugin 0.14 - wont merge multiple xmls Code changed in jenkins User: Bruno P. Kinoshita Path: src/main/java/hudson/plugins/nunit/NUnitReportTransformer.java http://jenkins-ci.org/commit/nunit-plugin/c97be8f9e824624c923722a80e67f12f37003fab Log: Merge pull request #7 from akoeplinger/master FIXED JENKINS-14864 Merge multiple XMLs Compare: https://github.com/jenkinsci/nunit-plugin/compare/f73f7bdb0df8...c97be8f9e824 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nunit] (JENKINS-18642) Job build is marked as failed if NUnit test result contains only ignored tests
SCM/JIRA link daemon commented on JENKINS-18642 Job build is marked as failed if NUnit test result contains only ignored tests Code changed in jenkins User: bartensud Path: src/main/java/hudson/plugins/nunit/NUnitPublisher.java http://jenkins-ci.org/commit/nunit-plugin/84fa15267a1914c097fbe7975a816f23bf15ab8d Log: Fix for issue JENKINS-18642 (Job build is marked as failed if NUnit test result contains only ignored tests) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nunit] (JENKINS-18642) Job build is marked as failed if NUnit test result contains only ignored tests
SCM/JIRA link daemon commented on JENKINS-18642 Job build is marked as failed if NUnit test result contains only ignored tests Code changed in jenkins User: Bruno P. Kinoshita Path: src/main/java/hudson/plugins/nunit/NUnitPublisher.java http://jenkins-ci.org/commit/nunit-plugin/b4dce994b29118b093c32edd92e0d3efe1fe5a7c Log: Merge pull request #6 from bartensud/master Fix for issue JENKINS-18642 (Job build is marked as failed if NUnit test result contains only ignored tests) Compare: https://github.com/jenkinsci/nunit-plugin/compare/c97be8f9e824...b4dce994b291 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jenkins-multijob-plugin] (JENKINS-23967) Parametrised Job that should not trigger triggered anyways
Christian Prause created JENKINS-23967 Parametrised Job that should not trigger triggered anyways Issue Type: Bug Assignee: Unassigned Components: jenkins-multijob-plugin Created: 24/Jul/14 1:00 PM Description: I added Phase job with Parameters from properties file. "Don't trigger if any files are missing" is enabled. When I run the build I see: parameterizedtrigger Properties file properties did not exist. Not triggering due to missing file multiJob DontTriggerException: hudson.plugins.parameterizedtrigger.AbstractBuildParameters$DontTriggerException But still the job is triggered. Environment: Jenkins ver. 1.571 Multijob plugin 1.13 Project: Jenkins Priority: Major Reporter: Christian Prause This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jenkins-multijob-plugin] (JENKINS-23968) Add the ability make a phase job conditional
Christian Prause created JENKINS-23968 Add the ability make a phase job conditional Issue Type: Bug Assignee: Unassigned Components: jenkins-multijob-plugin Created: 24/Jul/14 1:06 PM Description: Some of the jobs in a multjob phase are not always needed. The ability to read an configurable env var (boolean) to determine if a job should trigger would be nice. Environment: Jenkins ver. 1.571 Multijob plugin 1.13 Project: Jenkins Priority: Major Reporter: Christian Prause This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jenkins-multijob-plugin] (JENKINS-23968) Add the ability make a phase job conditional
Christian Prause updated JENKINS-23968 Add the ability make a phase job conditional Change By: Christian Prause (24/Jul/14 1:07 PM) Issue Type: Bug NewFeature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-23969) When restarting server builds nodes do not remain online
Richard Slade created JENKINS-23969 When restarting server builds nodes do not remain online Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 24/Jul/14 1:10 PM Description: When restarting the server the build nodes constantly switch between online and offline. Log file contains the following Jul 24, 2014 8:08:24 AM WARNING hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor monitor Failed to monitor auto-tst-dev-w1 for Free Disk Space java.nio.channels.ClosedChannelException at sun.nio.ch.SocketChannelImpl.ensureWriteOpen(SocketChannelImpl.java:249) at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:440) at hudson.remoting.SocketChannelStream$2.write(SocketChannelStream.java:62) at java.nio.channels.Channels.writeFullyImpl(Channels.java:78) at java.nio.channels.Channels.writeFully(Channels.java:101) at java.nio.channels.Channels.access$000(Channels.java:61) at java.nio.channels.Channels$1.write(Channels.java:174) at java.io.ObjectOutputStream$BlockDataOutputStream.drain(ObjectOutputStream.java:1857) at java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(ObjectOutputStream.java:1766) at java.io.ObjectOutputStream.writeFatalException(ObjectOutputStream.java:1560) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:349) at hudson.remoting.Command.writeTo(Command.java:83) at hudson.remoting.ClassicCommandTransport.write(ClassicCommandTransport.java:51) at hudson.remoting.Channel.send(Channel.java:545) at hudson.remoting.Request.callAsync(Request.java:208) at hudson.remoting.Channel.callAsync(Channel.java:766) at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMonitorDescriptor.java:76) at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:280) Jul 24, 2014 8:08:24 AM WARNING hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor monitor Failed to monitor auto-tst-prd-w1 for Free Disk Space hudson.remoting.ChannelClosedException: channel is already closed at hudson.remoting.Channel.send(Channel.java:541) at hudson.remoting.Request.callAsync(Request.java:208) at hudson.remoting.Channel.callAsync(Channel.java:766) at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMonitorDescriptor.java:76) at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:280) Caused by: java.nio.channels.AsynchronousCloseException at java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:205) at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:386) at hudson.remoting.SocketChannelStream$1.read(SocketChannelStream.java:33) at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:65) at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:109) at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:103) at java.io.InputStream.read(InputStream.java:101) at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:81) at hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:82) at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2291) at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2584) at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2594) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1316) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:70) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) Environment: Ubuntu Project: Jenkins
[JIRA] [unity3d-plugin] (JENKINS-23958) Pipe Broken
Tommi Kiviniemi updated JENKINS-23958 Pipe Broken Change By: Tommi Kiviniemi (24/Jul/14 1:24 PM) Environment: * MacOSX , * SlavenoderunningonsamemachineasJenkins(connectedviaSSHtolocalhost,samejenkinsuserrunningeverything) *UnityCacheserver(runningonsamemachineasJenkinsandUnityslavenode) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-23867) Incompatibility with Jenkins 1.572 or later
stevengbrown commented on JENKINS-23867 Incompatibility with Jenkins 1.572 or later Hmm, I'm not able to reproduce that here. Can you give me instructions? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-23867) Incompatibility with Jenkins 1.572 or later
Dirk Kuypers commented on JENKINS-23867 Incompatibility with Jenkins 1.572 or later Hm, maybe it has something to do with our Jenkins instance running inside TOMCAT? I am no web developer at all, I just installed Firebug and watched a console log. It says: POST logText/progressiveHtml 400 Bad Request 9ms X-Requested-With XMLHttpRequest X-Prototype-Version 1.7 Accept text/_javascript_, text/html, application/xml, text/xml, / Content-type application/x-www-form-urlencoded; charset=UTF-8 X-ConsoleAnnotator CfFWnogZhdvgnyjZWUp2Rl1RIZUjCgdBEGKRj0u3Ka67ePzonjQMfryJ7cJoItYR/kFd2JtjWzlEdCVsr0aiA6y1IHq1dn0TMVvjiOZyC1gC/WW27p+qPDC0dVmJ6kt5lZFFNKIe9xyGXB6K+BSwaiOxYl/Ry/OCOlYoB1g9O/iXt1W/Lum9c+Fl4Lf2Uw1H2M496ZvEc13R8twCTQ3/fVbnjbZgqoMjCc1AaSLhI5PIHbwei41Vfs/B3ZYY Anything more I could do to help you? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [msbuild] (JENKINS-22461) New MSBuild release has a space in the installation path; causes msbuild plugin to fail
Ross Inglis commented on JENKINS-22461 New MSBuild release has a space in the installation path; causes msbuild plugin to fail What worked for me was using the short path. E.G. C:\PROGRA~2\MSBuild\12.0\Bin\MSBuild.exe (Use the DOS command "dir /X" to verify this name on your platform, it just 'might' be different) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-23969) When restarting server builds nodes do not remain online
Mark Waite commented on JENKINS-23969 When restarting server builds nodes do not remain online Can you provide more details of the configured environment and how it is configured? In particular, the types of information described in what to report in the description of an issue report will be more likely to allow the Jenkins developers to more rapidly understand and resolve the problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb] (JENKINS-23103) Specify branches to build
Johannes Schüth commented on JENKINS-23103 Specify branches to build Hello Ray, yes it does indeed. I added the feature to ghprb and i totally forgot about this ticket. Thanks for the info about the wiki. I wasn't aware the feature was already released. Nice to see that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb] (JENKINS-23103) Specify branches to build
Johannes Schüth resolved JENKINS-23103 as Fixed Specify branches to build Feature was added to ghprb https://github.com/timols/jenkins-gitlab-merge-request-builder-plugin/pull/75 Change By: Johannes Schüth (24/Jul/14 3:39 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] [plugin] (JENKINS-23878) Add in the GUI an option to restart master (same function as /restart url)
Daniel Beck updated JENKINS-23878 Add in the GUI an option to restart master (same function as /restart url) Change By: Daniel Beck (24/Jul/14 3:43 PM) Component/s: plugin 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] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Jeff Dege commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 This just bit me. We use SubWCRev as a part of our build process, to inject the SVN revision number into the project's version number. (Generating Properties\AssemblyInfo.cs from a template.) I've just failed at moving our first project that does this into Jenkins, because our build machine has SVN 1.8.3 installed, and it can't read the SVN 1.7 workspace that Jenkins' SVN plugin creates. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Kelvin Fielding commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 I found if you put a pre build step of svn upgrade. And make the svn always refresh then it works. Not pretty but hey it works. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-23970) CLI authentication with username/password try to read my .ssh/id_rsa and prompts for key password
Bruno Meneguello created JENKINS-23970 CLI authentication with username/password try to read my .ssh/id_rsa and prompts for key password Issue Type: Improvement Assignee: Bruno Meneguello Components: cli Created: 24/Jul/14 5:08 PM Description: My .ssh/id_rsa is password protected and even when i try to connect with username/password cli tries to read it. Project: Jenkins Priority: Minor Reporter: Bruno Meneguello This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-23971) NumberFormatException when tailing node log (ssh unix slave, ec2)
Craig Ringer created JENKINS-23971 NumberFormatException when tailing node log (ssh unix slave, ec2) Issue Type: Bug Assignee: Francis Upton Components: core, ec2 Created: 24/Jul/14 5:22 PM Description: When tailing the log of a newly launched ssh unix slave, Jenkins suddenly stopped showing the log and instead reported: javax.servlet.ServletException: java.lang.NumberFormatException: For input string: "5584start=208664" at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at com.cloudbees.jenkins.support.slowrequest.SlowRequestFilter.doFilter(SlowRequestFilter.java:37) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:117) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:79) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at
[JIRA] [core] (JENKINS-23971) NumberFormatException when tailing node log (ssh unix slave, ec2)
Craig Ringer commented on JENKINS-23971 NumberFormatException when tailing node log (ssh unix slave, ec2) This doesn't seem to disrupt the ssh communication channel; slave/master communication continues and logs are captured as normal. Re-entering the node's page and opening the log again shows the rest of the log. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-21335) Forward slashes in a File Parameter's file location cause parameter download links to break
Eric Anker commented on JENKINS-21335 Forward slashes in a File Parameters file location cause parameter download links to break Those settings fixed it. Thank you so much for your attention to this issue! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-blocker] (JENKINS-23961) Not able to run the gradle plugin for the incremental build
LNP assigned JENKINS-23961 to Jenkins Admin User Not able to run the gradle plugin for the incremental build Change By: LNP (24/Jul/14 5:34 PM) Assignee: JenkinsAdminUser This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-line] (JENKINS-23960) Not able to configure Test report configuration
LNP assigned JENKINS-23960 to Jenkins Admin User Not able to configure Test report configuration Change By: LNP (24/Jul/14 5:34 PM) Assignee: JenkinsAdminUser This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testexecuter] (JENKINS-23957) Not able to generate the test result with Nunit plugin
LNP assigned JENKINS-23957 to Jenkins Admin User Not able to generate the test result with Nunit plugin Change By: LNP (24/Jul/14 5:35 PM) Assignee: JenkinsAdminUser This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2] (JENKINS-23972) EC2: support new General Purpose EBS storage
Craig Ringer created JENKINS-23972 EC2: support new General Purpose EBS storage Issue Type: New Feature Assignee: Francis Upton Components: ec2 Created: 24/Jul/14 5:50 PM Description: It'd be handy to support the new "General Purpose" (gp2) EBS storage type for nodes launched via the ec2-plugin. It's a lot faster and only slightly more expensive. I hope to get the chance to implement this soon. Project: Jenkins Labels: slave ec2 ebs Priority: Minor Reporter: Craig Ringer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-17614) Jenkins triggers builds on git SCM changes, but nothing changed
Xavier Shay edited a comment on JENKINS-17614 Jenkins triggers builds on git SCM changes, but nothing changed I am seeing a similiar issue: particular builds always building twice. Still trying to narrow down a repro. This issue occurs when a branch with the same name exists in two different subbranches, e.g. 'origin/features/new_feature' and 'origin/new_feature' This is not the case for my setup. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-17614) Jenkins triggers builds on git SCM changes, but nothing changed
Xavier Shay commented on JENKINS-17614 Jenkins triggers builds on git SCM changes, but nothing changed I am seeing a similiar issue: particular builds always building twice. Still trying to narrow down a repro. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [release] (JENKINS-23973) environment variables for release plugin are not affecting SCM step
Grigoriy Milman created JENKINS-23973 environment variables for release plugin are not affecting SCM step Issue Type: Bug Assignee: Peter Hayes Components: release Created: 24/Jul/14 6:35 PM Description: We have environment variables set up at the beginning at "Prepare an environment for the run" and used through the entire build. We need to modify some of them in case of release run. We set the new values by using Inject environment variable at "Before release build". Override build parameters is checked. We need updated values before and during SCM runs, which is a prebuild step, but it not happened. The original values are used before and during SCM runs, and new values are injected only at build step. What is really strange that release parameters are available at prebuild steps, as expected! See the fragment of the build log below. INTEGRITY_PROJECT variable is holding path to the branch of the project in SCM repository. There is a default value for the standard, not release build. For release run, it should be modified based on the release parameter DEVELOPMENT_PATH. It became properly modified but not at prebuild step, where it is used, but only at build step, which is too late! EnvInject - Loading node environment variables. EnvInject - Preparing an environment for the build. EnvInject - Keeping Jenkins system variables. EnvInject - Keeping Jenkins build variables. EnvInject - Injecting as environment variables the properties content INTEGRITY_PROJECT=/repository/CorporateMeasurementTechnologies/SWProduction/TestPlans/TestplanModule/Joule_4140_Module_Test_Frozen/project.pj EnvInject - Variables injected successfully. EnvInject - Injecting contributions. Building in workspace D:\Jenkins_ROOT\NGMP.Testplan.Joule.4140.Module.Frozen Running Prebuild steps NGMP.Testplan.Joule.4140.Module.Frozen $ cmd /c call C:\Windows\TEMP\hudson5103745806814541490.bat D:\Jenkins_ROOT\NGMP.Testplan.Joule.4140.Module.FrozenREM ---Before SCM runs D:\Jenkins_ROOT\NGMP.Testplan.Joule.4140.Module.FrozenREM @echo DEVELOPMENT_PATH=Rev_13_Bug_Fix DEVELOPMENT_PATH=Rev_13_Bug_Fix INTEGRITY_PROJECT=/repository/CorporateMeasurementTechnologies/SWProduction/TestPlans/TestplanModule/Joule_4140_Module_Test_Frozen/project.pj D:\Jenkins_ROOT\NGMP.Testplan.Joule.4140.Module.Frozenexit 0 Success build forhudson.tasks.BatchFile@17f5bbc Change Log: http://ds-jenk2-1.biotronik.com:8080/job/NGMP-Testplan.Joule-4140-Module-Test-Frozen/16/changes Build Log: http://ds-jenk2-1.biotronik.com:8080/job/NGMP-Testplan.Joule-4140-Module-Test-Frozen/16/console Preparing to execute si projectinfo for /repository/CorporateMeasurementTechnologies/SWProduction/TestPlans/TestplanModule/Joule_4140_Module_Test_Frozen/project.pj Preparing to execute si viewproject for #/repository/CorporateMeasurementTechnologies#s=SWProduction/SWProduction.pj#s=TestPlans/TestPlans.pj#TestplanModule/Joule_4140_Module_Test_Frozen Checkout directory is D:\Jenkins_ROOT\NGMP.Testplan.Joule.4140.Module.Frozen\Sandbox\SWProduction\Testplans\TestplanModule\Joule_4140_Module_Test_Frozen A clean copy is requested; deleting contents of D:\Jenkins_ROOT\NGMP.Testplan.Joule.4140.Module.Frozen\Sandbox\SWProduction\Testplans\TestplanModule\Joule_4140_Module_Test_Frozen Populating clean workspace... Successfully checked out 119 files! Saving current Integrity Project configuration... Writing build change log... Change log successfully generated: D:\Program Files (x86)\Jenkins\jobs\NGMP-Testplan.Joule-4140-Module-Test-Frozen\builds\2014-07-24_10-42-03\changelog.xml EnvInject - Injecting environment variables from a build step. EnvInject - Injecting as environment variables the properties content INTEGRITY_PROJECT=#/repository/CorporateMeasurementTechnologies#s=SWProduction/SWProduction.pj#s=TestPlans/TestPlans.pj#TestplanModule/Joule_4140_Module_Test_Frozen#d=Rev_13_Bug_Fix Project: Jenkins
[JIRA] [release] (JENKINS-23973) environment variables for release plugin are not affecting prebuild step!
Grigoriy Milman updated JENKINS-23973 environment variables for release plugin are not affecting prebuild step! Change By: Grigoriy Milman (24/Jul/14 6:36 PM) Summary: environmentvariablesforreleasepluginarenotaffecting SCM prebuild step ! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-23974) Private maven repo got wipe out every build
dan tran created JENKINS-23974 Private maven repo got wipe out every build Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: p4 Created: 24/Jul/14 6:44 PM Description: I am using latest p4jenkin from workshop dev branch ( 1.0.6-SNAPSHOT? ) Looks like latest change wipes out workspace/.reposiotry ( private maven repo) for every build Project: Jenkins Priority: Critical Reporter: dan tran This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-auth] (JENKINS-23975) CLI No such job when get-job unless anonymous has Job/Read permission
Bruno Meneguello created JENKINS-23975 CLI No such job when get-job unless anonymous has Job/Read permission Issue Type: Bug Assignee: Jesse Glick Components: matrix-auth Created: 24/Jul/14 7:17 PM Description: I'm trying to read a job configuration via jenkins-cli.jar with username/password and without granting Job/Read (only this) to Anonymous, the message "No such job 'xxx'" is shown Project: Jenkins Priority: Major Reporter: Bruno Meneguello This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-23415) 2 Jobs w/same repo. Job triggers twice when first triggered job is Git SCM is still downloading
Xavier Shay commented on JENKINS-23415 2 Jobs w/same repo. Job triggers twice when first triggered job is Git SCM is still downloading I am seeing something very similar to this, I suspect it might be the same issue. We have one large repo with multiple builds configured off it using different branches. We use /git/notifyCommit endpoint to trigger builds. Pushing one of the branches causes a double build. I haven't narrowed down a repro yet, but will add more here as I figure it out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-23314) LR Scenario does not return SLA information in results
Terri Calderone commented on JENKINS-23314 LR Scenario does not return SLA information in results We have developed a fix which adds the transaction name output for Average and Percentile SLAs. We will be requesting a code merge of the fix on git hub today. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-17346) git project building twice every time new change committed
Xavier Shay commented on JENKINS-17346 git project building twice every time new change committed Looks like same issue as https://issues.jenkins-ci.org/browse/JENKINS-23415 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-21335) Forward slashes in a File Parameter's file location cause parameter download links to break
Daniel Beck resolved JENKINS-21335 as Not A Defect Forward slashes in a File Parameters file location cause parameter download links to break Not a Jenkins issue. Added to documentation in the wiki. Change By: Daniel Beck (24/Jul/14 7:37 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-23976) CopyArtifact plugin does not like incorrect build selector.
Damien Nozay created JENKINS-23976 CopyArtifact plugin does not like incorrect build selector. Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: copyartifact Created: 24/Jul/14 7:49 PM Description: Steps to repro: add manual promotion process to a dummy job add copy artifacts from another project to promotion process project name = $PROMOTED_JOB_FULL_NAME which build = "specified by a build parameter" parameter name = $PROMOTED_NUMBER FATAL: : only whitespace content allowed before start tag and not 1 (position: START_DOCUMENT seen 1... @1:1) com.thoughtworks.xstream.io.StreamException: : only whitespace content allowed before start tag and not 1 (position: START_DOCUMENT seen 1... @1:1) at com.thoughtworks.xstream.io.xml.XppReader.pullNextEvent(XppReader.java:124) at com.thoughtworks.xstream.io.xml.AbstractPullReader.readRealEvent(AbstractPullReader.java:148) at com.thoughtworks.xstream.io.xml.AbstractPullReader.readEvent(AbstractPullReader.java:141) at com.thoughtworks.xstream.io.xml.AbstractPullReader.move(AbstractPullReader.java:118) at com.thoughtworks.xstream.io.xml.AbstractPullReader.moveDown(AbstractPullReader.java:103) at com.thoughtworks.xstream.io.xml.XppReader.init(XppReader.java:63) at com.thoughtworks.xstream.io.xml.AbstractXppDriver.createReader(AbstractXppDriver.java:54) at com.thoughtworks.xstream.XStream.fromXML(XStream.java:916) at com.thoughtworks.xstream.XStream.fromXML(XStream.java:907) at hudson.plugins.copyartifact.BuildSelectorParameter.getSelectorFromXml(BuildSelectorParameter.java:80) at hudson.plugins.copyartifact.ParameterizedBuildSelector.getBuild(ParameterizedBuildSelector.java:52) at hudson.plugins.copyartifact.CopyArtifact.perform(CopyArtifact.java:263) at hudson.plugins.promoted_builds.Promotion$RunnerImpl.build(Promotion.java:281) at hudson.plugins.promoted_builds.Promotion$RunnerImpl.doRun(Promotion.java:223) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:566) at hudson.model.Run.execute(Run.java:1665) at hudson.model.Run.run(Run.java:1612) at hudson.plugins.promoted_builds.Promotion.run(Promotion.java:173) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:246) Caused by: org.xmlpull.v1.XmlPullParserException: only whitespace content allowed before start tag and not 1 (position: START_DOCUMENT seen 1... @1:1) at org.xmlpull.mxp1.MXParser.parseProlog(MXParser.java:1519) at org.xmlpull.mxp1.MXParser.nextImpl(MXParser.java:1395) at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093) at com.thoughtworks.xstream.io.xml.XppReader.pullNextEvent(XppReader.java:109) ... 19 more This is a user error, I should have picked "specific build" in order to use $PROMOTED_NUMBER. Validation during the job configuration would have helped in this case make things more fool-proof. Environment: centos 6.4, jenkins LTS 1.532.3, copyartifact 1.30 Project: Jenkins Priority: Major Reporter: Damien Nozay This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Josh Kelley commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 @Jeff Dege - We do something similar but were able to work around this by updating our script to check for the SVN_REVISION environment variable (see the Jenkins Subversion plugin page) and, if that's present, use that instead of trying to check the revision itself. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-23314) LR Scenario does not return SLA information in results
Terri Calderone commented on JENKINS-23314 LR Scenario does not return SLA information in results created a pull request for review that can be found here: https://github.com/hpsa/hp-application-automation-tools-plugin/pull/1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds] (JENKINS-23977) Promoted-builds does not allow build secrets
Damien Nozay created JENKINS-23977 Promoted-builds does not allow build secrets Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: promoted-builds Created: 24/Jul/14 8:14 PM Description: we have a promotion process where we want to do: get artifacts from build we want to promote copy them to some secure server I am not able to do: provide build secrets to promotion process (credentials-binding plugin) inject password into promotion process (envinject plugin) trigger another job with parameters (e.g. delegate copying the artifacts to the secure server to another job). I am also not able to do: configure another job to poll for promoted builds and get the build information for the build that got promoted, all I get is LEGACYCODECAUSE Environment: promoted-builds 2.17, jenkins LTS 1.532.3, credentials 1.15, credentials-binding 1.0, envinject 1.89 Project: Jenkins Priority: Major Reporter: Damien Nozay This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Jeff Dege commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 I just installed the SVN 1.7.14 command-line tools on the build machine. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-23971) NumberFormatException when tailing node log (ssh unix slave, ec2)
Daniel Beck commented on JENKINS-23971 NumberFormatException when tailing node log (ssh unix slave, ec2) Are you behind a reverse proxy? If so, does this also happen when accessing Jenkins directly? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-23415) 2 Jobs w/same repo. Job triggers twice when first triggered job is Git SCM is still downloading
Mark Waite commented on JENKINS-23415 2 Jobs w/same repo. Job triggers twice when first triggered job is Git SCM is still downloading If you're using fast remote polling (the default), and if your "Branches to build" setting matches more than one branch in the repository, then you might consider upgrading to git-client-plugin 1.10.0 and modifying your "Branches to build" to use the "refs/heads/branchName" syntax rather than the "origin/master" syntax. The git-client-plugin 1.10.0 release adds a way to unambiguously specify a branch name, while still allowing the earlier syntax and its related ambiguity. Refer to Alexander Link's summary for more details. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [postbuild-task] (JENKINS-23952) Cannot create 2 Post Build Tasks
ikedam updated JENKINS-23952 Cannot create 2 Post Build Tasks Please write environments where you have the problem (the version of Jenkins, Flexible publish plugin, Post build task plugin). This is an issue of Post build task plugin. It is built for so old Jenkins (1.357), does not support structured form submission, and does not work with Flexible Publish plugin which is designed for modern plugins supporting structured form submission. I refile this issue for postbuild-task plugin, but I'm not sure there is still a maintainer for postbuild-task plugin. You might try any-buildstep plugin, which allows to use builders (such as execute shell, execute Windows batch) for actions of Flexible Publish. Change By: ikedam (24/Jul/14 11:29 PM) Assignee: bap Component/s: postbuild-task Component/s: flexible-publish This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [postbuild-task] (JENKINS-23952) Postbuild task plugin doesn't work with Flexible Publish plugin
ikedam updated JENKINS-23952 Postbuild task plugin doesnt work with Flexible Publish plugin Change By: ikedam (24/Jul/14 11:31 PM) Summary: Cannotcreate2PostBuildTasks PostbuildtaskplugindoesntworkwithFlexiblePublishplugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-23872) Jenkins users disappeared!
Daniel Beck commented on JENKINS-23872 Jenkins users disappeared! Would be interesting to know what the first Jenkins version to break was. If you're affected, could you please try to determine this? Given the range, 1.566 seems like a likely candidate (JENKINS-22247). This line looks suspicious: https://github.com/jenkinsci/jenkins/compare/jenkins-1.565...jenkins-1.566#diff-fb790d926ccb14a63b5c55893f64d31dR144 Still, weird that it affects Windows according to the report. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-23963) Computer's sidepanel.jelly should use ${rootURL}/${it.url} instead of relative URLs
Daniel Beck
commented on JENKINS-23963
Computers sidepanel.jelly should use ${rootURL}/${it.url} instead of relative URLs
Not sure when I have the time, so anyone feel free to take over.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-23963) Computer's sidepanel.jelly should use ${rootURL}/${it.url} instead of relative URLs
Daniel Beck
assigned JENKINS-23963 to Daniel Beck
Computers sidepanel.jelly should use ${rootURL}/${it.url} instead of relative URLs
Change By:
Daniel Beck
(24/Jul/14 11:41 PM)
Assignee:
DanielBeck
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23965) Discard Old Builds does not work properly with Execute concurrent builds if necessary enabled. Not all builds are completely removed.
Daniel Beck commented on JENKINS-23965 Discard Old Builds does not work properly with Execute concurrent builds if necessary enabled. Not all builds are completely removed. Could you show builds directory contents and an excerpt of the jenkins.log logging completion of the builds? How long are those builds running each? Why is their completion dependent on jobC in the description? What is the configuration of jobA (i.e. what build steps, post-build steps, etc.)? Also, The number of running jobA should be bigger than number set in Max # of builds to keep is there a situation other than what seems to be a nonsensical configuration that this issue occurs in? I'm trying to determine what priority this should be. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22009) Git Polling Keeps Detecting Changes When Variables in refspec
Jakob Korherr started work on JENKINS-22009 Git Polling Keeps Detecting Changes When Variables in refspec Change By: Jakob Korherr (25/Jul/14 12:07 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] [git] (JENKINS-23450) Initial checkout doesn't create directory listed in Check out to a sub-directory
Derek Douville
commented on JENKINS-23450
Initial checkout doesnt create directory listed in Check out to a sub-directory
I figured out now that to get $GIT_BRANCH recognized in the subdirectory field, you can NOT use { } (that is, ${GIT_BRANCH} will fail, but $GIT_BRANCH succeeds). Thus, now, we are able to checkout to a subdirectory in the workspace at $GIT_BRANCH/src and then in the build script, cd into $WORKSPACE/GIT_BRANCH/src and go ahead and 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] [github] (JENKINS-16297) FATAL: Could not apply tag [project name]test-17
Steve Jansen updated JENKINS-16297 FATAL: Could not apply tag [project name]test-17 Change By: Steve Jansen (25/Jul/14 12:12 AM) Attachment: screenshot.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin] (JENKINS-22047) Add option to reduce noise in logs
SCM/JIRA link daemon commented on JENKINS-22047 Add option to reduce noise in logs Code changed in jenkins User: Bruno P. Kinoshita Path: src/main/java/org/tap4j/plugin/TapParser.java src/main/java/org/tap4j/plugin/TapPublisher.java src/main/resources/org/tap4j/plugin/TapPublisher/config.jelly src/test/java/org/tap4j/plugin/issue16647/TestIssue16647.java src/test/java/org/tap4j/plugin/issue16964/TestIssue16964.java http://jenkins-ci.org/commit/tap-plugin/239c532ed290149d3b0fd3d3f72e67e761400683 Log: Merge pull request #7 from sschuberth/master FIXED JENKINS-22047 Add option to reduce noise in logs Compare: https://github.com/jenkinsci/tap-plugin/compare/65b57b2cbbea...239c532ed290 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-16297) FATAL: Could not apply tag [project name]test-17
Steve Jansen resolved JENKINS-16297 as Not A Defect FATAL: Could not apply tag [project name]test-17 See comments. Change By: Steve Jansen (25/Jul/14 12:12 AM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin] (JENKINS-22047) Add option to reduce noise in logs
SCM/JIRA link daemon commented on JENKINS-22047 Add option to reduce noise in logs Code changed in jenkins User: Bruno P. Kinoshita Path: src/main/java/org/tap4j/plugin/TapParser.java src/main/java/org/tap4j/plugin/TapPublisher.java src/main/resources/org/tap4j/plugin/TapPublisher/config.jelly src/test/java/org/tap4j/plugin/issue16647/TestIssue16647.java src/test/java/org/tap4j/plugin/issue16964/TestIssue16964.java http://jenkins-ci.org/commit/tap-plugin/82167d204f8cb02150c07c42724b75aee7cfbb15 Log: FIXED JENKINS-22047 Add option to reduce noise in logs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-16297) FATAL: Could not apply tag [project name]test-17
Steve Jansen commented on JENKINS-16297 FATAL: Could not apply tag [project name]test-17 This is not a bug in Jenkins. Git is complaining that you have not configured your username/email address. See https://help.github.com/articles/setting-your-email-in-git This can be configured globally for the Jenkins user identity, or you can configure per job by clicking "SCM Git Additional Behaviours" and adding the custom username/email address behaviour. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-16297) FATAL: Could not apply tag [project name]test-17
Steve Jansen edited a comment on JENKINS-16297 FATAL: Could not apply tag [project name]test-17 Closing - not a defect. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nunit] (JENKINS-14864) NUnit Plugin 0.14 - won't merge multiple xmls
Bruno P. Kinoshita closed JENKINS-14864 as Fixed NUnit Plugin 0.14 - wont merge multiple xmls Pull request merged, should be fixed in 0.16 Change By: Bruno P. Kinoshita (25/Jul/14 12:20 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] [nunit] (JENKINS-18642) Job build is marked as failed if NUnit test result contains only ignored tests
Bruno P. Kinoshita resolved JENKINS-18642 as Fixed Job build is marked as failed if NUnit test result contains only ignored tests Fixed in 0.16 Change By: Bruno P. Kinoshita (25/Jul/14 12:20 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] [nunit] (JENKINS-18642) Job build is marked as failed if NUnit test result contains only ignored tests
Bruno P. Kinoshita started work on JENKINS-18642 Job build is marked as failed if NUnit test result contains only ignored tests Change By: Bruno P. Kinoshita (25/Jul/14 12:20 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] [git] (JENKINS-20427) Build Parameter variable in branch name causes polling to detect false changes in GIT
Derek Douville
commented on JENKINS-20427
Build Parameter variable in branch name causes polling to detect false changes in GIT
I've been struggling with the same problem all week.
What I've determined is that the git plugin is either ignoring any variables created in Parameterized Build, or they are not getting passed. However, Parameterized Build can override variables the Git Plugin cares about.
Environment:
Use separate directories for workspace set to $GIT_BRANCH/src
Delete workspace Force Clone
Test Case 1: Override GIT_BRANCH
If you create a GIT_BRANCH parameter and run a build with garbage text, you can see the github plugin use that text (by the way, overriding GIT_BRANCH is bad, because it will override all of your automatic github push triggers too). This test shows that Parameterized Build at least runs before the git plugin uses its GIT_BRANCH variable.
Test Case 2: Create a new variable "MYBRANCH", specify $MYBRANCH as the branch to build.
If you now run a paramarized build and set this with some garbage (eg. not a real branch), the git clone should fail. But $MYBRANCH is treated as whitespace because it doesn't exist to the git plugin, thus performing default build behavior and building the last branch to get an update.
Test Case 3: Wrap MYBRANCH with curly braces ${MYBRANCH}
No difference
Test Case 4: Put garbage directly into the branch to build path
Type "asdasd" into the branch to build and see the build fail.
I also then added the EnvInject plugin and attempted to set the GIT_BRANCH variable from there, based on another variable's value, to no success.
My conclusion is that the Git plugin is not evaluating any environment variables passed into the branch specifications. This basically means parameterized builds are useless.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-20427) Build Parameter variable in branch name causes polling to detect false changes in GIT
Derek Douville
edited a comment on JENKINS-20427
Build Parameter variable in branch name causes polling to detect false changes in GIT
I've been struggling with the same problem all week.
What I've determined is that the git plugin is either ignoring any variables created in Parameterized Build, or they are not getting passed. However, Parameterized Build can override variables the Git Plugin cares about.
Environment:
Use separate directories for workspace set to $GIT_BRANCH/src
Delete workspace Force Clone
Git Plugin: 2.2.2
Git Client Plugin: 1.10
GitHub API Plugin: 1.55
GitHub Plugin: 1.90
Test Case 1: Override GIT_BRANCH
If you create a GIT_BRANCH parameter and run a build with garbage text, you can see the github plugin use that text (by the way, overriding GIT_BRANCH is bad, because it will override all of your automatic github push triggers too). This test shows that Parameterized Build at least runs before the git plugin uses its GIT_BRANCH variable.
Test Case 2: Create a new variable "MYBRANCH", specify $MYBRANCH as the branch to build.
If you now run a paramarized build and set this with some garbage (eg. not a real branch), the git clone should fail. But $MYBRANCH is treated as whitespace because it doesn't exist to the git plugin, thus performing default build behavior and building the last branch to get an update.
Test Case 3: Wrap MYBRANCH with curly braces ${MYBRANCH}
No difference
Test Case 4: Put garbage directly into the branch to build path
Type "asdasd" into the branch to build and see the build fail.
I also then added the EnvInject plugin and attempted to set the GIT_BRANCH variable from there, based on another variable's value, to no success.
My conclusion is that the Git plugin is not evaluating any environment variables passed into the branch specifications. This basically means parameterized builds are useless.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-23590) Change is detected when a branch is deleted and job is built.
Mark Waite closed JENKINS-23590 as Cannot Reproduce Change is detected when a branch is deleted and job is built. Change By: Mark Waite (25/Jul/14 1:49 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-23590) Change is detected when a branch is deleted and job is built.
Mark Waite resolved JENKINS-23590 as Cannot Reproduce Change is detected when a branch is deleted and job is built. I was unable to duplicate the problem. I tried the following steps Define a job which uses git://github.com/MarkEWaite/git-client-plugin.git Define "Branches to build" as "/temporary" Push a branch "temporary-test-for-JENKINS-23590 Configure polling once a minute Configure a build step "git status" to report the repository state Wait 1 minute and confirm that the branch is pulled and built Delete the branch Wait 1 minute, confirm that polling happened, and that the build did not start The polling log correctly lists that temporary branch still in the workspace repository, since I had not configured "Prune stale branches" as an "Additional Behaviour". Configure "Prune stale branches" Wait for polling Confirm from polling log that branch has been removed from workspace repository Change By: Mark Waite (25/Jul/14 1:49 AM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-23091) Git. Problem with encoding in the list changes
Mark Waite edited a comment on JENKINS-23091 Git. Problem with encoding in the list changes I believe this bug is fixed by a recent change from Kohsuke Kawaguchi. Should be in the next release of git-plugin, 2.3 or later. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-23091) Git. Problem with encoding in the list changes
Mark Waite resolved JENKINS-23091 as Fixed Git. Problem with encoding in the list changes I believe this bug is fixed by a recent change from Kohsuke Kawaguchi. Change By: Mark Waite (25/Jul/14 1: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] [git-client] (JENKINS-21520) NoClassDefFoundError in git client 1.6.1
Mark Waite resolved JENKINS-21520 as Cannot Reproduce NoClassDefFoundError in git client 1.6.1 I'm unable to duplicate this bug, nor do there seem to be ongoing reports of the problem. Closing it as "Cannot reproduce". Change By: Mark Waite (25/Jul/14 2:03 AM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-21520) NoClassDefFoundError in git client 1.6.1
Mark Waite closed JENKINS-21520 as Cannot Reproduce NoClassDefFoundError in git client 1.6.1 Change By: Mark Waite (25/Jul/14 2:03 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22009) Git Polling Keeps Detecting Changes When Variables in refspec
Jakob Korherr commented on JENKINS-22009 Git Polling Keeps Detecting Changes When Variables in refspec Created pull request on github: https://github.com/jenkinsci/git-plugin/pull/245 Please merge. Change contains fix and test case. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [timestamper] (JENKINS-23867) Incompatibility with Jenkins 1.572 or later
A. Kirby commented on JENKINS-23867 Incompatibility with Jenkins 1.572 or later I also am having issues. The plugin worked until 1.572 was released. I uninstalled it since it was having an impact on my console output. When I saw that the latest resolved the issues, I re-installed it but it still doesn't work. I do see the script.js being loaded so I walked the code. Since the span.timestamper isn't being added to the DOM the script.js does nothing. I used a little jQuery to add the span in myself, and it did render the radio buttons but the timestamps still didn't show up. Something in the plugin isn't inserting the span needed for the script to work, and there could be something else wrong that's not allowing the console output to show the timestamps. I am running Jenkins 1.573 now and the latest Timestamper plugin. I have used Chrome, IE and FF, flushed my cache and tried different machines. I believe the problem is in the plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
