[JIRA] [jenkins-reviewbot] (JENKINS-19642) ReviewBot plugin fails after 'apply patch'
Dan Albu commented on JENKINS-19642 ReviewBot plugin fails after 'apply patch' Well for example i whant to run multiple patch jobs but with different patches. Right now i don't have the ability from the plugin to set up more repos and links If you whant we can schedule a session when you have time and talk over skype This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [buildgraph-view] (JENKINS-19470) Build Graph not displaying
Bob Loren commented on JENKINS-19470 Build Graph not displaying Is there any possibility to debug build graph view ? We've got one job - it hasn't change since it has been created, but for some builds we've got graph but for other we haven't, just white page without any error or information in logs files. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-19743) Massive parallel builds sometimes cause errors in LogRotation
Oleg Nenashev commented on JENKINS-19743 Massive parallel builds sometimes cause errors in LogRotation > Does this issue still occur on recent Jenkins versions? I don't know. I was able to reproduce it on 1.532.x, but have not ever tested it on newer versions > How can this be reproduced? Reproduction conditions: Fast FreeStyleProject with parallel builds enabled Many executors (I've reproduced it on a test server with 16 slaves / 90 executors). Since there's no votes/watches, we could just close the issue with a "cannot reproduce" state This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-19743) Massive parallel builds sometimes cause errors in LogRotation
Oleg Nenashev resolved JENKINS-19743 as Cannot Reproduce Massive parallel builds sometimes cause errors in LogRotation Change By: Oleg Nenashev (03/Oct/14 8:23 AM) Status: Open Resolved Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24987) [Regression] Default permission when archiving a build
tristan bessoussa created JENKINS-24987 [Regression] Default permission when archiving a build Issue Type: Bug Assignee: Unassigned Attachments: 2014-10-03_1034.png Components: core Created: 03/Oct/14 8:46 AM Description: Hi, It seems that there a regression with a recent patch. Whem i'm building my application, and archiving it in order to deploy the application, the default permission seems to have changed in *a bad way*. You can see the screenshot attached that the v1.0.6 has "normal" permission but after a jenkins update, the version 1.0.8 on the screenshot have really weird permissions which prevent the webserver from reading the content of the folder. (i had to manually set the correct permissions for 1.0.9) I didn't touch the build script responsible of building the archive or the deployment method between those versions. I suspect the umask PR thing to be the cause (but this is just a guess) : https://github.com/jenkinsci/jenkins/pull/1397 Environment: Jenkins v1.582 / Debian 7 Project: Jenkins Priority: Blocker Reporter: tristan bessoussa This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-24986) Offer an alternate location to store plugins and groovy hook scripts
Nicolas De Loof created JENKINS-24986 Offer an alternate location to store plugins and groovy hook scripts Issue Type: New Feature Assignee: Nicolas De Loof Components: core Created: 03/Oct/14 8:46 AM Description: A requested feature on Docker official jenkins image is ability to created derived images with custom plugins. But as jenkins_home is a volume the Docker image can't be built with custom plugins / hook scripts. This feature request is about introducing, in addition to jenkins.war:/WEB-INF and JENKINS_HOME, a supported directory where jenkins would pick-up plugins and hook scripts. Project: Jenkins Priority: Minor Reporter: Nicolas De Loof This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-24970) Blank page when reapproving
Maxime Lemanissier reopened JENKINS-24970 Blank page when reapproving Hi Daniel, Thanks for the link to JENKINS-22550. I have upgraded GHPRB plugin to 1.16-1 and I don't get the NoSuchMethodError anymore, but I still get the blank page when I re-execute a promotion. In my case, a given promotion with manual approval can only be run once on a given build. Change By: Maxime Lemanissier (03/Oct/14 8:47 AM) Resolution: Duplicate Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-24946) JUnit Tests Results fail to archive in V1.582
Duncan Shepherd commented on JENKINS-24946 JUnit Tests Results fail to archive in V1.582 Thanks for your response Daniel. Sadly, nothing out of the ordinary, which I do realise is very unhelpful. If you could suggest where I might look, I can scan the logs in more detail looking for specific tell-tale signs, but when I diff the logs from a build success with these build failures, aside from dates and paths etc, they are the same until the archive unit tests portion. What I can tell you is that the build artifacts are all correct and the unit tests run happily, it is only when they are to be archived the job fails. I checked the folder which the unit tests write the XML files to, it is correct. I checked all of the XMLs themselves, they are well formed. I checked the path given for the archiving of the test results, it matches where they are I downgraded Jenkins back to a previous version before JUnit was split out to a plugin, and the job script executes without issue. Happy to provide any further details in order to help track this issue down. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-22358) Jenkins 1.556 gives 'Error 404 Not Found'
Pawel Grzegrzolka reopened JENKINS-22358 Jenkins 1.556 gives 'Error 404 Not Found' I have the same issue with Jenkins 1.583. Tried with IE 10 and Firefox (32). Both have the same issue. Network setup doesn't matter since the same issue occurs on the localhost. I'm using RoleBasedAuthorizationStrategy. Change By: Pawel Grzegrzolka (03/Oct/14 9:06 AM) Resolution: Incomplete 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] [active-directory] (JENKINS-22358) Jenkins 1.556 gives 'Error 404 Not Found'
Pawel Grzegrzolka commented on JENKINS-22358 Jenkins 1.556 gives 'Error 404 Not Found' I've just noticed that secured connection (SSL) doesn't have this issue. Jetty complains only when trying to connect via http. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-18403) Jenkins 1.518 causes Java 5 Maven builds to fail
Bernat Bautista commented on JENKINS-18403 Jenkins 1.518 causes Java 5 Maven builds to fail Helo, After upgrading from 1.551, the same happens again: With 1.551: Parsing POMs [AGD-ActuarialEngine_9010_Nightly] $ /usr/lib/jvm/jdk1.5.0_22/bin/java -Xmx512M -XX:MaxPermSize=512M -cp /data/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.5.jar:/data/jenkins/tools/maven3.0.4/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /data/jenkins/tools/maven3.0.4 /var/lib/tomcat6/webapps/jenkins/WEB-INF/lib/remoting-2.33.jar /data/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.5.jar /data/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-commons-1.5.jar 50617 <===[JENKINS REMOTING CAPACITY]===>channel started ERROR: JENKINS-18403 JDK 5 not supported to run Maven; retrying with slave Java and setting compile/test properties to point to /usr/lib/jvm/jdk1.5.0_22 [AGD-ActuarialEngine_9010_Nightly] $ /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/bin/java -Xmx512M -XX:MaxPermSize=512M -cp /data/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.5.jar:/data/jenkins/tools/maven3.0.4/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /data/jenkins/tools/maven3.0.4 /var/lib/tomcat6/webapps/jenkins/WEB-INF/lib/remoting-2.33.jar /data/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.5.jar /data/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-commons-1.5.jar 60808 With 1.582 Parsing POMs [AGD-ActuarialEngine_9010_Nightly] $ /usr/lib/jvm/jdk1.5.0_22/bin/java -Xmx512M -XX:MaxPermSize=512M -cp /data/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.5.jar:/data/jenkins/tools/maven3.0.4/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /data/jenkins/tools/maven3.0.4 /var/lib/tomcat6/webapps/jenkins/WEB-INF/lib/remoting-2.45.jar /data/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.5.jar /data/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-commons-1.5.jar 60914 Exception in thread "main" java.lang.UnsupportedClassVersionError: Bad version number in .class file at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:621) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) at java.net.URLClassLoader.access$100(URLClassLoader.java:56) at java.net.URLClassLoader$1.run(URLClassLoader.java:195) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(ClassRealm.java:386) at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:42) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:244) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:230) at org.jvnet.hudson.maven3.agent.Maven3Main.main(Maven3Main.java:135) at org.jvnet.hudson.maven3.agent.Maven3Main.main(Maven3Main.java:64) ERROR: Failed to parse POMs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-18403) Jenkins 1.518 causes Java 5 Maven builds to fail
Bernat Bautista edited a comment on JENKINS-18403 Jenkins 1.518 causes Java 5 Maven builds to fail Helo, After upgrading from 1.551 to 1.582, the same happens again: With 1.551: Parsing POMs [AGD-ActuarialEngine_9010_Nightly] $ /usr/lib/jvm/jdk1.5.0_22/bin/java -Xmx512M -XX:MaxPermSize=512M -cp /data/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.5.jar:/data/jenkins/tools/maven3.0.4/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /data/jenkins/tools/maven3.0.4 /var/lib/tomcat6/webapps/jenkins/WEB-INF/lib/remoting-2.33.jar /data/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.5.jar /data/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-commons-1.5.jar 50617 <===[JENKINS REMOTING CAPACITY]===>channel started ERROR: JENKINS-18403 JDK 5 not supported to run Maven; retrying with slave Java and setting compile/test properties to point to /usr/lib/jvm/jdk1.5.0_22 [AGD-ActuarialEngine_9010_Nightly] $ /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/bin/java -Xmx512M -XX:MaxPermSize=512M -cp /data/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.5.jar:/data/jenkins/tools/maven3.0.4/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /data/jenkins/tools/maven3.0.4 /var/lib/tomcat6/webapps/jenkins/WEB-INF/lib/remoting-2.33.jar /data/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.5.jar /data/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-commons-1.5.jar 60808 With 1.582 Parsing POMs [AGD-ActuarialEngine_9010_Nightly] $ /usr/lib/jvm/jdk1.5.0_22/bin/java -Xmx512M -XX:MaxPermSize=512M -cp /data/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.5.jar:/data/jenkins/tools/maven3.0.4/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /data/jenkins/tools/maven3.0.4 /var/lib/tomcat6/webapps/jenkins/WEB-INF/lib/remoting-2.45.jar /data/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.5.jar /data/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-commons-1.5.jar 60914 Exception in thread "main" java.lang.UnsupportedClassVersionError: Bad version number in .class file at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:621) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) at java.net.URLClassLoader.access$100(URLClassLoader.java:56) at java.net.URLClassLoader$1.run(URLClassLoader.java:195) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(ClassRealm.java:386) at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:42) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:244) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:230) at org.jvnet.hudson.maven3.agent.Maven3Main.main(Maven3Main.java:135) at org.jvnet.hudson.maven3.agent.Maven3Main.main(Maven3Main.java:64) ERROR: Failed to parse POMs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-24936) Support for Stash Browser for Git plugin
SCM/JIRA link daemon commented on JENKINS-24936 Support for Stash Browser for Git plugin Code changed in jenkins User: Daniel Spilker Path: docs/Home.md docs/Job-reference.md job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/ScmContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/scm/GitBrowserContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/scm/GitContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/ScmHelperSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/7e79e0937304e8b2093ec74f294f10a87dc2f45d Log: Merge branch 'JENKINS-24936' Conflicts: docs/Home.md Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/443b624e3d0e...7e79e0937304 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-24936) Support for Stash Browser for Git plugin
SCM/JIRA link daemon commented on JENKINS-24936 Support for Stash Browser for Git plugin Code changed in jenkins User: Christian Galsterer Path: docs/Home.md docs/Job-reference.md job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/scm/GitContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/ScmHelperSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/4744347a4be6ea6971b1fa0528fc5065588c9bda Log: JENKINS-24936 Support for Stash Browser for Git 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] [promoted-builds] (JENKINS-24970) Blank page when reapproving
Maxime Lemanissier commented on JENKINS-24970 Blank page when reapproving One precision that might be important : this user does not have the 'promote' permission (though he's able to run the promotion using the button 'approve' - button 'force promotion' is not displayed) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-22358) Jenkins 1.556 gives 'Error 404 Not Found'
Daniel Beck commented on JENKINS-22358 Jenkins 1.556 gives 'Error 404 Not Found' What container is Jenkins running in? Could you provide the contents of the /systemInfo page of Jenkins? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-22358) Jenkins 1.556 gives 'Error 404 Not Found'
Daniel Beck edited a comment on JENKINS-22358 Jenkins 1.556 gives 'Error 404 Not Found' What container is Jenkins running in? Could you provide the contents of the /systemInfo page of Jenkins? What is the URL the 'login' link points to, does it contain this suffix? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-24946) JUnit Tests Results fail to archive in V1.582
Daniel Beck commented on JENKINS-24946 JUnit Tests Results fail to archive in V1.582 Which version of Jenkins did you downgrade to? Could you try pinpointing the version where it breaks? Is it really the one where the plugin was extracted? What does the rest of the job configuration look like? Could you try setting up a minimal job that fails (and can be uploaded to allow others to reproduce the problem, i.e. only public or demo/dummy files), e.g. one where the XML file is set up in a batch step instead of compiling? Does it also happen on other Windows slaves? Does it happen when run on master? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-19530) Unable to parameterize the file path when using hp-application-automation-tools-plugin
Jaydeep Patel
commented on JENKINS-19530
Unable to parameterize the file path when using hp-application-automation-tools-plugin
Hi Amit, I am after similar functionality as well.
i actually have fixed it in the code more according to my requirments
public override TestSuiteRunResults Run()
{
if (!Connected)
return null;
TestSuiteRunResults activeRunDesc = new TestSuiteRunResults();
//find all the testSets under if given some folders in our list
try
{
FindAllTestSetsUnderFolders();
}
catch (Exception ex)
{
ConsoleWriter.WriteErrLine(string.Format(Resources.AlmRunnerErrorBadQcInstallation, ex.Message, ex.StackTrace));
return null;
}
//run all the TestSets
foreach (string testset in TestSets)
{
string testset1 = testset.TrimEnd("".ToCharArray());
int pos = testset1.LastIndexOf('');
string tsDir = "";
string tsName = testset1;
if (pos != -1)
{
tsDir = testset1.Substring(0, pos).Trim("".ToCharArray());
tsName = testset1.Substring(pos, testset1.Length - pos).Trim("".ToCharArray());
if (tsName.Contains('%'))
{
var sTemp = tsName.Replace("%", "");
string value = System.Environment.GetEnvironmentVariable(sTemp.ToString(),EnvironmentVariableTarget.Machine);
tsName = value;
}
}
this bit divides them into two directory path being parameterized and the testset name being parameterized.
i couldnt build the plugin because my work proxy does not allow maven to be executed. hope this helps
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-19530) Unable to parameterize the file path when using hp-application-automation-tools-plugin
Jaydeep Patel
edited a comment on JENKINS-19530
Unable to parameterize the file path when using hp-application-automation-tools-plugin
Hi Amit, I am after similar functionality as well.
i actually have fixed it in the code more according to my requirments
///
public override TestSuiteRunResults Run()
{
if (!Connected)
return null;
TestSuiteRunResults activeRunDesc = new TestSuiteRunResults();
//find all the testSets under if given some folders in our list
try
{
FindAllTestSetsUnderFolders();
}
catch (Exception ex)
{
ConsoleWriter.WriteErrLine(string.Format(Resources.AlmRunnerErrorBadQcInstallation, ex.Message, ex.StackTrace));
return null;
}
//run all the TestSets
foreach (string testset in TestSets)
{
string testset1 = testset.TrimEnd("".ToCharArray());
int pos = testset1.LastIndexOf('');
string tsDir = "";
string tsName = testset1;
if (pos != -1)
{
tsDir = testset1.Substring(0, pos).Trim("".ToCharArray());
tsName = testset1.Substring(pos, testset1.Length - pos).Trim("".ToCharArray());
if (tsDir.Contains('%'))
{
var sTemp = tsName.Replace("%", "");
string sTempvalue = System.Environment.GetEnvironmentVariable(sTemp.ToString(), EnvironmentVariableTarget.Machine);
tsDir = sTempvalue;
}
if (tsName.Contains('%'))
{
var sTemp = tsName.Replace("%", "");
string sTempvalue = System.Environment.GetEnvironmentVariable(sTemp.ToString(), EnvironmentVariableTarget.Machine);
tsName = sTempvalue;
}
}
TestSuiteRunResults desc = RunTestSet(tsDir, tsName, Timeout, RunMode, RunHost);
if (desc != null)
activeRunDesc.AppendResults(desc);
}
return activeRunDesc;
}
this bit divides them into two directory path being parameterized and the testset name being parameterized.
i couldnt build the plugin because my work proxy does not allow maven to be executed. hope this helps , please let me know when the next Release is 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] [active-directory] (JENKINS-22358) Jenkins 1.556 gives 'Error 404 Not Found'
Pawel Grzegrzolka updated JENKINS-22358 Jenkins 1.556 gives 'Error 404 Not Found' Change By: Pawel Grzegrzolka (03/Oct/14 11:14 AM) Attachment: system_info.docx This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-22358) Jenkins 1.556 gives 'Error 404 Not Found'
Pawel Grzegrzolka updated JENKINS-22358 Jenkins 1.556 gives 'Error 404 Not Found' Change By: Pawel Grzegrzolka (03/Oct/14 11:14 AM) Attachment: system_info.docx This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-22358) Jenkins 1.556 gives 'Error 404 Not Found'
Pawel Grzegrzolka commented on JENKINS-22358 Jenkins 1.556 gives 'Error 404 Not Found' What do you mean by a container? Please find attached systeminfo. URL points to the http://hostname:8080/;jsessionid=jxe4566niq5m10476zliw7ge This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-22358) Jenkins 1.556 gives 'Error 404 Not Found'
Pawel Grzegrzolka edited a comment on JENKINS-22358 Jenkins 1.556 gives 'Error 404 Not Found' I'm using pure Jenkins service - which uses Jetty by default. Please find attached systeminfo. URL points to the http://hostname:8080/;jsessionid=jxe4566niq5m10476zliw7ge This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-22358) Jenkins 1.556 gives 'Error 404 Not Found'
Pawel Grzegrzolka edited a comment on JENKINS-22358 Jenkins 1.556 gives 'Error 404 Not Found' I'm using pure Jenkins service - which uses Jetty by default. Please find attached systeminfo. Login page is http://hostname:8080/login?from=%F, since 'log in' button points to the http://hostname:8080/;jsessionid=jxe4566niq5m10476zliw7ge (with a random crap at the end). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cron_column] (JENKINS-24988) [cron column] Allow to hide all or specific comments in cron-schedules to make column not take up all the space
centic updated JENKINS-24988 [cron column] Allow to hide all or specific comments in cron-schedules to make column not take up all the space Change By: centic (03/Oct/14 11:39 AM) Description: Currently the text from the cron-schedule is displayed with all comments included. While this is nice sometimes to explain why a schedule is done, it is not very useful for the cron column as it make the column take a lot of screen real-estate, e.g. !Clipboard_2014-10-03_13-38-17.png |border=1 !An option to not show comments at all or a way to write comments so that they are ignored (e.g. by having double ## as prefix in the line) would be nice. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cron_column] (JENKINS-24988) [cron column] Allow to hide all or specific comments in cron-schedules to make column not take up all the space
centic created JENKINS-24988 [cron column] Allow to hide all or specific comments in cron-schedules to make column not take up all the space Issue Type: Improvement Assignee: Unassigned Attachments: Clipboard_2014-10-03_13-38-17.png Components: cron_column Created: 03/Oct/14 11:38 AM Description: Currently the text from the cron-schedule is displayed with all comments included. While this is nice sometimes to explain why a schedule is done, it is not very useful for the cron column as it make the column take a lot of screen real-estate, e.g. An option to not show comments at all or a way to write comments so that they are ignored (e.g. by having double ## as prefix in the line) would be nice. Project: Jenkins Priority: Minor Reporter: centic This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pmd] (JENKINS-24873) Wrong number of new warnings
Sergey Ryazantsev reopened JENKINS-24873 Wrong number of new warnings I've installed analysis-core v. 1.61, but nothing is changed. Change By: Sergey Ryazantsev (03/Oct/14 11:51 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] [pmd] (JENKINS-24873) Wrong number of new warnings
Sergey Ryazantsev edited a comment on JENKINS-24873 Wrong number of new warnings I've installed analysis-core v. 1.61, but nothing was changed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pmd] (JENKINS-24873) Wrong number of new warnings
Ulli Hafner commented on JENKINS-24873 Wrong number of new warnings Did you restart the build? Previous results are persisted and cannot not be changed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-24936) Support for Stash Browser for Git plugin
Daniel Spilker resolved JENKINS-24936 as Fixed Support for Stash Browser for Git plugin Will be released in 1.26. Change By: Daniel Spilker (03/Oct/14 12:08 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pmd] (JENKINS-24873) Wrong number of new warnings
Sergey Ryazantsev commented on JENKINS-24873 Wrong number of new warnings Actually, I've created a new job. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [bitbucket] (JENKINS-24989) Support Mercurial repositories
benoit guerin created JENKINS-24989 Support Mercurial repositories Issue Type: New Feature Assignee: Unassigned Components: bitbucket Created: 03/Oct/14 12:23 PM Description: Very nice plugin for whom uses BitBucket. But would be nicer if it supports mercurial (hg) repositories ! Project: Jenkins Priority: Minor Reporter: benoit guerin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-24395) Fatal error with coming Jenkins ver. 1.577
valipost nicolas commented on JENKINS-24395 Fatal error with coming Jenkins ver. 1.577 I have the latest version of Jenkins and the latest version of EmailExt and I still have this problem. If I can give you any useful any info, just ask for them. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2] (JENKINS-17086) Use IAM Role when creating instance
Maarten Groot commented on JENKINS-17086 Use IAM Role when creating instance It's already released. It only starts slaves with an IAM role, it doesn't use its own IAM role to query for regions, AMIs or starting slaves. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [configurationslicing] (JENKINS-16855) Add "Allow broken build claiming" function
SCM/JIRA link daemon commented on JENKINS-16855 Add "Allow broken build claiming" function Code changed in jenkins User: ninian Path: pom.xml src/main/java/configurationslicing/claim/ClaimSlicer.java src/test/java/configurationslicing/claim/ClaimSlicerTest.java http://jenkins-ci.org/commit/configurationslicing-plugin/e1d546944f7509b7960001ea36b64d5f4003c710 Log: JENKINS-16855: Add claim build action configuration slicer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [configurationslicing] (JENKINS-16855) Add "Allow broken build claiming" function
SCM/JIRA link daemon commented on JENKINS-16855 Add "Allow broken build claiming" function Code changed in jenkins User: ninian Path: pom.xml src/main/java/configurationslicing/claim/ClaimSlicer.java src/test/java/configurationslicing/claim/ClaimSlicerTest.java http://jenkins-ci.org/commit/configurationslicing-plugin/6cec5bb74c18afb00053bf9d000af291d7326b0e Log: Merge pull request #9 from ninian/master JENKINS-16855: Add claim build action configuration slicer Compare: https://github.com/jenkinsci/configurationslicing-plugin/compare/ded86667f54a...6cec5bb74c18 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [configurationslicing] (JENKINS-16855) Add "Allow broken build claiming" function
SCM/JIRA link daemon commented on JENKINS-16855 Add "Allow broken build claiming" function Code changed in jenkins User: ninian Path: pom.xml http://jenkins-ci.org/commit/configurationslicing-plugin/a150eb81deb0d634c865f9aa199a5c11e4b5fe42 Log: JENKINS-16855: Problem reported with PR seems to be related to JENKINS-6687, reported fixed in 1.420 of jenkins, so I've moved the base version forward to a LTS build after that point. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-6687) Remove hard dependency on com.sun.mirror.apt.* packages and classes
SCM/JIRA link daemon commented on JENKINS-6687 Remove hard dependency on com.sun.mirror.apt.* packages and classes Code changed in jenkins User: ninian Path: pom.xml http://jenkins-ci.org/commit/configurationslicing-plugin/a150eb81deb0d634c865f9aa199a5c11e4b5fe42 Log: JENKINS-16855: Problem reported with PR seems to be related to JENKINS-6687, reported fixed in 1.420 of jenkins, so I've moved the base version forward to a LTS build after that point. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-24860) Allow to disable build trigger
Martin Meyer commented on JENKINS-24860 Allow to disable build trigger Thanks for the feedback. I think easyness of implementation along with usefulness should influence development (so you certainly SHOULD take easyness into consideration as well). Anyway, I tried out the flexible publish plugin and it actually does what I want. It even works with the build pipeline plugin (even though I wouldn't see the Run? condition there but that's a (visual) build pipeline plugin issue... I still feel that a 'Disabled' option would be quite a natural extension to the already present options of the plugin (genreally, if you have 'always', you might as well have 'never'). But I can live with the flexible publish 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] [configurationslicing] (JENKINS-23169) NPE at Stapler.tryInvoke
Ninian commented on JENKINS-23169 NPE at Stapler.tryInvoke Looks like this should be fixed by the PR just merged, https://github.com/jenkinsci/configurationslicing-plugin/pull/8 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [configurationslicing] (JENKINS-23169) NPE at Stapler.tryInvoke
Ninian started work on JENKINS-23169 NPE at Stapler.tryInvoke Change By: Ninian (03/Oct/14 1:11 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [configurationslicing] (JENKINS-23169) NPE at Stapler.tryInvoke
Ninian resolved JENKINS-23169 as Fixed NPE at Stapler.tryInvoke Will be fixed in the next release, 1.39 Change By: Ninian (03/Oct/14 1:13 PM) Status: In Progress Resolved Assignee: mdonohue Ninian 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] [configurationslicing] (JENKINS-16855) Add "Allow broken build claiming" function
Ninian started work on JENKINS-16855 Add "Allow broken build claiming" function Change By: Ninian (03/Oct/14 1:16 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [configurationslicing] (JENKINS-16855) Add "Allow broken build claiming" function
Ninian resolved JENKINS-16855 as Fixed Add "Allow broken build claiming" function Should be included in the next version 1.39 Change By: Ninian (03/Oct/14 1:16 PM) Status: In Progress Resolved Assignee: mdonohue Ninian 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] [ghprb] (JENKINS-24820) Environment is not fulfilled
Yuriy Syrovetskiy commented on JENKINS-24820 Environment is not fulfilled Does it really need a webhook to get pull requests? It's difficult a little to assign a reachable from Github address to my local Jenkins node. Why it is not just pulling pull requests? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-24395) Fatal error with coming Jenkins ver. 1.577
Daniel Beck commented on JENKINS-24395 Fatal error with coming Jenkins ver. 1.577 valipost nicolas: What specific problem do you have? Are there exception stack traces, and if so, please post them. What versions of email-ext and Jenkins are installed specifically? Is the JUnit plugin enabled? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-24987) [Regression] Default permission when archiving a build
Daniel Beck commented on JENKINS-24987 [Regression] Default permission when archiving a build Why are you reporting a bug (Blocker even) instead of just changing the setting you're obviously aware of? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-24986) Offer an alternate location to store plugins and groovy hook scripts
Daniel Beck commented on JENKINS-24986 Offer an alternate location to store plugins and groovy hook scripts What's wrong with changing jenkins.war? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-24987) [Regression] Default permission when archiving a build
tristan bessoussa commented on JENKINS-24987 [Regression] Default permission when archiving a build Because this bug prevent me from deploying without human interaction. And which setting are you referring to ? If I was aware of a solution I wouldn't bother you in here. Just trying to help. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-24987) [Regression] Default permission when archiving a build
tristan bessoussa edited a comment on JENKINS-24987 [Regression] Default permission when archiving a build Because this bug prevent me from deploying without human interaction. And which setting are you referring to ? If I was aware of a solution I wouldn't bother you in here. Just trying to help by providing the more detail I can. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-24395) Fatal error with coming Jenkins ver. 1.577
Alex Earl commented on JENKINS-24395 Fatal error with coming Jenkins ver. 1.577 also, did you restart Jenkins after updating 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] [core] (JENKINS-24966) Debian init script says: [OK] when failing on port check.
Daniel Beck commented on JENKINS-24966 Debian init script says: [OK] when failing on port check. Could you try changing the line in the Jenkins init script that says check_tcp_port "http" "$HTTP_PORT" "8080" || return 1 to return 2 instead? I have no Debian system to try this with, and I don't want to commit something untested. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-24966) Debian init script says: [OK] when failing on port check.
Daniel Beck assigned JENKINS-24966 to Daniel Beck Debian init script says: [OK] when failing on port check. Change By: Daniel Beck (03/Oct/14 1:45 PM) Assignee: Daniel Beck This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-19374) issue with HP Application Automation Tools plugin - error: Could not create scheduler, please verify ALM client installation on run mach
Marlene Macdonald commented on JENKINS-19374 issue with HP Application Automation Tools plugin - error: Could not create scheduler, please verify ALM client installation on run machine by downloading and in installing the add-in form: http://Almserver:Portnumber/qcbin/TDConnectivity_index.html We have tried the clean and reinstall and no change, the same error is present. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-24987) [Regression] Default permission when archiving a build
Daniel Beck commented on JENKINS-24987 [Regression] Default permission when archiving a build You found https://github.com/jenkinsci/jenkins/pull/1397 which includes the line (second commit): only set umask if set in /etc/default/jenkins referencing https://github.com/jenkinsci/jenkins/blob/master/debian/debian/jenkins.default#L45 So it seemed obvious you knew about this option. It's also noted in the change log at http://jenkins-ci.org/changelog#v1.579 Does the presence of this option resolve this issue for 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] [mercurial] (JENKINS-24953) Filenames with accents cause the changelog to appear empty
Samuel Delisle
commented on JENKINS-24953
Filenames with accents cause the changelog to appear empty
It's currently set to Cp1252. No idea how I could try with different values for this...
If it's relevant in any way, the command Jenkins uses, as seen in the console output, uses --encoding UTF-8:
[workspace] $ hg log --template "{desc|xmlescape}{file_adds|stringify|xmlescape}{file_dels|stringify|xmlescape}{files|stringify|xmlescape}{parents}\n" --rev default:0 --follow --prune 437fba1b4ca5207fa18a08d0b72c88d753c2412b --encoding UTF-8 --encodingmode replace
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-24395) Fatal error with coming Jenkins ver. 1.577
valipost nicolas commented on JENKINS-24395 Fatal error with coming Jenkins ver. 1.577 I did restart Jenkins. I have JUnit installed, Jenkins 1.583 and ExmailExt 2.38.2 This is the stack trace I have Overriding default server settings, creating our own session ERROR: Publisher hudson.plugins.emailext.ExtendedEmailPublisher aborted due to exception java.lang.NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTestResultAction; at hudson.plugins.emailext.plugins.content.FailedTestsContent.evaluate(FailedTestsContent.java:47) at org.jenkinsci.plugins.tokenmacro.DataBoundTokenMacro.evaluate(DataBoundTokenMacro.java:189) at org.jenkinsci.plugins.tokenmacro.TokenMacro.expand(TokenMacro.java:182) at org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll(TokenMacro.java:233) at hudson.plugins.emailext.plugins.ContentBuilder.transformText(ContentBuilder.java:71) at hudson.plugins.emailext.ExtendedEmailPublisher.getContent(ExtendedEmailPublisher.java:597) at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:476) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:290) at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:281) at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:233) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.cleanUp(Build.java:192) at hudson.model.Run.execute(Run.java:1791) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-24966) Debian init script says: [OK] when failing on port check.
Rovanion Luckey commented on JENKINS-24966 Debian init script says: [OK] when failing on port check. This change makes the init script report [fail]. Going on, is the port hard coded in the init script? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial] (JENKINS-24953) Filenames with accents cause the changelog to appear empty
Daniel Beck commented on JENKINS-24953 Filenames with accents cause the changelog to appear empty In the script that starts Jenkins (java -jar jenkins.war) add a parameter -Dfile.encoding=UTF-8 to the left of the -jar parameter. If installed using the Windows installer, you need to change jenkins.xml to include that. (Note that this may have unintended side effects) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-24966) Debian init script says: [OK] when failing on port check.
SCM/JIRA link daemon commented on JENKINS-24966 Debian init script says: [OK] when failing on port check. Code changed in jenkins User: Daniel Beck Path: debian/debian/jenkins.init http://jenkins-ci.org/commit/jenkins/2b6c00db3406c753291ff00ccd16d64ad5f92a78 Log: [FIXED JENKINS-24966] Return failure when port is in use Both 0 and 1 are used to indicate some kind of success (the latter when Jenkins doesn't need to be started because it was already running), so we need to return 2. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-24966) Debian init script says: [OK] when failing on port check.
Mark Waite edited a comment on JENKINS-24966 Debian init script says: [OK] when failing on port check. Rovanion Luckey I think you may have found another bug in the init script with that observation. /etc/default/jenkins includes a line (on Debian): HTTP_PORT=8080 It seems like the init script check_tcp_port call might need to use that variable. Unfortunately, I'm not sure when the /etc/default/jenkins file is sourced into the init script, so it may not yet be available when that call is made. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-24966) Debian init script says: [OK] when failing on port check.
Mark Waite commented on JENKINS-24966 Debian init script says: [OK] when failing on port check. I think you may have found another bug in the init script with that observation. /etc/default/jenkins includes a line (on Debian): HTTP_PORT=8080 It seems like the init script check_tcp_port call might need to use that variable. Unfortunately, I'm not sure when the /etc/default/jenkins file is sourced into the init script, so it may not yet be available when that call is made. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-24966) Debian init script says: [OK] when failing on port check.
SCM/JIRA link daemon resolved JENKINS-24966 as Fixed Debian init script says: [OK] when failing on port check. Change By: SCM/JIRA link daemon (03/Oct/14 2:07 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24966) Debian init script says: [OK] when failing on port check.
Daniel Beck commented on JENKINS-24966 Debian init script says: [OK] when failing on port check. Alright, committed the fix towards 1.584 or 1.585 (not sure which due to mid-week 1.583 release). The port is not hard coded, as you can by from the use of $HTTP_PORT variable. See /etc/defaults/jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-17511) Option to disable "download as zip" in workspace
dan russell commented on JENKINS-17511 Option to disable "download as zip" in workspace Didn't even know this was an option till one of our junior devs tried to kill our jenkins instance using this functionality. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-24395) Fatal error with coming Jenkins ver. 1.577
Daniel Beck commented on JENKINS-24395 Fatal error with coming Jenkins ver. 1.577 Stop Jenkins, delete the folder JENKINS_HOME/plugins/email-ext/, and start it again. I confirmed in the Maven Repo that it does not use that method. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial] (JENKINS-24953) Filenames with accents cause the changelog to appear empty
Samuel Delisle edited a comment on JENKINS-24953 Filenames with accents cause the changelog to appear empty Using -Dfile.encoding=UTF-8 does not have any effect on the contents of changelog.xml, the issue is still present. Tested this only with the Jenkins 1.565.2 install. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-24966) Debian init script says: [OK] when failing on port check.
Rovanion Luckey commented on JENKINS-24966 Debian init script says: [OK] when failing on port check. The config is sourced as the fifth active line in the init script. Though I'm wondering about the line in function do_start() which reads: check_tcp_port "http" "$HTTP_PORT" "8080" || return 2 I'm wondering why 8080 is there as well as $HTTP_PORT. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial] (JENKINS-24953) Filenames with accents cause the changelog to appear empty
Samuel Delisle commented on JENKINS-24953 Filenames with accents cause the changelog to appear empty Using -Dfile.encoding=UTF-8 does not have any effect on the contents of changelog.xml, the issue is still present. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-24987) [Regression] Default permission when archiving a build
tristan bessoussa edited a comment on JENKINS-24987 [Regression] Default permission when archiving a build I wasn't excepting a BC break on a minor update, but my bad on this. Unfortunatly, 1) I commented the umask in `/etc/default/jenkins` as advised 2) I restarted jenkins `service jenkins restart` 3) I rebuilt the release of v1.0.9 of my application. The result is the same after extract:, `drwxr-x--- 12 jenkins jenkins 4096 Oct 1 18:08 v1.0.9` I tried this again and before launching the build, I ereased all previous v1.0.9 archieved builds. The result is the same. Does umask need to be set at a particular version to restore original settings ? Or do I need to reset my whole workspace so it can git clone with correct file/folder permission ? (The date still refer to the first time I built this tag) Thanks for your help . This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-24966) Debian init script says: [OK] when failing on port check.
Daniel Beck commented on JENKINS-24966 Debian init script says: [OK] when failing on port check. 8080 is the default used when HTTP_PORT is empty, so it's passed as an alternative port to check. The function is defined in the same file. (Of course one possible issue would be behavior with HTTP_PORT=-1, but that's an unrelated different issue.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24987) [Regression] Default permission when archiving a build
tristan bessoussa commented on JENKINS-24987 [Regression] Default permission when archiving a build I wasn't excepting a BC break on a minor update, but my bad on this. Unfortunatly, 1) I commented the umask in `/etc/default/jenkins` as advised 2) I restarted jenkins `service jenkins restart` 3) I rebuilt the release of v1.0.9 of my application. The result is the same after extract:, `drwxr-x--- 12 jenkins jenkins 4096 Oct 1 18:08 v1.0.9` I tried this again and before launching the build, I ereased all previous v1.0.9 builds. The result is the same. Does umask need to be set at a particular version to restore original settings ? Or do I need to reset my whole workspace so it can git clone with correct file/folder permission ? (The date still refer to the first time I built this tag) Thanks for your help . This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-17511) Option to disable "download as zip" in workspace
Daniel Beck commented on JENKINS-17511 Option to disable "download as zip" in workspace Workaround: Restrict workspace access to users who know better. Voters/Watchers: Is this still a problem for you despite JENKINS-20345 being fixed since Jenkins 1.549 / 1.532.3? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-24966) Debian init script says: [OK] when failing on port check.
Rovanion Luckey commented on JENKINS-24966 Debian init script says: [OK] when failing on port check. Ah, well then's everything fine and dandy! Have a great friday! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-24987) [Regression] Default permission when archiving a build
Daniel Beck commented on JENKINS-24987 [Regression] Default permission when archiving a build I'm a bit surprised it didn't work. Add diagnostic output to make sure your umask setting is correct. Try creating a new job that only touches a file on the master node. What are the permissions? Try service stop/start instead of restart. Probably useless, but who knows. Try changing the jenkins init script to completely remove --umask argument. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-17511) Option to disable "download as zip" in workspace
dan russell commented on JENKINS-17511 Option to disable "download as zip" in workspace Yes we've just restricted workspaces to admins, though I can see developers needing access to the workspace to debug test failures, which is why this improvement would be nice to have. We are on 1.555, it was more an issue with UI/server becoming unresponsive when he tried to download a workspace of 42k files creating a 5.6gb zip file. Not so much a jenkins specific issue! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-17511) Option to disable "download as zip" in workspace
dan russell edited a comment on JENKINS-17511 Option to disable "download as zip" in workspace Yes we've just restricted workspaces to admins, though I can see developers needing access to the workspace to debug test failures, which is why this improvement would be nice to have. We are on 1.555, it was more an issue with UI/server becoming unresponsive when he tried to download a workspace of 42k files creating a 5.6gb zip file. Not so much a jenkins specific issue, as once we realised the cause it sorted itself out pretty quickly! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-20481) Successful builds fails at the end (Could not initialize class hudson.util.jna.GNUCLibrary)
Oleg Nenashev updated JENKINS-20481 Successful builds fails at the end (Could not initialize class hudson.util.jna.GNUCLibrary) Change By: Oleg Nenashev (03/Oct/14 2:39 PM) 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] [core] (JENKINS-17611) WinIOException: Failed to create a symlink to builds/lastStableBuild error=183:null
Petar Petrov commented on JENKINS-17611 WinIOException: Failed to create a symlink to builds/lastStableBuild error=183:null Didn't see it recently. Using 1.567 now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-17611) WinIOException: Failed to create a symlink to builds/lastStableBuild error=183:null
Petar Petrov resolved JENKINS-17611 as Cannot Reproduce WinIOException: Failed to create a symlink to builds/lastStableBuild error=183:null Change By: Petar Petrov (03/Oct/14 2:41 PM) Status: Open Resolved Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-18921) OutOfMemoryError while serializing test reports to send from salve to master
Oleg Nenashev updated JENKINS-18921 OutOfMemoryError while serializing test reports to send from salve to master Could be an issue in Maven plugin as well Change By: Oleg Nenashev (03/Oct/14 2:43 PM) Component/s: maven-plugin Component/s: javatest-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] [scriptler] (JENKINS-18862) Add an ability to specify external GIT repository for scripts
Daniel Serodio commented on JENKINS-18862 Add an ability to specify external GIT repository for scripts This would be useful for us too. Because of company policy, all source code must be stored in our company's Git server. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-23122) Cross-Site-Scripting (XSS) Vulnarability: Github Titles rendered unescaped to build description
Skuli Arnlaugsson commented on JENKINS-23122 Cross-Site-Scripting (XSS) Vulnarability: Github Titles rendered unescaped to build description Jens Brejner comment fixed this for me - configure Global Security to show "Safe Html" and it appears rendered. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-24966) Debian init script says: [OK] when failing on port check.
dogfood commented on JENKINS-24966 Debian init script says: [OK] when failing on port check. Integrated in jenkins_main_trunk #3718 [FIXED JENKINS-24966] Return failure when port is in use (Revision 2b6c00db3406c753291ff00ccd16d64ad5f92a78) Result = SUCCESS daniel-beck : 2b6c00db3406c753291ff00ccd16d64ad5f92a78 Files : debian/debian/jenkins.init This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-8217) Extension settings aren't reloaded from XML files
Daniel Beck updated JENKINS-8217 Extension settings aren't reloaded from XML files Adjusted issue title to reflect scope. Adjusted priority to be consistent with JIRA priority descriptions. Still not sure whether this is actually a bug, leaving it in. Change By: Daniel Beck (03/Oct/14 4:05 PM) Summary: Ant Settings Extension settings aren't reloaded from hudson.tasks.Ant.xml XML files Priority: Critical Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cucumber-testresult] (JENKINS-24457) VERY poor performance on big json files.
teilo commented on JENKINS-24457 VERY poor performance on big json files. Comment from reporter: "This only happens if there is a large (100+) build history" This may indicating a recursive load issue - re-opened to investigate. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-24435) Test results are not joined properly when used with standard junit test result publisher
teilo updated JENKINS-24435 Test results are not joined properly when used with standard junit test result publisher getTestResult is singular from the Run type Change By: teilo (03/Oct/14 4:07 PM) 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] [cucumber-testresult] (JENKINS-24061) Cucumber json test reporting fails when parsing result with status pending
SCM/JIRA link daemon commented on JENKINS-24061 Cucumber json test reporting fails when parsing result with status pending Code changed in jenkins User: James Nord Path: src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/BackgroundResult.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/BeforeAfterResult.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberTestResult.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberTestResultArchiver.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/FeatureResult.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/ScenarioResult.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/ScenarioToHTML.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/StepResult.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/TagResult.java src/test/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberJSONParserTest.java src/test/resources/org/jenkinsci/plugins/cucumber/jsontestsupport/ScenarioResultTest/pending.json http://jenkins-ci.org/commit/cucumber-testresult-plugin/c19e0f727b46b0d89d5db7130ec2f5c5349bbe48 Log: [FIXED JENKINS-24061] pending steps are not handled correctly. Pending steps now show up as skipped tests in 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] [cucumber-testresult] (JENKINS-24061) Cucumber json test reporting fails when parsing result with status pending
SCM/JIRA link daemon resolved JENKINS-24061 as Fixed Cucumber json test reporting fails when parsing result with status pending Change By: SCM/JIRA link daemon (03/Oct/14 4:13 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] [naginator] (JENKINS-24715) Naginator progressive retry is not working
SCM/JIRA link daemon commented on JENKINS-24715 Naginator progressive retry is not working Code changed in jenkins User: Sergei Ivanov Path: src/test/java/com/chikli/hudson/plugin/naginator/NaginatorListenerTest.java http://jenkins-ci.org/commit/naginator-plugin/887a80203e8fff06b4590fb5224972ecbcdc0c81 Log: JENKINS-24715: fixed failing unit test (which relied on incorrect implementation of progressive delay) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [naginator] (JENKINS-24715) Naginator progressive retry is not working
SCM/JIRA link daemon commented on JENKINS-24715 Naginator progressive retry is not working Code changed in jenkins User: galunto Path: .gitignore pom.xml src/main/java/com/chikli/hudson/plugin/naginator/ProgressiveDelay.java src/main/resources/com/chikli/hudson/plugin/naginator/ProgressiveDelay/help.html src/test/java/com/chikli/hudson/plugin/naginator/NaginatorListenerTest.java src/test/java/com/chikli/hudson/plugin/naginator/ProgressiveDelayTest.java http://jenkins-ci.org/commit/naginator-plugin/9e561c2c079668015f083adc2bb10c064f3a7155 Log: Merge pull request #7 from sergei-ivanov/master JENKINS-24715: fixed progressive delay calculation Compare: https://github.com/jenkinsci/naginator-plugin/compare/22c0c130eb6a...9e561c2c0796 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [naginator] (JENKINS-24715) Naginator progressive retry is not working
SCM/JIRA link daemon commented on JENKINS-24715 Naginator progressive retry is not working Code changed in jenkins User: Sergei Ivanov Path: .gitignore pom.xml src/main/java/com/chikli/hudson/plugin/naginator/ProgressiveDelay.java src/main/resources/com/chikli/hudson/plugin/naginator/ProgressiveDelay/help.html src/test/java/com/chikli/hudson/plugin/naginator/ProgressiveDelayTest.java http://jenkins-ci.org/commit/naginator-plugin/d7efb1a9ba79324ceb428c25e5833c88c1cc9a3a Log: JENKINS-24715: fixed progressive delay calculation This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-24435) Test results are not joined properly when used with standard junit test result publisher
teilo commented on JENKINS-24435 Test results are not joined properly when used with standard junit test result publisher Addressed by https://github.com/jenkinsci/cucumber-testresult-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-24435) Test results are not joined properly when used with standard junit test result publisher
teilo resolved JENKINS-24435 as Fixed Test results are not joined properly when used with standard junit test result publisher Change By: teilo (03/Oct/14 4:25 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24901) Automatic tool installation of maven does not use settings from "Maven Configuration" section
David Karlsen commented on JENKINS-24901 Automatic tool installation of maven does not use settings from "Maven Configuration" section Wihtout using maven opts, generated cmd line will be: [traxidx-srv] $ /var/jenkins_home/tools/hudson.model.JDK/jdk8oracle/bin/java -cp /var/jenkins_home/plugins/maven-plugin/WEB-INF/lib/maven31-agent-1.5.jar:/var/jenkins_home/tools/hudson.tasks.Maven_MavenInstallation/maven/boot/plexus-classworlds-2.5.1.jar:/var/jenkins_home/tools/hudson.tasks.Maven_MavenInstallation/maven/conf/logging jenkins.maven3.agent.Maven31Main /var/jenkins_home/tools/hudson.tasks.Maven_MavenInstallation/maven /var/jenkins_home/war/WEB-INF/lib/remoting-2.46.jar /var/jenkins_home/plugins/maven-plugin/WEB-INF/lib/maven31-interceptor-1.5.jar /var/jenkins_home/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-commons-1.5.jar 45302 <===[JENKINS REMOTING CAPACITY]===>channel started Executing Maven: -B -f /var/jenkins_home/workspace/traxidx-srv/pom.xml -Dmaven.repo.local=/var/jenkins_home/workspace/traxidx-srv/.repository clean install [INFO] Scanning for projects... (See the two attachments for global config of system and project). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24901) Automatic tool installation of maven does not use settings from "Maven Configuration" section
David Karlsen updated JENKINS-24901 Automatic tool installation of maven does not use settings from "Maven Configuration" section Change By: David Karlsen (03/Oct/14 4:58 PM) Attachment: Screen Shot 2014-10-03 at 18.56.01.png Attachment: Screen Shot 2014-10-03 at 18.48.47.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] [core] (JENKINS-1917) Split build queue into three: Waiting, Blocked, Scheduled
Daniel Beck resolved JENKINS-1917 as Incomplete Split build queue into three: Waiting, Blocked, Scheduled Patch seems to have been disappeared (and wouldn't merge anymore anyway, so resolving as Incomplete). Change By: Daniel Beck (03/Oct/14 5:26 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-slaves] (JENKINS-20108) SSH slaves can block for a long time in NativePRNG
Greg horvath commented on JENKINS-20108 SSH slaves can block for a long time in NativePRNG Just ran in to the same issue. Wonder if we can get this moving, as the ticket is almost a year old. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-20103) ListTagParameter value doesn't show up in build api
Daniel Beck updated JENKINS-20103 ListTagParameter value doesn't show up in build api Change By: Daniel Beck (03/Oct/14 5:52 PM) Priority: Blocker Major 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.
