[JIRA] [core] (JENKINS-24014) Jenkins wrongly(?) warns that "reverse proxy set up is broken" when using autorefresh link.
Daniel Beck assigned JENKINS-24014 to Daniel Beck Jenkins wrongly(?) warns that "reverse proxy set up is broken" when using autorefresh link. Change By: Daniel Beck (01/Aug/14 6:47 AM) Assignee: Daniel Beck This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24054) REST API endpoint should have consistent prefix
Daniel Beck resolved JENKINS-24054 as Not A Defect REST API endpoint should have consistent prefix Change By: Daniel Beck (01/Aug/14 6:44 AM) 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] [core] (JENKINS-24054) REST API endpoint should have consistent prefix
Daniel Beck edited a comment on JENKINS-24054 REST API endpoint should have consistent prefix It's there because it's a form action for the UI. There's nothing that can be done about that. If it's not documented as being part of the supported API (i.e. intended to be used programmatically), you're on your own. Even if it were documented as API (triggering builds comes to mind), there's no inconsistency: You get data from Jenkins by accessing (object)/api/xml or (object)/api/json and you perform actions using (object)/(action). Two different schemes for two different kinds of 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] [core] (JENKINS-24054) REST API endpoint should have consistent prefix
Daniel Beck commented on JENKINS-24054 REST API endpoint should have consistent prefix It's there because it's a form action for the UI. There's nothing that can be done about that. If it's not documented as being part of the supported API (i.e. intended to be used programmatically), you're on you're own. Even if it were documented as API (triggering builds comes to mind), there's no inconsistency: You get data from Jenkins by accessing (object)/api/xml or (object)/api/json and you perform actions using (object)/(action). Two different schemes for two different kinds of 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] [maven] (JENKINS-23123) NPE from MavenSiteArchiver.getModulePath
Johannes Schaefer updated JENKINS-23123 NPE from MavenSiteArchiver.getModulePath Hello, I have the same issue in my project. So I prepared a test project to reproduce this behavior. Unfortunately I wasn't able to debug and fix this problem. I hope this test project helps the maintainers to fix this issue in one of the next releases. Change By: Johannes Schaefer (01/Aug/14 6:37 AM) Attachment: testExampleForJira.zip This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-24054) REST API endpoint should have consistent prefix
Sam Xiao commented on JENKINS-24054 REST API endpoint should have consistent prefix It is probably never advertised, but it's there and it works! (yeah i know, it needs to be better documented.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [urltrigger] (JENKINS-24073) Multiple jobs with same URL only trigger once
Ryan Finnie updated JENKINS-24073 Multiple jobs with same URL only trigger once Change By: Ryan Finnie (01/Aug/14 5:43 AM) Description: I have a setup where multiple jobs poll a single URL's modification time, in " N H * * * *". The expected behavior would be for all jobs to trigger throughout the hour after the change is detected. What actually happens is the first job to poll and detect the update will trigger the job, but later jobs' polls will detect "no changes".This suggests the backend is keeping a global URL->attributes array which is updated as each of the polls run. I believe instead the attributes used to detect changes should be per-job, or at least an option to switch between global or per-job.A workaround would be to add ?[unique string] to each of the jobs' URLs, but this will not be possible in all cases. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [urltrigger] (JENKINS-24073) Multiple jobs with same URL only trigger once
Ryan Finnie created JENKINS-24073 Multiple jobs with same URL only trigger once Issue Type: Bug Assignee: Gregory Boissinot Components: urltrigger Created: 01/Aug/14 5:39 AM Description: I have a setup where multiple jobs poll a single URL's modification time, in "N * * * *". The expected behavior would be for all jobs to trigger throughout the hour after the change is detected. What actually happens is the first job to poll and detect the update will trigger the job, but later jobs' polls will detect "no changes". This suggests the backend is keeping a global URL->attributes array which is updated as each of the polls run. I believe instead the attributes used to detect changes should be per-job, or at least an option to switch between global or per-job. A workaround would be to add ?[unique string] to each of the jobs' URLs, but this will not be possible in all cases. Environment: URLTrigger 0.37, Jenkins ver. 1.565.1 Project: Jenkins Priority: Minor Reporter: Ryan Finnie This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [sbt] (JENKINS-23545) Linux master, windows slave causes the sbt plugin to create an incorrect path to java
Brenna Flood edited a comment on JENKINS-23545 Linux master, windows slave causes the sbt plugin to create an incorrect path to java I just noticed the same behavior with my company's Jenkins implementation today. Master is CentOS 5, slave is Windows 7. Jenkins 1.483, manually installed JDK 1.7 (56). Any advice on a fix for this is appreciated! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [sbt] (JENKINS-23545) Linux master, windows slave causes the sbt plugin to create an incorrect path to java
Brenna Flood commented on JENKINS-23545 Linux master, windows slave causes the sbt plugin to create an incorrect path to java I just noticed the same behavior with my company's Jenkins implementation today. Master is CentOS 5, slave is Windows 7. Jenkins 1.483. Any advice on a fix for this is appreciated! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [build-with-parameters] (JENKINS-24008) Jobs stuck while waiting for an executor (and executors are available)
Daniel Beck updated JENKINS-24008 Jobs stuck while waiting for an executor (and executors are available) Damien has determined that it seems the Build with Params feature causes this issue. From #jenkins (IRC): [00:22:41] danielbeck: found the issue [00:22:53] some users click on "build with params" [00:23:01] and that fails [00:23:07] <+danielbeck> Build with Parameters Plugin? [00:23:14] lemme look [00:25:13] danielbeck: /parambuild/ so i think yes Change By: Daniel Beck (31/Jul/14 10:35 PM) Affects Version/s: current This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [build-with-parameters] (JENKINS-24008) Jobs stuck while waiting for an executor (and executors are available)
Damien Nozay updated JENKINS-24008 Jobs stuck while waiting for an executor (and executors are available) Change By: Damien Nozay (31/Jul/14 10:35 PM) Component/s: build-with-parameters Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24008) Jobs stuck while waiting for an executor (and executors are available)
Damien Nozay commented on JENKINS-24008 Jobs stuck while waiting for an executor (and executors are available) found the issue. some folks use "build with params" -> /job/runtest/job/DevPrecheckin/parambuild/ this ALWAYS fails. some folks use "build with parameters" -> /job/runtest/job/DevPrecheckin/build this works. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23724) Node creation page cannot be displayed in IE 10 (normal mode)
Henrik Ygge
commented on JENKINS-23724
Node creation page cannot be displayed in IE 10 (normal mode)
I investigated this a bit.
For some reason IE10 decides to crash if document.getElementsByName is called (which is done in confirm.js) and there is an element with a name-attribute without a value. In this case the attribute came from the makeButton function in hudson-behaviour.js where the name was an empty string ("") which is not null but should probably still not be set on the element.
I have a created a pull request for this. It works locally for me, I hope I haven't broken anything. Attributes without value will no longer be set on buttons, which seems safe to me.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24050) All slaves disconnect and no new slaves can connect due to CancelledKeyException in org.jenkinsci.remoting
Kevin Browder commented on JENKINS-24050 All slaves disconnect and no new slaves can connect due to CancelledKeyException in org.jenkinsci.remoting @James: So I think the closed channel exception is actually closer to the Jenkins-22932 bug (if so you should repopen, since I had reopened before realizing I had a different root cause I then closed). However one could argue that the "selector" loop should actually catch all NIO errors and try again instead of it's current behavior of killing the loop entirely so it might be the case that the fix ends up being the same. Additionally I've implemented a patch that implements the key.isValid() check above: https://github.com/kbrowder/remoting/commit/e2fae6f798480cef1753cd3a1fe8d49d7dcd528e I've not had a chance to test this out though (not sure how I would, need to figure out the unittests). Additionally I think changing how the error checking is done might be a safer strategy and it might fix both issues. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [discard-old-build] (JENKINS-24072) Should allow to set global defaults retention policy for all jobs
Sam Xiao created JENKINS-24072 Should allow to set global defaults retention policy for all jobs Issue Type: New Feature Assignee: nkns165 Components: discard-old-build Created: 31/Jul/14 9:26 PM Description: Although this is a very nice plugin, but it would be nice if this setting can take 1 step further into the global default settings, so if we have 1000 jobs, we don't have to manually set it for 1000 jobs for each job on the retention policy Project: Jenkins Priority: Major Reporter: Sam Xiao This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [docker-build-step] (JENKINS-24071) Docker build step tries to build on master and not slave
Hack Kampbjørn created JENKINS-24071 Docker build step tries to build on master and not slave Issue Type: Bug Assignee: vjuranek Components: docker-build-step Created: 31/Jul/14 9:05 PM Description: When running a Docker build step create image command on a slave it tries to run it on the master 21:15:04 Building remotely on pollux (twins) in workspace /var/lib/jenkins/workspace/oracle-java7/jenkins-slave-docker ... 21:15:11 FATAL: configured dockerFolder '/var/lib/jenkins/workspace/oracle-java7/jenkins-slave-docker/' does no exist. 21:15:11 java.lang.IllegalArgumentException: configured dockerFolder '/var/lib/jenkins/workspace/oracle-java7/jenkins-slave-docker/' does no exist. 21:15:11 at org.jenkinsci.plugins.dockerbuildstep.cmd.CreateImageCommand.execute(CreateImageCommand.java:85) 21:15:11 at org.jenkinsci.plugins.dockerbuildstep.DockerBuilder.perform(DockerBuilder.java:65) Manually creating the workspace on master, and it goes one step further 22:52:40 FATAL: configured dockerFolder '/var/lib/jenkins/workspace/oracle-java7/jenkins-slave-docker' does not contain a Dockerfile. 22:52:40 java.lang.IllegalArgumentException: configured dockerFolder '/var/lib/jenkins/workspace/oracle-java7/jenkins-slave-docker' does not contain a Dockerfile. 22:52:40 at org.jenkinsci.plugins.dockerbuildstep.cmd.CreateImageCommand.execute(CreateImageCommand.java:91) 22:52:40 at org.jenkinsci.plugins.dockerbuildstep.DockerBuilder.perform(DockerBuilder.java:65) And creating an empty Dockerfile goes one more step but it keeps trying to build on master and not slave 22:55:56 FATAL: com.kpelykh.docker.client.DockerException: Dockerfile /var/lib/jenkins/workspace/oracle-java7/jenkins-slave-docker/Dockerfile is empty 22:55:56 java.lang.RuntimeException: com.kpelykh.docker.client.DockerException: Dockerfile /var/lib/jenkins/workspace/oracle-java7/jenkins-slave-docker/Dockerfile is empty 22:55:56 at org.jenkinsci.plugins.dockerbuildstep.cmd.CreateImageCommand.execute(CreateImageCommand.java:142) 22:55:56 at org.jenkinsci.plugins.dockerbuildstep.DockerBuilder.perform(DockerBuilder.java:65) Environment: Jenkins master is set to 0 executors and 'leave this node for tied jobs only' Project: Jenkins Labels: docker-build-step docker master slave Priority: Major Reporter: Hack Kampbjørn This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-24008) Jobs stuck while waiting for an executor (and executors are available)
Damien Nozay
commented on JENKINS-24008
Jobs stuck while waiting for an executor (and executors are available)
Jenkins.instance.queue.items.each {
println "queue item " + it.id
it.properties.each { p -> println p }
println "#"
}
gives
Result
queue item 1053
pending=false
searchName=null
causeOfBlockage=Waiting for next available executor on dev-precheckin
searchIndex=hudson.search.FixedSet@75a939b7
stuck=false
inQueueSince=1406839798417
buildable=true
url=""
search=hudson.search.Search@390c59ba
api=hudson.model.Api@59d6df98
blocked=false
class=class hudson.model.Queue$BuildableItem
searchUrl=null
actions=[hudson.model.CauseAction@b2b5830, hudson.model.CauseAction@4aaabd0a, hudson.model.ParametersAction@f6101d2]
params=
bundleUrl=[redacted]
RUNTEST_ARGS=[redacted]
USEEXISTING=0
runtest.cfg=
allActions=[hudson.model.CauseAction@b2b5830, hudson.model.CauseAction@4aaabd0a, hudson.model.ParametersAction@f6101d2]
inQueueForString=5 min 41 sec
causes=[hudson.model.Cause$UserIdCause@6b05930]
future=hudson.model.queue.FutureImpl@4f3075d4
why=Waiting for next available executor on dev-precheckin
assignedLabel=dev-precheckin
displayName=null
#
queue item 1052
pending=false
searchName=null
searchIndex=hudson.search.FixedSet@1ee7ba0f
inQueueSince=1406839386074
buildable=true
url=""
search=hudson.search.Search@7f683ea2
api=hudson.model.Api@14e83f07
blocked=false
class=class hudson.model.Queue$BuildableItem
searchUrl=null
actions=[hudson.model.ParametersAction@259ebb6f, hudson.model.CauseAction@582387b4]
allActions=[hudson.model.ParametersAction@259ebb6f, hudson.model.CauseAction@582387b4]
inQueueForString=12 min
causes=[hudson.model.Cause$UserIdCause@4c6b144b]
future=hudson.model.queue.FutureImpl@2075b176
displayName=null
#
Result: [Lhudson.model.Queue$Item;@1b81ef4a
the item 1052 is causing problems for everything else.
after removing 1052 it works.
some users are able to make it fail 100% of the time.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-24008) Jobs stuck while waiting for an executor (and executors are available)
Damien Nozay
commented on JENKINS-24008
Jobs stuck while waiting for an executor (and executors are available)
Jenkins.instance.queue.items.each { println it.id }
Jenkins.instance.queue.items[0].properties.each { println it }
1052
pending=false
searchName=null
searchIndex=hudson.search.FixedSet@1e171554
inQueueSince=1406839386074
buildable=true
url=""
search=hudson.search.Search@7d794d3a
api=hudson.model.Api@26bd5b31
blocked=false
class=class hudson.model.Queue$BuildableItem
searchUrl=null
actions=[hudson.model.ParametersAction@259ebb6f, hudson.model.CauseAction@582387b4]
allActions=[hudson.model.ParametersAction@259ebb6f, hudson.model.CauseAction@582387b4]
inQueueForString=3 min 9 sec
causes=[hudson.model.Cause$UserIdCause@4c6b144b]
future=hudson.model.queue.FutureImpl@2075b176
displayName=null
Result: {pending=false, searchName=null, searchIndex=hudson.search.FixedSet@1e171554, inQueueSince=1406839386074, buildable=true, url="" search=hudson.search.Search@7d794d3a, api=hudson.model.Api@26bd5b31, blocked=false, class=class hudson.model.Queue$BuildableItem, searchUrl=null, actions=[hudson.model.ParametersAction@259ebb6f, hudson.model.CauseAction@582387b4], allActions=[hudson.model.ParametersAction@259ebb6f, hudson.model.CauseAction@582387b4], inQueueForString=3 min 9 sec, causes=[hudson.model.Cause$UserIdCause@4c6b144b], future=hudson.model.queue.FutureImpl@2075b176, displayName=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] [p4] (JENKINS-24070) Error: Wipe Out Workspace blocked by SCM
Grant Limberg created JENKINS-24070 Error: Wipe Out Workspace blocked by SCM Issue Type: Bug Affects Versions: current Assignee: Paul Allen Components: p4 Created: 31/Jul/14 8:45 PM Description: It seems the P4 plugin is blocking requests to wipe out workspaces in Jenkins. Unfortunately, this is a necessity in some instances. The other Perforce plugin for Jenkins (https://wiki.jenkins-ci.org/display/JENKINS/Perforce+Plugin) will allow workspaces to be wiped, and then automatically does a force sync of the full p4 workspace on the next build. This issue and JENKINS-24025 are the only things blocking me from rolling out this P4 plugin across our build farm. In my testing of it thus far, it does seem to work better overall. Project: Jenkins Priority: Major Reporter: Grant Limberg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-24050) All slaves disconnect and no new slaves can connect due to CancelledKeyException in org.jenkinsci.remoting
Kevin Browder updated JENKINS-24050 All slaves disconnect and no new slaves can connect due to CancelledKeyException in org.jenkinsci.remoting Change By: Kevin Browder (31/Jul/14 8:29 PM) Summary: All slaves disconnect and no new slaves can connect due to CancelledKeyException in org.jenkinsci.remoting This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [github-oauth] (JENKINS-24069) Improve performance by caching and reducing number of github api calls
alex rothenberg created JENKINS-24069 Improve performance by caching and reducing number of github api calls Issue Type: Improvement Assignee: Sam Kottler Components: github-oauth Created: 31/Jul/14 8:17 PM Description: Github pull request #27 On jenkins instances with a large number of jobs the previous implementation got very slow because it made a github api call per job & did not do a great job of caching. This pull reduces the chatter with the github api by asking which repos the user has access to and caching the results. There are 2 big changes in this pull 1. The algorithm now builds and caches a list of "my repositories" It makes these api calls to github: 1. Get list of the non-organization repos user has access to /api/v3/user/repos 2. Get list of organizations with repos user has access to /api/v3/user/orgs. For each organization Get a list of repos in that org user has access to /api/v3/orgs/XXX/repos Because of pagination it sometimes makes several calls to get the full list of repos. 2. Cache list of public repositories for read-only access. For this it still makes an api call per repository but caches the results for all users. On my jenkins instance with ~400 projects this has improved performance from unusable (minutes to load the home page) to pretty fast (~4 seconds as it builds the cache and faster after that). Project: Jenkins Labels: plugin Priority: Major Reporter: alex rothenberg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-24008) Jobs stuck while waiting for an executor (and executors are available)
Damien Nozay commented on JENKINS-24008 Jobs stuck while waiting for an executor (and executors are available) the parameters to the jobs are standard types: 2 string parameters, 1 text parameter, 1 file parameter. querying /queue/api/xml raises java.io.IOException: Failed to write params at org.kohsuke.stapler.export.Property.writeTo(Property.java:120) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:187) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:182) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:182) at org.kohsuke.stapler.export.Property.writeValue(Property.java:232) at org.kohsuke.stapler.export.Property.writeValue(Property.java:169) at org.kohsuke.stapler.export.Property.writeValue(Property.java:137) at org.kohsuke.stapler.export.Property.writeTo(Property.java:114) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:187) at org.kohsuke.stapler.export.Model.writeTo(Model.java:154) at org.kohsuke.stapler.ResponseImpl.serveExposedBean(ResponseImpl.java:267) at hudson.model.Api.doXml(Api.java:97) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:622) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilt
[JIRA] [core] (JENKINS-24008) Jobs stuck while waiting for an executor (and executors are available)
Damien Nozay commented on JENKINS-24008 Jobs stuck while waiting for an executor (and executors are available) Hey Daniel, I'll be in chat, we can summarize our findings after a quick chat. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-24008) Jobs stuck while waiting for an executor (and executors are available)
Daniel Beck commented on JENKINS-24008 Jobs stuck while waiting for an executor (and executors are available) Are you using plugin-provided parameter types, if so, which? How are the builds triggered? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24008) Jobs stuck while waiting for an executor (and executors are available)
Damien Nozay commented on JENKINS-24008 Jobs stuck while waiting for an executor (and executors are available) if I try to go to the /job/runtest/job/DevPrecheckin/api/json url then I get java.io.IOException: Failed to write params at org.kohsuke.stapler.export.Property.writeTo(Property.java:120) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:187) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:182) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:182) at org.kohsuke.stapler.export.Property.writeValue(Property.java:232) at org.kohsuke.stapler.export.Property.writeValue(Property.java:137) at org.kohsuke.stapler.export.Property.writeTo(Property.java:114) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:187) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:182) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:182) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:182) at org.kohsuke.stapler.export.Model.writeTo(Model.java:154) at org.kohsuke.stapler.ResponseImpl.serveExposedBean(ResponseImpl.java:267) at hudson.model.Api.doJson(Api.java:195) at sun.reflect.GeneratedMethodAccessor1554.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:622) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(Abstrac
[JIRA] [core] (JENKINS-24008) Jobs stuck while waiting for an executor (and executors are available)
Damien Nozay updated JENKINS-24008 Jobs stuck while waiting for an executor (and executors are available) after scheduling another build, build history is still stuck, please note how it changed the numbers – the new queued item was inserted as #275 Change By: Damien Nozay (31/Jul/14 7:46 PM) Attachment: Screen Shot 2014-07-31 at 12.42.39 PM.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-24008) Jobs stuck while waiting for an executor (and executors are available)
Damien Nozay updated JENKINS-24008 Jobs stuck while waiting for an executor (and executors are available) build history with items stuck Change By: Damien Nozay (31/Jul/14 7:44 PM) Attachment: Screen Shot 2014-07-31 at 12.42.01 PM.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] [email-ext] (JENKINS-24063) Would be nice to have a "console" output area for template testing
Alex Earl updated JENKINS-24063 Would be nice to have a "console" output area for template testing Change By: Alex Earl (31/Jul/14 7:43 PM) Summary: Would be nice to have a "console" output are area for template 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-24063) Would be nice to have a "console" output are for template testing
Alex Earl updated JENKINS-24063 Would be nice to have a "console" output are for template testing Changing title to reflect a desire to have a "console" for debug messages when testing templates. Change By: Alex Earl (31/Jul/14 7:41 PM) Summary: How do I write Would be nice to job's have a " console " output from $SCRIPT Template are for template testing Component/s: email-ext Component/s: email-ext-template This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-template] (JENKINS-24063) How do I write to job's console output from $SCRIPT Template
Alex Earl commented on JENKINS-24063 How do I write to job's console output from $SCRIPT Template I think it would be good to have a console on the template testing page though, just for debug purposes. So, I'm going to retitle this issue and keep it open. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-24068) Plugin is unable to find UFT Test stored in shared drive, if path of the test cases is having spaces
Sumeet Kushwah created JENKINS-24068 Plugin is unable to find UFT Test stored in shared drive, if path of the test cases is having spaces Issue Type: Bug Affects Versions: current Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 31/Jul/14 7:29 PM Description: Plugin is unable to find the test case, when the path of the test case is having spaces in it. I tried moving all of the test cases to the shared drive and the parent folder path was having multiple white spaces. When i tried building the job, error was generated " File/Folder not found:". Due Date: 01/Jul/15 12:00 AM Project: Jenkins Priority: Major Reporter: Sumeet Kushwah This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [repository-connector] (JENKINS-23946) Artifact Resolver failed to expand tokens for [Artifact...
David Ishee commented on JENKINS-23946 Artifact Resolver failed to expand tokens for [Artifact... I'm seeing the same error too using parameters. Here is my stacktrace: java.lang.ClassCastException: hudson.model.StringParameterValue cannot be cast to org.jvnet.hudson.plugins.repositoryconnector.VersionParameterValue at org.jvnet.hudson.plugins.repositoryconnector.ArtifactResolver.checkVersionOverride(ArtifactResolver.java:183) at org.jvnet.hudson.plugins.repositoryconnector.ArtifactResolver.download(ArtifactResolver.java:127) at org.jvnet.hudson.plugins.repositoryconnector.ArtifactResolver.perform(ArtifactResolver.java:101) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:756) at hudson.model.Build$BuildExecution.build(Build.java:198) at hudson.model.Build$BuildExecution.doRun(Build.java:159) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1706) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:232) failed to expand tokens for [Artifact $MAVEN_GROUP:$ARTIFACT_ID:zip:dist-LMI:$VERSION] java.lang.ClassCastException: hudson.model.StringParameterValue cannot be cast to org.jvnet.hudson.plugins.repositoryconnector.VersionParameterValue at org.jvnet.hudson.plugins.repositoryconnector.ArtifactResolver.checkVersionOverride(ArtifactResolver.java:183) at org.jvnet.hudson.plugins.repositoryconnector.ArtifactResolver.download(ArtifactResolver.java:127) at org.jvnet.hudson.plugins.repositoryconnector.ArtifactResolver.perform(ArtifactResolver.java:101) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:756) at hudson.model.Build$BuildExecution.build(Build.java:198) at hudson.model.Build$BuildExecution.doRun(Build.java:159) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1706) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:232) Build step 'Artifact Resolver' marked build as failure This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-template] (JENKINS-24063) How do I write to job's console output from $SCRIPT Template
Frank Merrow commented on JENKINS-24063 How do I write to job's console output from $SCRIPT Template !!! You are right . . . listener works just fine in a build . . . I've been working “around” the fact I didn't have a logger in the Template for months now . . . When I started this project last December . . . I was a real Jenkins newb . . . how telling how I came to this conclusion . . . THANK YOU for pointing up the obvious. Frank This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-24067) Handling partial anonymous bind failures gracefully
Kohsuke Kawaguchi commented on JENKINS-24067 Handling partial anonymous bind failures gracefully My internal ticket number for this is ZD-19640 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-24067) Handling partial anonymous bind failures gracefully
Kohsuke Kawaguchi created JENKINS-24067 Handling partial anonymous bind failures gracefully Issue Type: Improvement Assignee: Unassigned Components: active-directory Created: 31/Jul/14 6:51 PM Description: While talking to one of the users troubleshooting their problem, I discovered that an AD forest can be set up such that the top-level domain does allow anonymous binds, but sub-domains do not. In such a situation, the anonymous bind will succeed, but when Jenkins tries to locate any users in it, it'll not find them, as users are all defined in sub-domains. As a result, any attempt to ActiveDirectoryUnixAuthenticationProvider.retrieveUser(name,null) (i.e., loading user without having his password) will fail with UsernameNotFoundException and not UserMayOrMayNotExistException. This makes Jenkins believe that it has positively determined that the user no longer exists in AD, and thus refuses to let the user login with API token, even if the API token matches up. Jenkins' behaviour is reasonable here, as this is the only situation where Jenkins can positively determine that the user do not exist. If we treat this situation as UserMayOrMayNotExistException, there will never be UsernameNotFoundException, and we'll end up allowing users to login via API token even after he was removed from AD — a security hole. I'm not sure how to address this, but leaving this as an open issue to see if other people are impacted by this, and see if we can come up with some compromise to avoid this kind of hard-to-diagnose problems. Project: Jenkins Priority: Major Reporter: Kohsuke Kawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24062) Icons in context menu broken
dogfood commented on JENKINS-24062 Icons in context menu broken Integrated in jenkins_main_trunk #3570 [FIXED JENKINS-24062] Icons in context menu broken (Revision 4fd154eee9153142c7fd308a12f48afdb0956f3b) Result = SUCCESS tom.fennelly : 4fd154eee9153142c7fd308a12f48afdb0956f3b Files : core/src/main/resources/lib/layout/task.jelly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-22525) "incompatible InnerClasses attribute" error in IBM J9 VM
dogfood commented on JENKINS-22525 "incompatible InnerClasses attribute" error in IBM J9 VM Integrated in jenkins_main_trunk #3569 [FIXED JENKINS-22525] (Revision 4e23793f62aa5019226f2ba96f8063f01affeb92) Result = SUCCESS kohsuke : 4e23793f62aa5019226f2ba96f8063f01affeb92 Files : pom.xml core/pom.xml changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-22525) "incompatible InnerClasses attribute" error in IBM J9 VM
Kohsuke Kawaguchi
edited a comment on JENKINS-22525
"incompatible InnerClasses attribute" error in IBM J9 VM
As for ItemList not in the InnerClasses attribute, I'm discovering with the following test case that if a nested/inner class is marked as private, it does not get recorded in the InnerClasses attribute:
public class App
{
private static class Foo {}
private class Bar {}
static class Alpha {}
class Bravo {}
public static void main( String[] args )
{
System.out.println(Foo.class.getEnclosingClass());
System.out.println(Bar.class.getEnclosingClass());
System.out.println(Alpha.class.getEnclosingClass());
System.out.println(Bravo.class.getEnclosingClass());
}
}
Classfile /files/kohsuke/ws/jenkins/investigations/JENKINS-22525/jenkins22525/target/classes/test/App.class
Last modified Jul 31, 2014; size 1158 bytes
MD5 checksum 264ed3611a578e1a4c8e2d4e0ea8b378
Compiled from "App.java"
public class test.App
SourceFile: "App.java"
InnerClasses:
#11= #8 of #9; //Bravo=class test/App$Bravo of class test/App
static #13= #7 of #9; //Alpha=class test/App$Alpha of class test/App
RuntimeInvisibleAnnotations:
0: #57()
minor version: 0
major version: 49
flags: ACC_PUBLIC, ACC_SUPER
Classfile /files/kohsuke/ws/jenkins/investigations/JENKINS-22525/jenkins22525/target/classes/test/App$Foo.class
Last modified Jul 31, 2014; size 303 bytes
MD5 checksum 3f4b082e8d8c5cbf85d4afeb7807b253
Compiled from "App.java"
class test.App$Foo
SourceFile: "App.java"
minor version: 0
major version: 49
flags: ACC_SUPER
Classfile /files/kohsuke/ws/jenkins/investigations/JENKINS-22525/jenkins22525/target/classes/test/App$Alpha.class
Last modified Jul 31, 2014; size 309 bytes
MD5 checksum df99610f5b28798c5f07f308b749df89
Compiled from "App.java"
class test.App$Alpha
SourceFile: "App.java"
InnerClasses:
static #10= #2 of #16; //Alpha=class test/App$Alpha of class test/App
minor version: 0
major version: 49
flags: ACC_SUPER
This seems to violate JVM spec of the InnerClass attribute. J9 VM accepts this without reporting an error. In this case I don't understand how JVM can correctly determine that App$Foo has an enclosing class. From the byte code, there's no way to distinguish this vs compiling the following class:
class App {}
class App$Foo {} // '$' is a legal character in a class name in Java
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22525) "incompatible InnerClasses attribute" error in IBM J9 VM
Kohsuke Kawaguchi
commented on JENKINS-22525
"incompatible InnerClasses attribute" error in IBM J9 VM
As for ItemList not in the InnerClasses attribute, I'm discovering with the following test case that if a nested/inner class is marked as private, it does not get recorded in the InnerClasses attribute:
public class App
{
private static class Foo {}
private class Bar {}
static class Alpha {}
class Bravo {}
public static void main( String[] args )
{
System.out.println(Foo.class.getEnclosingClass());
System.out.println(Bar.class.getEnclosingClass());
System.out.println(Alpha.class.getEnclosingClass());
System.out.println(Bravo.class.getEnclosingClass());
}
}
Classfile /files/kohsuke/ws/jenkins/investigations/JENKINS-22525/jenkins22525/target/classes/test/App.class
Last modified Jul 31, 2014; size 1158 bytes
MD5 checksum 264ed3611a578e1a4c8e2d4e0ea8b378
Compiled from "App.java"
public class test.App
SourceFile: "App.java"
InnerClasses:
#11= #8 of #9; //Bravo=class test/App$Bravo of class test/App
static #13= #7 of #9; //Alpha=class test/App$Alpha of class test/App
RuntimeInvisibleAnnotations:
0: #57()
minor version: 0
major version: 49
flags: ACC_PUBLIC, ACC_SUPER
Classfile /files/kohsuke/ws/jenkins/investigations/JENKINS-22525/jenkins22525/target/classes/test/App$Foo.class
Last modified Jul 31, 2014; size 303 bytes
MD5 checksum 3f4b082e8d8c5cbf85d4afeb7807b253
Compiled from "App.java"
class test.App$Foo
SourceFile: "App.java"
minor version: 0
major version: 49
flags: ACC_SUPER
Classfile /files/kohsuke/ws/jenkins/investigations/JENKINS-22525/jenkins22525/target/classes/test/App$Alpha.class
Last modified Jul 31, 2014; size 309 bytes
MD5 checksum df99610f5b28798c5f07f308b749df89
Compiled from "App.java"
class test.App$Alpha
SourceFile: "App.java"
InnerClasses:
static #10= #2 of #16; //Alpha=class test/App$Alpha of class test/App
minor version: 0
major version: 49
flags: ACC_SUPER
This seems to violate JVM spec of the InnerClass attribute. J9 VM accepts this without reporting an error.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [mansion-cloud] (JENKINS-24066) Can't create a New Slave Template from the existing DEV@cloud slave templates
Tracy Kennedy created JENKINS-24066 Can't create a New Slave Template from the existing DEV@cloud slave templates Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: Screen Shot 2014-07-31 at 1.17.57 PM.png Components: mansion-cloud Created: 31/Jul/14 5:15 PM Description: When I try to copy the "DEV@cloud Standard Linux" template, I get an error that that template doesn't exist. Project: Jenkins Labels: template slave cloudbees dev@cloud Priority: Minor Reporter: Tracy Kennedy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-24062) Icons in context menu broken
SCM/JIRA link daemon commented on JENKINS-24062 Icons in context menu broken Code changed in jenkins User: tfennelly Path: core/src/main/resources/lib/layout/task.jelly http://jenkins-ci.org/commit/jenkins/4fd154eee9153142c7fd308a12f48afdb0956f3b Log: [FIXED JENKINS-24062] Icons in context menu broken This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-24062) Icons in context menu broken
SCM/JIRA link daemon resolved JENKINS-24062 as Fixed Icons in context menu broken Change By: SCM/JIRA link daemon (31/Jul/14 5:14 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] [email-ext-template] (JENKINS-24063) How do I write to job's console output from $SCRIPT Template
Alex Earl commented on JENKINS-24063 How do I write to job's console output from $SCRIPT Template Are you trying to get logs during template testing? I could possibly add a console, but there currently isn't any rendering. When you run an actual build, the listener object should work just fine. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [s3] (JENKINS-23432) S3 publisher fails with "String index out of range" error
Trey Duskin commented on JENKINS-23432 S3 publisher fails with "String index out of range" error I have this problem as well. It seems to happen when I specify multiple files separated by commas in the Source field. If I leave it blank or only specify one fileset, the upload works fine. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-template] (JENKINS-24063) How do I write to job's console output from $SCRIPT Template
Frank Merrow commented on JENKINS-24063 How do I write to job's console output from $SCRIPT Template It is just inconceivable to me that given I have the build object . . . I cannot SOMEHOW jump to the console logger for that build. I haven't figured it out yet . . . which matches your suggestion it cannot be done . . . but it just seems like it "should be" possible. Frank This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-22525) Jenkins global configuration unreadable on IBM J9 (so slaves lost)
Kohsuke Kawaguchi commented on JENKINS-22525 Jenkins global configuration unreadable on IBM J9 (so slaves lost) Code change in bridge-method-injector This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-22525) "incompatible InnerClasses attribute" error in IBM J9 VM
Jesse Glick updated JENKINS-22525 "incompatible InnerClasses attribute" error in IBM J9 VM Change By: Jesse Glick (31/Jul/14 4:56 PM) Labels: java-ibm lts-candidate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-22525) "incompatible InnerClasses attribute" error in IBM J9 VM
Kohsuke Kawaguchi updated JENKINS-22525 "incompatible InnerClasses attribute" error in IBM J9 VM Changed the title to accurately capture the issue. Change By: Kohsuke Kawaguchi (31/Jul/14 4:53 PM) Summary: Jenkins global configuration unreadable on "incompatible InnerClasses attribute" error in IBM J9 (so slaves lost) VM 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] [core] (JENKINS-22525) Jenkins global configuration unreadable on IBM J9 (so slaves lost)
Jesse Glick commented on JENKINS-22525 Jenkins global configuration unreadable on IBM J9 (so slaves lost) Also it seems like https://bugs.openjdk.java.net/browse/JDK-6746955 and https://bugs.openjdk.java.net/browse/JDK-8015927 might be the more relevant issues. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-22525) Jenkins global configuration unreadable on IBM J9 (so slaves lost)
SCM/JIRA link daemon resolved JENKINS-22525 as Fixed Jenkins global configuration unreadable on IBM J9 (so slaves lost) Change By: SCM/JIRA link daemon (31/Jul/14 4:48 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22525) Jenkins global configuration unreadable on IBM J9 (so slaves lost)
SCM/JIRA link daemon commented on JENKINS-22525 Jenkins global configuration unreadable on IBM J9 (so slaves lost) Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html core/pom.xml pom.xml http://jenkins-ci.org/commit/jenkins/4e23793f62aa5019226f2ba96f8063f01affeb92 Log: [FIXED JENKINS-22525] Integrated a bridge-method-injector that rebuilds the constant pool from scratch. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-22525) Jenkins global configuration unreadable on IBM J9 (so slaves lost)
Jesse Glick commented on JENKINS-22525 Jenkins global configuration unreadable on IBM J9 (so slaves lost) More useful bug link: https://bugs.openjdk.java.net/browse/JDK-5053846 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-template] (JENKINS-24063) How do I write to job's console output from $SCRIPT Template
Frank Merrow commented on JENKINS-24063 How do I write to job's console output from $SCRIPT Template While I have been on the list for while (jenkins-users of whatever it is called), the message never got posted . . . so I assume I am stuck behind some moderator. I am not against posting code, but there is a LOT of it AND . . . I'm not sure it helps. The Groovy Template is fairly complex, creating a custom GroovyClassLoader() to go find some classes, create objects and then make calls on those object to create the email body. Having said all of that though, for the purposes of this discussion, it basically comes down to this for a template: <% how to I write to the job's console output here? %> The "out" variable writes directly into the email body. "listener" was set by EmailExtTemplateAction to TaskListener.NUL at the call to ScriptContent.evaluate() . . . so while there is a listener variable given to the template, it doesn't seem useful. None of the other variable provided by StriptContent() seem helpful either: build, listener, it, rooturl and project. So I am looking for a way to put a few lines of output into the job's console output given the environment shown above . . . my code is pretty much irrelevant to the question. If you have a solution for the template shown above, it will work in my environment as well. Frank This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-template] (JENKINS-24063) How do I write to job's console output from $SCRIPT Template
Alex Earl commented on JENKINS-24063 How do I write to job's console output from $SCRIPT Template There is no log when using template testing sadly. The listener is set to a valid listener object when running under an actual job. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-24055) Matrix Job Unable To Sync
Ryan Hummer commented on JENKINS-24055 Matrix Job Unable To Sync yes we use slaves nodes. We never run any jobs on our master node. I'll see if I can find anything in the logs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [crowd2] (JENKINS-23208) Backtrace when trying to use 'remember me' with latest crowd auth plugin
Kanstantsin Shautsou commented on JENKINS-23208 Backtrace when trying to use 'remember me' with latest crowd auth plugin Added one more fix, please test this https://jenkins.ci.cloudbees.com/job/plugins/job/crowd2-plugin/20/org.jenkins-ci.plugins$crowd2/ hpi build and reply wether you use sso and what jenkins version you have. If everything ok i will release new 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] [p4] (JENKINS-24055) Matrix Job Unable To Sync
Paul Allen commented on JENKINS-24055 Matrix Job Unable To Sync I'm unable to reproduce this with a simple setup (all running on the master). Do you use slave nodes? Are they pinned in any way? Please can you see if there are any clues in the Jenkins log (stack trace etc...) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-22525) Jenkins global configuration unreadable on IBM J9 (so slaves lost)
Kohsuke Kawaguchi commented on JENKINS-22525 Jenkins global configuration unreadable on IBM J9 (so slaves lost) Relevant StackOverflow thread and BugParade entry, which indicates the fix to javac made it into JDK8 b92. Looks like J9 VM is failing to handle this rare situation correctly. I think I'll work around this problem in bridge method injector to reshuffle constant pools and eliminate duplicates. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-24064) war-for-test makes for excessively large artifacts of Jenkins core
Daniel Beck commented on JENKINS-24064 war-for-test makes for excessively large artifacts of Jenkins core Since the checksums are identical, Artifactory deduplicates. Check the filestore, they're stored by checksum. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-24064) war-for-test makes for excessively large artifacts of Jenkins core
Daniel Beck edited a comment on JENKINS-24064 war-for-test makes for excessively large artifacts of Jenkins core Since the checksums are identical, Artifactory deduplicates. Check the filestore, they're stored by checksum. But Maven isn't as clever... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-template] (JENKINS-24063) How do I write to job's console output from $SCRIPT Template
Alex Earl commented on JENKINS-24063 How do I write to job's console output from $SCRIPT Template I never saw your request on the mailing list, which list did you send it to? Just to verify you are using the listener object provided to the template, correct? Can you show some example code? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-template] (JENKINS-24063) How do I write to job's console output from $SCRIPT Template
Frank Merrow commented on JENKINS-24063 How do I write to job's console output from $SCRIPT Template In general, I agree. I did that . . . no answer. The best solution I have at this time is for the Groovy Script Template to create a JSON file, that can then be picked up by the pre-send script and directed to the console. That solution doesn't set well with me though . . . but at this time it is the best I've got. Frank This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [artifactory] (JENKINS-24065) I wiil be glad to get Daily status report on the various metrics, such as cyclomatic complexity (CCM) , number of errors (CPP), e.t.c.
Ruslan Babayev created JENKINS-24065 I wiil be glad to get Daily status report on the various metrics, such as cyclomatic complexity (CCM) , number of errors (CPP), e.t.c. Issue Type: New Feature Assignee: yossis Components: artifactory Created: 31/Jul/14 3:59 PM Description: I would like this report organized in an easy-to-read (probably tabular) format. Due Date: 31/Jul/14 12:00 AM Environment: Code Analysis, Source Monitor Project: Jenkins Priority: Trivial Reporter: Ruslan Babayev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-24064) war-for-test makes for excessively large artifacts of Jenkins core
Jesse Glick created JENKINS-24064 war-for-test makes for excessively large artifacts of Jenkins core Issue Type: Task Assignee: Unassigned Components: core Created: 31/Jul/14 3:55 PM Description: The war-for-test artifact is used so that functional tests in plugins can have jenkins.war of the selected version in their classpath, thus letting the WAR exploder do its work. Yet this means that the space consumption in the Maven repository for each release is considerably larger than it really should be, since we store the 65Mb WAR twice! Should explore whether there is some other means of locating jenkins.war that does not involve making a full copy. Can we store a placeholder JAR and have WarExploder look up jenkins.war using a relative path in the local repository? (And is there some way to force the WAR to be downloaded by the time the rest runs?) Or can the handler for the primary WAR artifact be customized to mark it as being valid to include in classpaths? Project: Jenkins Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-template] (JENKINS-24063) How do I write to job's console output from $SCRIPT Template
Alex Earl commented on JENKINS-24063 How do I write to job's console output from $SCRIPT Template In general, for questions, it is best to use the mailing list. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-template] (JENKINS-24063) How do I write to job's console output from $SCRIPT Template
Frank Merrow created JENKINS-24063 How do I write to job's console output from $SCRIPT Template Issue Type: Task Assignee: Alex Earl Components: email-ext-template Created: 31/Jul/14 3:37 PM Description: I can "get by" inside the Jenkins JVM, but I am no guru. So I am in the middle of my Groovy Template and need to log a few lines of output into the job's console output. I have the build variable and it seems to me that from there I should be able to find the console . . . but I have yet to figure that out (if it is possible at all). The logger you passed me seems to be TaskLister.NULL, so that isn't useful. Your ExtendedEmailPublisherContext contains a pointer to the Listener . . . but there is no way to get to that instance that I can see, though if I am wrong, please enlighten me. It doesn't have to be pretty . . . I am willing to jump from object to object to find the damn thing, I just have yet to figure out a path to it. I have thought of going back up to the project and searching out the EmailExt plugin from there, but I doubt that will be helpful because it won't be a "build specific" copy. Though perhaps having found that, there is a way to jump to the build specific copy . . . if so please. If there is a way . . . please enlighten me. Frank Project: Jenkins Priority: Major Reporter: Frank Merrow This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-23762) Adding a mixin class to Job leaks memory from every DSL run
Jesse Glick commented on JENKINS-23762 Adding a mixin class to Job leaks memory from every DSL run Right, monkey-patching seems to not introduce a leak (though it could lead to race conditions and inter-script interference); it is mixins which are really problematic. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-24046) Updating a WAR should unpin a plugin which is now older than the bundled plugin
Jesse Glick commented on JENKINS-24046 Updating a WAR should unpin a plugin which is now older than the bundled plugin Well, by the time an admin sees that, you are already either running a possibly fatal mismatch of versions, or have rejected the combination (JENKINS-21486) and so have disabled the dependent plugin. Better for Jenkins to try to fix the problem immediately, and perhaps issue a warning later about what it did, than to knowingly run a broken configuration. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-24050) All slaves disconnect and no new slaves can connect CancelledKeyException in org.jenkinsci.remoting
Jesse Glick updated JENKINS-24050 All slaves disconnect and no new slaves can connect CancelledKeyException in org.jenkinsci.remoting Change By: Jesse Glick (31/Jul/14 3:26 PM) Assignee: Kohsuke Kawaguchi Component/s: core Component/s: slave-status This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-24051) Move icon shim plugin out into a repo of its own
Jesse Glick commented on JENKINS-24051 Move icon shim plugin out into a repo of its own Sure, core/pom.xml shows plenty of dependencies on libraries elsewhere in the jenkinsci org (or even other orgs, like kohsuke). So long as the dependency is not expected to be constantly changing (and in conjunction with changes to jenkins source files), this is fine. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-22008) buildTimeTrend only shows the last 20 builds
Jesse Glick commented on JENKINS-22008 buildTimeTrend only shows the last 20 builds Should also stop firing off ~40 AJAX requests in parallel the way it does now, which probably saturates request handling threads, and may increase contention. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-24062) Icons in context menu broken
Tom FENNELLY created JENKINS-24062 Icons in context menu broken Issue Type: Bug Assignee: Tom FENNELLY Components: core Created: 31/Jul/14 2:31 PM Project: Jenkins Labels: user-experience Priority: Major Reporter: Tom FENNELLY This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-24051) Move icon shim plugin out into a repo of its own
Tom FENNELLY commented on JENKINS-24051 Move icon shim plugin out into a repo of its own At the moment, Jenkins core has a dependency on the code in ui-ext/icon/module. This dependency may go away if we move Jenkins core to using CSS based icons (something I was planning on doing). For now though, lets assume the dep will not go away. Is there a dependency pattern like this already i.e. Jenkins core having a dependency on other Jenkins artifacts that do not live in https://github.com/jenkinsci/jenkins (i.e. live somewhere else in https://github.com/jenkinsci)? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [scm-sync-configuration] (JENKINS-24060) Is it possible to backup the "nextBuildNumber" for each project?
alex rothenberg resolved JENKINS-24060 as Not A Defect Is it possible to backup the "nextBuildNumber" for each project? Apologies for creating in jira where it does not belong. Change By: alex rothenberg (31/Jul/14 2:22 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] [core] (JENKINS-22525) Jenkins global configuration unreadable on IBM J9 (so slaves lost)
Kohsuke Kawaguchi commented on JENKINS-22525 Jenkins global configuration unreadable on IBM J9 (so slaves lost) Just for the sake of completeness I manually patched Queue.class after transformation to have its classFile.this_class index points to #283, not #400, and now J9 VM is happy. Wow. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [repository-connector] (JENKINS-23946) Artifact Resolver failed to expand tokens for [Artifact...
hcguersoy commented on JENKINS-23946 Artifact Resolver failed to expand tokens for [Artifact... Hi, the same issue here, too. We use a parameter for the version field (which comes from ParametriziedTriggerPlugin). Now the build fails with a error that it can't cast from StringParameterValue to VersionParameterValue. We now downgraded to 0.8.2 as 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] [core] (JENKINS-24051) Move icon shim plugin out into a repo of its own
Jesse Glick commented on JENKINS-24051 Move icon shim plugin out into a repo of its own In fact I think the whole ui-ext subdirectory should be in its own repo with its own version numbering scheme. Also the artifactId of the plugin should not end in -plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-24060) Is it possible to backup the "nextBuildNumber" for each project?
Daniel Beck
updated JENKINS-24060
Is it possible to backup the "nextBuildNumber" for each project?
FYI, Jira is not a support site. If you have a question, IRC or the jenkinsci-users list would be more appropriate.
Change By:
Daniel Beck
(31/Jul/14 1:46 PM)
Description:
I would like to backup the nextBuildNumber file for each project so I can recreate my jenkins master if it blows up. I've tried including
"
{code}
**/jobs/*/nextBuildNumber
"
{code}
on the configure system page but it doesn't seem to work.Am I doing something wrong or is this not supported?Thank you for creating this plugin
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-24060) Is it possible to backup the "nextBuildNumber" for each project?
alex rothenberg created JENKINS-24060 Is it possible to backup the "nextBuildNumber" for each project? Issue Type: Bug Assignee: Frédéric Camblor Components: scm-sync-configuration Created: 31/Jul/14 1:34 PM Description: I would like to backup the nextBuildNumber file for each project so I can recreate my jenkins master if it blows up. I've tried including "*/jobs//nextBuildNumber" on the configure system page but it doesn't seem to work. Am I doing something wrong or is this not supported? Thank you for creating this plugin Environment: SUSE Linux Enterprise Server 11 (x86_64) VERSION = 11 PATCHLEVEL = 3 Jenkins ver. 1.532.1 Project: Jenkins Labels: plugin Priority: Major Reporter: alex rothenberg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-22525) Jenkins global configuration unreadable on IBM J9 (so slaves lost)
Kohsuke Kawaguchi
commented on JENKINS-22525
Jenkins global configuration unreadable on IBM J9 (so slaves lost)
After looking further into javap source code, I discovered why the following difference in the output happens:
- 1: getfield #2 // Field buildables:Lhudson/model/Queue$ItemList;
+ 1: getfield #2 // Field hudson/model/Queue.buildables:Lhudson/model/Queue$ItemList;
When printing the content of constant pool for these instructions, javap attempts to simplify the reference within the same class by omitting the class name as follows:
int tag = cpInfo.getTag();
switch (tag) {
case CONSTANT_Methodref:
case CONSTANT_InterfaceMethodref:
case CONSTANT_Fieldref:
// simplify references within this class
CPRefInfo ref = (CPRefInfo) cpInfo;
try {
if (ref.class_index == classFile.this_class)
cpInfo = classFile.constant_pool.get(ref.name_and_type_index);
} catch (ConstantPool.InvalidIndex e) {
// ignore, for now
}
}
print(tagName(tag) + " " + stringValue(cpInfo));
This check compares the constant pool index, not the actual content. The fieldref constant pool remains unchanged at #283.#624 before/after transformation, but classFile.this_class that references the class name itself changes from #283 to #400.
The constant pool entry #400 is "Class #891", just like #283. IOW, javac produces Queue.class that contains two identical constant pool entries, which is suprising.
It is still unclear as to whether this difference in the class file triggers the "incompatible InnerClasses attribute" problem.
I think the next step is to modify class file to insert InnerClass attribute for Queue$ItemList, as the lack of this entry does seem to violate JVM spec. If that is the case, the question remains as to why J9VM was happy with the class before transformation.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [build-user-vars] (JENKINS-18535) Retrieve the users e-mail building the job or promoting the job
Lorelei McCollum commented on JENKINS-18535 Retrieve the users e-mail building the job or promoting the job Is this already done? Wondering when the next release of the plugin will be? From looking in GIT seems it is in the source? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-10131) Git polling shouldn't need a workspace on a slave.
Mark Waite closed JENKINS-10131 as Fixed Git polling shouldn't need a workspace on a slave. Change By: Mark Waite (31/Jul/14 1:03 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] [git] (JENKINS-10131) Git polling shouldn't need a workspace on a slave.
Mark Waite resolved JENKINS-10131 as Fixed Git polling shouldn't need a workspace on a slave. As described in the bug report, this is resolved. The git plugin does not require a workspace for polling, and the default (as of git plugin 2.0) is to not use a workspace for polling. The problems described by Owen Jacobson (and others) still exist for the somewhat more advanced use cases like excluding users, excluding files, and including files, but the basic issue reported by the bug is fixed. Change By: Mark Waite (31/Jul/14 1:03 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] [git] (JENKINS-22547) Git timeout setting does not work for checkout
Mark Waite resolved JENKINS-22547 as Fixed Git timeout setting does not work for checkout Fixed in git plugin 2.2.3, released 31 July 2014 Change By: Mark Waite (31/Jul/14 12:58 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22547) Git timeout setting does not work for checkout
Mark Waite closed JENKINS-22547 as Fixed Git timeout setting does not work for checkout Change By: Mark Waite (31/Jul/14 12:59 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] [git] (JENKINS-20767) Git plugin 2.0: Git polling causes builds even if no changes
Mark Waite closed JENKINS-20767 as Fixed Git plugin 2.0: Git polling causes builds even if no changes Change By: Mark Waite (31/Jul/14 12:57 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] [git] (JENKINS-20767) Git plugin 2.0: Git polling causes builds even if no changes
Phil Seremin commented on JENKINS-20767 Git plugin 2.0: Git polling causes builds even if no changes Bingo. Thanks for your comments, and sorry for wasting your time. My pre-build step script includes a version update if code changes are detected. It then commits and pushes the new version to the main Git repo. Therefore before the first build is finished Jenkins is already notified about a new commit (by itself) which it reacts to by starting a second build. At least that's how I understand it now. I have set the job to ignore commits by jenkins user, and will see if the Branch Specifier set to "refs/remotes/origin/master" helps the double build issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-22400) Git timeout on other actions than fetch/clone
Mark Waite commented on JENKINS-22400 Git timeout on other actions than fetch/clone Timeout on checkout is implement in git plugin 2.2.3, released 31 July 2014. Timeout on clean is not yet implemented. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23675) The git plugin is not working correctly when the repository url has job parameter and any repository credentials
Mark Waite closed JENKINS-23675 as Fixed The git plugin is not working correctly when the repository url has job parameter and any repository credentials Fixed in git plugin 2.2.3, released 31 July 2014 Change By: Mark Waite (31/Jul/14 12:45 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] [slave-status] (JENKINS-24050) All slaves disconnect and no new slaves can connect CancelledKeyException in org.jenkinsci.remoting
Kevin Browder
commented on JENKINS-24050
All slaves disconnect and no new slaves can connect CancelledKeyException in org.jenkinsci.remoting
OK so I think the core issue is that org.jenkinsci.remoting.nio.NioChannelHub.java's line 513 is:
if (key.isReadable()) {
where as I think it should be:
if (key.isValid() && key.isReadable()) {
I guess this would fix the issue assuming that selectedKeys().iterator() is thread safe (I don't really know much about nio), actually it probably makes sense just to add a catch to one of the handlers in the same method (I think the one at http://git.io/VtniaQ).
Basically my thoughts as to what's happening is that isReadable is generating a CancelledKeyException which ends up getting caught by the RuntimeException handler (at http://git.io/l-5MhA) which ends up killing the loop and attempts to abort everything, including the selector that's not-valid (which gives the message in the description).
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [slave-status] (JENKINS-22932) Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted
Kevin Browder resolved JENKINS-22932 as Fixed Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted Actually I think what Andy, Patricia and myself are seeing has a separate root cause and is not a regression of this issue per se. See https://issues.jenkins-ci.org/browse/JENKINS-24050 Change By: Kevin Browder (31/Jul/14 12:20 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-20767) Git plugin 2.0: Git polling causes builds even if no changes
Mark Waite commented on JENKINS-20767 Git plugin 2.0: Git polling causes builds even if no changes I don't see many differences between your config.xml and the version I used to test the behaviour. Some of the differences I see (which may be worth you investigating): I enabled "prune stale branches" as an additional behaviour (since I don't like have stale branches lurking in my Jenkins workspaces). If you have stale branches in the Jenkins workspace, that might (conceivably) cause a duplicate build I don't have a Pre-SCM build step. I don't know what's inside the script you use for your Pre-SCM build step, but that might cause enough of a repository change to result in an additional build This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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
Phil Seremin commented on JENKINS-20767 Git plugin 2.0: Git polling causes builds even if no changes I've attached a file. Git Build Data page shows identical information for both normal and duplicate builds. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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
Phil Seremin updated JENKINS-20767 Git plugin 2.0: Git polling causes builds even if no changes Change By: Phil Seremin (31/Jul/14 11:47 AM) Attachment: config.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-19764) Jenkins with custom build record root dir: renaming a job should create the new build record dir if it does not already exist
Daniel Beck
commented on JENKINS-19764
Jenkins with custom build record root dir: renaming a job should create the new build record dir if it does not already exist
It's fairly obvious from the source code diff of the linked issue that the code assumes the parent directory to exist.
I.e. /foo/bar/${ITEM_FULL_NAME} is OK, /foo/bar/${ITEM_FULL_NAME}/baz is not.
Will likely also fail when using Folders plugin so ITEM_FULL_NAME is multiple nested dirs.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [slave-status] (JENKINS-24050) All slaves disconnect and no new slaves can connect CancelledKeyException in org.jenkinsci.remoting
James Noonan commented on JENKINS-24050 All slaves disconnect and no new slaves can connect CancelledKeyException in org.jenkinsci.remoting I was going to raise a second defect, but I think this is similar enough. When the problem occurs, the Slaves Console shows 'Connected'. However, the master shows them all disconnected. The only way to recover so far is to restart Jenkins. We are running Master on WindowsServer2012, on VMWare. We are running about 70 slaves, a mix OSX10.9, Win7, and Linux Sled 11 on VMWare. There are some other variants. We are running Jenkins 1.563. This issue has occurred three times for us. Two cases are independent; one occurred shortly after the first and the JVM was not restarted, so perhaps recovery between the 1st and 2nd time was not complete. We have not identified a trigger cause for this problem. The thread count starts to increase linearly once the problem occurs, but we believe that this is a symptom. In the JavaMelody Monitoring Plugin, there may be a difference between the reported thread number on the machine in two different places. The graph showed 4000 (it was running but down for 30 hours). However, the thread count below showed 400. I believe that the first figure maybe the JVM's count while the second is Jenkins'. In normal operation, we see about 200 threads. (However, we restarted, so I am not 100% sure that this is correct). We see the following messages in the error log. The same exception occurs for each of our slaves within a short period of time. Jul 31, 2014 5:13:17 AM jenkins.slaves.JnlpSlaveAgentProtocol$Handler$1 onClosed WARNING: NioChannelHub keys=86 gen=1625477529: Computer.threadPoolForRemoting 58 for + terminated java.io.IOException: Failed to abort at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:184) at org.jenkinsci.remoting.nio.NioChannelHub.abortAll(NioChannelHub.java:599) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:481) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.nio.channels.ClosedChannelException at sun.nio.ch.SocketChannelImpl.shutdownInput(Unknown Source) at sun.nio.ch.SocketAdaptor.shutdownInput(Unknown Source) at org.jenkinsci.remoting.nio.Closeables$1.close(Closeables.java:20) at org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport.closeR(NioChannelHub.java:289) at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport$1.call(NioChannelHub.java:226) at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport$1.call(NioChannelHub.java:224) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:474) ... 6 more In the first case, we also saw ping timeouts occur at about the same time as the problem. These were not present in the other case. On the latest case, there was a single slave losing network connectivity and we saw this exception in advance of when the 'crash' happened. However, I believe this to be a coincidence. The exception occurs in the logs without all slaves losing connectivity from time to time. We see other exceptions in the logs. However, these seem to be related to us shutting down idle machines, or the Disk Usage Util plugin, and seem unrelated. Last week, we increased the load on our machine from about 40-slaves to 70, and also increased the number of jobs. Before this, we had not seen this problem. We are planning to upgrade to take in the (now reopened) fix for 22932. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.googl
[JIRA] [build-failure-analyzer] (JENKINS-24059) NullPointerException on non-existent downstream builds
Stefan Eder commented on JENKINS-24059 NullPointerException on non-existent downstream builds Pull request: https://github.com/jenkinsci/build-failure-analyzer-plugin/pull/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] [core] (JENKINS-19764) Jenkins with custom build record root dir: renaming a job should create the new build record dir if it does not already exist
Alex Ouzounis commented on JENKINS-19764 Jenkins with custom build record root dir: renaming a job should create the new build record dir if it does not already exist Hi Daniel, Thanks for looking into it. Just for the record I am using Jenkins 1.570 and the rename seems to correctly rename the job but not all builds get moved over. It also throws the exception below though. java.io.IOException: failed to rename /jenkinsBuilds/TEST_rename/builds to /jenkinsBuilds/TEST_rename_test/builds at hudson.model.Job.renameTo(Job.java:621) at hudson.model.Job.doDoRename(Job.java:1403) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) Looking at the actual file system I see: jenkins@XXX:/jenkinsBuilds/TEST_rename$ cd builds/ jenkins@XXX:/jenkinsBuilds/TEST_rename/builds$ ls 1 19 2014-07-30_17-23-04 2014-07-31_09-56-51 2014-07-31_10-26-19 28 lastFailedBuild 10 22014-07-30_17-23-30 2014-07-31_09-57-16 2014-07-31_10-26-40 29 lastStableBuild 11 20 2014-07-30_17-24-08 2014-07-31_09-57-57 2014-07-31_11-12-08 3 lastSuccessfulBuild 12 2014-07-30_16-48-31 2014-07-30_17-24-54 2014-07-31_10-05-06 21 30 lastUnstableBuild 13 2014-07-30_17-07-42 2014-07-31_09-29-30 2014-07-31_10-08-27 22 4 lastUnsuccessfulBuild 14 2014-07-30_17-09-56 2014-07-31_09-30-18 2014-07-31_10-17-19 23 5 15 2014-07-30_17-11-57 2014-07-31_09-42-30 2014-07-31_10-19-40 24 6 16 2014-07-30_17-12-39 2014-07-31_09-51-33 2014-07-31_10-21-26 25 7 17 2014-07-30_17-14-08 2014-07-31_09-54-51 2014-07-31_10-22-25 26 8 18 2014-07-30_17-22-21 2014-07-31_09-55-25 2014-07-31_10-24-56 27 9 ... jenkins@XXX:/jenkinsBuilds$ cd TEST_rename_test/ jenkins@XXX:/jenkinsBuilds/TEST_rename_test$ ls builds jenkins@XXX:/jenkinsBuilds/TEST_rename_test$ cd builds/ jenkins@XXX:/jenkinsBuilds/TEST_rename_test/builds$ ls 28 30 lastFailedBuild lastStableBuild lastSuccessfulBuild lastUnstableBuild lastUnsuccessfulBuild It is fairly obvious something is going wrong. Manually copying the files sorts out the problem ofcourse. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-19764) Jenkins with custom build record root dir: renaming a job should create the new build record dir if it does not already exist
Alex Ouzounis edited a comment on JENKINS-19764 Jenkins with custom build record root dir: renaming a job should create the new build record dir if it does not already exist Hi Daniel, Thanks for looking into it. Just for the record I am using Jenkins 1.570 and the rename seems to correctly to rename the job but not all builds get moved over. It also throws the exception below though. java.io.IOException: failed to rename /jenkinsBuilds/TEST_rename/builds to /jenkinsBuilds/TEST_rename_test/builds at hudson.model.Job.renameTo(Job.java:621) at hudson.model.Job.doDoRename(Job.java:1403) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) Looking at the actual file system I see: jenkins@XXX:/jenkinsBuilds/TEST_rename$ cd builds/ jenkins@XXX:/jenkinsBuilds/TEST_rename/builds$ ls 1 19 2014-07-30_17-23-04 2014-07-31_09-56-51 2014-07-31_10-26-19 28 lastFailedBuild 10 22014-07-30_17-23-30 2014-07-31_09-57-16 2014-07-31_10-26-40 29 lastStableBuild 11 20 2014-07-30_17-24-08 2014-07-31_09-57-57 2014-07-31_11-12-08 3 lastSuccessfulBuild 12 2014-07-30_16-48-31 2014-07-30_17-24-54 2014-07-31_10-05-06 21 30 lastUnstableBuild 13 2014-07-30_17-07-42 2014-07-31_09-29-30 2014-07-31_10-08-27 22 4 lastUnsuccessfulBuild 14 2014-07-30_17-09-56 2014-07-31_09-30-18 2014-07-31_10-17-19 23 5 15 2014-07-30_17-11-57 2014-07-31_09-42-30 2014-07-31_10-19-40 24 6 16 2014-07-30_17-12-39 2014-07-31_09-51-33 2014-07-31_10-21-26 25 7 17 2014-07-30_17-14-08 2014-07-31_09-54-51 2014-07-31_10-22-25 26 8 18 2014-07-30_17-22-21 2014-07-31_09-55-25 2014-07-31_10-24-56 27 9 ... jenkins@XXX:/jenkinsBuilds$ cd TEST_rename_test/ jenkins@XXX:/jenkinsBuilds/TEST_rename_test$ ls builds jenkins@XXX:/jenkinsBuilds/TEST_rename_test$ cd builds/ jenkins@XXX:/jenkinsBuilds/TEST_rename_test/builds$ ls 28 30 lastFailedBuild lastStableBuild lastSuccessfulBuild lastUnstableBuild lastUnsuccessfulBuild It is fairly obvious something is going wrong. Manually copying the files sorts out the problem ofcourse. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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.
