[JIRA] [core] (JENKINS-21589) Unresolvable (environment) variables lead to failing maven builds
Stephan Krull
created JENKINS-21589
Unresolvable (environment) variables lead to failing maven builds
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
globalenv.png, mvnconf.png
Components:
core, maven
Created:
31/Jan/14 8:16 AM
Description:
The following scenario leads to failing builds because of faulty behaviour of Jenkins:
create a global environment variable:
create a job (maven or freestyle; did not test it on matrix)
configure maven: (enter the global env variable)
run the job
you get something like:
Modules changed, recalculating dependency graph
maven-agent.jar already up to date
classworlds.jar already up to date
maven-interceptor.jar already up to date
maven2.1-interceptor.jar already up to date
[amavenjob] $ java -Xmx512m -XX:MaxPermSize=256m -cp PATH/jenkins-slave/maven-agent.jar:PATH/jenkins-slave/classworlds.jar hudson.maven.agent.Main PATH/maven/current PATH/jenkins-slave/slave.jar PATH/jenkins-slave/maven-interceptor.jar 40919 PATH/jenkins-slave/maven2.1-interceptor.jar
===[JENKINS REMOTING CAPACITY]===channel started
log4j:WARN No appenders could be found for logger (org.apache.commons.beanutils.converters.BooleanConverter).
log4j:WARN Please initialize the log4j system properly.
Executing Maven: -B -f PATH/jenkins-slave/workspace/amavenjob/pom.xml clean install ${JOB_MVN_PARAM}
[INFO] Scanning for projects...
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Invalid task '${JOB_MVN_PARAM}': you must specify a valid lifecycle phase, or a goal in the format plugin:goal or pluginGroupId:pluginArtifactId:pluginVersion:goal
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 1 second
[INFO] Finished at: Fri Jan 31 09:12:40 CET 2014
[INFO] Final Memory: 3M/59M
[INFO]
channel stopped
Finished: FAILURE
Environment:
Jenkins 1.532.1 (LTS); JRE 7; Unix Daemon
maven-plugin 2.0.3
Project:
Jenkins
Priority:
Major
Reporter:
Stephan Krull
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21589) Unresolvable (environment) variables lead to failing maven builds
Stephan Krull
commented on JENKINS-21589
Unresolvable (environment) variables lead to failing maven builds
Maven is not able to ignore a placeholder in its commandline. Jenkins has to do that just before calling maven.
Maybe other tools are affected too.
I propose to filter the maven goals before committing them to a Builder.
For a private hotfix I used this method:
private ListString getListWithoutUnresolvableVariables(ArgumentListBuilder alb)
{
ListString result = new LinkedListString();
// pattern taken from hudson.Util.VARIABLE
final Pattern varPattern = Pattern.compile("\\$([A-Za-z0-9_]+|\\{[A-Za-z0-9_.]+\\}|\\$)");
for( String entry : alb.toList())
{
Matcher m = varPattern.matcher(entry);
final String intern = m.replaceAll("").trim();
if (0 intern.length())
{
result.add(intern);
}
}
return result;
}
to modify the calculated hudson.util.ArgumentListBuilder in hudson.maven.MavenModuleSetBuild.MavenModuleSetBuildExecution.doRun(BuildListener). This works well for Maven jobs but not for freestyle jobs.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21030) Git CLI cannot clone with ssh protocol on Windows if Git is in non-default location
SCM/JIRA link daemon resolved JENKINS-21030 as Fixed Git CLI cannot clone with ssh protocol on Windows if Git is in non-default location Change By: SCM/JIRA link daemon (31/Jan/14 8:40 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] [git] (JENKINS-21030) Git CLI cannot clone with ssh protocol on Windows if Git is in non-default location
SCM/JIRA link daemon commented on JENKINS-21030 Git CLI cannot clone with ssh protocol on Windows if Git is in non-default location Code changed in jenkins User: Wannes Sels Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java http://jenkins-ci.org/commit/git-client-plugin/602d9055eceda6ed3596155a2b0ece9b3e17090a Log: FIXED JENKINS-21030 look for ssh.exe next to known git.exe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21030) Git CLI cannot clone with ssh protocol on Windows if Git is in non-default location
SCM/JIRA link daemon commented on JENKINS-21030 Git CLI cannot clone with ssh protocol on Windows if Git is in non-default location Code changed in jenkins User: Nicolas De loof Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java http://jenkins-ci.org/commit/git-client-plugin/fe2623a5192ee83715a369ca436583bbad3d Log: Merge pull request #91 from wannessels/master FIXED JENKINS-21030 Compare: https://github.com/jenkinsci/git-client-plugin/compare/2a1749a45817...fe2623a5192e This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21030) Git CLI cannot clone with ssh protocol on Windows if Git is in non-default location
Wannes Sels
commented on JENKINS-21030
Git CLI cannot clone with ssh protocol on Windows if Git is in non-default location
I've created a pull request which should fix this.
Additionally, you might run in to error messages like this:
{{'c:\Program' is not recognized as an internal or external command,
operable program or batch file.}}
git-client creates temporary .bat files to pass credentials to ssh.exe, but msysgit doesn't like it if those .bat files are in a path with spaces.
See msysgit issue 203.
A workaround is to set the jenkins temp folder to a path without spaces. Add something like -Djava.io.tmpdir=C:\temp to your jenkins startup parameters.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21487) Frozen UI
Arnaud Héritier updated JENKINS-21487 Frozen UI Change By: Arnaud Héritier (31/Jan/14 8:43 AM) Priority: Major Blocker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21030) Git CLI cannot clone with ssh protocol on Windows if Git is in non-default location
Wannes Sels
edited a comment on JENKINS-21030
Git CLI cannot clone with ssh protocol on Windows if Git is in non-default location
I've created a pull request which should fix this.
Additionally, you might run in to error messages like this:
{{
'c:\Program' is not recognized as an internal or external command,
operable program or batch file.
}}
git-client creates temporary .bat files to pass credentials to ssh.exe, but msysgit doesn't like it if those .bat files are in a path with spaces.
See msysgit issue 203.
A workaround is to set the jenkins temp folder to a path without spaces. Add something like -Djava.io.tmpdir=C:\temp to your jenkins startup parameters.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21030) Git CLI cannot clone with ssh protocol on Windows if Git is in non-default location
Wannes Sels edited a comment on JENKINS-21030 Git CLI cannot clone with ssh protocol on Windows if Git is in non-default location I've created a pull request which should fix this. Additionally, you might run in to error messages like this: 'c:\Program' is not recognized as an internal or external command, operable program or batch file. git-client creates temporary .bat files to pass credentials to ssh.exe, but msysgit doesn't like it if those .bat files are in a path with spaces. See msysgit issue 203. A workaround is to set the jenkins temp folder to a path without spaces. Add something like -Djava.io.tmpdir=C:\temp to your jenkins startup parameters. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21487) Frozen UI
Daniel Beck
commented on JENKINS-21487
Frozen UI
Arnaud: Given kutzi's hypothesis about certain plugins loading too many builds, what's the result of this script in your Script Console (in Manage Jenkins):
def builds = Jenkins.instance.getAllItems(Job.class).collect { it.builds.size() }
println builds.sum()
println builds.sort()
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [prqa] (JENKINS-21588) PRQA plugin runs if previous build steps failed ( praqma case 10681 )
Jens Brejner updated JENKINS-21588 PRQA plugin runs if previous build steps failed ( praqma case 10681 ) Change By: Jens Brejner (31/Jan/14 9:23 AM) Summary: PRQApluginrunsifpreviousbuildstepsfailed (praqmacase10681) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21589) Unresolvable (environment) variables lead to failing maven builds
Stephan Krull commented on JENKINS-21589 Unresolvable (environment) variables lead to failing maven builds Maybe someone is interested in the usecase of the scenario described above: We are using homogeneous maven commands for all maven jobs that are based on company standard. Additionally these jobs are created from a template where the global environment variables are configured. Now and then a developer needs additional parameters added to the standard maven command. With Hudson I defined a placeholder environment variable without a value, the developer did an overwrite of this variable on his maven job. With Jenkins overwriting an environment variable does not work. I deleted the placeholder from the global environments an got the error message that is base to this issue because the placeholders are not configured in every job. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xcode] (JENKINS-16771) Xcode plugin doesn't read the Source Trees setting from the IDE
Olivier Guizol commented on JENKINS-16771 Xcode plugin doesnt read the Source Trees setting from the IDE I ended up with the same problem and here my analysis: When building using Xcode.app, we can see that source trees are set in environment variables (when variables are dumped in the logs). setenv SOURCE_TREE_NAME=/path/to/source/ Using Jenkins plugin which calls the command line there is no such line in the logs. Looking at the xcode-plugin code, XCodeBuilder.java does not have a source tree parameter. It should be added. A solution could be to read the preference file ~/Library/Preferences/com.apple.dt.Xcode.plist and extract the value for the key named IDEApplicationwideBuildSettings. This is a dictionary where the keys are the source tree names and the values are the associated path. Another solution would be to provide a new section in the xcode plugin page so that we can set source trees. A workaround may be to set these variables with the setenv plugin, but I haven't tested this one yet. Some interesting links: http://stackoverflow.com/questions/12010718/configure-xcode-source-trees-from-command-line http://www.cocoabuilder.com/archive/xcode/283358-xcodebuilds-fails-where-xcode-app-succeeds-source-tree-problem.html Hope this helps. Olivier This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xcode] (JENKINS-16771) Xcode plugin doesn't read the Source Trees setting from the IDE
Olivier Guizol edited a comment on JENKINS-16771 Xcode plugin doesnt read the Source Trees setting from the IDE I ended up with the same problem and here's my analysis: When building using Xcode.app, we can see that source trees are set in environment variables (when variables are dumped in the logs). setenv SOURCE_TREE_NAME=/path/to/source/ Using Jenkins plugin which calls the command line there is no such line in the logs. Looking at the xcode-plugin code, XCodeBuilder.java does not have a source tree parameter. It should be added. A solution could be to read the preference file ~/Library/Preferences/com.apple.dt.Xcode.plist and extract the value for the key named IDEApplicationwideBuildSettings. This is a dictionary where the keys are the source tree names and the values are the associated path. Another solution would be to provide a new section in the xcode plugin page so that we can set source trees. A workaround may be to set these variables with the setenv plugin, but I haven't tested this one yet. Some interesting links: http://stackoverflow.com/questions/12010718/configure-xcode-source-trees-from-command-line http://www.cocoabuilder.com/archive/xcode/283358-xcodebuilds-fails-where-xcode-app-succeeds-source-tree-problem.html Hope this helps. Olivier This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21487) Frozen UI
Arnaud Héritier commented on JENKINS-21487 Frozen UI Hi guys, Another morning, another TD : https://gist.github.com/aheritier/8728536 and another one 20 min after : https://gist.github.com/aheritier/8728670 I may try to disable the priority sorter plugin. I updated it several weeks ago but that's right that I changed its configuration recently to get ride of its legacy mode thus it may be a good culprit. Good idea to check the plugins updates time from the disk (just for what was changed since january, the problem started around 20th Jan) : 0 -rw-r--r-- 1 jenkins jenkins 0 Jan 29 18:24 project-stats-plugin.jpi.disabled 164K -rw-r--r-- 1 jenkins jenkins 163K Jan 29 18:20 promoted-builds.jpi 11M -rw-r--r-- 1 jenkins jenkins 11M Jan 29 18:20 email-ext.jpi 11M -rw-r--r-- 1 jenkins jenkins 11M Jan 29 18:20 maven-plugin.jpi 0 -rw-r--r-- 1 jenkins jenkins 0 Jan 29 18:20 maven-plugin.jpi.pinned 48K -rw-r--r-- 1 jenkins jenkins 48K Jan 29 18:20 rebuild.jpi 1.2M -rw-r--r-- 1 jenkins jenkins 1.2M Jan 29 18:20 jenkins-multijob-plugin.jpi 52K -rw-r--r-- 1 jenkins jenkins 51K Jan 21 18:08 ldap.jpi 0 -rw-r--r-- 1 jenkins jenkins 0 Jan 21 18:08 ldap.jpi.pinned 32K -rw-r--r-- 1 jenkins jenkins 31K Jan 21 18:08 radiatorviewplugin.jpi 0 -rw-r--r-- 1 jenkins jenkins 0 Jan 21 18:07 disk-usage.jpi.disabled 5.1M -rw-r--r-- 1 jenkins jenkins 5.1M Jan 16 21:40 git.jpi 2.3M -rw-r--r-- 1 jenkins jenkins 2.3M Jan 16 10:23 git-client.jpi 100K -rw-r--r-- 1 jenkins jenkins 99K Jan 16 10:23 PrioritySorter.jpi 5.1M -rw-r--r-- 1 jenkins jenkins 5.1M Jan 9 10:54 build-pipeline-plugin.jpi 32K -rw-r--r-- 1 jenkins jenkins 30K Jan 9 10:54 nested-view.jpi 56K -rw-r--r-- 1 jenkins jenkins 53K Jan 9 10:54 translation.jpi 0 -rw-r--r-- 1 jenkins jenkins 0 Jan 9 10:54 translation.jpi.pinned 56K -rw-r--r-- 1 jenkins jenkins 56K Jan 9 10:54 buildresult-trigger.jpi 44K -rw-r--r-- 1 jenkins jenkins 44K Jan 6 18:31 multiple-scms.jpi 84K -rw-r--r-- 1 jenkins jenkins 83K Jan 6 18:31 xcode-plugin.jpi UnstableJobsPortlet is from the dashboard plugin AFAIR. About the number of builds kept I always reduced them a long time ago. If I have no error all jobs must be configured with : daysToKeep15/daysToKeep numToKeep15/numToKeep artifactDaysToKeep10/artifactDaysToKeep artifactNumToKeep10/artifactNumToKeep The maven plugin version is 2.0.1 and 2.0.3 seems to be out. I will try to give it a try This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xcode] (JENKINS-16771) Xcode plugin doesn't read the Source Trees setting from the IDE
Olivier Guizol edited a comment on JENKINS-16771 Xcode plugin doesnt read the Source Trees setting from the IDE I ended up with the same problem and here's my analysis: When building using Xcode.app, we can see that source trees are set in environment variables (when variables are dumped in the logs). setenv SOURCE_TREE_NAME=/path/to/source/ Using Jenkins plugin which calls the command line there is no such line in the logs. Looking at the xcode-plugin code, XCodeBuilder.java does not have a source tree parameter. It should be added. A solution could be to read the preference file ~/Library/Preferences/com.apple.dt.Xcode.plist and extract the value for the key named IDEApplicationwideBuildSettings. This is a dictionary where the keys are the source tree names and the values are the associated path. Another solution would be to provide a new section in the xcode plugin page so that we can set source trees. A workaround may be to set these variables with the EnvInject Plugin, but I haven't tested this one yet. Some interesting links: http://stackoverflow.com/questions/12010718/configure-xcode-source-trees-from-command-line http://www.cocoabuilder.com/archive/xcode/283358-xcodebuilds-fails-where-xcode-app-succeeds-source-tree-problem.html Hope this helps. Olivier This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [prqa] (JENKINS-21588) PRQA plugin runs if previous build steps failed ( praqma case 10681 )
Mads Nielsen commented on JENKINS-21588 PRQA plugin runs if previous build steps failed ( praqma case 10681 ) Hey Mikko, We're aware of your issue and will take a look at when time permits Best regards, Mads This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [keyboard-shortcuts] (JENKINS-20696) Configure/edit keyboard shortcuts
Damien Finck commented on JENKINS-20696 Configure/edit keyboard shortcuts Hi, Yes, I know that my change is no the good solution, but it's a temporary solution pending the improvement. Personally, I think the shortcut should be "g-b" by default rather than "b", beacause other shortcut are like "g-x" and because "b" may be unintentionally type. Add the way to edit/modify the keyboard shortcuts is more complex and take times. So, do you think that I must rollback my changes ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [master-slave] (JENKINS-21590) Master cannot connect to slave / search for Java on slave fails
Eike Poegel updated JENKINS-21590 Master cannot connect to slave / search for Java on slave fails Change By: Eike Poegel (31/Jan/14 9:43 AM) Summary: Mastercannotconnectto client slave /searchforJavaonslavefails This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [master-slave] (JENKINS-21590) Master cannot connect to client / search for Java on slave fails
Eike Poegel created JENKINS-21590 Master cannot connect to client / search for Java on slave fails Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: master-slave Created: 31/Jan/14 9:42 AM Description: Jenkins v1.549 fails to start up Windows jenskin-slave service: Cannot find installed Java version on slave host. Jenkins v1.546 works fine. Windows Slaves Plugin is v1.0 Environment: Windows XP Project: Jenkins Priority: Critical Reporter: Eike Poegel This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xcode] (JENKINS-16771) Xcode plugin doesn't read the Source Trees setting from the IDE
Olivier Guizol edited a comment on JENKINS-16771 Xcode plugin doesnt read the Source Trees setting from the IDE I ended up with the same problem and here's my analysis: When building using Xcode.app, we can see that source trees are set in environment variables (when variables are dumped in the logs). setenv SOURCE_TREE_NAME=/path/to/source/ Using Jenkins plugin which calls the command line there is no such line in the logs. Looking at the xcode-plugin code, XCodeBuilder.java does not have a source tree parameter. It should be added. A solution could be to read the preference file ~/Library/Preferences/com.apple.dt.Xcode.plist and extract the value for the key named IDEApplicationwideBuildSettings. This is a dictionary where the keys are the source tree names and the values are the associated path. Another solution would be to provide a new section in the xcode plugin page so that we can set source trees. A workaround I tested and seems to work is to set these variables with the EnvInject Plugin. Some interesting links: http://stackoverflow.com/questions/12010718/configure-xcode-source-trees-from-command-line http://www.cocoabuilder.com/archive/xcode/283358-xcodebuilds-fails-where-xcode-app-succeeds-source-tree-problem.html Hope this helps. Olivier This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [performance-plugin] (JENKINS-21591) Error threshold should accept a float instead of an int
Arjun Urs created JENKINS-21591 Error threshold should accept a float instead of an int Issue Type: Improvement Assignee: Manuel Carrasco Components: performance-plugin Created: 31/Jan/14 10:02 AM Description: Error threshold field is defined as an int. It should be able to accept a floating point number. Project: Jenkins Priority: Major Reporter: Arjun Urs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [active-directory] (JENKINS-21592) ActiveDirectory plugin crashes Jenkins on login
Craig Lawton-Devine created JENKINS-21592 ActiveDirectory plugin crashes Jenkins on login Issue Type: Bug Assignee: Unassigned Components: active-directory Created: 31/Jan/14 10:43 AM Description: Updated Jenkins this morning (no issues), and then updated all my plugins and got this stack trace. It seems to related to the active-directory plugin. If I clear my cookies then Jenkins shows the dashboard ok, but as soon as I try to log in then I get another stack trace and I'm not logged in. Stack trace java.lang.NoClassDefFoundError: hudson/tasks/Mailer$UserProperty at hudson.plugins.active_directory.ActiveDirectoryAuthenticationProvider.retrieveUser(ActiveDirectoryAuthenticationProvider.java:116) at hudson.plugins.active_directory.AbstractActiveDirectoryAuthenticationProvider.loadUserByUsername(AbstractActiveDirectoryAuthenticationProvider.java:30) at org.acegisecurity.ui.rememberme.TokenBasedRememberMeServices.loadUserDetails(TokenBasedRememberMeServices.java:308) at org.acegisecurity.ui.rememberme.TokenBasedRememberMeServices.autoLogin(TokenBasedRememberMeServices.java:218) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$1.autoLogin(ActiveDirectorySecurityRealm.java:140) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:104) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:949) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1011) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:644) at
[JIRA] [testflight] (JENKINS-21593) If commit message are several lines, only the first is displayed.
Ricardo Ruiz created JENKINS-21593 If commit message are several lines, only the first is displayed. Issue Type: Bug Assignee: Unassigned Components: testflight Created: 31/Jan/14 10:49 AM Description: If commit message are several lines, only the first is displayed when submitting to testflight servers. So, you may not see important information. Project: Jenkins Priority: Major Reporter: Ricardo Ruiz This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
Peter Phillips commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) Agreed, but the temp directory needs to have a .git/config file too. This can be achieved by either running git init in that directory, or it sound like creating an empty .git/config file will work too. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [slave-setup] (JENKINS-21570) Slave JNLP not signed by a CA causes issues with Java 7.51
Simon Strauch commented on JENKINS-21570 Slave JNLP not signed by a CA causes issues with Java 7.51 The Website http://www.java.com/en/download/help/java_blocked.xml describes 3 of 2 topics that went wrong in the JNLP-Slave. 1st: self-signed certificat. I used this description to extract the public key and add it to Java as Signer CA: stackoverflow: Extract raw X.509 Certificate from a signed APK or JAR Now Java Webstart begin to except the JAR file. But the 2nd Problem is: Missing required Permissions manifest attribute in main jar The MANIFEST.MF file does not contain the Permissions attribute. The workaround is to add the download server URL. That work. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dashboard-view] (JENKINS-21578) CCE since ${jobs} includes non-Job's
SCM/JIRA link daemon
resolved JENKINS-21578 as Fixed
CCE since ${jobs} includes non-Jobs
Change By:
SCM/JIRA link daemon
(31/Jan/14 11:23 AM)
Status:
InProgress
Resolved
Resolution:
Fixed
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dashboard-view] (JENKINS-21578) CCE since ${jobs} includes non-Job's
SCM/JIRA link daemon
commented on JENKINS-21578
CCE since ${jobs} includes non-Jobs
Code changed in jenkins
User: Marco Ambu
Path:
src/main/resources/hudson/plugins/view/dashboard/DashboardPortlet/index.jelly
http://jenkins-ci.org/commit/dashboard-view-plugin/0481b6f2ef6ea09c376f94566f566772d504e69f
Log:
Merge pull request #23 from jglick/folder-CCE-JENKINS-21578
FIXED JENKINS-21578 Ensure that ${jobs} is really a CollectionJob
Compare: https://github.com/jenkinsci/dashboard-view-plugin/compare/d1801567045a...0481b6f2ef6e
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [dashboard-view] (JENKINS-21578) CCE since ${jobs} includes non-Job's
SCM/JIRA link daemon
commented on JENKINS-21578
CCE since ${jobs} includes non-Jobs
Code changed in jenkins
User: Jesse Glick
Path:
src/main/resources/hudson/plugins/view/dashboard/DashboardPortlet/index.jelly
http://jenkins-ci.org/commit/dashboard-view-plugin/baa8c5043072c6cc7a3cf44f002d55befd86f1c5
Log:
FIXED JENKINS-21578 Ensure that ${jobs} is really a CollectionJob, with no Folder for example.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [windows-slaves] (JENKINS-21542) Cannot launch Windows libvirt slaves due to missing method on SmbFileInputStream
Johan Cronje commented on JENKINS-21542 Cannot launch Windows libvirt slaves due to missing method on SmbFileInputStream Verified that downgrading to 1.545 solved the issue for us. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [delivery-pipeline] (JENKINS-21435) CSS fixes for stage
Patrik Boström closed JENKINS-21435 as Fixed CSS fixes for stage Released Change By: Patrik Boström (31/Jan/14 12:29 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [delivery-pipeline] (JENKINS-21549) Can not resolve status for downstream jobs in folders
Patrik Boström closed JENKINS-21549 as Fixed Can not resolve status for downstream jobs in folders Released Change By: Patrik Boström (31/Jan/14 12:29 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [promoted-builds] (JENKINS-19863) Can we get more colors for promotion stars?
Marvi Benedet commented on JENKINS-19863 Can we get more colors for promotion stars? pulled https://github.com/jenkinsci/promoted-builds-plugin/pull/35 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [delivery-pipeline] (JENKINS-21533) Links when using folders is wrong
Patrik Boström closed JENKINS-21533 as Fixed Links when using folders is wrong Released Change By: Patrik Boström (31/Jan/14 12:30 PM) Status: Resolved Closed Assignee: PatrikBoström This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Sergey Saraev commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 +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/groups/opt_out.
[JIRA] [s3] (JENKINS-21594) JENKINS-16025 broke non-wirldcard S3 upload
Brice Figureau created JENKINS-21594 JENKINS-16025 broke non-wirldcard S3 upload Issue Type: Bug Affects Versions: current Assignee: Michael Watt Components: s3 Created: 31/Jan/14 12:38 PM Description: The fix for JENKINS-16025 broke the case when you're trying to upload to S3 a single file without using a wildcard. For instance: bucket: bucket/path/to/artifact source: *.tar.gz will correctly upload all tar.gz to the destination bucket in the /path/to/artifact folder. But: bucket: bucket/path/to/artifact source: myfile.tar.gz will unfortunately upload the myfile.tar.gz content into the 'artifact' directory. Project: Jenkins Priority: Major Reporter: Brice Figureau This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [promoted-builds] (JENKINS-19863) Can we get more colors for promotion stars?
Marvi Benedet commented on JENKINS-19863 Can we get more colors for promotion stars? (poll requested) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [s3] (JENKINS-21594) JENKINS-16025 broke non-wirldcard S3 upload
Brice Figureau commented on JENKINS-21594 JENKINS-16025 broke non-wirldcard S3 upload This is fixed in this PR: https://github.com/jenkinsci/s3-plugin/pull/21 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [keyboard-shortcuts] (JENKINS-20696) Configure/edit keyboard shortcuts
jieryn
commented on JENKINS-20696
Configure/edit keyboard shortcuts
As the original author of this plugin, I can tell you the motiviation behind that scheme. The single key characters are for frequent DO_THIS type things, like Open a job that is highlighted, or move up and down in a job list (e.g. View). The g-X combinations are for dramatic movement across major boundaries. Like GO-HOME, GO-CONFIGURE, GO-VIEW{prompt}. The G means GO, to GO to another page kind of thing.
I am really happy that someone is using and contributing to the plugin. I just see this change as breaking some key behavior, and frankly speaking, the people that use keyboard shortcuts are obsessive types that do not like behavior being 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/groups/opt_out.
[JIRA] [s3] (JENKINS-21594) JENKINS-16025 broke non-wirldcard S3 upload
SCM/JIRA link daemon commented on JENKINS-21594 JENKINS-16025 broke non-wirldcard S3 upload Code changed in jenkins User: David Beer Path: src/main/java/hudson/plugins/s3/S3BucketPublisher.java http://jenkins-ci.org/commit/s3-plugin/679f74801e65cb863a9dc6e3c5ebb0846e6429d7 Log: Merge pull request #21 from masterzen/fix/JENKINS-21594-no-wildcard-upload JENKINS-21594: Allow to upload file without wildcard Compare: https://github.com/jenkinsci/s3-plugin/compare/519a55f5c806...679f74801e65 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [s3] (JENKINS-21594) JENKINS-16025 broke non-wirldcard S3 upload
SCM/JIRA link daemon commented on JENKINS-21594 JENKINS-16025 broke non-wirldcard S3 upload Code changed in jenkins User: Brice Figureau Path: src/main/java/hudson/plugins/s3/S3BucketPublisher.java http://jenkins-ci.org/commit/s3-plugin/40c193421e90fac7033f78a64a0a3e48e150cac0 Log: JENKINS-21594: Allow to upload file without wildcard Commit 24a3b881 introduced a feature for wildcard uploads, but broke the original behavior if your upload is configured with a straight filename. For instance: Destination bucket: path/to/dir Source: file.tar.gz Would be uploaded as path/to/dir, missing completely the source file name. This commit fixes this specific issue. 1 https://github.com/jenkinsci/s3-plugin/commit/24a3b88a7b9acb0532deabe686944e53747c49a9 Signed-off-by: Brice Figureau br...@daysofwonder.com This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [s3] (JENKINS-21594) JENKINS-16025 broke non-wirldcard S3 upload
David Beer resolved JENKINS-21594 as Fixed JENKINS-16025 broke non-wirldcard S3 upload Change By: David Beer (31/Jan/14 1:34 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] [active-directory] (JENKINS-21583) Attempting to configure the active-directory plugin caused an error that now prevents Jenkins from starting up
Robert Campbell
commented on JENKINS-21583
Attempting to configure the active-directory plugin caused an error that now prevents Jenkins from starting up
I've looked through some source. Looks like the acegi RememberMeAuthenticationProvider only takes a 'key' parameter from Spring. So that has to be the culprit that is being sent in null or empty. Then I found the call in the active-directory plugin in a groovy script:
...
bean(RememberMeAuthenticationProvider) {
key = Hudson.getInstance().getSecretKey();
},
...
But nothing in the active-directory plugin ever sets the SecretKey, unless it is a side effect of a call that I haven't noticed. So I'm not sure what is causing getSecretKey to return null or an empty string.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21326) email-ext.jar might need to be rebuilt in email-ext 2.37
Karl Theil commented on JENKINS-21326 email-ext.jar might need to be rebuilt in email-ext 2.37 Thanks, fixed for me too. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [active-directory] (JENKINS-21592) ActiveDirectory plugin crashes Jenkins on login
Craig Lawton-Devine updated JENKINS-21592 ActiveDirectory plugin crashes Jenkins on login Change By: Craig Lawton-Devine (31/Jan/14 1:56 PM) Priority: Blocker Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [active-directory] (JENKINS-21592) ActiveDirectory plugin crashes Jenkins on login
Craig Lawton-Devine commented on JENKINS-21592 ActiveDirectory plugin crashes Jenkins on login After a bit of investigation it seems Jenkins not not restart properly after installing the updates. I stopped Jenkins but java.exe hadn't released the port and resulted in 2 instances running. I killed java and restarted Jenkins, and now everything is back to normal. I've reduced the severity of the bug to minor. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [support-core] (JENKINS-21595) Include recent access logs
Jesse Glick created JENKINS-21595 Include recent access logs Issue Type: New Feature Assignee: Unassigned Components: support-core Created: 31/Jan/14 2:07 PM Description: Since Jenkins bugs sometimes involve 404s or similar problems especially from AJAX requests, or performance issues caused by excessive REST API calls, it would be useful for a support bundle to include something like a web server's access log, probably just for the past 100 or so requests. Minimally it should display the request URI and the response status code. (I am assuming it is possible to capture requests in an early servlet filter, as the Monitoring plugin does.) Project: Jenkins Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobconfighistory] (JENKINS-19170) Display all changes within a folder
Stefan Brausch commented on JENKINS-19170 Display all changes within a folder Jesse: is this feature implement with https://github.com/jenkinsci/jobConfigHistory-plugin/pull/21 ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [jobconfighistory] (JENKINS-19874) Loading job config history with over 20,000 entries takes over 5 minutes
Stefan Brausch commented on JENKINS-19874 Loading job config history with over 20,000 entries takes over 5 minutes Can we close this issue? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobconfighistory] (JENKINS-18900) [JobConfigurationHistory] Wrong history being displayed
Stefan Brausch assigned JENKINS-18900 to Stefan Brausch [JobConfigurationHistory] Wrong history being displayed Change By: Stefan Brausch (31/Jan/14 2:20 PM) Assignee: MirkoFriedenhagen StefanBrausch This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [jobconfighistory] (JENKINS-18900) [JobConfigurationHistory] Wrong history being displayed
Stefan Brausch commented on JENKINS-18900 [JobConfigurationHistory] Wrong history being displayed Sorry Steffen for the delay. Do you've still this problem? Are any files inside the not shown folders? If yes, please could you paste the content of history.xml here? Thanks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [jobconfighistory] (JENKINS-18949) Renaming Project causes content encoding error
Stefan Brausch commented on JENKINS-18949 Renaming Project causes content encoding error I can't see any impact from jobconfighistory for your problem. Do you have still this problem? If yes, which other plugins and which jenkins master version do you use 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/groups/opt_out.
[JIRA] [jobconfighistory] (JENKINS-19874) Loading job config history with over 20,000 entries takes over 5 minutes
Sagi Sinai-Glazer commented on JENKINS-19874 Loading job config history with over 20,000 entries takes over 5 minutes Stefan - If it's not going to be fixed - then you can close it. I have no use for an open-unaddressed JIRA ticket. Having said that, I would prefer to keep it as a backlog item... Purging part of the history does help, but it's still not efficient to go through ALL the entries. As far as I can tell - enabling paging or some other form of partial loading is the only way to actually resolve this issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [analysis-core] (JENKINS-21596) Support ReSharper commandline output
Pete W created JENKINS-21596 Support ReSharper commandline output Issue Type: New Feature Assignee: Ulli Hafner Components: analysis-core, dry, violations Created: 31/Jan/14 2:29 PM Description: Would be good to support the xml outputs in reports from the resharper commandline tools. http://confluence.jetbrains.com/display/NETCOM/Introducing+ReSharper+Command+Line+Tools Project: Jenkins Labels: violations ReSharper dry dupfinder inspectcode Priority: Major Reporter: Pete W This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [jobconfighistory] (JENKINS-13288) Config history does not appear for certain jobs
Stefan Brausch edited a comment on JENKINS-13288 Config history does not appear for certain jobs No answer for a lot of months. I think we can close this issue! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobconfighistory] (JENKINS-13288) Config history does not appear for certain jobs
Stefan Brausch commented on JENKINS-13288 Config history does not appear for certain jobs No answer for a lot of month. I think we can close this issue! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-21597) New Maven Plugin causes build listeners to be called after the completion of every module, causing a lot of plugins to break
Stephan Pauxberger created JENKINS-21597 New Maven Plugin causes build listeners to be called after the completion of every module, causing a lot of plugins to break Issue Type: Bug Assignee: Unassigned Components: maven Created: 31/Jan/14 2:34 PM Description: Also, this causes an extreme slow down, especially when using incremental build. In our case, we have a huge project (~100 modules). An incremental build, which should only build about 5 modules waits for about 2 minutes (while moving through the listeners for all NOT_BUILT modules), before actually starting to work. This was introduced by the fix for JENKINS-18846. Project: Jenkins Priority: Major Reporter: Stephan Pauxberger This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [maven] (JENKINS-21597) New Maven Plugin causes slowdown for huge multimodule projects
Stephan Pauxberger updated JENKINS-21597 New Maven Plugin causes slowdown for huge multimodule projects Change By: Stephan Pauxberger (31/Jan/14 2:36 PM) Summary: NewMavenPlugincauses buildlistenerstobecalledafterthecompletionofeverymodule,causingalotofpluginstobreak slowdownforhugemultimoduleprojects Description: Thisisduetothefact,thatnowallbuildlistenersarecalledaftereverymoduleaswell.Thismightalsobreakplugins. Also,this causesanextremeslowdown,especially leadstoconfusingbehaviour whenusingincremental build builds .Inourcase,wehaveahugeproject(~100modules).Anincrementalbuild,whichshouldonlybuildabout5moduleswaitsforabout2minutes(whilemovingthroughthelistenersforallNOT_BUILTmodules),beforeactuallystartingtowork.Thiswasintroducedbythefixfor[JENKINS-18846]. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [warnings] (JENKINS-21596) Support ReSharper commandline output
Ulli Hafner updated JENKINS-21596 Support ReSharper commandline output Change By: Ulli Hafner (31/Jan/14 2:38 PM) Component/s: warnings Component/s: violations Component/s: dry Component/s: analysis-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/groups/opt_out.
[JIRA] [checkstyle] (JENKINS-20070) Restore sax parser system property after XML parsing
SCM/JIRA link daemon commented on JENKINS-20070 Restore sax parser system property after XML parsing Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/analysis/util/SaxSetup.java http://jenkins-ci.org/commit/analysis-core-plugin/b5457a8ecc62847e87aa28016de97255128c3c35 Log: JENKINS-20070 Clear SAX system property afterwards. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [warnings] (JENKINS-21596) Support ReSharper commandline output
Pete W commented on JENKINS-21596 Support ReSharper commandline output Ah i see! thanks for the pointer. I will watch with anticipation This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [promoted-builds] (JENKINS-19863) Can we get more colors for promotion stars?
Marvi Benedet updated JENKINS-19863 Can we get more colors for promotion stars? Change By: Marvi Benedet (31/Jan/14 2:45 PM) Attachment: stars.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20286) JGit incorrectly reports changes detected when polling
Mark Waite updated JENKINS-20286 JGit incorrectly reports changes detected when polling Change By: Mark Waite (31/Jan/14 2:45 PM) Description: AJenkins multi-configuration jobconfiguredwiththeGitpluginusingtheJGitimplementationwillexecutethejobateachpollinginterval,evenwhentherewerenochangesonthegitrepository.Thesamejob,configuredwiththeGitpluginusingthegitcommandlineimplementationonlyexecutesthejobwhentherewerechangesinthegitrepository.TheproblemisvisiblewithbothagitprotocolrepositoryandwithaGitHubrepositoryusingthehttpsprotocol.Samplejobdefinitionswhichshowtheproblemareattached.ThejobdefinitionswithjgitintheXMLfilenameshowtheproblem.ThejobdefinitionswithcliintheXMLfilenamedonotshowtheproblem.Thereisasimpleworkaroundfortheproblem.AddtheForcepollingusingworkspacetothejobconfigurationthroughtheAdditionalBehaviourssectionofthegitpluginconfigurationforthejob. Thatavoidstheproblemls-remoteintheJGitpluginimplementation.Unfortunately,italsoslowsthepollingprocessinthosecaseswheretherepositorydoesnotalreadyexistAnotherworkaroundistoremovewildcardsfromthebranchnameinthejobdefinition.Unfortunately,thatremovestheabilitytomonitormultiplebrancheswithasingleJenkinsjob. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [checkstyle] (JENKINS-20070) Restore sax parser system property after XML parsing
SCM/JIRA link daemon commented on JENKINS-20070 Restore sax parser system property after XML parsing Code changed in jenkins User: Ulli Hafner Path: plugin/src/test/java/hudson/plugins/findbugs/parser/FindBugsParserTest.java http://jenkins-ci.org/commit/findbugs-plugin/9dbc7313bfe3f624db6a6bcefdaa093ad618ddca Log: JENKINS-20070 Clear SAX system property afterwards. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [warnings] (JENKINS-19689) Expand relative paths even if 'resolve relative paths option' is not checked
SCM/JIRA link daemon resolved JENKINS-19689 as Fixed Expand relative paths even if resolve relative paths option is not checked Change By: SCM/JIRA link daemon (31/Jan/14 2:47 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [warnings] (JENKINS-19689) Expand relative paths even if 'resolve relative paths option' is not checked
SCM/JIRA link daemon commented on JENKINS-19689 Expand relative paths even if resolve relative paths option is not checked Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/analysis/core/FilesParser.java src/main/java/hudson/plugins/analysis/core/ParserResult.java src/test/java/hudson/plugins/analysis/core/ParserResultTest.java http://jenkins-ci.org/commit/analysis-core-plugin/44c263a4904a6f895f1e8336c871202ada041c37 Log: FIXED JENKINS-19689 Improved option resolve relative paths: Always concatenate workspace prefix and relative path 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/groups/opt_out.
[JIRA] [warnings] (JENKINS-19689) Expand relative paths even if 'resolve relative paths option' is not checked
SCM/JIRA link daemon commented on JENKINS-19689 Expand relative paths even if resolve relative paths option is not checked Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/warnings/WarningsPublisher.java http://jenkins-ci.org/commit/warnings-plugin/4605175e8aae6c16b169cd35bca2441c91738d10 Log: FIXED JENKINS-19689 Improved option resolve relative paths: Always concatenate workspace prefix and relative path 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/groups/opt_out.
[JIRA] [jobconfighistory] (JENKINS-19874) Loading job config history with over 20,000 entries takes over 5 minutes
Stefan Brausch resolved JENKINS-19874 as Fixed Loading job config history with over 20,000 entries takes over 5 minutes Close this issue. Change By: Stefan Brausch (31/Jan/14 2:58 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] [jobconfighistory] (JENKINS-21598) Paging for jobconfighistory entries
Stefan Brausch created JENKINS-21598 Paging for jobconfighistory entries Issue Type: New Feature Assignee: Mirko Friedenhagen Components: jobconfighistory Created: 31/Jan/14 2:56 PM Environment: Show only x entries per site of jobconfighistory page. Load only this entries from directory also (performance). Project: Jenkins Priority: Major Reporter: Stefan Brausch This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [warnings] (JENKINS-21569) Expose current input line in groovy script
SCM/JIRA link daemon resolved JENKINS-21569 as Fixed Expose current input line in groovy script Change By: SCM/JIRA link daemon (31/Jan/14 3:01 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] [elastic-axis] (JENKINS-21599) Support label expressions in addition to fixed labels
Jesse Glick created JENKINS-21599 Support label expressions in addition to fixed labels Issue Type: New Feature Assignee: Unassigned Components: elastic-axis Created: 31/Jan/14 2:59 PM Description: It would be useful to be able to specify a label _expression_ such as linux amd64 in the label list. Project: Jenkins Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [warnings] (JENKINS-21569) Expose current input line in groovy script
SCM/JIRA link daemon commented on JENKINS-21569 Expose current input line in groovy script Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/warnings/parser/DynamicParser.java src/main/java/hudson/plugins/warnings/parser/GroovyExpressionMatcher.java http://jenkins-ci.org/commit/warnings-plugin/fb9924a16dead75cdf8a73b811c4824b413a0a6d Log: FIXED JENKINS-21569 Expose current line in groovy. Added getCurrentLine() method for line based parsers. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [jobconfighistory] (JENKINS-19170) Display all changes within a folder
Jesse Glick commented on JENKINS-19170 Display all changes within a folder No. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [subversion] (JENKINS-5107) Subversion credentials management
Jesse Glick resolved JENKINS-5107 as Duplicate Subversion credentials management Change By: Jesse Glick (31/Jan/14 3:14 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [security] (JENKINS-18250) A user with configure permission for a project cannot add SVN+SSH credentials without having global config permissions
Jesse Glick commented on JENKINS-18250 A user with configure permission for a project cannot add SVN+SSH credentials without having global config permissions PR is still mergeable; TBD whether this issue is still relevant. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [warnings] (JENKINS-21569) Expose current input line in groovy script
Ulli Hafner reopened JENKINS-21569 Expose current input line in groovy script Hmm, is not that easy... Change By: Ulli Hafner (31/Jan/14 3:13 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] [subversion] (JENKINS-14229) How Credential plugin work with Subversion plugin
Jesse Glick resolved JENKINS-14229 as Fixed How Credential plugin work with Subversion plugin 2.0 has been released. Change By: Jesse Glick (31/Jan/14 3:13 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobconfighistory] (JENKINS-19170) Display all changes within a folder
Daniel Beck commented on JENKINS-19170 Display all changes within a folder Stefan: To clarify, PR 21 added the 'Config History' sidepanel link to Folders, similar to jobs, showing just the changes of the folder configuration itself (e.g. health metrics, display name, …). JENKINS-20999 tracked that change. This issue is about a new feature for folders: An aggregating view of all config changes within a certain Folder, no matter whether the folder "F", or jobs "F/job1" or "F/jobN" within it were changed. Similar to /jobConfigHistory/?filter=jobs (+created +deleted), but for a folder. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Hendrik Stehr commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 +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/groups/opt_out.
[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Peter Schmitz commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 +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/groups/opt_out.
[JIRA] [warnings] (JENKINS-21569) Expose current input line in groovy script
SCM/JIRA link daemon resolved JENKINS-21569 as Fixed Expose current input line in groovy script Change By: SCM/JIRA link daemon (31/Jan/14 3:26 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [warnings] (JENKINS-21569) Expose current input line in groovy script
Ulli Hafner commented on JENKINS-21569 Expose current input line in groovy script The line number is exposed via property 'lineNumber'. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [warnings] (JENKINS-21569) Expose current input line in groovy script
SCM/JIRA link daemon commented on JENKINS-21569 Expose current input line in groovy script Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/warnings/parser/DynamicParser.java src/main/java/hudson/plugins/warnings/parser/GroovyExpressionMatcher.java src/test/java/hudson/plugins/warnings/parser/DynamicParserTest.java http://jenkins-ci.org/commit/warnings-plugin/c2fcaec495f69bb8a90b0edc83b03a22635bb30a Log: FIXED JENKINS-21569 Expose variable lineNumber in groovy. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [jobconfighistory] (JENKINS-21600) Enable paging to improve performance
Sagi Sinai-Glazer created JENKINS-21600 Enable paging to improve performance Issue Type: Improvement Affects Versions: current Assignee: Mirko Friedenhagen Components: jobconfighistory Created: 31/Jan/14 3:39 PM Description: In case there are jobs with a very long configuration history - currently loading the history page takes a few minutes. Enabling paging that show only a portion of the information at the time will significantly improve the performance. This way you can show 100 entries per page, or even better set a default number and let the user change it in case he wants to see more. Project: Jenkins Labels: performance paging Priority: Major Reporter: Sagi Sinai-Glazer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [windows-slaves] (JENKINS-21373) Unable to connect to Windows slave after upgrade to Jenkins ver. 1.547
Jesse Glick commented on JENKINS-21373 Unable to connect to Windows slave after upgrade to Jenkins ver. 1.547 Possibly: https://github.com/jenkinsci/jenkins/pull/1106 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [jobconfighistory] (JENKINS-19170) Display all changes within a folder
Jesse Glick commented on JENKINS-19170 Display all changes within a folder Exactly, thanks for the summary. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [windows-slaves] (JENKINS-21542) Cannot launch Windows libvirt slaves due to missing method on SmbFileInputStream
Vincent Latombe resolved JENKINS-21542 as Duplicate Cannot launch Windows libvirt slaves due to missing method on SmbFileInputStream Fixed through https://github.com/jenkinsci/jenkins/pull/1106 Change By: Vincent Latombe (31/Jan/14 3:45 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [windows-slaves] (JENKINS-21373) Unable to connect to Windows slave after upgrade to Jenkins ver. 1.547
Vincent Latombe resolved JENKINS-21373 as Fixed Unable to connect to Windows slave after upgrade to Jenkins ver. 1.547 Change By: Vincent Latombe (31/Jan/14 3:44 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] [windows-slaves] (JENKINS-21373) Unable to connect to Windows slave after upgrade to Jenkins ver. 1.547
SCM/JIRA link daemon commented on JENKINS-21373 Unable to connect to Windows slave after upgrade to Jenkins ver. 1.547 Code changed in jenkins User: Jesse Glick Path: changelog.html http://jenkins-ci.org/commit/jenkins/f9810b5131e3024930df233a02a356e3cb5b5f84 Log: JENKINS-21373 Noting. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [ec2] (JENKINS-21601) ec2 plugin - ssh connection timeouts if an Init Script is used
Chris Fortier created JENKINS-21601 ec2 plugin - ssh connection timeouts if an Init Script is used Issue Type: Bug Affects Versions: current Assignee: Chris Fortier Components: ec2 Created: 31/Jan/14 3:52 PM Description: If an Init Script is passed there are three sessions opened but only one of them is closed. At the end of the init script processing, the initial sessions timeout and the ssh sessions timeout. Launching slave agent: java -jar /tmp/slave.jar ===JENKINS REMOTING CAPACITY===Slave.jar version: 2.33 This is a Unix slave Evacuated stdout Slave successfully connected and online ERROR: Connection terminated java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2596) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1317) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:369) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:71) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) Environment: CentOS 6.4 Project: Jenkins Priority: Minor Reporter: Chris Fortier This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
François Dumont commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 Still not assigned, with so many people who want 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] [core] (JENKINS-21474) Jenkins crash on startup after upgrade from 1.546 to 1.548
Jesse Glick assigned JENKINS-21474 to Oliver Gondža Jenkins crash on startup after upgrade from 1.546 to 1.548 https://github.com/jenkinsci/jenkins/pull/741 Change By: Jesse Glick (31/Jan/14 3:57 PM) Assignee: KohsukeKawaguchi OliverGondža This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Egor Sukhanov commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 +1, waiting This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [jobconfighistory] (JENKINS-19170) Display all changes within a folder
Stefan Brausch commented on JENKINS-19170 Display all changes within a folder okay, thanks for this information This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-10468) Build Queue does not show the executor a build is waiting for
SCM/JIRA link daemon commented on JENKINS-10468 Build Queue does not show the executor a build is waiting for Code changed in jenkins User: Fred G Path: core/src/main/java/hudson/model/queue/CauseOfBlockage.java http://jenkins-ci.org/commit/jenkins/b89b44816311b933be56b1452820ea71b7127b22 Log: FIXED JENKINS-10468 - Build Queue does not show the executor a build is waiting for This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Jeff Behnke commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 +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/groups/opt_out.
[JIRA] [ghprb] (JENKINS-18737) ghprb - Check pull requests for specific branch only
Ray Sennewald commented on JENKINS-18737 ghprb - Check pull requests for specific branch only Worked with David on this, and we refactored the code. We closed the original pull request and have a new one available for it here: https://github.com/janinko/ghprb/pull/115. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21448) Report number of all jobs as part of usage statistics
Jesse Glick updated JENKINS-21448 Report number of all jobs as part of usage statistics Change By: Jesse Glick (31/Jan/14 4:35 PM) Labels: folders This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [matrix] (JENKINS-21602) Option to exclude off-line Slaves in Individual Slaves
Frank Merrow created JENKINS-21602 Option to exclude off-line Slaves in Individual Slaves Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: matrix Created: 31/Jan/14 4:38 PM Description: I would like to use a Matrix Job to release software to Jenkins Master and Slaves. Unfortunately, if any slave is off-line the job never finishes which means it will not run again (at the next release) without manual intervention. I would either like an "on-line slaves only" option, or for something like this to work as a combination filter: Hudson.instance.getComputer(label == "master"?"":label).getNode().getChannel() != null The above scriptlet works fine in scriptler, but I cannot seem to get it running (with or without an import) in the combination filter. The combination box will not properly process "import" and without the import "Hudson" is undefined. Environment: All Project: Jenkins Priority: Major Reporter: Frank Merrow This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20892) /{view,computer,user}/*/builds /job/*/buildTimeTrend block HTTP response on build record loading
Jesse Glick
commented on JENKINS-20892
/{view,computer,user}/*/builds /job/*/buildTimeTrend block HTTP response on build record loading
@domi if that is a regression. The issue does not say.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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.
