[JIRA] [build-pipeline] (JENKINS-18720) Build Pipeline plugin stopped working after upgrade to 1.522
Dinesh S commented on JENKINS-18720 Build Pipeline plugin stopped working after upgrade to 1.522 I updated the Pipeline plugin from 1.3.4.1 to 1.3.5 as well as teh Artifactory plugin and it seems to have resolved the build plugin issue. However i still see the following error in the logs. Jul 12, 2013 3:00:31 AM jenkins.InitReactorRunner$1 onAttained INFO: Prepared all plugins Jul 12, 2013 3:00:38 AM hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 error WARNING: Failed to instantiate optional component org.jfrog.hudson.ivy.ArtifactoryIvyConfigurator$DescriptorImpl; skipping Jul 12, 2013 3:00:39 AM jenkins.InitReactorRunner$1 onAttained INFO: Started all plugins This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-18721) ListView asks for all jobs too often
stanislav bashkirtsev created JENKINS-18721 ListView asks for all jobs too often Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 12/Jul/13 7:47 AM Description: ListView has problems with performance because it asks for all jobs while figuring out what jobs it contains. The reason we should care - it always asks for ACL. In our project we use RBAC plugin, we also have 3000 jobs in Jenkins which together kills the performance. Details: ListView#202 here it asks for all items to find those that match the regexp pattern ListView#171 again asks for all jobs just to get Items from Job Names ListView#181 and again asks for all jobs for the sake of filtering. Solution: ListView should get the list of items once and reuse it in all subsequent situation. Instead of building a list of Job Names it's better to build a list of Items in ListView#202 Fix Versions: current Project: Jenkins Labels: performance Priority: Critical Reporter: stanislav bashkirtsev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [msbuild] (JENKINS-18560) Extra " when forming cmd line arguments for parameters containing a space
Thomas Fields commented on JENKINS-18560 Extra " when forming cmd line arguments for parameters containing a space Cmd line on version 1.17 is: cmd.exe /C C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe /nr:false /maxcpucount:8 /verbosity:normal "/p:Configuration=Debug;Platform=Any CPU" /p:VisualStudioVersion=10.0 /p:CONFIG=Debug;VS=10.0;TARGET=Any+CPU;branch=Live Tools\Source\AssetAnalyzer\AssetAnalyzer.sln && exit %%ERRORLEVEL%% from C:\JCI\jobs\AssetAnalyzer-Live\workspace\CONFIG\Debug\TARGET\Any CPU\VS\10.0 I just realised that my suggestion of "/p:Configuration="Debug";Platform="Any CPU" will have quote mismatch so not sure what the fix is here. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [ssh-slaves] (JENKINS-18706) ssh-saves 0.27 and jenknis 1.522 not working: java.io.IOException: Unexpected termination of the channel
Thomas Lallart commented on JENKINS-18706 ssh-saves 0.27 and jenknis 1.522 not working: java.io.IOException: Unexpected termination of the channel Just adding some infos for same problem that I previously posted in https://issues.jenkins-ci.org/browse/JENKINS-13869 Hi I have 3 jenkins Slaves connecting with SSHSlaveAgent and private key : 2 RedHat 6 Linux nodes and 1 Solaris X node. Updating Jenkins from 1.514 to 1.522, I got now on my Solaris node : 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:2571) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1315) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:369) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:72) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) Connecting directly from command line with ssh user@host works well. My Linux nodes are connected but Jenkins say that clock are not synchronized, 1 day and 1 hour late. However, I'm pretty sure that my master and this nodes have the same time synchronized by a ntp server. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nodelabelparameter] (JENKINS-18722) starting build redirects to blank URL
hbockelmann created JENKINS-18722 starting build redirects to blank URL Issue Type: Bug Assignee: domi Components: nodelabelparameter Created: 12/Jul/13 8:25 AM Description: I have a simple parametrized job using node parameter to determine on which slave it should run. Whenever I start a job manually choosing a node and clicking the build button, my browser gets redirected to the URL "https://myserver.domain/jenkins/job/test/build?delay=0sec" which is a blank page. To start further jobs and/or work with jenkins I have to change the URL manually. I cannot believe that this is an intended behaviour?! Environment: CentOS release 5.9, Jenkins version 1.519, NodeLabel Parameter plugin 1.4 Project: Jenkins Labels: nodelabelparameter Priority: Minor Reporter: hbockelmann This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-18723) Relative links to job are built very slowly
stanislav bashkirtsev created JENKINS-18723 Relative links to job are built very slowly Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 12/Jul/13 8:32 AM Description: If a View contains 10 jobs, while building relative links Jenkins would build this view 10 times iterating over all Jenkins jobs. This is an extremely inefficient way of building links. Details: projectView.jelly#L84 this one asks Functions to build a relative link. Functions.java#L951 it obtains all items of the view which builds it and accesses Security to iterate through all the jobs in Jenkins. Note, that this code was added 2 months ago. Either there should be a different way of building relative path or a different way for building view items. Fix Versions: current Project: Jenkins Priority: Major Reporter: stanislav bashkirtsev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-18721) ListView asks for all jobs too often
stanislav bashkirtsev updated JENKINS-18721 ListView asks for all jobs too often Change By: stanislav bashkirtsev (12/Jul/13 9:03 AM) Priority: Critical Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18723) Relative links to job are built very slowly
stanislav bashkirtsev updated JENKINS-18723 Relative links to job are built very slowly Change By: stanislav bashkirtsev (12/Jul/13 9:02 AM) Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [buildresulttrigger] (JENKINS-18667) NullPointerException when saving job config
Florian Doersch commented on JENKINS-18667 NullPointerException when saving job config same here This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [job-dsl-plugin] (JENKINS-18492) Inception: Create DSL build step to add DSL Job execution as step
Jens Hausherr
edited a comment on JENKINS-18492
Inception: Create DSL build step to add DSL Job execution as step
An example might be useful.
Currently I have around 50 projects in our internal github, most are using git-flow for managing releases and features. That means that I have two core jobs for branches (develop and master) that change rather infrequently.
For each project there are a number of short-lived branches for features, releases and hotfixes (branch names: feature/, release/, hotfix/*) where I would like to check and (re-)create Jobs for each branch more frequently than for the main ones.
So here is my current solution (the important parts):
Unable to find source-code formatter for language: groovy. Available languages are: _javascript_, sql, xhtml, actionscript, none, html, xml, javarepositories.each { repo ->
/* get branches from github */
branches.each {
def branchName = it.name
switch (branchName) {
case productionBranchName:
case developmentBranchName:
job {
/* define a job for each master(production) and develop (development) branch
}
break
default:
/* skip other branches now */
break
}
}
/* generate monitor job per repository */
job {
triggers {
cron 'H/5 * * * *'
}
steps {
dsl {
removeAction('DELETE')
//text readFileFromWorkspace('templates.monitor-job.groovy')
text """/* Job for monitoring feature/release and other branches. Generated code, DO NOT EDIT!! */
/* iterae over branches */
branches.each {
def branchName = it.name
/* Skip all non-feature/release/hotfix branches */
if (branchName =~ /(feature|release|hotfix)\\/.+/) {
job {
name "${baseJobName}-\${branchName.replaceAll('/', '-')}"
/* use develop job as template */
using "${baseJobName}-${developmentBranchName}"
/* build steps */
}
}
}
"""
}
}
}
}
Basically I install the two main jobs that only change when I update the initial DSL specification. The monitor job runs on a rather frequent cron schedule to catch all short-lived branches and creates jobs for feature branches based on the current development-Branch job definition.
As the DSL keeps track both of the generated jobs and of the templates that have been used for jobs I get an automatic cascade that updates my feature branches whenever I roll out changes to the development branch. And jobs for feature branches that no longer exist get deleted automatically.
Integrating the DSL definition as String enables to generate a customized job template for each repository (necessary as there is a different template job for each repository)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [job-dsl-plugin] (JENKINS-18492) Inception: Create DSL build step to add DSL Job execution as step
Jens Hausherr
commented on JENKINS-18492
Inception: Create DSL build step to add DSL Job execution as step
An example might be useful.
Currently I have around 50 projects in our internal github, most are using git-flow for managing releases and features. That means that I have two core jobs for branches (develop and master) that change rather infrequently.
For each project there are a number of short-lived branches for features, releases and hotfixes (branch names: feature/, release/, hotfix/*) where I would like to check and (re-)create Jobs for each branch more frequently than for the main ones.
So here is my current solution (the important parts):
Unable to find source-code formatter for language: groovy. Available languages are: _javascript_, sql, xhtml, actionscript, none, html, xml, javarepositories.each { repo ->
/* get branches from github */
branches.each {
def branchName = it.name
switch (branchName) {
case productionBranchName:
case developmentBranchName:
job {
/* define a job for each master(production) and develop (development) branch
}
break
default:
/* skip other branches now */
break
}
}
/* generate monitor job per repository */
job {
triggers {
cron 'H/5 * * * *'
}
steps {
dsl {
removeAction('DELETE')
//text readFileFromWorkspace('templates.monitor-job.groovy')
text """/* Job for monitoring feature/release and other branches. Generated code, DO NOT EDIT!! */
/* iterae over branches */
branches.each {
def branchName = it.name
/* Skip all non-feature/release/hotfix branches */
if (branchName =~ /(feature|release|hotfix)\\/.+/) {
job {
name "${baseJobName}-\${branchName.replaceAll('/', '-')}"
/* use develop job as template */
using "${baseJobName}-${developmentBranchName}"
scm {
github(ghproject, "origin/\${branchName}", 'ssh', 'source.xing.com')
}
}
}
}
"""
}
}
}
}
Basically I install the two main jobs that only change when I update the initial DSL specification. The monitor job runs on a rather frequent cron schedule to catch all short-lived branches and creates jobs for feature branches based on the current development-Branch job definition.
As the DSL keeps track both of the generated jobs and of the templates that have been used for jobs I get an automatic cascade that updates my feature branches whenever I roll out changes to the development branch. And jobs for feature branches that no longer exist get deleted automatically.
Integrating the DSL definition as String enables to generate a customized job template for each repository (necessary as there is a different template job for each repository)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-18725) Builds are failing after upgrade to 1.522
Dinesh S created JENKINS-18725 Builds are failing after upgrade to 1.522 Issue Type: Bug Assignee: Unassigned Components: maven Created: 12/Jul/13 9:32 AM Description: All my maven builds are failing after i upgraded to 1.522 with the error "Remote call on Channel to Maven failed.. below is the Stacktrace [DealEngineNG] $ /export/opt/jdk/1.6.0_20/bin/java -cp /var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.3.jar:/var/tmp/3rdparty/maven-3.0.4/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /var/tmp/3rdparty/maven-3.0.4 /var/cache/jenkins/war/WEB-INF/lib/remoting-2.28.jar /var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.3.jar 50937 <===[JENKINS REMOTING CAPACITY]===>channel started channel stopped ERROR: Failed to parse POMs java.io.IOException: Remote call on Channel to Maven [/export/opt/jdk/1.6.0_20/bin/java, -cp, /var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.3.jar:/var/tmp/3rdparty/maven-3.0.4/boot/plexus-classworlds-2.4.jar, org.jvnet.hudson.maven3.agent.Maven3Main, /var/tmp/3rdparty/maven-3.0.4, /var/cache/jenkins/war/WEB-INF/lib/remoting-2.28.jar, /var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.3.jar, 50937] failed at hudson.remoting.Channel.call(Channel.java:722) at hudson.maven.ProcessCache$MavenProcess.call(ProcessCache.java:156) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:586) at hudson.model.Run.execute(Run.java:1593) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:491) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:247) Caused by: java.lang.UnsatisfiedLinkError: /export/opt/jdk/1.6.0_20/jre/lib/amd64/xawt/libmawt.so: libXtst.so.6: cannot open shared object file: No such file or directory at java.lang.ClassLoader$NativeLibrary.load(Native Method) at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1803) at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1699) at java.lang.Runtime.load0(Runtime.java:770) at java.lang.System.load(System.java:1003) at java.lang.ClassLoader$NativeLibrary.load(Native Method) at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1803) at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1720) at java.lang.Runtime.loadLibrary0(Runtime.java:823) at java.lang.System.loadLibrary(System.java:1028) at sun.security.action.LoadLibraryAction.run(LoadLibraryAction.java:50) at java.security.AccessController.doPrivileged(Native Method) at java.awt.Toolkit.loadLibraries(Toolkit.java:1592) at java.awt.Toolkit.(Toolkit.java:1614) at java.awt.Color.(Color.java:263) at hudson.util.ColorPalette.(ColorPalette.java:39) at hudson.model.BallColor.(BallColor.java:56) at hudson.model.Result.(Result.java:51) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:169) at $Proxy7.(Unknown Source) at sun.reflect.GeneratedSerializationConstructorAccessor40.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at java.io.ObjectStreamClass.newInstance(ObjectStreamClass.java:924) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1737) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1947) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1871) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351) at java.util.HashMap.readObject(HashMap.java:1030) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method
[JIRA] [dashboard-view] (JENKINS-18726) UI: "Build scheduled" tooltip covers next sechedule build button
Steve Sutton created JENKINS-18726 UI: "Build scheduled" tooltip covers next sechedule build button Issue Type: Bug Assignee: Peter Hayes Components: dashboard-view Created: 12/Jul/13 9:34 AM Description: When clicking on the "schedule build" button in the dashboard, a tooltip "build scheduled" appears. This tooltip covers the next "schedule build" button, so I cannot schedule multiple builds in succession without waiting for the tooltip to disappear . very frustrating when I have deadlines causing me massive amounts of stress as it is.. Environment: debian squeeze Project: Jenkins Priority: Minor Reporter: Steve Sutton This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [build-pipeline] (JENKINS-18720) Build Pipeline plugin stopped working after upgrade to 1.522
Dinesh S closed JENKINS-18720 as Fixed Build Pipeline plugin stopped working after upgrade to 1.522 Change By: Dinesh S (12/Jul/13 9:46 AM) Status: Open Closed 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] [maven] (JENKINS-18725) Builds are failing after upgrade to 1.522
Dinesh S commented on JENKINS-18725 Builds are failing after upgrade to 1.522 Also the build is specifically happening on the master and not on any slaves. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tap] (JENKINS-18703) TAP Plugin Table of Contents
Ralph Bolton updated JENKINS-18703 TAP Plugin Table of Contents Change By: Ralph Bolton (12/Jul/13 10:15 AM) Attachment: jenkins-tap-table-of-contents-mock-up.pdf This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [tap] (JENKINS-18703) TAP Plugin Table of Contents
Ralph Bolton updated JENKINS-18703 TAP Plugin Table of Contents Change By: Ralph Bolton (12/Jul/13 10:18 AM) Attachment: jenkins-tap-table-of-contents-mock-up.pdf This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [cli] (JENKINS-15784) Groovy-Scripts with CLI are not working with Crowd 2 Plugin
Thomas S. resolved JENKINS-15784 as Cannot Reproduce Groovy-Scripts with CLI are not working with Crowd 2 Plugin Cannot Reproduce Error in 1.509.2 LTS. So for me this error is gone. Change By: Thomas S. (12/Jul/13 10:25 AM) Status: Open Resolved Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tap] (JENKINS-18703) TAP Plugin Table of Contents
Ralph Bolton commented on JENKINS-18703 TAP Plugin Table of Contents Hi Bruno, That's great news - thanks for looking at this! I've attached a mock-up (sorry, I attached an old one and a newer, more correct one, but can't delete the old one). In short, I'd like some sort of "table of contents" (TOC) at the top of the page (before any TAP tables) that lists the various files that have been processed. Even just a bullet-list would be sufficient (as shown in my mock-up). I propose that the names of the files be hyperlinks to the tables below (eg. "part1.tap" in the TOC hyperlinks to an anchor tag on the "File: part1.tap" text ahead of the table of TAP output for that file). In my mock-up, each entry in the table of contents has summary information about the number of tests that have passed/failed etc. This information is optional, but adds some value to the table (and invites the TOC becoming an actual table, although this also is optional). It's up to you, but I'd suggest maybe making the display of table of contents a "tick box" option. The reason I say this is that we have a number of builds which only have one TAP file in them - a table of contents for such a build is confusing and unnecessary, so I imagine we'd want to turn off the TOC for such a build. Another possibility would be to suppress the TOC if it only has one entry in it, although again, this is optional. Honestly, anything you want to do would be great - we have a build with nearly 4000 tests over 20 files - making that page a bit easier to use would be super-cool. Thanks again - really appreciate it. ...Ralph This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [github] (JENKINS-18710) Selected "Let Jenkins auto-manage hook URLs", but never adds webhook to enterprise github
Nathan McDonald commented on JENKINS-18710 Selected "Let Jenkins auto-manage hook URLs", but never adds webhook to enterprise github Patched the plugin and removed the outer if condition so same code runs for our enterprise github. This seems to work for us and the hooks get added to github enterprise. Still not sure what the intended purpose of this if clause was, git history shows it was added ages ago when support for github enterprise was first being added, which would seem to suggest hooks have never been auto added for enterprise github instances... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-18725) Builds are failing after upgrade to 1.522
sogabe commented on JENKINS-18725 Builds are failing after upgrade to 1.522 Caused by: java.lang.UnsatisfiedLinkError: /export/opt/jdk/1.6.0_20/jre/lib/amd64/xawt/libmawt.so: libXtst.so.6: cannot open shared object file: No such file or directory libXtst.so.6 seems to be broken. check it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-18725) Builds are failing after upgrade to 1.522
Dinesh S commented on JENKINS-18725 Builds are failing after upgrade to 1.522 None of these builds were failing so far till I upgraded the jenkins version. so i am wondering why this error. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [github] (JENKINS-18710) Selected "Let Jenkins auto-manage hook URLs", but never adds webhook to enterprise github
Nathan McDonald commented on JENKINS-18710 Selected "Let Jenkins auto-manage hook URLs", but never adds webhook to enterprise github Pull request for fix we're using: https://github.com/jenkinsci/github-plugin/pull/31 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [cpptest] (JENKINS-18727) The cppTest 9.5 xml output doesn't match the current parser rule
Adrien Lecharpentier created JENKINS-18727 The cppTest 9.5 xml output doesn't match the current parser rule Issue Type: Bug Assignee: Gregory Boissinot Components: cpptest Created: 12/Jul/13 12:49 PM Description: The cppTest framework has changed its output format. The current parser doesn't correctly interpret the content. Environment: jenkins 1.410, cpptest-plugin 0.9 Project: Jenkins Priority: Major Reporter: Adrien Lecharpentier This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [configurationslicing] (JENKINS-18554) NPE in Maven Version slicer in 1.37
Jacob Robertson commented on JENKINS-18554 NPE in Maven Version slicer in 1.37 I've looked at this, and it looks pretty clear that the code changes made by Nicolas De Loof from CloudBees causes this. The plugin wasn't designed to handle "getAllItems", and that code change was made without enough testing. I have assigned the ticket to him. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [configurationslicing] (JENKINS-18455) all modules of all maven projects are listed separately
Jacob Robertson commented on JENKINS-18455 all modules of all maven projects are listed separately I've looked at this, and it looks pretty clear that the code changes made by Nicolas De Loof from CloudBees causes this. The plugin wasn't designed to handle "getAllItems", and that code change was made without enough testing. I have assigned the ticket to him. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [cpptest] (JENKINS-18727) The cppTest 9.5 xml output doesn't match the current parser rule
Adrien Lecharpentier updated JENKINS-18727 The cppTest 9.5 xml output doesn't match the current parser rule Change By: Adrien Lecharpentier (12/Jul/13 12:50 PM) Issue Type: Bug Improvement This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-18728) FATAL exception in hudson.model.AbstractBuild.getPreviousBuild at the end of matrix parent job
masarie...@gmail.com M. created JENKINS-18728 FATAL exception in hudson.model.AbstractBuild.getPreviousBuild at the end of matrix parent job Issue Type: Bug Affects Versions: current Assignee: Alex Earl Components: email-ext Created: 12/Jul/13 1:04 PM Description: After upgrading from 2.25 to 2.30.2 on Jenkins 1.480.3, every matrix project throws the following exception at the end of the matrix parent job. I have the "Trigger only for parent job" option enabled. FATAL: hudson.model.AbstractBuild.getPreviousBuild()Lhudson/model/AbstractBuild; java.lang.NoSuchMethodError: hudson.model.AbstractBuild.getPreviousBuild()Lhudson/model/AbstractBuild; at hudson.plugins.emailext.plugins.trigger.FixedTrigger.trigger(FixedTrigger.java:21) at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:282) at hudson.plugins.emailext.ExtendedEmailPublisher.access$100(ExtendedEmailPublisher.java:82) at hudson.plugins.emailext.ExtendedEmailPublisher$1.endBuild(ExtendedEmailPublisher.java:800) at hudson.matrix.MatrixBuild$MatrixBuildExecution.post2(MatrixBuild.java:387) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:640) at hudson.model.Run.execute(Run.java:1527) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:289) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) at hudson.model.OneOffExecutor.run(OneOffExecutor.java:66) Project: Jenkins Priority: Blocker Reporter: masarie...@gmail.com 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] [jacoco] (JENKINS-16786) Please make the "N/A" white, not black. :-)
Jason Faas commented on JENKINS-16786 Please make the "N/A" white, not black. :-) Another reason to move N/A to white is to differentiate it from jobs with < 5% code coverage. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-18671) Clock Difference broken on Manage Nodes page
dogfood commented on JENKINS-18671 Clock Difference broken on Manage Nodes page Integrated in jenkins_main_trunk #2706 [FIXED JENKINS-18671] Clock Difference broken on Manage Nodes page (Revision da9c2c55c1962dc805a3bc74f7950379371dab98) Result = SUCCESS richm : da9c2c55c1962dc805a3bc74f7950379371dab98 Files : changelog.html core/src/main/java/hudson/model/Slave.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-18728) FATAL exception in hudson.model.AbstractBuild.getPreviousBuild at the end of matrix parent job
Alessio M. closed JENKINS-18728 as Not A Defect FATAL exception in hudson.model.AbstractBuild.getPreviousBuild at the end of matrix parent job I just realized the latest versions of the plug-in are meant for Jenkins 1.509 or newer Change By: Alessio M. (12/Jul/13 1:34 PM) Status: Open Closed Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tap] (JENKINS-18703) TAP Plugin Table of Contents
Bruno P. Kinoshita commented on JENKINS-18703 TAP Plugin Table of Contents Thanks for the mock up Ralph! 4000 tests? Wow, there's another issue regarding performance/scalability of the plug-in. I'll try to include that one in this release too :o) Probably your job/builds will load faster after that is fixed. Will take a look with calm on your mock up during the weekend. Thanks again! /B This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [msbuild] (JENKINS-17876) MSBuild Command Line Arguments quotes being stripped...not 5552
damian dixon commented on JENKINS-17876 MSBuild Command Line Arguments quotes being stripped...not 5552 It looks like this fix has introduced a problem with the following command line: /p:"VCBuildAdditionalOptions=/M20" /p:Configuration="Debug for Release" /p:platform="Win32" /v:n This ends up thus: cmd.exe /C C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\msbuild.exe /p:"VCBuildAdditionalOptions=/M20" '/p:Configuration="Debug for Release"' /p:platform="Win32" /v:n C:\hudson\config\jobs\MapLink-Checkout\workspace\SDK\ThirdParty\Xalan-C\Xalan-Cx.sln && exit Giving the following error: MSBUILD : error MSB1008: Only one project can be specified. Switch: Release This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-18728) FATAL exception in hudson.model.AbstractBuild.getPreviousBuild at the end of matrix parent job
Alex Earl commented on JENKINS-18728 FATAL exception in hudson.model.AbstractBuild.getPreviousBuild at the end of matrix parent job That's correct, sorry if there was any confusion. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [tap] (JENKINS-18703) TAP Plugin Table of Contents
Ralph Bolton commented on JENKINS-18703 TAP Plugin Table of Contents Hi Bruno, Yeah, we're running tests against our DNS domains; for each domain there's probably a dozen tests or more, and we've got quite a few domains, especially when you include the subdomains we care about too. I've sent you a tar file with some example .tap files in it (to your Yahoo email address). That may help you see what we're seeing in this particular Jenkins build Cheers, ...Ralph This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [ssh-credentials] (JENKINS-18729) Verify passphrase in form validation
Jesse Glick created JENKINS-18729 Verify passphrase in form validation Issue Type: Improvement Assignee: stephenconnolly Components: ssh-credentials Created: 12/Jul/13 3:17 PM Description: If for Private Key you have specified From the Jenkins master ~/.ssh and you enter a Passphrase, there should be form validation checking whether the passphrase is valid. Project: Jenkins Labels: usability Priority: Minor 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] [maven] (JENKINS-18459) IOException: No Such File
Fabrice Bacchella commented on JENKINS-18459 IOException: No Such File And so ? I don't see the relation to bug 15120 and it's no use to solve the problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [promoted-builds] (JENKINS-8963) Remote API to create/delete/modify promotions
eguess74 commented on JENKINS-8963 Remote API to create/delete/modify promotions It is very weird to me that promoted builds plugin has separate configuration file to begin with. If it wouldn't - there would be no problem at all. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [buildresulttrigger] (JENKINS-18716) build is triggering to early
Marcus Mosttler commented on JENKINS-18716 build is triggering to early We have daily builds that running every morning (as well as on demand during the day). We also have a set of deploy jobs that deploy designated builds to our test environments. The deploy jobs are triggered on the successful completion of the build it is configured to watch (the build that currently is to be deployed to that test environment). Looking at the builds and deploys this morning I saw that it once again triggered too early causing the previous builds to be deployed. I cycled the Jenkins service hoping if the memory was cleared that maybe it would start working like it did originally. After restarting the service a number of deploy jobs were triggered for some reason and deployed older builds that have already been successfully run in the past. Not sure why it decided to trigger the jobs after a restart. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [thinBackup] (JENKINS-18730) Allow triggering of backups from CLI
kevin ran created JENKINS-18730 Allow triggering of backups from CLI Issue Type: Improvement Assignee: Thomas Fürer Components: thinBackup Created: 12/Jul/13 4:15 PM Description: It would be nice if I could invoke a restore from shell / BASH Project: Jenkins Priority: Major Reporter: kevin ran This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-8963) Remote API to create/delete/modify promotions
Jesse Glick commented on JENKINS-8963 Remote API to create/delete/modify promotions It is not an arbitrarily separate configuration file; it is done this way because each promotion process is actually a “job” to Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-17768) Repository URL with parameter triggers failure of the field checker
Greg Hansen commented on JENKINS-17768 Repository URL with parameter triggers failure of the field checker This is similar to 18714 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17768) Repository URL with parameter triggers failure of the field checker
Greg Hansen edited a comment on JENKINS-17768 Repository URL with parameter triggers failure of the field checker This is similar to JENKINS-18714 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-7291) Flyweight jobs and zero executors
recampbell reopened JENKINS-7291 Flyweight jobs and zero executors This doesn't resolve the issue for me. I see the master computer, but it is not used for the main matrix job. Instead, a cloud slave is provisioned. Steps to repro: 1. Create a matrix job with a single configuration, no labels 2. Ensure that Jenkins.numExecutors = 0 3. Ensure that a cloud plugin can provision slaves 4. Run the matrix job The matrix job won't run on the master, but will result in a slave being provisioned. Change By: recampbell (12/Jul/13 5:04 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] [nodelabelparameter] (JENKINS-18722) starting build redirects to blank URL
domi resolved JENKINS-18722 as Duplicate starting build redirects to blank URL This is an issue in the core (JENKINS-18425) and resolved with version 1.521 Change By: domi (12/Jul/13 5: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] [core] (JENKINS-7291) Flyweight jobs and zero executors
Jesse Glick commented on JENKINS-7291 Flyweight jobs and zero executors @recampbell: you backported https://github.com/jenkinsci/jenkins/commit/a114c693bc61c564232e78c9fffb5de1ef946ea8, or are testing a 1.510+ build with the original fix, and still see the issue? And did you verify that it is the matrix run which waits for, and runs on, the cloud slave instead of master, as opposed to the matrix configuration run which naturally has to run on the cloud slave? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-7291) Flyweight jobs and zero executors
Jesse Glick edited a comment on JENKINS-7291 Flyweight jobs and zero executors @recampbell: you backported https://github.com/jenkinsci/jenkins/commit/a114c693bc61c564232e78c9fffb5de1ef946ea8, or are testing a 1.510+ build with the original fix, and still see the issue? And did you verify that it is the matrix run which waits for, and runs on, the cloud slave instead of master, as opposed to the matrix configuration run which naturally has to run on the cloud slave? (Does testFlyweightTasksWithoutMasterExecutors pass?) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [crowd] (JENKINS-18731) crowd authentication suddenly stopped working after chaning the domain of jenkins
ssbarnea created JENKINS-18731 crowd authentication suddenly stopped working after chaning the domain of jenkins Issue Type: Bug Assignee: rmangi Components: crowd, crowd2 Created: 12/Jul/13 5:39 PM Description: Crowd authentication worked perfectly until we moved jenkins to another domain. The "funny" part is the if I check the logs jenkins says that the user was authenticated but in fact the login button does nothing. Temporarly we switched back to LDAP authentication, which BTW worked without any problem. Clearly there is something that prefect crowd2 from saving the authentication. Environment: jenkins-1522 Project: Jenkins Priority: Major Reporter: ssbarnea This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [crowd] (JENKINS-18731) crowd authentication suddenly stopped working after chaning the domain of jenkins
ssbarnea
updated JENKINS-18731
crowd authentication suddenly stopped working after chaning the domain of jenkins
Change By:
ssbarnea
(12/Jul/13 5:43 PM)
Description:
Crowd authentication worked perfectly until we moved jenkins to another domain.The "funny" part is the if I check the logs jenkins says that the user was authenticated but in fact the login button does nothing.Temporarly we switched back to LDAP authentication, which BTW worked without any problem.Clearly there is something that prefect crowd2 from saving the authentication.
{code}https://crowd.domain.com/crowdjenkinspassjira-usersfalse60 {code}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [deploy] (JENKINS-11134) Hide the red x button to abort the build
Kohsuke Kawaguchi resolved JENKINS-11134 as Incomplete Hide the red x button to abort the build Can you elaborate bit more on what you mean? Does this have anything to do with the deploy plugin? Change By: Kohsuke Kawaguchi (12/Jul/13 6:04 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-7291) Flyweight jobs and zero executors
recampbell resolved JENKINS-7291 as Fixed Flyweight jobs and zero executors Sorry, my mistake in backporting. Change By: recampbell (12/Jul/13 6:17 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] [urltrigger] (JENKINS-18683) Jenkins 1.522 config changes cannot be saved
Stephen Tunney commented on JENKINS-18683 Jenkins 1.522 config changes cannot be saved Any movement on this? It is killing my jobs as well +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] [xcode] (JENKINS-18732) Xcode Plugin gets bundle identifier, except with a few odd characters at beginning and end, which sounds like an encoding issue, in Xcode 5.
Bob The Builder Can He Fix It? created JENKINS-18732 Xcode Plugin gets bundle identifier, except with a few odd characters at beginning and end, which sounds like an encoding issue, in Xcode 5. Issue Type: Bug Assignee: Unassigned Components: xcode Created: 12/Jul/13 8:02 PM Description: Log: Code Sign error: No matching provisioning profiles found: No provisioning profiles matching the bundle identifier “com.whatever.my.bundle.id.is” were found. Before Upgrading to xcode 5, the plugin worked fine. I can confirm that I have multiple provisioning profiles that match the bundle id, just without the weird characters. Environment: Mac OSX Mountain Lion. Xcode 5. Plugin Version 1.3.3 Project: Jenkins Labels: xcode Priority: Blocker Reporter: Bob The Builder Can He Fix It? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [tap] (JENKINS-18703) TAP Plugin Table of Contents
Bruno P. Kinoshita commented on JENKINS-18703 TAP Plugin Table of Contents Interesting! > Yeah, we're running tests against our DNS domains; Do you have any literature about it? I've never heard about testing DNS domains :o) 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] [urltrigger] (JENKINS-18683) Jenkins 1.522 config changes cannot be saved
kevin ran commented on JENKINS-18683 Jenkins 1.522 config changes cannot be saved Same problem here. +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] [email-ext] (JENKINS-18517) Content token reference help bubble evaluated multiple times on Job Configuration page
Mike Liu commented on JENKINS-18517 Content token reference help bubble evaluated multiple times on Job Configuration page Please kindly provide when this fix will be released (supposingly 2.31). We are suffering from the same issue reported here. Thank you very much This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [build-token-root] (JENKINS-18733) Null pointer exception when trying to use build-token-root
Josh Love created JENKINS-18733 Null pointer exception when trying to use build-token-root Issue Type: Bug Affects Versions: current Assignee: Jesse Glick Attachments: buildbytoken_20130712-1744_catalina.out Components: build-token-root Created: 12/Jul/13 9:45 PM Description: I am new to jenkins and trying to test the "trigger build remotely" feature for some of our jobs. Upon further research I found that I need to use this plugin in order to have "Anonymous" kick off the build. We are using LDAP authentication via Atlassian crowd for our regular users. After installing the plugin I created a simple job that only has an "execute shell" build step that has a simple "echo 'test succesful'" inside it. I use the url https://servername.domainname.com/ops-deploy/buildbyToken/build?jobname=joshtest/ This results in a nullpointer exception. I've verified that the anonymous user has read and build (just. I'm trying to access it via the following manner (the --insecure is to ignore the self signed certificate) curl -i --insecure 'https://servername.domainname.com/ops-deploy/buildByToken/build?jobname=joshtest' Environment: redhat linux 6, running under tomcat Fix Versions: current Project: Jenkins Priority: Minor Reporter: Josh Love This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [build-token-root] (JENKINS-18733) Null pointer exception when trying to use build-token-root
Josh Love updated JENKINS-18733 Null pointer exception when trying to use build-token-root Change By: Josh Love (12/Jul/13 9:46 PM) Description: I am new to jenkins and trying to test the "trigger build remotely" feature for some of our jobs. Upon further research I found that I need to use this plugin in order to have "Anonymous" kick off the build.We are using LDAP authentication via Atlassian crowd for our regular users.After installing the plugin I created a simple job that only has an "execute shell" build step that has a simple "echo 'test succesful'" inside it.I use the url https://servername.domainname.com/ops-deploy/buildbyToken/build?jobname=joshtest/This results in a nullpointer exception. I've verified that the anonymous user has read and build (just permissions .I'm trying to access it via the following manner (the --insecure is to ignore the self signed certificate)curl -i --insecure 'https://servername.domainname.com/ops-deploy/buildByToken/build?jobname=joshtest' This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-18734) BuildStepCompatibilityLayer.perform throw UnsupportedOperation when invoked using classes that subclass Build
Brendan Nolan
created JENKINS-18734
BuildStepCompatibilityLayer.perform throw UnsupportedOperation when invoked using classes that subclass Build
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
core
Created:
12/Jul/13 9:46 PM
Description:
The following code will throw an unsupported operation.
FreeStyleBuild mock = Mockito.mock(FreeStyleBuild.class,Mockito.CALLS_REAL_METHODS);
ArtifactArchiver artifactArchiver = new ArtifactArchiver("", "", true);
artifactArchiver.perform(mock, null, null);
I came across the issue when trying to call the ArtifactArchiver via the groovy plugin on a MatrixRun build.
The BuildStepCompatibilityLayer should check if the implementing BuildStep provides an implementation of the {perform(AbstractBuild build, Launcher launcher, BuildListener listener)}
Project:
Jenkins
Labels:
build
Priority:
Major
Reporter:
Brendan Nolan
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-18734) BuildStepCompatibilityLayer.perform throws UnsupportedOperation when invoked using classes that subclass Build
Brendan Nolan
updated JENKINS-18734
BuildStepCompatibilityLayer.perform throws UnsupportedOperation when invoked using classes that subclass Build
Change By:
Brendan Nolan
(12/Jul/13 9:53 PM)
Summary:
BuildStepCompatibilityLayer.perform
throw
throws
UnsupportedOperation when invoked using classes that subclass Build
Description:
The following code will throw an unsupported operation.{code}FreeStyleBuild mock = Mockito.mock(FreeStyleBuild.class,Mockito.CALLS_REAL_METHODS); ArtifactArchiver artifactArchiver = new ArtifactArchiver("", "", true);artifactArchiver.perform(mock, null, null);{code}I came across the issue when trying to call the ArtifactArchiver via the groovy plugin on a MatrixRun build. The BuildStepCompatibilityLayer should check if the implementing BuildStep provides an implementation of the {perform(AbstractBuild build, Launcher launcher, BuildListener listener)}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [build-token-root] (JENKINS-18733) Null pointer exception when trying to use build-token-root
Josh Love updated JENKINS-18733 Null pointer exception when trying to use build-token-root Change By: Josh Love (12/Jul/13 9:54 PM) Description: I am new to jenkins and trying to test the "trigger build remotely" feature for some of our jobs. Upon further research I found that I need to use this plugin in order to have "Anonymous" kick off the build.We are using LDAP authentication via Atlassian crowd for our regular users.After installing the plugin I created a simple job that only has an "execute shell" build step that has a simple "echo 'test succesful'" inside it.I use the url https://servername.domainname.com/ops-deploy/buildbyToken/build?jobname=joshtest / &token=test This results in a nullpointer exception. I've verified that the anonymous user has read and build permissions.I'm trying to access it via the following manner (the --insecure is to ignore the self signed certificate)curl -i --insecure 'https://servername.domainname.com/ops-deploy/buildByToken/build?jobname=joshtest &token=test ' This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [build-token-root] (JENKINS-18733) Null pointer exception when trying to use build-token-root
Josh Love resolved JENKINS-18733 as Fixed Null pointer exception when trying to use build-token-root it's just job - not jobname like I saw on some examples online it seems. Sorry! Change By: Josh Love (12/Jul/13 9:56 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] [build-flow] (JENKINS-18735) Make the parameter definitions available readily
Kohsuke Kawaguchi created JENKINS-18735 Make the parameter definitions available readily Issue Type: Bug Assignee: Nicolas De Loof Components: build-flow Created: 12/Jul/13 10:05 PM Description: Sometimes a build script wants to introspect parameter definitions of a job. Imagine you have a choice parameter that has A, B, and C as legal values, and want to write a flow script that executes all of them. Making this reflection-like information easily accessible from a flow script would be a win. Project: Jenkins Priority: Major Reporter: Kohsuke Kawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [build-flow] (JENKINS-18735) Make the parameter definitions available readily
Kohsuke Kawaguchi updated JENKINS-18735 Make the parameter definitions available readily Change By: Kohsuke Kawaguchi (12/Jul/13 10:05 PM) Issue Type: Bug New Feature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-18734) BuildStepCompatibilityLayer.perform throws UnsupportedOperation when invoked using classes that subclass Build
Brendan Nolan
updated JENKINS-18734
BuildStepCompatibilityLayer.perform throws UnsupportedOperation when invoked using classes that subclass Build
Change By:
Brendan Nolan
(12/Jul/13 10:13 PM)
Description:
The following code will throw an unsupported operation.{code}FreeStyleBuild mock = Mockito.mock(FreeStyleBuild.class,Mockito.CALLS_REAL_METHODS); ArtifactArchiver artifactArchiver = new ArtifactArchiver("", "", true);artifactArchiver.perform(mock, null, null);{code}I came across the issue when trying to call the ArtifactArchiver via the groovy plugin on a MatrixRun build. The BuildStepCompatibilityLayer should check if the implementing BuildStep provides an implementation of the {
{
perform(AbstractBuild build, Launcher launcher, BuildListener listener)}
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [pam-auth] (JENKINS-18736) PAM authertication over NIS server does not work
Petr Prochazka created JENKINS-18736 PAM authertication over NIS server does not work Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: pam-auth Created: 12/Jul/13 10:16 PM Description: We use NIS authentication to unix servers. I tried to configure Jenkins to authenticated via PAM plugin. I logon successful with local user, but if I try logon with user defined on NIS server, logon failed. Exception in catalina.out: 13.7.2013 0:09:04 hudson.security.AuthenticationProcessingFilter2 onUnsuccessfulAuthentication INFO: Login attempt failed org.acegisecurity.BadCredentialsException: pam_authenticate failed : Authentication failure; nested exception is org.jvnet.libpam.PAMException: pam_authenticate failed : Authentication failure at hudson.security.PAMSecurityRealm.authenticate(PAMSecurityRealm.java:78) at hudson.security.AbstractPasswordBasedSecurityRealm$Authenticator.retrieveUser(AbstractPasswordBasedSecurityRealm.java:136) at org.acegisecurity.providers.dao.AbstractUserDetailsAuthenticationProvider.authenticate(AbstractUserDetailsAuthenticationProvider.java:122) at org.acegisecurity.providers.ProviderManager.doAuthentication(ProviderManager.java:200) at org.acegisecurity.AbstractAuthenticationManager.authenticate(AbstractAuthenticationManager.java:47) at org.acegisecurity.ui.webapp.AuthenticationProcessingFilter.attemptAuthentication(AuthenticationProcessingFilter.java:74) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:252) 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.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:47) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:470) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:300) at org.apache.coyote.ajp.AjpAprProcessor.process(AjpAprProcessor.java:433)
[JIRA] [build-token-root] (JENKINS-18733) Null pointer exception when trying to use build-token-root
Jesse Glick resolved JENKINS-18733 as Not A Defect Null pointer exception when trying to use build-token-root Change By: Jesse Glick (12/Jul/13 10:25 PM) Status: Reopened Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-token-root] (JENKINS-18733) Null pointer exception when trying to use build-token-root
Jesse Glick reopened JENKINS-18733 Null pointer exception when trying to use build-token-root Change By: Jesse Glick (12/Jul/13 10:25 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] [core] (JENKINS-18734) BuildStepCompatibilityLayer.perform throws UnsupportedOperation when invoked using classes that subclass Build
Brendan Nolan commented on JENKINS-18734 BuildStepCompatibilityLayer.perform throws UnsupportedOperation when invoked using classes that subclass Build Added pull request - https://github.com/jenkinsci/jenkins/pull/847 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-18517) Content token reference help bubble evaluated multiple times on Job Configuration page
Alex Earl commented on JENKINS-18517 Content token reference help bubble evaluated multiple times on Job Configuration page I am trying to fix up a couple more bugs for 2.31. I hope to release early next week. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-18590) When you populate recipients on failure but disable failure emails, the address is used for first failure rather than the default list
Alex Earl commented on JENKINS-18590 When you populate recipients on failure but disable failure emails, the address is used for first failure rather than the default list I can't replicate this issue. Only the correct email addresses are added to the email if I have first failure and failure setup as you have them. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ghprb] (JENKINS-18737) ghprb - Check pull requests for specific branch only
Kevin Benton created JENKINS-18737 ghprb - Check pull requests for specific branch only Issue Type: Improvement Assignee: Honza Brázdil Components: ghprb Created: 13/Jul/13 1:08 AM Description: Currently, ghprb checks every pull request on a repository. I need a way to specify a specific branch since the "Branch Specifier" and "Refspec" option are used by ghprb. The pull requests are not grouped by branch in the refs directory, so there is no way to do it with a custom Refspec that I can see. The plugin already checks the branch here: https://github.com/jenkinsci/ghprb-plugin/blob/master/src/main/java/org/jenkinsci/plugins/ghprb/GhprbPullRequest.java#L38 It would make sense to have a check right after that line to see if there is a defined allowed branch and if it matches that. Project: Jenkins Priority: Major Reporter: Kevin Benton This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [gerrit-trigger] (JENKINS-15823) Make GerritCause a Subclass of SCMTriggerCause
rin_ne closed JENKINS-15823 as Fixed Make GerritCause a Subclass of SCMTriggerCause Seems already merged Change By: rin_ne (13/Jul/13 1:56 AM) Status: Open Closed 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] [gerrit-trigger] (JENKINS-15654) Trigger on reason provided so as to change behavior for change-merged
rin_ne commented on JENKINS-15654 Trigger on reason provided so as to change behavior for change-merged Seems such parameter has been provided since Gerrit Trigger 2.9.0 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-15264) 'Build Current Patches Only' clears entire queue
rin_ne closed JENKINS-15264 as Fixed 'Build Current Patches Only' clears entire queue Change By: rin_ne (13/Jul/13 2:27 AM) Status: Open Closed 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] [gerrit-trigger] (JENKINS-12690) JenkinsTrigger does not understand SSH Key with a password
rin_ne commented on JENKINS-12690 JenkinsTrigger does not understand SSH Key with a password Do you think that passphrase is used for key validation in authentication phase? No. It is used to generate signature. If privatekey requires passphrase, it would be used. But if not, it has never been used. So, If you set the path to privatekey file generated by step 4, your password would not be used in any authentication process. I think that current behavior about SSH you see is correct. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [gerrit-trigger] (JENKINS-7024) Gerrit comment: "Build Started nulljob/foo/1/"
rin_ne closed JENKINS-7024 as Won't Fix Gerrit comment: "Build Started nulljob/foo/1/" It is rare situation and workaround is here. so no problem if close. Change By: rin_ne (13/Jul/13 3:47 AM) Status: Open Closed Resolution: Won't Fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18715) scandir being triggered by FingerPrint.save
Hua Zhang commented on JENKINS-18715 scandir being triggered by FingerPrint.save The first test of this PR looks good. The fingerprinting was fast enough not giving me enough time to take a thread dump via GUI (next week I will be able to put this on field test). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [scm-sync-configuration] (JENKINS-18715) scandir being triggered by FingerPrint.save
Hua Zhang updated JENKINS-18715 scandir being triggered by FingerPrint.save Change By: Hua Zhang (13/Jul/13 6:55 AM) Environment: Jenkins 1.518 SCM Sync Configuration Plugin 0.0.7.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.
