[JIRA] [findbugs] (JENKINS-8558) FindBugs plugin should allow choice of "priority" vs. "rank"

[ullrich.haf...@gmail.com (JIRA)]

Ulli Hafner
 resolved  JENKINS-8558 as Fixed


FindBugs plugin should allow choice of "priority" vs. "rank"
















Please create a new feature issue in Jira rather than opening this already fixed one. 

I can provide there some more details on how to implement that. 





Change By:


Ulli Hafner
(13/Mar/14 6:49 AM)




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/d/optout.

[JIRA] [xcode] (JENKINS-12510) Custom xcodebuild arguments values are not persisted

[wharpr...@java.net (JIRA)]

wharpreet
 reopened  JENKINS-12510


Custom xcodebuild arguments values are not persisted
















Still facing this issue with 1.4.1
And checked the master branch in github, the changed made for 1.3.1 are still present.





Change By:


wharpreet
(13/Mar/14 6:08 AM)




Resolution:


Fixed





Status:


Resolved
Reopened



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-9775) Generic URL to access latest log for job

[o.v.nenas...@gmail.com (JIRA)]

Oleg Nenashev
 closed  JENKINS-9775 as Fixed


Generic URL to access latest log for job
















Yes, the issue was really outdated





Change By:


Oleg Nenashev
(13/Mar/14 4:40 AM)




Status:


Resolved
Closed





Assignee:


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/d/optout.

[JIRA] [subversion] (JENKINS-22167) subversion checkout failure

[fengqiao...@139.com (JIRA)]

qiao feng
 created  JENKINS-22167


subversion checkout failure















Issue Type:


Bug



Assignee:


Unassigned


Components:


subversion



Created:


13/Mar/14 3:57 AM



Description:


error log:
Started by user admin
[EnvInject] - Loading node environment variables.
Building in workspace /root/.jenkins/workspace/GAIA_Auto
FATAL: null
java.lang.UnsupportedOperationException
	at java.util.AbstractMap$SimpleImmutableEntry.setValue(AbstractMap.java:759)
	at hudson.EnvVars.resolve(EnvVars.java:340)
	at hudson.scm.SubversionSCM.getLocations(SubversionSCM.java:521)
	at hudson.scm.SubversionSCM.buildEnvVars(SubversionSCM.java:689)
	at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:938)
	at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:865)
	at hudson.model.AbstractProject.checkout(AbstractProject.java:1411)
	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:671)
	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:580)
	at hudson.model.Run.execute(Run.java:1670)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:231)




Due Date:


13/Mar/14 12:00 AM




Environment:


CentOS release 6.2 (Final)  



java version "1.7.0_21"

Java(TM) SE Runtime Environment (build 1.7.0_21-b11)



VisualSVN Server Manager

版本: 2.1.4



Jenkins ver. 1.552




Project:


Jenkins



Priority:


Major



Reporter:


qiao feng

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git] (JENKINS-21952) Git Plugin fails to resolve tags containing a slash since 2.0.1

[mark.earl.wa...@gmail.com (JIRA)]

Mark Waite
 commented on  JENKINS-21952


Git Plugin fails to resolve tags containing a slash since 2.0.1
















	Is the problem only on initial clone of the repository, or on later clones as well?
	When you browse the workspace, are the tags you're seeing in .git/refs/tags ?
	Can any of the tags in the repository be used as the "branch to build"?
	Is the behavior the same for command line git and JGit?





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git] (JENKINS-22144) Can't specify remote repository's branch to build

[mark.earl.wa...@gmail.com (JIRA)]

Mark Waite
 commented on  JENKINS-22144


Can't specify remote repository's branch to build















kompiro yes, there is a pending commit to complete the work. I had missed there another commit was needed, but the author of the commit detected the gap and has submitted a proposed change.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git] (JENKINS-22144) Can't specify remote repository's branch to build

[mark.earl.wa...@gmail.com (JIRA)]

Mark Waite
 commented on  JENKINS-22144


Can't specify remote repository's branch to build















kompiro yes, there is a pending commit to complete the work. I had missed there another commit was needed, but the author of the commit detected the gap and has submitted a proposed change.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git] (JENKINS-22144) Can't specify remote repository's branch to build

[komp...@java.net (JIRA)]

kompiro
 commented on  JENKINS-22144


Can't specify remote repository's branch to build















Thanks your comment.

I added "remotes/" to "Branch Specifier" like "remotes/aaa/master", Git Plugin 2.0.4 couldn't verify the format.
I updated Git Plugin to 2.0.5-SNAPSHOT and git-client-plugin 1.6.5-SNAPSHOT,
the plugin could verify the format. But it couldn't checkout the specified remote branch.

Does Jenkins Git plugin team work in progress about this 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/d/optout.

[JIRA] [core] (JENKINS-9775) Generic URL to access latest log for job

[k...@kohsuke.org (JIRA)]

Kohsuke Kawaguchi
 resolved  JENKINS-9775 as Fixed


Generic URL to access latest log for job
















It's called permalink and it exists. For example, https://ci.jenkins-ci.org/view/Jenkins%20core/job/jenkins_main_trunk/lastBuild/console





Change By:


Kohsuke Kawaguchi
(13/Mar/14 1:07 AM)




Status:


Open
Resolved





Assignee:


Kohsuke Kawaguchi





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [seleniumhq] (JENKINS-11317) SeleniumReport struckedat--INFO - Checking Resource aliases

[lavoie.rich...@gmail.com (JIRA)]

Richard Lavoie
 updated  JENKINS-11317


SeleniumReport struckedat--INFO - Checking Resource aliases
















Wrong component





Change By:


Richard Lavoie
(13/Mar/14 12:37 AM)




Component/s:


seleniumhq





Component/s:


selenium



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [unity3d-plugin] (JENKINS-22166) Exceptions thrown in builder script shown in console output

[skro...@yahoo.com (JIRA)]

Jeffery Chow
 created  JENKINS-22166


Exceptions thrown in builder script shown in console output















Issue Type:


New Feature



Assignee:


lacostej



Components:


unity3d-plugin



Created:


13/Mar/14 12:19 AM



Description:


I want to add a data validation step to our build process. Errors should throw an exception. However this exception isn't being displayed in Jenkin's console output (which would be handy).

As a quick test:
http://screencast.com/t/Fx9hE3WK
yields this in Jenkins:
http://screencast.com/t/7GGjMiqbOf (no "Testing")




Environment:


OS X 10.8.5




Project:


Jenkins



Priority:


Minor



Reporter:


Jeffery Chow

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [findbugs] (JENKINS-22165) Confusing label for the list of regex that include and exclude files

[elifar...@gmail.com (JIRA)]

Elifarley
 updated  JENKINS-22165


Confusing label for the list of regex that include and exclude files
















Change By:


Elifarley
(12/Mar/14 11:02 PM)




Attachment:


JENKINS-22165.patch



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [findbugs] (JENKINS-22165) Confusing label for the list of regex that include and exclude files

[elifar...@gmail.com (JIRA)]

Elifarley
 updated  JENKINS-22165


Confusing label for the list of regex that include and exclude files
















Change By:


Elifarley
(12/Mar/14 11:00 PM)




Issue Type:


Bug
Patch



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [findbugs] (JENKINS-22165) Confusing label for the list of regex that include and exclude files

[elifar...@gmail.com (JIRA)]

Elifarley
 created  JENKINS-22165


Confusing label for the list of regex that include and exclude files















Issue Type:


Bug



Assignee:


Ulli Hafner



Components:


findbugs



Created:


12/Mar/14 10:59 PM



Description:


The labels "Bugs to include" and "Bugs to ignore" seem to refer to bugs that can be included or ignored.

However, what they really specify is a list of regex that include or exclude files from being processed by findbugs, not bugs.


Here's my proposed patch:
—


diff --git a/plugin/src/main/resources/findbugs/filter.jelly b/plugin/src/main/resources/findbugs/filter.jelly
— a/plugin/src/main/resources/findbugs/filter.jelly
+++ b/plugin/src/main/resources/findbugs/filter.jelly
@@ -6,10 +6,10 @@
 
   xmlns:l="/lib/layout" xmlns:t="/lib/hudson" xmlns:f="/lib/form">


	
+
   
 
	
+
   
 







Project:


Jenkins



Priority:


Minor



Reporter:


Elifarley

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [ghprb] (JENKINS-22164) Unable to start build with trigger phrase

[jm.nie...@gmail.com (JIRA)]

Joshua Niehus
 created  JENKINS-22164


Unable to start build with trigger phrase















Issue Type:


Bug



Affects Versions:


current



Assignee:


Honza Brázdil



Components:


ghprb



Created:


12/Mar/14 10:21 PM



Description:


I have trigger phrase set and checked the "Only use trigger phrase for build triggering"

Trigger phrase: .buildme.
Only use trigger phrase for build triggering [x]

When I uncheck the "Only use trigger phrase for build triggering" checkbox then it works




Project:


Jenkins



Priority:


Major



Reporter:


Joshua Niehus

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [warnings] (JENKINS-22139) Maven warnings details are broken

[arca...@ivanov.biz (JIRA)]

Arcadiy Ivanov
 commented on  JENKINS-22139


Maven warnings details are broken















Thanks a lot! When is this fix getting into a released plugin version?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [xcode] (JENKINS-22163) Xcode plugin: Can't use environment variable

[wharpr...@java.net (JIRA)]

wharpreet
 created  JENKINS-22163


Xcode plugin: Can't use environment variable















Issue Type:


Bug



Assignee:


Unassigned


Components:


xcode



Created:


12/Mar/14 10:00 PM



Description:


Xcode plugin doesn't populate any variable passed through shell (just above it).
The Variables are passed using export. But in the xcode plugin they remain unchanged.
Example: /Users/haps/Downloads/${EMBED}
OR: PROVISIONING_PROFILE=${PROVISIONING_PROFILE}

The first one of from "Embedded Profile" field and later from "Custom xcodebuild arguments"

Also JENKINS-14375 says that this issue was solved in xcode version 1.3.1, but somehow seems to be reappeared in newer one.




Environment:


Jenkins Version: 1.544

Xcode Plugin Version: 1.4.1




Project:


Jenkins



Priority:


Major



Reporter:


wharpreet

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [sloccount] (JENKINS-21921) Lazy loaded report details are never released

[scm_issue_l...@java.net (JIRA)]

SCM/JIRA link daemon
 commented on  JENKINS-21921


Lazy loaded report details are never released















Code changed in jenkins
User: Michal Turek
Path:
 src/main/java/hudson/plugins/sloccount/SloccountResult.java
http://jenkins-ci.org/commit/sloccount-plugin/32b1fa89cbe28eeb0831db3d1f9dae39bb102a35
Log:
  JENKINS-21921 Lazy loaded report details are never released


	SloccountResult.lazyLoad() caches the data to a member variable. SloccountResult objects (all build.xml files) are loaded during Jenkins startup and never released so Java garbage collector has no chance to trash the lazy loaded details since the reference exists forever. This is kind of a memory leak.
	Lazy loading reads the data everytime and doesn't use any cache, saving of memory is now prefered to performace. It is not expected the user will show the details very often, so it should be ok.
	Explicit calls of convertLegacyData() replaced by readResolve() from Java serialization with the same effect.
	Report object made transient, null is always passed in SloccountPublisher while storing.































This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [sloccount] (JENKINS-22160) Fix findings from FindBugs static analysis

[mixaltu...@users.sf.net (JIRA)]

Michal Turek
 closed  JENKINS-22160 as Fixed


Fix findings from FindBugs static analysis
















Change By:


Michal Turek
(12/Mar/14 9:28 PM)




Status:


Resolved
Closed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [sloccount] (JENKINS-21921) Lazy loaded report details are never released

[mixaltu...@users.sf.net (JIRA)]

Michal Turek
 closed  JENKINS-21921 as Fixed


Lazy loaded report details are never released
















Change By:


Michal Turek
(12/Mar/14 9:27 PM)




Status:


Resolved
Closed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [sloccount] (JENKINS-21921) Lazy loaded report details are never released

[mixaltu...@users.sf.net (JIRA)]

Michal Turek
 updated  JENKINS-21921


Lazy loaded report details are never released
















Change By:


Michal Turek
(12/Mar/14 9:26 PM)




Issue Type:


Improvement
Bug



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [sloccount] (JENKINS-21921) Lazy loaded report details are never released

[mixaltu...@users.sf.net (JIRA)]

Michal Turek
 resolved  JENKINS-21921 as Fixed


Lazy loaded report details are never released
















Fixed, will be released in version 1.16.





Change By:


Michal Turek
(12/Mar/14 9:27 PM)




Status:


In Progress
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [sloccount] (JENKINS-22160) Fix findings from FindBugs static analysis

[scm_issue_l...@java.net (JIRA)]

SCM/JIRA link daemon
 commented on  JENKINS-22160


Fix findings from FindBugs static analysis















Code changed in jenkins
User: Michal Turek
Path:
 src/main/java/hudson/plugins/sloccount/SloccountDiff.java
 src/main/java/hudson/plugins/sloccount/SloccountPublisher.java
 src/main/java/hudson/plugins/sloccount/SloccountResult.java
 src/main/java/hudson/plugins/sloccount/model/SloccountParser.java
http://jenkins-ci.org/commit/sloccount-plugin/f336a1898e7699c22597abcf21861fd915fde943
Log:
  JENKINS-22160 Fix findings from FindBugs static analysis


	SloccountParser: Possible null pointer dereference.
	SloccountDiff: Class defines compareTo(SloccountDiff) and uses Object.equals().
	SloccountPublisher: Format string should use %n rather than \n.
	BreadCrumbResult: Implements same interface as superclass.































This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [sloccount] (JENKINS-22160) Fix findings from FindBugs static analysis

[mixaltu...@users.sf.net (JIRA)]

Michal Turek
 resolved  JENKINS-22160 as Fixed


Fix findings from FindBugs static analysis
















Fixed, will be released in version 1.16.





Change By:


Michal Turek
(12/Mar/14 9:27 PM)




Status:


In Progress
Resolved





Fix Version/s:


current





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [update-center] (JENKINS-22162) no GUI update option for snapshot builds of Jenkins

[st...@gpgtools.org (JIRA)]

steve steve
 created  JENKINS-22162


no GUI update option for snapshot builds of Jenkins















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


update-center



Created:


12/Mar/14 9:19 PM



Description:


Under Jenkins > Manage Jenkins there once was an update button to update to the latest snapshot build. Since several snapshot builds (not sure when exactly the button disappeared) there's no longer the option for that. E.g. 1.553 and 1.552 both did not show any update option despite 1.554 being available.

Would be great to have this back to ensure an easy update option for not so tech savvy users.




Environment:


OSX 10.8




Project:


Jenkins



Labels:


update
snapshot




Priority:


Major



Reporter:


steve steve

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-21881) Make X-Frame-Options configurable

[dan...@beckweb.net (JIRA)]

Daniel Beck
 commented on  JENKINS-21881


Make X-Frame-Options configurable















Is this really something that needs a solution in core, especially if there's already a plugin for it?

If so, why not provide an unrestricted "Raw HTML" markup formatter with core? It has legitimate use cases even though it's a bad idea for most installs – just like removing X-Frame-Options in core.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [gui] (JENKINS-22161) Selecting a default view type on the new view page

[nicolascoque...@gmail.com (JIRA)]

Nicolas Coquelet
 created  JENKINS-22161


Selecting a default view type on the new view page















Issue Type:


Improvement



Affects Versions:


current



Assignee:


Unassigned


Components:


gui



Created:


12/Mar/14 7:57 PM



Description:


If you try to create a new view, given a name and press Enter (no action on view type selector),
The form is sent, but without default view type 
resulting the error message : No view type is specified

Specially when we have only one view type, 
it could be interesting to propose a default selection.

It's up to you





Project:


Jenkins



Labels:


view




Priority:


Trivial



Reporter:


Nicolas Coquelet

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [sloccount] (JENKINS-21921) Lazy loaded report details are never released

[mixaltu...@users.sf.net (JIRA)]

Michal Turek
 started work on  JENKINS-21921


Lazy loaded report details are never released
















Change By:


Michal Turek
(12/Mar/14 7:51 PM)




Status:


Open
In Progress



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [sloccount] (JENKINS-22160) Fix findings from FindBugs static analysis

[mixaltu...@users.sf.net (JIRA)]

Michal Turek
 started work on  JENKINS-22160


Fix findings from FindBugs static analysis
















Change By:


Michal Turek
(12/Mar/14 7:45 PM)




Status:


Open
In Progress



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [sloccount] (JENKINS-22160) Fix findings from FindBugs static analysis

[mixaltu...@users.sf.net (JIRA)]

Michal Turek
 created  JENKINS-22160


Fix findings from FindBugs static analysis















Issue Type:


Bug



Affects Versions:


current



Assignee:


Michal Turek



Components:


sloccount



Created:


12/Mar/14 7:45 PM



Description:


FindBugs reports several issues present in the code.




Environment:


All




Project:


Jenkins



Priority:


Minor



Reporter:


Michal Turek

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [job-import] (JENKINS-22159) Cannot create jobs when running on Java 1.8

[atehran...@gmail.com (JIRA)]

Abraham Tehrani
 created  JENKINS-22159


Cannot create jobs when running on Java 1.8















Issue Type:


Bug



Affects Versions:


current



Assignee:


jieryn



Components:


job-import



Created:


12/Mar/14 7:43 PM



Description:


Download jenkins.war version 1.554
Run jenkins java -jar jenkins.war using java 1.8 (see version info above)
Note the exception at startup
Mar 12, 2014 12:39:11 PM hudson.model.ComputerSet 
WARNING: Failed to instantiate NodeMonitors
java.lang.ArrayIndexOutOfBoundsException: -1
	at com.thoughtworks.xstream.core.util.OrderRetainingMap.entrySet(OrderRetainingMap.java:77)
	at java.util.HashMap.putMapEntries(HashMap.java:511)
	at java.util.HashMap.putAll(HashMap.java:784)
	at com.thoughtworks.xstream.core.util.OrderRetainingMap.(OrderRetainingMap.java:36)
	at com.thoughtworks.xstream.converters.reflection.FieldDictionary.buildMap(FieldDictionary.java:135)
	at com.thoughtworks.xstream.converters.reflection.FieldDictionary.fieldsFor(FieldDictionary.java:76)
	at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:127)
	at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:149)
	at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:108)
	at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69)
	at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58)
	at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43)
	at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:88)
	at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.writeItem(AbstractCollectionConverter.java:64)
	at hudson.util.DescribableList$ConverterImpl.marshal(DescribableList.java:259)
	at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69)
	at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58)
	at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43)
	at com.thoughtworks.xstream.core.TreeMarshaller.start(TreeMarshaller.java:82)
	at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.marshal(AbstractTreeMarshallingStrategy.java:37)
	at com.thoughtworks.xstream.XStream.marshal(XStream.java:898)
	at com.thoughtworks.xstream.XStream.marshal(XStream.java:887)
	at com.thoughtworks.xstream.XStream.toXML(XStream.java:860)
	at hudson.XmlFile.write(XmlFile.java:178)
	at hudson.model.ComputerSet$1.save(ComputerSet.java:81)
	at hudson.util.PersistedList.onModified(PersistedList.java:173)
	at hudson.util.PersistedList.replaceBy(PersistedList.java:85)
	at hudson.model.ComputerSet.(ComputerSet.java:447)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:483)
	at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:105)
	at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:169)
	at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)
	at jenkins.model.Jenkins$7.runTask(Jenkins.java:899)
	at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)
	at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:744)

Lastly, when you attempt to create a new job you get the Jenkins Devil StackTrace page with the following stacktrace.

Stack trace

javax.servlet.ServletException: java.lang.ArrayIndexOutOfBoundsException: -1
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858

[JIRA] [findbugs] (JENKINS-8558) FindBugs plugin should allow choice of "priority" vs. "rank"

[elifar...@gmail.com (JIRA)]

Elifarley
 reopened  JENKINS-8558


FindBugs plugin should allow choice of "priority" vs. "rank"
















Hi Prof. Hafner,

I'm using Findbugs Plugin v. 4.56, and I'm still unable to configure which ranks are displayed in each plugin priority (high, normal and low).

Maye I could provide a patch... Would you have any jump-starting tips, like which files I'll probably need to change?

Thanks!





Change By:


Elifarley
(12/Mar/14 7:33 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/d/optout.

[JIRA] [plugin] (JENKINS-22158) Wrong parsing of revision for externals causes infinite builds

[imakow...@gmail.com (JIRA)]

Ireneusz Makowski
 commented on  JENKINS-22158


Wrong parsing of revision for externals causes infinite builds 















hudson.util.IOException2: revision check failed on http://svnserver:81/svn/pdr/App/Branches/ModernUI/SharedItems/ConfigurationFiles
	at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:189)
	at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:132)
	at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:736)
	at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:897)
	at hudson.model.AbstractProject.checkout(AbstractProject.java:1411)
	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652)
	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:561)
	at hudson.model.Run.execute(Run.java:1665)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:246)
Caused by: org.tmatesoft.svn.core.SVNException: svn: E175002: REPORT /svn/pdr/!svn/bc/84343/App/Branches/ModernUI/SharedItems/ConfigurationFiles failed
	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:386)
	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373)
	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361)
	at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707)
	at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:334)
	at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:324)
	at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.logImpl(DAVRepository.java:995)
	at org.tmatesoft.svn.core.io.SVNRepository.log(SVNRepository.java:1035)
	at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:181)
	at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35)
	at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20)
	at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238)
	at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294)
	at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:967)
	at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:872)
	at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:177)
	... 11 more
Caused by: svn: E175002: REPORT /svn/pdr/!svn/bc/84343/App/Branches/ModernUI/SharedItems/ConfigurationFiles failed
	at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208)
	at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:154)
	at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:97)
	... 27 more
Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: -11
	at java.lang.String.substring(Unknown Source)
	at java.lang.String.substring(Unknown Source)
	at hudson.scm.DirAwareSVNXMLLogHandler.handleLogEntry(DirAwareSVNXMLLogHandler.java:90)
	at org.tmatesoft.svn.core.internal.wc2.compat.SvnCodec$7.receive(SvnCodec.java:167)
	at org.tmatesoft.svn.core.internal.wc2.compat.SvnCodec$7.receive(SvnCodec.java:164)
	at org.tmatesoft.svn.core.wc2.SvnReceivingOperation.receive(SvnReceivingOperation.java:78)
	at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.handleLogEntry(SvnRemoteLog.java:199)
	at org.tmatesoft.svn.core.internal.io.dav.DAVRepository$1.handleLogEntry(DAVRepository.java:950)
	at org.tmatesoft.svn.core.internal.io.dav.handlers.DAVLogHandler.endElement(DAVLogHandler.java:226)
	at org.tmatesoft.svn.core.internal.io.dav.handlers.BasicDAVHandler.endElement(BasicDAVHandler.java:103)
	at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(Unknown Source)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(Unknown Source)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(Unknown Source)
	at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(Unknown Source)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScanner

Maven builds fail with 0ms

[thunderbird]

We are experiencing a terrible issue after the recent upgrade to LTS version
1.532.2, wherein few maven builds show they failed after 0ms, but
technically they took the time they had to really execute and even ran
totally successful sometimes..

The following image shows the actual build time trend with 0ms few times
 

The next image shows the console output where sometimes the builds are even
abruptly stopped and dont display any useful logging from the console nor
from the jenkins master
 

The third image shows where the build itself was successful, but jenkins
marked the build as failure and claims the entire build time took 0ms

 

Any input is highly appreciated..



--
View this message in context: 
http://jenkins-ci.361315.n4.nabble.com/Maven-builds-fail-with-0ms-tp4694286.html
Sent from the Jenkins issues mailing list archive at Nabble.com.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [plugin] (JENKINS-22158) Wrong parsing of revision for externals causes infinite builds

[imakow...@gmail.com (JIRA)]

Ireneusz Makowski
 created  JENKINS-22158


Wrong parsing of revision for externals causes infinite builds 















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


plugin, subversion



Created:


12/Mar/14 6:51 PM



Description:


Svn pool causes infinite builds because revision for some of the externals is wrong parsed. It always says that revision is changed from -1 although it should be 84343:

Started on Mar 12, 2014 7:43:54 PM
Received SCM poll call on plkrbuild02 for ManufacturingProcessIntelligence on Mar 12, 2014 7:43:54 PM
http://svnserver:81/svn/PDR/App/Branches/ModernUI/SharedItems/Resources is at revision 84,343
  (changed from -1)
http://svnserver:81/svn/PDR/App/Branches/ModernUI/Manufacturing Process Intelligence/Implementation is at revision 84,343
http://svnserver:81/svn/pdr/App/Master/SharedItems/TestsConfigurationFiles is at revision 87,219
Done. Took 0.91 sec
Changes found




Environment:


Windows 2008 R2 64bit, Jenkins 1.532.2




Project:


Jenkins



Priority:


Blocker



Reporter:


Ireneusz Makowski

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git] (JENKINS-22156) Git Plugin Json call key error for Jenkins job trigged by polling

[tee...@hotmail.com (JIRA)]

Vasee Seeva
 resolved  JENKINS-22156 as Not A Defect


Git Plugin Json call key error for Jenkins job trigged by polling
















Actually found out the order of the lastBuiltRevision key change due to Environment Injector Plugin installation. 





Change By:


Vasee Seeva
(12/Mar/14 6:30 PM)




Status:


Open
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/d/optout.

[JIRA] [parameterized-trigger] (JENKINS-22125) FATAL: Illegal choice: incremental caused by Parameterized Trigger Plugin 2.23

[darrell.no...@gmail.com (JIRA)]

Darrell Hamilton
 started work on  JENKINS-22125


FATAL: Illegal choice: incremental caused by Parameterized Trigger Plugin 2.23
















Change By:


Darrell Hamilton
(12/Mar/14 6:20 PM)




Status:


Open
In Progress



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [parameterized-trigger] (JENKINS-22125) FATAL: Illegal choice: incremental caused by Parameterized Trigger Plugin 2.23

[darrell.no...@gmail.com (JIRA)]

Darrell Hamilton
 commented on  JENKINS-22125


FATAL: Illegal choice: incremental caused by Parameterized Trigger Plugin 2.23















I've submitted a pull request implementing my proposed solution, https://github.com/jenkinsci/parameterized-trigger-plugin/pull/63



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [junit] (JENKINS-17189) Test results for the 'api' package hijacked by jenkins api documentation

[mark.earl.wa...@gmail.com (JIRA)]

Mark Waite
 resolved  JENKINS-17189 as Won't Fix


Test results for the 'api' package hijacked by jenkins api documentation
















Cannot fix this because the /api/ ending within the URL is taken as the entry point for API calls.





Change By:


Mark Waite
(12/Mar/14 5:54 PM)




Status:


Open
Resolved





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/d/optout.

[JIRA] [ghprb] (JENKINS-22157) Web Hook Does not Start a build

[kings...@chartboost.com (JIRA)]

Kingston Lee
 created  JENKINS-22157


Web Hook Does not Start a build















Issue Type:


Bug



Assignee:


Honza Brázdil



Components:


ghprb



Created:


12/Mar/14 5:50 PM



Description:


I've been trying to get the GitHub Pull Request Builder plugin working.

I set it up based on the instructions listed on the plugin page.

After creating a new pull request, I can confirm Jenkins receives the payload in the logs:

Mar 12, 2014 10:32:33 AM INFO org.jenkinsci.plugins.ghprb.GhprbRootAction doIndex
Got payload event: pull_request

Unfortunately, it stops there.  No build gets triggered.  I did find that configuring the Jenkins job, and then saving (with no changes) will trigger the builds to start happening.

I've checked the logs to see what is happening but it only shows this from the save configure trigger.

Mar 12, 2014 10:35:54 AM INFO org.jenkinsci.plugins.ghprb.GhprbPullRequest 
Created pull request #170 on test/test by  updated at: 3/12/14 10:18 AM SHA: 
Mar 12, 2014 10:35:54 AM INFO org.jenkinsci.plugins.ghprb.GhprbRepository createCommitStatus
Setting status of  to PENDING with url null and message:  Merged build triggered.
Mar 12, 2014 10:35:54 AM INFO org.jenkinsci.plugins.ghprb.GhprbRepository createCommitStatus
Setting status of  to PENDING with url http://:8080/job/BuildTests/8/ and message: Merged build started.
Mar 12, 2014 10:35:54 AM INFO org.jenkinsci.plugins.ghprb.GhprbPullRequest build
 Merged build triggered.
Mar 12, 2014 10:36:12 AM INFO hudson.model.Run execute
iOS SDK PR Tests #8 main build action completed: SUCCESS
Mar 12, 2014 10:36:12 AM INFO org.jenkinsci.plugins.ghprb.GhprbRepository createCommitStatus
Setting status of  to SUCCESS with url http://:8080/job/BuildTests/8/ and message: Merged build finished.




Project:


Jenkins



Priority:


Major



Reporter:


Kingston Lee

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git] (JENKINS-22156) Git Plugin Json call key error for Jenkins job trigged by polling

[tee...@hotmail.com (JIRA)]

Vasee Seeva
 created  JENKINS-22156


Git Plugin Json call key error for Jenkins job trigged by polling















Issue Type:


Bug



Affects Versions:


current



Assignee:


Nicolas De Loof



Components:


git



Created:


12/Mar/14 5:45 PM



Description:


After updating Git Plugin to version 2.0.4, Jenkins job that was trigged by polling not retrieving lastBuiltRevision key for JSON call. 

I am using following query in the job to identify last successful build's git SHA key. 

CURL_RESULT=`curl -s -S $JOB_URL'lastSuccessfulBuild/api/json'`
git_last_successful_build_shakey=`echo "${CURL_RESULT}" | python -c 'import json,sys,os;obj=json.loads(sys.stdin.read());print obj["'"actions"'"][4]["'"lastBuiltRevision"'"]["'"SHA1"'"]'`

When I use direct JSON URL it is displaying the value but job trigged by polling is not getting the key lastBuiltRevision





Environment:


Jenkins server running on Linux platform. 




Fix Versions:


current



Project:


Jenkins



Priority:


Major



Reporter:


Vasee Seeva

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [configurationslicing] (JENKINS-21445) Job Disabled Build Slicer do not check project already disabled

[m...@moerk.org (JIRA)]

Mike Moerk
 commented on  JENKINS-21445


Job Disabled Build Slicer do not check project already disabled















This seems to be an issue with all checkbox (boolean) slicers.  If I select "configuration by view" by clicking a view on the left column, when I submit it's as if I unchecked all the boxes on all the other views.  This happens on Job Disabled Build Slicer (bool) as well as Block Build when Upstream Building Slicer (bool).



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [clearcase] (JENKINS-11462) cleartool error does not fail build

[garep...@gmail.com (JIRA)]

Garen Parham
 commented on  JENKINS-11462


cleartool error does not fail build















FYI, previously this was marked as a duplicate of JENKINS-21684, but that issue was also marked as a duplicate of this one (creating a cycle) – so I've removed the link 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/d/optout.

[JIRA] [parameterized-trigger] (JENKINS-22125) FATAL: Illegal choice: incremental caused by Parameterized Trigger Plugin 2.23

[darrell.no...@gmail.com (JIRA)]

Darrell Hamilton
 commented on  JENKINS-22125


FATAL: Illegal choice: incremental caused by Parameterized Trigger Plugin 2.23















To get things started, yes this appears to be originating in the patch I submitted, so I'll field any fixes.

I think an ideal solution would be to simply try/catch the attempt to convert the value and if an IllegalArgumentException gets thrown back, simply use the original value instead of trying to convert it. Although this contravenes the definition of the parameter on the target job, it will broaden compatibility with any existing use cases.

@dmaslakov, I am hesitant to make this behavior optional as it better ensures the parameters behave as their defined rather than how they're passed. I would propose, instead, that the choice parameter be extended with an optional "accept anything" behavior to accommodate @mwebber's particular use case.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [gerrit-trigger] (JENKINS-22155) NullpointerException when loading dynamic config jobs when updated to 2.11

[rsand...@java.net (JIRA)]

rsandell
 commented on  JENKINS-22155


NullpointerException when loading dynamic config jobs when updated to 2.11















This is due to the serverName not being fully migrated to the dynamic trigger config. e.g. serverName is null.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [gerrit-trigger] (JENKINS-22155) NullpointerException when loading dynamic config jobs when updated to 2.11

[rsand...@java.net (JIRA)]

rsandell
 created  JENKINS-22155


NullpointerException when loading dynamic config jobs when updated to 2.11















Issue Type:


Bug



Assignee:


rsandell



Components:


gerrit-trigger



Created:


12/Mar/14 5:07 PM



Description:


See the stacktrace

Mar 12, 2014 5:37:05 PM jenkins.InitReactorRunner$1 onTaskFailed
SEVERE: Failed Loading job Gerrit_check_job
java.lang.NullPointerException
at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTriggerTimer.schedule(GerritTriggerTimer.java:87)
at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTriggerTimerTask.(GerritTriggerTimerTask.java:44)
at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTrigger.start(GerritTrigger.java:352)
at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTrigger.start(GerritTrigger.java:110)
at hudson.model.AbstractProject.onLoad(AbstractProject.java:327)
at hudson.model.Project.onLoad(Project.java:90)
at hudson.model.Items.load(Items.java:221)
at jenkins.model.Jenkins$18.run(Jenkins.java:2616)
at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146)
at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
at jenkins.model.Jenkins$7.runTask(Jenkins.java:945)
at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)




Project:


Jenkins



Priority:


Critical



Reporter:


rsandell

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [email-ext] (JENKINS-22154) Add option to temporary deactivate the plugin in the project settings

[slide.o....@gmail.com (JIRA)]

Alex Earl
 commented on  JENKINS-22154


Add option to temporary deactivate the plugin in the project settings















It's not a workaround, the emergency reroute was added for this purpose.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [master-slave] (JENKINS-21875) NullPointerException when trying to mark slave temporarily offline

[vivek.a...@gmail.com (JIRA)]

Vivek Ayer
 commented on  JENKINS-21875


NullPointerException when trying to mark slave temporarily offline















I'm seeing this Jenkins v1.554 on CentOS 6.5.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [email-ext] (JENKINS-22154) Add option to temporary deactivate the plugin in the project settings

[masternoob...@gmail.com (JIRA)]

Alexander Dobetsberger
 commented on  JENKINS-22154


Add option to temporary deactivate the plugin in the project settings















or to add a new checkbox in the project settings so there is no need for a workaround 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [email-ext] (JENKINS-22154) Add option to temporary deactivate the plugin in the project settings

[slide.o....@gmail.com (JIRA)]

Alex Earl
 commented on  JENKINS-22154


Add option to temporary deactivate the plugin in the project settings















The other option would be to use the emergency reroute in the global settings so that emails are only sent to you while you are testing.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [email-ext] (JENKINS-22154) Add option to temporary deactivate the plugin in the project settings

[masternoob...@gmail.com (JIRA)]

Alexander Dobetsberger
 updated  JENKINS-22154


Add option to temporary deactivate the plugin in the project settings
















Change By:


Alexander Dobetsberger
(12/Mar/14 4:54 PM)




Priority:


Major
Minor



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [email-ext] (JENKINS-22154) Add option to temporary deactivate the plugin in the project settings

[masternoob...@gmail.com (JIRA)]

Alexander Dobetsberger
 commented on  JENKINS-22154


Add option to temporary deactivate the plugin in the project settings















hmm yes thats true but i have many triggers with different configurations, so i would have to take a screenshot or something so i don't forget the setting, that is pretty annoying



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [email-ext] (JENKINS-22154) Add option to temporary deactivate the plugin in the project settings

[slide.o....@gmail.com (JIRA)]

Alex Earl
 commented on  JENKINS-22154


Add option to temporary deactivate the plugin in the project settings















This is as easy as unchecking boxes in the advanced area for the various triggers...with no checkboxes for who to send to, it won't send to anyone.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [email-ext] (JENKINS-22154) Add option to temporary deactivate the plugin in the project settings

[masternoob...@gmail.com (JIRA)]

Alexander Dobetsberger
 created  JENKINS-22154


Add option to temporary deactivate the plugin in the project settings















Issue Type:


New Feature



Assignee:


Alex Earl



Components:


email-ext



Created:


12/Mar/14 4:45 PM



Description:


When i change something in my buildscript/buildsettings and i want to test that configuration, our developers get pretty high amounts of spam when i test the new stuff (failed and successful builds etc.)

A checkbox to deactivate the plugin in the project settings would be very useful for tests like this.




Project:


Jenkins



Priority:


Major



Reporter:


Alexander Dobetsberger

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [warnings] (JENKINS-22139) Maven warnings details are broken

[scm_issue_l...@java.net (JIRA)]

SCM/JIRA link daemon
 commented on  JENKINS-22139


Maven warnings details are broken















Code changed in jenkins
User: Ulli Hafner
Path:
 src/main/java/hudson/plugins/analysis/core/ParserResult.java
http://jenkins-ci.org/commit/analysis-core-plugin/3ddc1d7912a072efb8173c1ce527089de403db70
Log:
  [FIXED JENKINS-22139] Don't expand empty path with workspace root.





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [warnings] (JENKINS-22139) Maven warnings details are broken

[scm_issue_l...@java.net (JIRA)]

SCM/JIRA link daemon
 resolved  JENKINS-22139 as Fixed


Maven warnings details are broken
















Change By:


SCM/JIRA link daemon
(12/Mar/14 4:41 PM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [warnings] (JENKINS-22139) Maven warnings details are broken

[ullrich.haf...@gmail.com (JIRA)]

  
Ulli Hafner
 edited a comment on  JENKINS-22139


Maven warnings details are broken
















I think I understand now what's going on, there is no filename given at all. Actually the console log should be shown when clicking on the link...



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [warnings] (JENKINS-22139) Maven warnings details are broken

[scm_issue_l...@java.net (JIRA)]

SCM/JIRA link daemon
 commented on  JENKINS-22139


Maven warnings details are broken















Code changed in jenkins
User: Ulli Hafner
Path:
 analysis-collector
http://jenkins-ci.org/commit/analysis-suite-plugin/193401128ce4ecd00772d9bf5616d6b757d86fb8
Log:
  [FIXED JENKINS-22139] Don't expand empty path with workspace root.





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [warnings] (JENKINS-22139) Maven warnings details are broken

[ullrich.haf...@gmail.com (JIRA)]

Ulli Hafner
 commented on  JENKINS-22139


Maven warnings details are broken















I think I understand now whats going on, there is no filename given at all. Actually the console log should be shown when clicking on the link...



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [parameterized-trigger] (JENKINS-22125) FATAL: Illegal choice: incremental caused by Parameterized Trigger Plugin 2.23

[dmasla...@java.net (JIRA)]

Dmitry Maslakov
 commented on  JENKINS-22125


FATAL: Illegal choice: incremental caused by Parameterized Trigger Plugin 2.23















@ikedam, downstream job A uses parameter values as-is, i.e. unexpected values e, f, g are used in processing exactly as expected values a, b, c does. In my case parameter types are just a facade for user-friendly UI, but as build execution is started the values are just strings (like environment variables).


And answering to your questions:

How does downstram project A uses values e, f, g?
In same way as values a, b, c. One of my real example for parameter meaning is a set of host names where SSH session will connect to.

Does A use those unexpected values in builds,
Yes.

or does not use those valus when unexpected values passed or triggered as downstream?
Not using will require additional checks and custom code in build steps. No, I did not skip unexpected values.

I want to know what happens in your case if simply omitting parameters failed to cenvert.
It will fail the build of job A. Behavior you suggest is in same sense harmful and not backward compatible as one implemented in version 2.23.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [confluence-publisher] (JENKINS-22153) Add attachment comment for confluence publisher

[gle...@engel.org (JIRA)]

Glenn Engel
 created  JENKINS-22153


Add attachment comment for confluence publisher















Issue Type:


New Feature



Assignee:


Joe Hansche



Components:


confluence-publisher



Created:


12/Mar/14 4:34 PM



Description:


When uploading artifacts to confluence it would be helpful if the upload could also update the comment for the attachment with data from the build such as build number, version etc.

I envision this as an additional string parameter that can have environment variables in the string.  e.g. Build ${BUILD_NUMBER}-${BUILD_ID}

This is supported by the confluence-cli tool so it should be possible.




Project:


Jenkins



Priority:


Major



Reporter:


Glenn Engel

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [warnings] (JENKINS-22139) Maven warnings details are broken

[ullrich.haf...@gmail.com (JIRA)]

Ulli Hafner
 commented on  JENKINS-22139


Maven warnings details are broken















But what is the actual maven line in your console log? Can you please show me that, it is used as basis for the parser.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [gerrit-trigger] (JENKINS-12921) Trigger fails to build with "Null value not allowed as an environment variable: GIT_BRANCH" error

[sschube...@gmail.com (JIRA)]

Sebastian Schuberth
 commented on  JENKINS-12921


Trigger fails to build with "Null value not allowed as an environment variable: GIT_BRANCH" error















As to why this happens, rsandell's explanation sounds quite convincing to me. However, for me the fix was to use $GERRIT_BRANCH (not $GERRIT_PATCHSET_REVISION) as the branch specifier. That's also what's recommended at [1]: "You may also need to set 'Branches to build' to $GERRIT_BRANCH".

[1] https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger#GerritTrigger-UsagewiththeGitPlugin



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-21579) Very slow resource loading from UberClassLoader

[sdrot...@gmail.com (JIRA)]

Steve Roth
 commented on  JENKINS-21579


Very slow resource loading from UberClassLoader















I am seeing this as well, on 1.553, but without the cloudbees-template plugin installed.


Handling GET /job/something/configure : http-bio-5269-exec-1805" daemon prio=5 RUNNABLE
	java.lang.Throwable.fillInStackTrace(Native Method)
	java.lang.Throwable.(Throwable.java:196)
	java.lang.Exception.(Exception.java:41)
	javax.naming.NamingException.(NamingException.java:109)
	javax.naming.NameNotFoundException.(NameNotFoundException.java:33)
	org.apache.naming.resources.BaseDirContext.lookup(BaseDirContext.java:500)
	org.apache.naming.resources.ProxyDirContext.lookup(ProxyDirContext.java:308)
	org.apache.catalina.loader.WebappClassLoader.findResources(WebappClassLoader.java:1315)
	java.lang.ClassLoader.getResources(ClassLoader.java:1040)
	java.lang.ClassLoader.getResources(ClassLoader.java:1036)
	java.lang.ClassLoader.getResources(ClassLoader.java:1036)
	org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:957)
	org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:935)
	sun.reflect.GeneratedMethodAccessor61.invoke(Unknown Source)
	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	java.lang.reflect.Method.invoke(Method.java:597)
	jenkins.ClassLoaderReflectionToolkit.invoke(ClassLoaderReflectionToolkit.java:44)
	jenkins.ClassLoaderReflectionToolkit._findResources(ClassLoaderReflectionToolkit.java:103)
	hudson.ClassicPluginStrategy$DependencyClassLoader.findResources(ClassicPluginStrategy.java:598)
	java.lang.ClassLoader.getResources(ClassLoader.java:1040)
	org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:957)
	org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:935)
	sun.reflect.GeneratedMethodAccessor61.invoke(Unknown Source)
	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	java.lang.reflect.Method.invoke(Method.java:597)
	jenkins.ClassLoaderReflectionToolkit.invoke(ClassLoaderReflectionToolkit.java:44)
	jenkins.ClassLoaderReflectionToolkit._findResources(ClassLoaderReflectionToolkit.java:103)
	hudson.ClassicPluginStrategy$DependencyClassLoader.findResources(ClassicPluginStrategy.java:598)
	java.lang.ClassLoader.getResources(ClassLoader.java:1040)
	org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:957)
	org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:935)
	sun.reflect.GeneratedMethodAccessor61.invoke(Unknown Source)
	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	java.lang.reflect.Method.invoke(Method.java:597)
	jenkins.ClassLoaderReflectionToolkit.invoke(ClassLoaderReflectionToolkit.java:44)
	jenkins.ClassLoaderReflectionToolkit._findResources(ClassLoaderReflectionToolkit.java:103)
	hudson.ClassicPluginStrategy$DependencyClassLoader.findResources(ClassicPluginStrategy.java:598)
	java.lang.ClassLoader.getResources(ClassLoader.java:1040)
	org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:957)
	org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:935)
	sun.reflect.GeneratedMethodAccessor61.invoke(Unknown Source)
	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	java.lang.reflect.Method.invoke(Method.java:597)
	jenkins.ClassLoaderReflectionToolkit.invoke(ClassLoaderReflectionToolkit.java:44)
	jenkins.ClassLoaderReflectionToolkit._findResources(ClassLoaderReflectionToolkit.java:103)
	hudson.ClassicPluginStrategy$DependencyClassLoader.findResources(ClassicPluginStrategy.java:598)
	java.lang.ClassLoader.getResources(ClassLoader.java:1040)
	org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:957)
	org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:935)
	sun.reflect.GeneratedMethodAccessor61.invoke(Unknown Source)
	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	java.lang.reflect.Method.invoke(Method.java:597)
	jenkins.ClassLoaderReflectionToolkit.invoke(ClassLoaderReflectionToolkit.java:44)
	jenkins.ClassLoaderReflectionToolkit._findResources(ClassLoaderReflectionToolkit.java:103)
	hudson.ClassicPluginStrategy$DependencyClassLoader.findResources(ClassicPluginStrategy.java:598)
	java.lang.ClassLoader.getResources(ClassLoader.java:1040)
	org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:957)
	org.apache.tools.ant.AntClassLoader.findResources(An

[JIRA] [tap] (JENKINS-17960) Indicate if tests don't go to plan

[ja...@howeswho.co.uk (JIRA)]

James Howe
 resolved  JENKINS-17960 as Fixed


Indicate if tests don't go to plan
















This looks like it now works as I would expect.





Change By:


James Howe
(12/Mar/14 3:58 PM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [tap] (JENKINS-19647) memory issues with multiconfig jobs and TAP plugin

[brunodepau...@yahoo.com.br (JIRA)]

Bruno P. Kinoshita
 commented on  JENKINS-19647


memory issues with multiconfig jobs and TAP plugin















Hi Ken, just a quick update on this issue. 

I'm releasing 1.18 with a few old pending issues tonight. 

1.19 will be focused in memory management and JVM crashes. 1.20 will be bugfixes and code review.

Sorry for taking so long to take care of this issue.

Cheers, 
Bruno



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [junit] (JENKINS-17189) Test results for the 'api' package hijacked by jenkins api documentation

[ever...@free.fr (JIRA)]

evernat
 commented on  JENKINS-17189


Test results for the 'api' package hijacked by jenkins api documentation















As francisdb I think that is unfortunate that, because of Jenkins, projects can't name a package with "api".



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [tap] (JENKINS-17960) Indicate if tests don't go to plan

[brunodepau...@yahoo.com.br (JIRA)]

Bruno P. Kinoshita
 commented on  JENKINS-17960


Indicate if tests don't go to plan















Yay, thanks for testing it so quickly James. Cutting a new release this night, 1.18 should be available in the update center within hours. 

Thanks again
Bruno



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [junit] (JENKINS-17189) Test results for the 'api' package hijacked by jenkins api documentation

[ever...@free.fr (JIRA)]

  
evernat
 edited a comment on  JENKINS-17189


Test results for the 'api' package hijacked by jenkins api documentation
















As francisdb I think it is unfortunate that, because of Jenkins, projects can't name a package with "api".



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [junit] (JENKINS-17189) Test results for the 'api' package hijacked by jenkins api documentation

[franci...@gmail.com (JIRA)]

francisdb
 commented on  JENKINS-17189


Test results for the 'api' package hijacked by jenkins api documentation















An option would be to add a prefix to the generated report pages paths. But if I am the only guy that cares about this I suppose you can close it as wontfix



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [junit] (JENKINS-17189) Test results for the 'api' package hijacked by jenkins api documentation

[mark.earl.wa...@gmail.com (JIRA)]

Mark Waite
 commented on  JENKINS-17189


Test results for the 'api' package hijacked by jenkins api documentation















No workaround is possible as far as I can tell because the processing of any URL that ends in /api/ is part of the Jenkins core.  The only work around is to publish your test results to another web server, or rename your package from api to something else.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [warnings] (JENKINS-22139) Maven warnings details are broken

[arca...@ivanov.biz (JIRA)]

Arcadiy Ivanov
 updated  JENKINS-22139


Maven warnings details are broken
















Change By:


Arcadiy Ivanov
(12/Mar/14 3:27 PM)




Attachment:


screenshot1.png





Attachment:


screenshot2.png



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [warnings] (JENKINS-22139) Maven warnings details are broken

[arca...@ivanov.biz (JIRA)]

Arcadiy Ivanov
 commented on  JENKINS-22139


Maven warnings details are broken















I don't think type matters, because none of them actually work.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [warnings] (JENKINS-22139) Maven warnings details are broken

[arca...@ivanov.biz (JIRA)]

  
Arcadiy Ivanov
 edited a comment on  JENKINS-22139


Maven warnings details are broken
















I don't think type matters, because none of them actually work.
Screenshots of warnings are attached.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [gradle] (JENKINS-21653) Gradle build command not working as Gradle version is unavailable for selection in Configure

[john.r.engel...@gmail.com (JIRA)]

John Engelman
 commented on  JENKINS-21653


Gradle build command not working as Gradle version is unavailable for selection in Configure















You'll need to configure a Gradle installation under Jenkins | Manage Jenkins | Gradle.
There you can set up different installations to either installed locations on the file system or have Jenkins automatically install it from gradle.org.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git] (JENKINS-21952) Git Plugin fails to resolve tags containing a slash since 2.0.1

[dejan2...@gmail.com (JIRA)]

Dejan Stojadinovic
 commented on  JENKINS-21952


Git Plugin fails to resolve tags containing a slash since 2.0.1















I'm also receiving error while trying to build from tag using Jenkins git plugin (version 2.0.4): 

ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.



Build from git branches works as expected.

Note that ALL of my tags contain numbers and dots only (no slashes), for example:

14.01
14.01.01
14.01.02
14.02
14.02.01
14.02.02
etc

Environment details:
Jenkins LTS: 1.532.2
Git (used by Jenkins: 1.7.11)
Jenkins Git client plugin: 1.6.4
Jenkins Git plugin: 2.0.4

Jenkins Git plugin downgrade to version 2.0.1 solves issue (i.e. I'm able to build from git tags with 2.0.1).



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [junit] (JENKINS-17189) Test results for the 'api' package hijacked by jenkins api documentation

[franci...@gmail.com (JIRA)]

francisdb
 commented on  JENKINS-17189


Test results for the 'api' package hijacked by jenkins api documentation















Also still have the issue, no workaround possible?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [tap] (JENKINS-17960) Indicate if tests don't go to plan

[brunodepau...@yahoo.com.br (JIRA)]

Bruno P. Kinoshita
 commented on  JENKINS-17960


Indicate if tests don't go to plan















Due to firewall policies in the office where I am atm I can't release an alpha version to the experimental update center 

I've attached a snapshot HPI with the latest code though, don't know if you can install it in some environment and try it. If so let me know if that works and feel free to update this issue. 

JENKINS-17960 is the only pending issue I'm waiting to cut a new release. Next release will focus in JVM crashes and memory management, and the following will be code review/smaller improvements.

Thanks!
Bruno



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [tap] (JENKINS-17960) Indicate if tests don't go to plan

[brunodepau...@yahoo.com.br (JIRA)]

Bruno P. Kinoshita
 updated  JENKINS-17960


Indicate if tests don't go to plan
















TAP Plug-in snapshot 2014-03-12 HPI file





Change By:


Bruno P. Kinoshita
(12/Mar/14 3:01 PM)




Attachment:


tap-snapshot-20140312.hpi



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-12875) "No valid crumb was included in the request" errors all around

[ranjit.vadak...@gmail.com (JIRA)]

Ranjit Vadakkan
 updated  JENKINS-12875


"No valid crumb was included in the request" errors all around
















Change By:


Ranjit Vadakkan
(12/Mar/14 2:46 PM)




Attachment:


Screen Shot 2014-03-12 at 10.43.58 AM.png



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-12875) "No valid crumb was included in the request" errors all around

[ranjit.vadak...@gmail.com (JIRA)]

  
Ranjit Vadakkan
 edited a comment on  JENKINS-12875


"No valid crumb was included in the request" errors all around
















To disable CSRF (Screenshot) - 

Jenkins > Manage Jenkins > Configure Global Security

At the very bottom, you will see a checkbox for "Prevent Cross Site Request Forgery exploits". Uncheck this and apply.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-12875) "No valid crumb was included in the request" errors all around

[ranjit.vadak...@gmail.com (JIRA)]

  
Ranjit Vadakkan
 edited a comment on  JENKINS-12875


"No valid crumb was included in the request" errors all around
















To disable CSRF: 

Jenkins > Manage Jenkins > Configure Global Security

At the very bottom, you will see a checkbox for "Prevent Cross Site Request Forgery exploits". Uncheck this and apply.

Screenshot



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-12875) "No valid crumb was included in the request" errors all around

[ranjit.vadak...@gmail.com (JIRA)]

Ranjit Vadakkan
 commented on  JENKINS-12875


"No valid crumb was included in the request" errors all around















To disable CSRF: 

Jenkins > Manage Jenkins > Configure Global Security

At the very bottom, you will see a checkbox for "Prevent Cross Site Request Forgery exploits". Uncheck this and apply.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8

[mikekonik...@gmail.com (JIRA)]

  
Mike Konikoff
 edited a comment on  JENKINS-18935


Make Subversion plugin support Subversion 1.8
















Downloaded and installed subversion Plug-in 2.3-SNAPSHOT (private-03/11/2014 20:58-kohsuke)

Manage Jenkins > Configure System > Subversion > Subversion Workspace Version > Missing option for 1.8

Also, getting a "Cant install ... from pristine store, because no checksum is recorded for this file" checking out a clean workspace. This does not occur when checking out from the same repo using svnkit 1.8.1.10101 with subclipse 1.10.3 in myeclipse.




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git] (JENKINS-20767) Git plugin 2.0: Git polling causes builds even if no changes

[alexanderl...@java.net (JIRA)]

alexanderlink
 commented on  JENKINS-20767


Git plugin 2.0: Git polling causes builds even if no changes















This small change should fix the issue: https://github.com/jenkinsci/git-plugin/pull/209

I'm not sure if maybe somewhere else "remotes/" is not handled correctly, but tests on our side look good.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials

[alex.d.alex...@gmail.com (JIRA)]

Alexander Alexeev
 commented on  JENKINS-21785


Check for changes in folders linked via svn:externals fails due to missing credentials















I've same problem after update to 1.554

And I have workaround for this bug.
I changed svn update option to
"Emulate clean checkout by first deleting unversioned/ignored files, then 'svn update'"



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8

[mikekonik...@gmail.com (JIRA)]

Mike Konikoff
 commented on  JENKINS-18935


Make Subversion plugin support Subversion 1.8















Manage Jenkins > Configure System > Subversion > Subversion Workspace Version > Missing option for 1.8

Also, getting a "Cant install ... from pristine store, because no checksum is recorded for this file" checking out a clean workspace. This does not occur when checking out from the same repo using svnkit 1.8.1.10101 with subclipse 1.10.3 in myeclipse.




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [tap] (JENKINS-17960) Indicate if tests don't go to plan

[ja...@howeswho.co.uk (JIRA)]

James Howe
 commented on  JENKINS-17960


Indicate if tests don't go to plan















That looks like it might work now 
I'd need something in the next couple of hours in order to test it before Monday.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-18313) "H" cron syntax - cannot specify "between 10 pm and 6 am"

[dave.ohls...@gmail.com (JIRA)]

Dave Ohlsson
 commented on  JENKINS-18313


"H" cron syntax - cannot specify "between 10 pm and 6 am"















@Jerzy: I tried your suggestion: it does not work. Why do you think it should work?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [tap] (JENKINS-17960) Indicate if tests don't go to plan

[brunodepau...@yahoo.com.br (JIRA)]

Bruno P. Kinoshita
 commented on  JENKINS-17960


Indicate if tests don't go to plan















By the way, I'm not exactly comparing the number of the last test, but comparing if the total of tests is equal to the expected number in the test plan. 

Do you see any problem in doing like that? 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [tap] (JENKINS-17960) Indicate if tests don't go to plan

[ja...@howeswho.co.uk (JIRA)]

  
James Howe
 edited a comment on  JENKINS-17960


Indicate if tests don't go to plan
















The logic for this feature should really be very simple.

if (planExists && numberAtEndOfPlan != numberOfLastTest) {

  log message that tests didn't go to plan

  if (status == SUCCESS) then status = UNSTABLE

}

The checkbox should not cause anything else to happen.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [tap] (JENKINS-17960) Indicate if tests don't go to plan

[ja...@howeswho.co.uk (JIRA)]

  
James Howe
 edited a comment on  JENKINS-17960


Indicate if tests don't go to plan
















The logic for this feature should really be very simple.

if (planExists && numberAtEndOfPlan != numberOfLastTest) {

log message that tests didn't go to plan

if (status == SUCCESS) then status = UNSTABLE

}

The checkbox should not cause anything else to happen.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [tap] (JENKINS-17960) Indicate if tests don't go to plan

[brunodepau...@yahoo.com.br (JIRA)]

Bruno P. Kinoshita
 commented on  JENKINS-17960


Indicate if tests don't go to plan















Not that one, I believe it was fixed in https://github.com/jenkinsci/tap-plugin/commit/9e60ea571d359a0c445a33f791e62ca6c5f87479#diff-7ebebde3074c0bb507b4983802c5803cL149, already released in the experimental update center. 

This new commit only simplifies the logic as you suggested. Let me know if I missed anything. Probably I can push more commits today before releasing 1.18-2-alpha tonight.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [tap] (JENKINS-17960) Indicate if tests don't go to plan

[ja...@howeswho.co.uk (JIRA)]

  
James Howe
 edited a comment on  JENKINS-17960


Indicate if tests don't go to plan
















The logic for this feature should really be very simple.

if (planExists && numberAtEndOfPlan != numberOfLastTest) {
  log message that tests didn't go to plan;
  if (status == SUCCESS) then status = UNSTABLE;
}

The checkbox should not cause anything else to happen.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [tap] (JENKINS-17960) Indicate if tests don't go to plan

[ja...@howeswho.co.uk (JIRA)]

James Howe
 commented on  JENKINS-17960


Indicate if tests don't go to plan















Does that commit also address the problem of all the results being lost if the tests don't go to plan?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git] (JENKINS-20767) Git plugin 2.0: Git polling causes builds even if no changes

[mark.earl.wa...@gmail.com (JIRA)]

Mark Waite
 commented on  JENKINS-20767


Git plugin 2.0: Git polling causes builds even if no changes















That's unfortunate.  Thanks for checking.  I'll need to defer to Nicolas DeLoof on how to resolve that.  I'm not sure if he'll want to have me revert your changes, or if we try to press forward and find some way to make the git plugin and the git client plugin agree on their handling of the specification of branches to build.

I'm quite hesitant to break backwards compatibility, because I don't know all the different ways people are dependent on the original behavior.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [parameterized-trigger] (JENKINS-22125) FATAL: Illegal choice: incremental caused by Parameterized Trigger Plugin 2.23

[de...@ikedam.jp (JIRA)]

ikedam
 commented on  JENKINS-22125


FATAL: Illegal choice: incremental caused by Parameterized Trigger Plugin 2.23















@mwebber
Would you report how to reproduce your problem?
Same to the case of @dmaslakov?

@dmaslakov
Let me know what you want to do with those projects.
How does downstram project A uses values e, f, g?
Does A use those unexpected values in builds, or does not use those valus when unexpected values passed or triggered as downstream?
I want to know what happens in your case if simply omitting parameters failed to cenvert.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [tap] (JENKINS-17960) Indicate if tests don't go to plan

[scm_issue_l...@java.net (JIRA)]

SCM/JIRA link daemon
 commented on  JENKINS-17960


Indicate if tests don't go to plan















Code changed in jenkins
User: Bruno P. Kinoshita
Path:
 src/main/java/org/tap4j/plugin/TapPublisher.java
http://jenkins-ci.org/commit/tap-plugin/275c599945025e3467bb42e9d82d3089ee25dc2b
Log:
  JENKINS-17960 Simplify logic





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git] (JENKINS-20767) Git plugin 2.0: Git polling causes builds even if no changes

[alexanderl...@java.net (JIRA)]

alexanderlink
 commented on  JENKINS-20767


Git plugin 2.0: Git polling causes builds even if no changes















Hello Mark,

I tried to test the latest git plugin (2.0.4) with the latest git-client plugin (1.6.4) and due to another change in the git plugin the approach with "remotes/origin/..." does not work!

Commit ea5cad7e2759d0c9f5ed723fe590f982b0bb818d "JENKINS-14026 DefaultBuildChooser should handle smartly branches with /" causes the issue.

When I specify "remotes/origin/feature1/master" the DefaultBuildChooser prepends the repo name (to String fqbn) "origin/remotes/origin/feature1/master" and for this String it is tried to get the head revision - which of course cannot work.

Shall I prepare another Pull Request or do you want to have a look into this?
Be aware that the help adjustments I contributed to the git plugin are already merged. The behaviour described there currently does not work due to above issue...

Thanks and regards,
Alex



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git] (JENKINS-22119) Fail to update update git repository with stored credential

[mark.earl.wa...@gmail.com (JIRA)]

  
Mark Waite
 edited a comment on  JENKINS-22119


Fail to update update git repository with stored credential
















Thanks for the hint to use bitbucket.

I can see the failure if I configure a credential with a username and password for a private bitbucket git repository.  If the bitbucket repository is public (which I had been using before), then the clone succeeds.  More exploration will be required.

I don't see the same failure if I configure a credential with a username and password for a private github repository.  Public github repositories also do not show any issue.



Provider
Private Repo
Public Repo


github   
 1.6.3 (ok)  
  1.6.3 (ok)


bitbucket
 1.6.3 (ok)  
  1.6.3 (ok)


github   
 1.6.4 (ok)  
  1.6.4 (ok)


bitbucket
 1.6.4 (bad) 
  1.6.4 (ok)





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.