[JIRA] (JENKINS-14637) Maven Deployment Linker does not support all permalinks types
domi assigned JENKINS-14637 to domi Maven Deployment Linker does not support all permalinks types Change By: domi (11/Mar/13 6:56 AM) Assignee: Dominik Bartholdi domi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14823) Use environment variables in Target definition
domi assigned JENKINS-14823 to domi Use environment variables in Target definition Change By: domi (11/Mar/13 6:54 AM) Assignee: Dominik Bartholdi domi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14817) Allow to dynamically map filenames on job start from Enviroment variables
domi assigned JENKINS-14817 to domi Allow to dynamically map filenames on job start from Enviroment variables Change By: domi (11/Mar/13 6:53 AM) Assignee: Dominik Bartholdi domi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14978) Maven Deployment Linker does not support 'dynamic' Project name (upstream uploader)
domi assigned JENKINS-14978 to domi Maven Deployment Linker does not support 'dynamic' Project name (upstream uploader) Change By: domi (11/Mar/13 6:54 AM) Assignee: Dominik Bartholdi domi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13902) Default slave should always start out as 'master'
domi assigned JENKINS-13902 to domi Default slave should always start out as 'master' Change By: domi (11/Mar/13 6:54 AM) Assignee: Dominik Bartholdi domi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16495) Saving global settings causes cross site request forgery option to be disabled
domi assigned JENKINS-16495 to domi Saving global settings causes cross site request forgery option to be disabled Change By: domi (11/Mar/13 6:52 AM) Assignee: Dominik Bartholdi domi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16413) Compatibility config-file-provider and release plugins
domi commented on JENKINS-16413 Compatibility config-file-provider and release plugins Since version 2.3 of the config-file-provider-plugin and jenkins 1.491, the settings.xml is handled correctly with the m2release plugin. but maybe you are talking about the other release plugin... I have never used it and I'm not sure what you mean by "are not available"? Each file provided by the config-file-provider can be used in every build (not only with maven) in different ways, e.g.: in the build environment as "Provide Configuration files" copy it to the workspace with a build step You can give the copied script a final name and/or expose its name as a variable to reuse/reference it where ever you like. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16413) Compatibility config-file-provider and release plugins
domi edited a comment on JENKINS-16413 Compatibility config-file-provider and release plugins Since version 2.3 of the config-file-provider-plugin and jenkins 1.491, the settings.xml is handled correctly with the m2release plugin. but maybe you are talking about the other release plugin... I have never used it and I'm not sure what you mean by "are not available"? Each file provided by the config-file-provider can be used in every build (not only with maven) in different ways, e.g.: in the build environment as "Provide Configuration files" copy it to the workspace with a build step You can also give the copied script a final name and/or expose its name as a variable to reuse/reference it where ever you like. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15962) Provide BuildStep that publishes selected config file.
domi resolved JENKINS-15962 as Fixed Provide BuildStep that publishes selected config file. implemented since version 2.4 Change By: domi (11/Mar/13 6:15 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14817) Allow to dynamically map filenames on job start from Enviroment variables
domi commented on JENKINS-14817 Allow to dynamically map filenames on job start from Enviroment variables by using environment variables in the target definition, is this now working 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/groups/opt_out.
[JIRA] (JENKINS-14663) Allow running of scripts on the local filesystem.
domi commented on JENKINS-14663 Allow running of scripts on the local filesystem. this might be ok in a single master mode, but when the script has to be executed on a node, this will fail... OK, we could still read the file from the filesystem on the master and copy it over to the node - but is there really much of an advantage? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17145) URLTrigger gives severe error message, envinject NPE
dmeibusch commented on JENKINS-17145 URLTrigger gives severe error message, envinject NPE This looks similar to JENKINS-16774, with a different stack trace (more recent version of plugin, 0.28). We have many jobs configured very similarly to this (same polling URL). Some fail to poll, others do not, others do occasionally - can't see any differences in job or execution to explain this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16694) Config-file-provider does not submit modified file (submit button simply does nothing at all)
domi commented on JENKINS-16694 Config-file-provider does not submit modified file (submit button simply does nothing at all) unfortunately I currently don't have a windoz/IE at hand, but could you please try to reproduce the issue with 1.503 or higher? There was an issues fixed which only happened in IE: https://issues.jenkins-ci.org/browse/JENKINS-16561 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17145) URLTrigger gives severe error message, envinject NPE
dmeibusch
created JENKINS-17145
URLTrigger gives severe error message, envinject NPE
Issue Type:
Bug
Assignee:
Gregory Boissinot
Components:
urltrigger
Created:
11/Mar/13 5:54 AM
Description:
Polling on master node fails with message:
Inspecting Monitor a change of the content content for URL ${JENKINS_URL}job/Commit/lastStableBuild/buildNumber
Polling started on Mar 11, 2013 1:00:10 AM
Polling for the job Functional_SV900
Looking nodes where the poll can be run.
Looking for a node to the restricted label master.
Can't find any eligible nodes.
Trying to poll on master node.
Polling on master.
[ERROR] - SEVERE - Polling error null
Stack trace (from Jenkins/Tomcat log file)
java.lang.NullPointerException
at org.jenkinsci.lib.envinject.service.EnvVarsResolver.gatherEnvVarsNode(EnvVarsResolver.java:160)
at org.jenkinsci.lib.envinject.service.EnvVarsResolver.getDefaultEnvVarsJob(EnvVarsResolver.java:89)
at org.jenkinsci.lib.envinject.service.EnvVarsResolver.getEnVars(EnvVarsResolver.java:68)
at org.jenkinsci.lib.envinject.service.EnvVarsResolver.getPollingEnvVars(EnvVarsResolver.java:36)
at org.jenkinsci.plugins.urltrigger.URLTrigger.getURLValue(URLTrigger.java:108)
at org.jenkinsci.plugins.urltrigger.URLTrigger.checkIfModifiedEntry(URLTrigger.java:136)
at org.jenkinsci.plugins.urltrigger.URLTrigger.checkIfModified(URLTrigger.java:125)
at org.jenkinsci.lib.xtrigger.AbstractTrigger$Runner.run(AbstractTrigger.java:197)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Environment:
Red Hat Enterprise Linux Server release 5.3 (Tikanga)
Java HotSpot(TM) 64-Bit Server VM (build 14.2-b01, mixed mode)
Jenkins 1.502
Project:
Jenkins
Priority:
Major
Reporter:
dmeibusch
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16774) URLTrigger gives severe error message instead of detecting change
dmeibusch commented on JENKINS-16774 URLTrigger gives severe error message instead of detecting change And now the issue has re-appeared on other builds - I'll raise a new issue with details. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-6691) EC2 plugin will launch more instances than cap allows if enough jobs are queued up while no instances are active
Emil Sit
commented on JENKINS-6691
EC2 plugin will launch more instances than cap allows if enough jobs are queued up while no instances are active
A related issue is that the nodes launched do not take into account the number of executors that will be provided by the new slave. Something like the below might address that.
diff --git a/src/main/java/hudson/plugins/ec2/EC2Cloud.java b/src/main/java/hudson/plugins/ec2/EC2Cloud.java
index 895..06e22b9 100644
--- a/src/main/java/hudson/plugins/ec2/EC2Cloud.java
+++ b/src/main/java/hudson/plugins/ec2/EC2Cloud.java
@@ -319,7 +319,7 @@ public abstract class EC2Cloud extends Cloud {
final SlaveTemplate t = getTemplate(label);
int amiCap = t.getInstanceCap();
-for( ; excessWorkload>0; excessWorkload-- ) {
+while (excessWorkload>0) {
if (!addProvisionedSlave(t.ami, amiCap)) {
break;
@@ -350,6 +350,9 @@ public abstract class EC2Cloud extends Cloud {
}
})
,t.getNumExecutors()));
+
+excessWorkload -= t.getNumExecutors();
+
}
return r;
} catch (AmazonClientException e) {
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17144) Add support for private keys for authentiation
Matthew Barr created JENKINS-17144 Add support for private keys for authentiation Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: swarm Created: 11/Mar/13 3:45 AM Description: CLI supports login via key pairs, it would be nice to be able to use the same solution for swarm plugin. Project: Jenkins Priority: Major Reporter: Matthew Barr This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15902) Add support for custom xcodebuild arguments
SCM/JIRA link daemon commented on JENKINS-15902 Add support for custom xcodebuild arguments Code changed in jenkins User: Stuart Whelan Path: src/main/java/jenkins/plugins/clangscanbuild/ClangScanBuildBuilder.java src/main/java/jenkins/plugins/clangscanbuild/commands/ScanBuildCommand.java src/main/resources/jenkins/plugins/clangscanbuild/ClangScanBuildBuilder/config.jelly src/main/resources/jenkins/plugins/clangscanbuild/ClangScanBuildBuilder/help-xcodebuildargs.html src/test/java/jenkins/plugins/clangscanbuild/ClangScanBuildBuilderTest.java src/test/java/jenkins/plugins/clangscanbuild/commands/ScanBuildCommandTest.java http://jenkins-ci.org/commit/clang-scanbuild-plugin/216a1fff17611f9dd4c56deba64c03f5b8c09b96 Log: JENKINS-15902 Add option to allow build arguments to be passed to xcode Compare: https://github.com/jenkinsci/clang-scanbuild-plugin/compare/b1f56a03ae30...216a1fff1761 – You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_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/groups/opt_out.
[JIRA] (JENKINS-15902) Add support for custom xcodebuild arguments
Stuart Whelan assigned JENKINS-15902 to Stuart Whelan Add support for custom xcodebuild arguments Change By: Stuart Whelan (10/Mar/13 9:28 PM) Assignee: Josh Kennedy Stuart Whelan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15902) Add support for custom xcodebuild arguments
Stuart Whelan started work on JENKINS-15902 Add support for custom xcodebuild arguments Change By: Stuart Whelan (10/Mar/13 9:28 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/groups/opt_out.
[JIRA] (TEST-36) Test Issue
Michael Clarke reopened TEST-36 Test Issue Change By: Michael Clarke (10/Mar/13 8:43 PM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (TEST-36) Test Issue
Michael Clarke resolved TEST-36 as Fixed Test Issue Change By: Michael Clarke (10/Mar/13 8:39 PM) Status: Open Resolved Fix Version/s: scm-sync-configuration 0.0.7 Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (TEST-36) Test Issue
Michael Clarke created TEST-36 Test Issue Issue Type: Bug Affects Versions: scm-sync-configuration 0.0.1 Assignee: Michael Clarke Components: test1 Created: 10/Mar/13 8:31 PM Description: Test issue Project: test Priority: Major Reporter: Michael Clarke This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17143) Plugin not saving vault executable path between server restarts
Stuart Whelan started work on JENKINS-17143 Plugin not saving vault executable path between server restarts Change By: Stuart Whelan (10/Mar/13 7:56 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/groups/opt_out.
[JIRA] (JENKINS-17143) Plugin not saving vault executable path between server restarts
Stuart Whelan created JENKINS-17143 Plugin not saving vault executable path between server restarts Issue Type: Bug Affects Versions: current Assignee: Stuart Whelan Components: vault-scm Created: 10/Mar/13 7:29 PM Description: Reported Issue: Jenkins server(v1.504) is installed on a 32-bit Windows 8 machine using the Vault plugin (v1.1.1). In the global configuration settings I have configured a vault installation which points to my vault client executable at “C:\Program Files\SourceGear\Vault Client\vault.exe”. Everything works great, until I restart the Jenkins server. On restart the “Path to Vault executable” is reset to “C:\Program Files (x86)\SourceGear\Vault Client\vault.exe”. It appears that the setting is not being saved. I peeked into the org.jvnet.hudson.plugins.VaultSCM.xml file and I see an element for the setting but its empty. Looking into the code I’m assuming the problem is with line 54 of VaultSCMInstallation.java where the vaultLocation variable is declared transient, which is going to make it so it doesn’t get serialized. I’m not a regular Java programmer, so that assumption may be wrong. Environment: Windows 8 32Bit, Jenkins 1.504 Project: Jenkins Labels: vault-scm Priority: Minor Reporter: Stuart Whelan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17009) Parameters with newlines should be stored as TextParameterValue
centic commented on JENKINS-17009 Parameters with newlines should be stored as TextParameterValue Done: https://github.com/jenkinsci/parameterized-trigger-plugin/pull/36 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17053) Warn user about variable names with . (dot)
Joris van der Pol commented on JENKINS-17053 Warn user about variable names with . (dot) Since variables with dots in it are common, I would say that the plugin should handle those. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17031) When adding a JSON "Custom file" double quotes are added breaking syntax
domi commented on JENKINS-17031 When adding a JSON "Custom file" double quotes are added breaking syntax I added a special file type for json, will be available with the next version. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17031) When adding a JSON "Custom file" double quotes are added breaking syntax
SCM/JIRA link daemon resolved JENKINS-17031 as Fixed When adding a JSON "Custom file" double quotes are added breaking syntax Change By: SCM/JIRA link daemon (10/Mar/13 5:40 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17031) When adding a JSON "Custom file" double quotes are added breaking syntax
SCM/JIRA link daemon commented on JENKINS-17031 When adding a JSON "Custom file" double quotes are added breaking syntax Code changed in jenkins User: imod Path: src/main/java/org/jenkinsci/plugins/configfiles/json/JsonConfig.java src/main/resources/org/jenkinsci/plugins/configfiles/Messages.properties src/main/resources/org/jenkinsci/plugins/configfiles/json/JsonConfig/JsonConfigProvider/newInstanceDetail.jelly src/main/resources/org/jenkinsci/plugins/configfiles/json/JsonConfig/JsonConfigProvider/newInstanceDetail.properties src/main/resources/org/jenkinsci/plugins/configfiles/json/JsonConfig/edit-config.jelly http://jenkins-ci.org/commit/config-file-provider-plugin/046add319839b7006e0fa0f6e694ebcdbca2766a Log: [FIXED JENKINS-17031] add new provider for Json files – You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_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/groups/opt_out.
[JIRA] (JENKINS-17142) java cli does not work behind proxy
Maciej Sawicki created JENKINS-17142 java cli does not work behind proxy Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: crumbs.trace Components: cli Created: 10/Mar/13 4:18 PM Description: Hi, I try to use jenkins cli but I got 403 errors: null:Downloads viroos$ java -jar ~/Downloads/jenkins-cli.jar -s https://dev.polidea.pl/jenkins help Exception in thread "main" java.io.IOException: Server returned HTTP response code: 403 for URL: https://dev.polidea.pl/jenkins/cli at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1625) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254) at hudson.cli.FullDuplexHttpStream.(FullDuplexHttpStream.java:77) at hudson.cli.CLI.connectViaHttp(CLI.java:156) at hudson.cli.CLI.(CLI.java:140) at hudson.cli.CLIConnectionFactory.connect(CLIConnectionFactory.java:68) at hudson.cli.CLI._main(CLI.java:439) at hudson.cli.CLI.main(CLI.java:374) I added my public key to may jerkins account so this is not the reason. I check jenkins logs and I find out: Mar 10, 2013 5:11:28 PM hudson.security.csrf.CrumbFilter doFilter WARNING: No valid crumb was included in request for /jenkins/cli. Returning 403. But I have ignore_invalid_headers off; directive added in my proxy server. I use to have crumb errors in web interface but after adding this directive I don't have such errors any more. I attached crumbs.trace file that you can open in charles proxy (www. charlesproxy.com) and shows sniffed jenkins cli <-> jenkins server conversation. Environment: Jenkins Master: OS: Ubuntu 12.04.2 LTS Jenkins: Jenkins ver. 1.492 Web proxy: OS: Ubuntu 12.04.1 www server: ngx_openresty/1.2.6.6 ignore_invalid_headers off; directive added!!! Client: OS: OS X 10.8.2 Java: Java HotSpot(TM) 64-Bit Server VM (build 23.6-b04, mixed mode) Jenkins client: downloaded from jenkins master Project: Jenkins Priority: Major Reporter: Maciej Sawicki This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15995) Arguments passed to Managed Script called in Conditional BuildStep could not be saved
SCM/JIRA link daemon commented on JENKINS-15995 Arguments passed to Managed Script called in Conditional BuildStep could not be saved Code changed in jenkins User: imod Path: src/main/java/org/jenkinsci/plugins/managedscripts/ScriptBuildStep.java src/main/java/org/jenkinsci/plugins/managedscripts/WinBatchBuildStep.java src/main/resources/org/jenkinsci/plugins/managedscripts/ScriptBuildStep/config.jelly src/main/resources/org/jenkinsci/plugins/managedscripts/WinBatchBuildStep/config.jelly http://jenkins-ci.org/commit/managed-scripts-plugin/3b1fc4da77cf822e6d3bd9d42b5c0310f52f0d93 Log: [FIXED JENKINS-15995] fix form submission – You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_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/groups/opt_out.
[JIRA] (JENKINS-15995) Arguments passed to Managed Script called in Conditional BuildStep could not be saved
SCM/JIRA link daemon resolved JENKINS-15995 as Fixed Arguments passed to Managed Script called in Conditional BuildStep could not be saved Change By: SCM/JIRA link daemon (10/Mar/13 4:06 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16449) When a job hits 'Max # of builds to keep' Nunit Publisher starts to throw NPE
Darren Gibson commented on JENKINS-16449 When a job hits 'Max # of builds to keep' Nunit Publisher starts to throw NPE It appears that I have managed to work around the issue by deleting the build where the issue first arose. While doing this I noticed something strange: the build that first failed had a time stamp of 20:39 the successful build before that was time stamped 19:30 (failed-1) the successful build before that was time stamped 15:50 (failed-2) the 15:50 folder contained a junitResult.xml time stamped at 19:30 ??? the build at 19:30 did not contain a junitResult.xml the build at 19:30 stated that "Notifying upstream projects of job completion" was a "SUCCESS" It appears that the build at 19:30 physically wrote its results to the previous builds folder, looking at the Test history it shows that build at 15:50 had twice as may tests run as normal. Deleting the 19:30 folder resolved the issue for me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-12826) empty repository browser url gives tomcat error page on different scm plugins
evernat commented on JENKINS-12826 empty repository browser url gives tomcat error page on different scm plugins reproduced with Jenkins 1.504 (using svn) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17064) Unable to edit some build definitions
Alex Earl commented on JENKINS-17064 Unable to edit some build definitions @Jason, please provide more information on what you are seeing, including exceptions, etc. Without that, I can't determine if its the same issue or another one. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16786) Please make the "N/A" white, not black. :-)
Jason Wooster edited a comment on JENKINS-16786 Please make the "N/A" white, not black. :-) I would prefer if the column was not enabled by default. We have a large number of jobs which don't actually build code and just execute tasks. And the jobs which do build code don't normally run code coverage currently (we're working on fixing that but it takes buy-in from the project teams). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16786) Please make the "N/A" white, not black. :-)
Jason Wooster commented on JENKINS-16786 Please make the "N/A" white, not black. :-) I would prefer if the column was not enabled by default. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17064) Unable to edit some build definitions
Jason Wooster commented on JENKINS-17064 Unable to edit some build definitions I still get this issue with email-ext 2.27.1 when using the latest stable build 1.480.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/groups/opt_out.
[JIRA] (JENKINS-10502) Add an option to make archiving the artifacts non-fatal if they don't exist
Pedro Rodriguez edited a comment on JENKINS-10502 Add an option to make archiving the artifacts non-fatal if they don't exist @evarnar: you've motivated me into getting involved! I've sent a request for this: https://github.com/jenkinsci/jenkins/pull/732 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
