[JIRA] (JENKINS-11547) Jobs trigger continually even though there are no changes due to git repository being "corrupt"
oliver zemann commented on JENKINS-11547 Jobs trigger continually even though there are no changes due to git repository being "corrupt" This bug is still open. And its the worst bug i have ever seen in jenkins! Is there any workaround expect switching to another CI? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11547) Jobs trigger continually even though there are no changes due to git repository being "corrupt"
oliver zemann commented on JENKINS-11547 Jobs trigger continually even though there are no changes due to git repository being "corrupt" [poll] Last Built Revision: Revision 671bae9b14bb9e65642ec808c2aee5f85aa0f87a (origin/HEAD, origin/master) ERROR: Workspace has a .git repository, but it appears to be corrupt. hudson.plugins.git.GitException: Result has multiple lines at hudson.plugins.git.GitAPI.firstLine(GitAPI.java:307) at hudson.plugins.git.GitAPI.validateRevision(GitAPI.java:281) at hudson.plugins.git.GitAPI.hasGitRepo(GitAPI.java:121) at hudson.plugins.git.GitSCM$1.invoke(GitSCM.java:736) at hudson.plugins.git.GitSCM$1.invoke(GitSCM.java:729) at hudson.FilePath.act(FilePath.java:842) at hudson.FilePath.act(FilePath.java:824) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:729) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) at hudson.scm.SCM.poll(SCM.java:373) at hudson.model.AbstractProject.poll(AbstractProject.java:1363) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(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) No Git repository yet, an initial checkout is required Done. Took 21 sec Changes found thats what i also found on some repo's, maybe it helps to find the problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14194) Stack Trace when going to main configuration page (throttle concurrent build plugin)
mwebber commented on JENKINS-14194 Stack Trace when going to main configuration page (throttle concurrent build plugin) There's no workaround as far as I know - this requires a coding change. I'll assign it to Andrew Bayer (id: abayer), who is listed at https://wiki.jenkins-ci.org/display/JENKINS/Throttle+Concurrent+Builds+Plugin as the plugin maintainer. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14194) Stack Trace when going to main configuration page (throttle concurrent build plugin)
mwebber assigned JENKINS-14194 to abayer Stack Trace when going to main configuration page (throttle concurrent build plugin) Assigning to abayer as the lsited maintained for this plugin. Change By: mwebber (06/Jul/12 7:33 AM) Assignee: abayer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14332) Repeated channel/timeout errors from Jenkins slave
olamy created JENKINS-14332 Repeated channel/timeout errors from Jenkins slave Issue Type: Bug Assignee: Unassigned Components: core Created: 06/Jul/12 9:45 AM Project: Jenkins Priority: Major Reporter: olamy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14332) Repeated channel/timeout errors from Jenkins slave
olamy updated JENKINS-14332 Repeated channel/timeout errors from Jenkins slave Change By: olamy (06/Jul/12 9:47 AM) Priority: Major Blocker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14332) Repeated channel/timeout errors from Jenkins slave
olamy commented on JENKINS-14332 Repeated channel/timeout errors from Jenkins slave happened with recent version Jenkins ver. 1.475-SNAPSHOT stack trace: Started by timer Building remotely on ubuntu1 in workspace /home/jenkins/jenkins-slave/workspace/Qpid-Java-Java-Test-0.16 hudson.util.IOException2: remote file operation failed: /home/jenkins/jenkins-slave/workspace/Qpid-Java-Java-Test-0.16 at hudson.remoting.Channel@22397ea8:ubuntu1 at hudson.FilePath.act(FilePath.java:838) at hudson.FilePath.act(FilePath.java:824) at hudson.FilePath.mkdirs(FilePath.java:890) at hudson.model.AbstractProject.checkout(AbstractProject.java:1243) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:589) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:494) at hudson.model.Run.execute(Run.java:1488) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Caused by: hudson.remoting.ChannelClosedException: channel is already closed at hudson.remoting.Channel.send(Channel.java:492) at hudson.remoting.Request.call(Request.java:129) at hudson.remoting.Channel.call(Channel.java:663) at hudson.FilePath.act(FilePath.java:831) ... 10 more Caused by: java.io.IOException at hudson.remoting.Channel.close(Channel.java:895) at hudson.slaves.ChannelPinger$1.onDead(ChannelPinger.java:110) at hudson.remoting.PingThread.ping(PingThread.java:114) at hudson.remoting.PingThread.run(PingThread.java:81) Caused by: java.util.concurrent.TimeoutException: Ping started on 1341557279424 hasn't completed at 1341557519424 ... 2 more Caused by: java.util.concurrent.TimeoutException at hudson.remoting.Request$1.get(Request.java:275) at hudson.remoting.Request$1.get(Request.java:210) at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59) at hudson.remoting.PingThread.ping(PingThread.java:107) ... 1 more Retrying after 10 seconds hudson.util.IOException2: remote file operation failed: /home/jenkins/jenkins-slave/workspace/Qpid-Java-Java-Test-0.16 at hudson.remoting.Channel@22397ea8:ubuntu1 at hudson.FilePath.act(FilePath.java:838) at hudson.FilePath.act(FilePath.java:824) at hudson.FilePath.mkdirs(FilePath.java:890) at hudson.model.AbstractProject.checkout(AbstractProject.java:1243) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:589) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:494) at hudson.model.Run.execute(Run.java:1488) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Caused by: hudson.remoting.ChannelClosedException: channel is already closed at hudson.remoting.Channel.send(Channel.java:492) at hudson.remoting.Request.call(Request.java:129) at hudson.remoting.Channel.call(Channel.java:663) at hudson.FilePath.act(FilePath.java:831) ... 10 more Caused by: java.io.IOException at hudson.remoting.Channel.close(Channel.java:895) at hudson.slaves.ChannelPinger$1.onDead(ChannelPinger.java:110) at hudson.remoting.PingThread.ping(PingThread.java:114) at hudson.remoting.PingThread.run(PingThread.java:81) Caused by: java.util.concurrent.TimeoutException: Ping started on 1341557279424 hasn't completed at 1341557519424 ... 2 more Caused by: java.util.concurrent.TimeoutException at hudson.remoting.Request$1.get(Request.java:275) at hudson.remoting.Request$1.get(Request.java:210) at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59) at hudson.remoting.PingThread.ping(PingThread.java:107) ... 1 more Retrying after 10 seconds hudson.util.IOException2: remote file operation failed: /home/jenkins/jenkins-slave/workspace/Qpid-Java-Java-Test-0.16 at hudson.remoting.Channel@22397ea8:ubuntu1 at hudson.FilePath.act(FilePath.java:838) at hudson.FilePath.act(FilePath.java:824) at hudson.FilePath.mkdirs(FilePath.java:890) at hudson.model.AbstractProject.checkout(AbstractProject.java:1243) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:589) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBu
[JIRA] (JENKINS-14301) Failed to use multiple plugin repositories
Nickolay Rumyantsev commented on JENKINS-14301 Failed to use multiple plugin repositories I seek through code and found the reason of that bug: list of updates is generated by UpdateCenter.getUpdates(); UpdateCenter.getUpdates() ->(call) UpdateSite.getUpdates() for each update site in UpdateCenter.sites. UpdateSite.getUpdates() iterates through ALL plugins from PluginManager.getPlugins() and gets only those that have new version. That means that as a result we have a list which contains (all updates list)x(number of update sites). It works perfectly if we have only one update site. I don't know the best way to fix it to preseve architecture integrity, so I ask someone to fix it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14333) Clang warning with cmake get parsed incorrectly
Roland Schulz created JENKINS-14333 Clang warning with cmake get parsed incorrectly Issue Type: Bug Assignee: Ulli Hafner Components: warnings Created: 06/Jul/12 10:39 AM Description: The line: [ 11%] scanner.cpp:1518:28: warning: Array access (via field 'yy_buffer_stack') results in a null pointer dereference gets parsed incorrectly. The progress percentage shown by cmake is mistaken as part of the file name. Project: Jenkins Priority: Major Reporter: Roland Schulz This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14301) Failed to use multiple update sites (plugin repositories)
Nickolay Rumyantsev updated JENKINS-14301 Failed to use multiple update sites (plugin repositories) Change By: Nickolay Rumyantsev (06/Jul/12 10:48 AM) Summary: Failed to use multiple update sites ( plugin repositories ) Affects Version/s: current Due Date: 3/Jul/12 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14334) Make possible to enable/disable signature check of update file for each update site independently
Nickolay Rumyantsev created JENKINS-14334 Make possible to enable/disable signature check of update file for each update site independently Issue Type: Improvement Assignee: Unassigned Components: core Created: 06/Jul/12 10:46 AM Description: Make possible to enable/disable signature check of update file for each update site independently. For now it is a global flag for all sites in the same time. Project: Jenkins Priority: Minor Reporter: Nickolay Rumyantsev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14301) Failed to use multiple update sites (plugin repositories)
Nickolay Rumyantsev edited a comment on JENKINS-14301 Failed to use multiple update sites (plugin repositories) I seek through code and found the reason of that bug: list of updates is generated by UpdateCenter.getUpdates(); UpdateCenter.getUpdates() ->(call) UpdateSite.getUpdates() for each update site in UpdateCenter.sites. UpdateSite.getUpdates() iterates through ALL plugins from PluginManager.getPlugins() and gets only those that have new version. That means that as a result we have a list which contains (all updates list)x(number of update sites). It works perfectly if we have only one update site. I don't know the best way to fix it while preserving architecture integrity, so I ask someone to fix it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14332) Repeated channel/timeout errors from Jenkins slave
Richard Mortimer commented on JENKINS-14332 Repeated channel/timeout errors from Jenkins slave The message looks ok to me. There is 360 seconds difference between the two timestamps which would be consistent with a timeout. However I have a feeling that this is due to some additional changes that Koshuke made when he merged my remoting pull-3. See https://github.com/jenkinsci/remoting/commit/aceaf5c038e8179723f9a83be6f994f37e7cfa46 Previously the TimeoutException (ping failed) message would only have been observed if a TimeoutException was received. Now the message will be logged when the loop ends. Maybe there is a real timeout/delay here that was previously hidden. One other note. The while(remaining>0) gets evaluated after a timeout exception but remaining will only get recalculated on the next loop so there will be an extra pass around the loop. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13871) Using "Conditional build step" and "Parameterized build step" in same step is preventing parallel executions of same job
Alexey Bespaly commented on JENKINS-13871 Using "Conditional build step" and "Parameterized build step" in same step is preventing parallel executions of same job We are experiencing the same problem in our automated regression test system built on Jenkins and are looking for a solution for this one to be able to parallelize our job execution. Is there anything I could help in terms of diagnosing the issue? The description from Jacobo looks exhaustive, though... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14335) Jenkins build API changeset contains duplicated fields
Richard Taylor
created JENKINS-14335
Jenkins build API changeset contains duplicated fields
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
perforce
Created:
06/Jul/12 11:32 AM
Description:
When getting data via the REST API
job/buildnum/api/json
or
job/buildnum/api/xml
The items in the changeSet contain duplicated fields. This causes the C# serialisation code we are using to throw an exception. Not sure if this is a Core issue or a Perforce Plugin issue so I'll try posting as perforce first.
"changeSet": {
"items": [{
"affectedPaths": ["MS3/code/app/drawtest/testrefimages/basiccombined_gnm.dds",
"MS3/code/app/drawtest/testrefimages/GRIT_d3dm.dds",
"MS3/code/app/drawtest/testrefimages/GRIT_d3dr.dds",
"MS3/code/app/drawtest/testrefimages/GRIT_gnmm.dds",
"MS3/code/app/drawtest/testrefimages/GRIT_gnmr.dds",
"MS3/code/app/drawtest/testrefimages/lighting_gnm.dds",
"MS3/code/app/drawtest/testrefimages/postfx_gnm.dds",
"MS3/code/app/drawtest/testrefimages/world_gnm.dds",
"MS3/tools/bin/bob/build_imagetests.xml"],
"author": {
"absoluteUrl": "http://nw01-evotools:8080/user/*",
"fullName": "*"
},
"commitId": null,
"msg": "image test images\n\treviewer=*",
"timestamp": -1,
"affectedPaths": ["MS3/code/app/drawtest/testrefimages/basiccombined_gnm.dds",
"MS3/code/app/drawtest/testrefimages/GRIT_d3dm.dds",
"MS3/code/app/drawtest/testrefimages/GRIT_d3dr.dds",
"MS3/code/app/drawtest/testrefimages/GRIT_gnmm.dds",
"MS3/code/app/drawtest/testrefimages/GRIT_gnmr.dds",
"MS3/code/app/drawtest/testrefimages/lighting_gnm.dds",
"MS3/code/app/drawtest/testrefimages/postfx_gnm.dds",
"MS3/code/app/drawtest/testrefimages/world_gnm.dds",
"MS3/tools/bin/bob/build_imagetests.xml"],
"author": {
"absoluteUrl": "http://nw01-evotools:8080/user/*",
"fullName": "*"
},
"changeNumber": "21754",
"changeTime": "2012-07-06 11:08:34",
"msg": "image test images\n\treviewer=*"
}],
"kind": null
},
Thanks
Environment:
Windows Server 2008 R2
Jenkins Winstone
Project:
Jenkins
Priority:
Major
Reporter:
Richard Taylor
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14336) Too many open files upon HTTP listener init or shutdown
Krzysztof Malinowski created JENKINS-14336 Too many open files upon HTTP listener init or shutdown Issue Type: Bug Assignee: Unassigned Components: core Created: 06/Jul/12 12:25 PM Description: Trying to navigate to Jenkins web site, browser keeps loading and loading. When checked on Jenkins console it showed that Jenkins failed with the following: Jul 6, 2012 1:49:28 PM winstone.Logger logInternal SEVERE: Error during HTTP listener init or shutdown java.net.SocketException: Too many open files at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:408) at java.net.ServerSocket.implAccept(ServerSocket.java:462) at java.net.ServerSocket.accept(ServerSocket.java:430) at winstone.HttpListener.run(HttpListener.java:136) at java.lang.Thread.run(Thread.java:662) I have verified open files and it seems that unreasonable large number of descriptors is open to various jar files, with jenkins-core being the leader: $ ls -la /proc/26867/fd | grep jar | wc -l 876 $ ls -la /proc/26867/fd | grep jenkins-core | wc -l 462 $ ls -la /proc/26867/fd | grep stapler | wc -l 173 Environment: Jenkins 1.472 on RHEL 5 x86_64 Project: Jenkins Priority: Major Reporter: Krzysztof Malinowski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-7666) ClassCastException parsing JUnit result
Falko Modler reopened JENKINS-7666 ClassCastException parsing JUnit result Today this problem occured in our site build. Jenkins version is: 1.471 See also (and the comments as well): http://www.beyondlinux.com/2011/04/20/running-sonar-in-jenkinshudson-org-dom4j-documentfactory-cannot-be-cast-to-org-dom4j-documentfactory/ Btw: We do not use sonar! So it seems it is not limited to sonar... Change By: Falko Modler (06/Jul/12 12:34 PM) Resolution: Cannot Reproduce Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14337) Multi-configuration job disappearing from list whether the file config.xml is edited.
Andre Teles created JENKINS-14337 Multi-configuration job disappearing from list whether the file config.xml is edited. Issue Type: Task Assignee: jieryn Components: config-autorefresh, matrix Created: 06/Jul/12 12:45 PM Description: I created a script to edit the file config.xml and complete the list of values in the Configuration Matrix>User-defined Axis. The script only add lines to the config.xml, for example: File before: ... false MY_VALUES 1_First_Value/ 2_Second_Value/ ... File after: ... false MY_VALUES 1_First_Value/ 2_Second_Value/ 3_Third_Value/ 4_Fourth_Value/ ... After modifying the file and reloading the data from disk, the job disappears on jenkins. If someone has some idea, I would be very thankful. Thanks in advance, Project: Jenkins Priority: Major Reporter: Andre Teles This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14337) Multi-configuration job disappearing from list whether the file config.xml is edited.
jieryn updated JENKINS-14337 Multi-configuration job disappearing from list whether the file config.xml is edited. Change By: jieryn (06/Jul/12 12:50 PM) Assignee: jieryn Component/s: config-autorefresh This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14338) NPE when retrieving "requester" address for a promoted build
Aron Sedlack created JENKINS-14338 NPE when retrieving "requester" address for a promoted build Issue Type: Bug Affects Versions: current Assignee: Slide-O-Mix Components: email-ext Created: 06/Jul/12 1:32 PM Description: We have started receiving NPE's during email creation. The issue goes away if we deselect the option to include the requester in the recipient list. A stack trace is below. Jul 06, 2012 8:09:23 AM hudson.plugins.emailext.ExtendedEmailPublisher sendMail WARNING: Could not send email. java.lang.NullPointerException at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:415) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:273) at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:265) at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:225) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:717) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:692) at hudson.model.Build$BuildExecution.cleanUp(Build.java:192) at hudson.model.Run.execute(Run.java:1528) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Thank you! Project: Jenkins Labels: plugin email-ext Priority: Minor Reporter: Aron Sedlack This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14340) Remote directory of a Transfer Set should resolve env variable more than once
chanti vlad created JENKINS-14340 Remote directory of a Transfer Set should resolve env variable more than once Issue Type: Improvement Affects Versions: current Assignee: Slide-O-Mix Components: publish-over-cifs, publish-over-ftp, publish-over-ssh Created: 06/Jul/12 1:51 PM Description: This is a small feature improvement for "Publish Over ..." I tested the plugin beforehand (1.7) and read this information: https://wiki.jenkins-ci.org/display/JENKINS/Publish+Over+...#PublishOver...-Remotedirectory https://wiki.jenkins-ci.org/display/JENKINS/Publish+Over+...#PublishOver...-examples The "Eg 3 Environment variables" works for variables that need be resolved only once (e.g $JOB_NAME/$BUILD_NUMBER) However, this won't work with a variable $MY_JOB_PARAM that is defined as $JOB_NAME/$BUILD_NUMBER. Would it be possible to have a mechanism to resolve the env variable more than once? Possibly, the level of resolution could be specified by a number to enter. Project: Jenkins Priority: Minor Reporter: chanti vlad This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14338) NPE when retrieving "requester" address for a promoted build
Slide-O-Mix commented on JENKINS-14338 NPE when retrieving "requester" address for a promoted build What 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
[JIRA] (JENKINS-9233) Builds hang on jabber notification when XMPP server is not responding
cforce commented on JENKINS-9233 Builds hang on jabber notification when XMPP server is not responding We have the same problem here. If javver server down, our builds freezes forever (can't even terminate them by clicking the cross, only by terminating the server - tomcat) This is a huge problem! Timeout is required or this in unusable. Please fix it, we like this plugin .. We use windows server 2008 and with Tomcat 7 jenkins 1.473 as war Jenkins Jabber notifier plugin 1.22 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14329) Trigger parameterized build and block as build step never returns (waiting for the completion of OtherBuild)
Ben Dean
updated JENKINS-14329
Trigger parameterized build and block as build step never returns (waiting for the completion of OtherBuild)
Editing description and components to reflect the cause of the problem being the SCM Sync Configuration Plugin.
Change By:
Ben Dean
(06/Jul/12 3:03 PM)
Environment:
OS: Windows Server 2008 R2Jenkins: 1.
461, 1.470, 1.
473
Jenkins
Parameterized
Build
Trigger plugin: 2.15
SCM Sync Configuration Plugin: 0.0.5
Description:
Very simple builds where Build {{A}} triggers build {{B}} and waits for completion results in the following output:{noformat}Started by user anonymous
[EnvInject] - Loading node environment variables.
Building in workspace C:\JW\AWaiting for the completion of B{noformat}And even after {{B}} has completed, {{A}} never finishes. Configuration files for builds {{A}} and {{B}} are attached.
We don't have
I tested
this
problem
in
all
the
last version
versions
of Jenkins
we were using, {{1
mentioned in the Environment section above and it was present in all of them
.
461}}
The problem seems to be caused by the SCM Sync Configuration Plugin
. I
don't know if
tested
it
's something new in
with a fresh install of Jenkins
{{1.473}}
and only the two plugins for SCM Sync and Parameterized Trigger enabled and the bug was present
.
Disabling SCM Sync caused it to go away.
Component/s:
scm-sync-configuration
Component/s:
plugin
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
[JIRA] (JENKINS-14329) SCM Sync Configuration plugin conflicts with Parameterized Trigger plugin. (stuck on waiting for the completion of OtherBuild)
Ben Dean updated JENKINS-14329 SCM Sync Configuration plugin conflicts with Parameterized Trigger plugin. (stuck on waiting for the completion of OtherBuild) fixing hilarious typo Change By: Ben Dean (06/Jul/12 3:06 PM) Summary: SCM Sync Configuration plugin conflicts with Parameterized Trigger plugin. ( suck stuck on waiting for the completion of OtherBuild) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14329) SCM Sync Configuration plugin conflicts with Parameterized Trigger plugin. (suck on waiting for the completion of OtherBuild)
Ben Dean updated JENKINS-14329 SCM Sync Configuration plugin conflicts with Parameterized Trigger plugin. (suck on waiting for the completion of OtherBuild) changing title to more accurately describe the problem Change By: Ben Dean (06/Jul/12 3:05 PM) Summary: SCM Sync Configuration plugin conflicts with Parameterized Trigger parameterized build and block as build step never returns plugin. ( suck on waiting for the completion of OtherBuild) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14341) Send email notification when node taken offline
Ben Golding created JENKINS-14341 Send email notification when node taken offline Issue Type: Improvement Assignee: sogabe Components: versioncolumn Created: 06/Jul/12 3:07 PM Description: Use case is: User updates the Jenkins master version VersionColumn takes the slaves offline due to incompatible slave version User forgets to check if slaves are running OK Enhancement request to send an email to administrator (should be configurable...) when slave(s) are taken offline due to incompatible version. One way this could be achieved is by integrating with Node Offline Notification Plugin. This plugin sends email notification if any slave goes offline due to network disconnect / crash / etc. However the deliberate taking offline by VersionColumn does NOT trigger this notification presently. (In that way the email address is only configured in one place for both plugins) Environment: Jenkins 1.472 VersionColumn Plugin 0.2 Node Offline Notification Plugin 1.0.3 Project: Jenkins Priority: Major Reporter: Ben Golding This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14340) Remote directory of a Transfer Set should resolve env variable more than once
chanti vlad commented on JENKINS-14340 Remote directory of a Transfer Set should resolve env variable more than once So you suggest "Publish Over ..." to integrate following plugin https://wiki.jenkins-ci.org/display/JENKINS/Token+Macro+Plugin right ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14063) Images are broken when not logged in
Marc Sanfacon commented on JENKINS-14063 Images are broken when not logged in I tried to open the image in a separate window and here is the error: Status Code: 500 Exception: Stacktrace: java.lang.NullPointerException at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:50) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:162) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:215) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:138) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown 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
[JIRA] (JENKINS-14063) Images are broken when not logged in
Marc Sanfacon resolved JENKINS-14063 as Fixed Images are broken when not logged in Use greenballs v 1.12+ Change By: Marc Sanfacon (06/Jul/12 3:50 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
[JIRA] (JENKINS-13325) PYTHONPATH gets undefined with latest 1.44 version of EnvInject
Marc Sanfacon reopened JENKINS-13325 PYTHONPATH gets undefined with latest 1.44 version of EnvInject Just upgraded to version 1.60 and I got this error, which looks the same... 13:03:32 [EnvInject] - Injecting environment variables from a build step. 13:03:32 [EnvInject] - Injecting as environment variables the properties file path 'BuildFingerprint.txt' 13:03:32 [EnvInject] - Variables injected successfully. 13:03:32 [EnvInject] - Unset unresolved 'PATH' variable. 13:03:32 [EnvInject] - Unset unresolved 'PYTHONPATH' variable. Change By: Marc Sanfacon (06/Jul/12 5:10 PM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14343) URL for ViewVC/ViewCVS contains portion of CVSROOT
Shane Turner created JENKINS-14343 URL for ViewVC/ViewCVS contains portion of CVSROOT Issue Type: Bug Assignee: Michael Clarke Components: cvs Created: 06/Jul/12 6:42 PM Description: I'm pretty sure that CVSPlugin 1.6 didn't have this problem, but with 2.4 my URLs for ViewCVS contain the path portion of my CVSROOT. For example: Example base URL for ViewCVS (FreeBSD-CVSweb): http://cvs.somewhere.net//cgi-bin/cvsweb/ CVSROOT=username@host:/var/lib/cvs Module being checked out: company/product/src Resulting URL: http://cvs.somewhere.net/cgi-bin/cvsweb/var/lib/cvs/company/product/src/Common/libs/widget/Widget.cc Previously, the URL would have been: http://cvs.somewhere.net/cgi-bin/cvsweb/company/product/src/Common/libs/widget/Widget.cc Environment: Ubuntu 10.04, Jenkins 1.473, CVS Plugin 2.4, FreeBSD-CVSweb (cvsweb 3:3.0.6-5) Project: Jenkins Labels: cvs plugin viewcvs viewvc cvsweb Priority: Minor Reporter: Shane Turner This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14344) invalid-authzid:
bob koertge created JENKINS-14344 invalid-authzid: Issue Type: Bug Assignee: kutzi Components: jabber Created: 06/Jul/12 7:26 PM Description: Here are my settings: https://skitch.com/bobdeskcom/efe4t/configure-system-jenkins This is the error I am getting. Any help would be greatly appreciated. Jul 6, 2012 7:21:43 PM hudson.plugins.jabber.im.transport.JabberIMConnection createConnection INFO: Trying to connect to XMPP on talk.google.com:5222/gmail.com with SASL Jul 6, 2012 7:21:43 PM hudson.plugins.jabber.im.transport.JabberIMConnection connect WARNING: SASL authentication PLAIN failed: invalid-authzid: at org.jivesoftware.smack.SASLAuthentication.authenticate(SASLAuthentication.java:337) at org.jivesoftware.smack.XMPPConnection.login(XMPPConnection.java:203) at hudson.plugins.jabber.im.transport.JabberIMConnection.createConnection(JabberIMConnection.java:311) at hudson.plugins.jabber.im.transport.JabberIMConnection.connect(JabberIMConnection.java:154) at hudson.plugins.jabber.im.transport.JabberIMConnectionProvider.createConnection(JabberIMConnectionProvider.java:42) at hudson.plugins.im.IMConnectionProvider.create(IMConnectionProvider.java:65) at hudson.plugins.im.IMConnectionProvider.access$600(IMConnectionProvider.java:22) at hudson.plugins.im.IMConnectionProvider$ConnectorRunnable.run(IMConnectionProvider.java:183) at java.lang.Thread.run(Thread.java:679) Project: Jenkins Priority: Major Reporter: bob koertge This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14345) Grails wrapper doesn't respect "Project Base Directory"
Stefan Hojer created JENKINS-14345 Grails wrapper doesn't respect "Project Base Directory" Issue Type: Bug Assignee: jeffg2one Components: grails Created: 06/Jul/12 9:21 PM Description: The grails plugin tries to start the "grailsw" grails wrapper from the workspace root instead of the "project base directory". The build will fail, as the grailsw (if present) is actually installed in the grails project base directory. Environment: Debian 6 with jenkins v1.473 and grails plugin v1.6.2 Project: Jenkins Priority: Major Reporter: Stefan Hojer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14332) Repeated channel/timeout errors from Jenkins slave
Richard Mortimer commented on JENKINS-14332 Repeated channel/timeout errors from Jenkins slave Ah I take some of that back. I didn't check the main jenkins build closely enough. Jenkins is using remoting 1.16 and this does not include the latest changes made by Kohsuke/me. The PingThread logic in 1.475-SNAPSHOT is unchanged since Sept/2011 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14347) Global & node level self-referencing variables should work
Jørgen Tjernø created JENKINS-14347 Global & node level self-referencing variables should work Issue Type: Bug Assignee: Gregory Boissinot Components: envinject Created: 06/Jul/12 9:49 PM Description: Global & node level variables do not seem to work like intended. Master & node configuration: /configure: PATH set to $PATH:/foo/ /computer/not_master/configure: PATH set to $PATH:/bar/ Job configuration: Default "Prepare an environment for the run" enabled, Properties Content: FOO=BAR Execute shell script: echo $PATH Expected output: When run on master: :/foo/ When run on non-master: :/foo/:/bar/ Actual output: When run on master: (no /foo/) When run on non-master: $PATH:/bar/:/bar/:/bar/:/bar/:/bar/:/bar/:/bar/:/bar/:/bar/:/bar/:/bar/:/bar/:/bar/:/bar/:/bar/:/bar/:/bar/ (literally contains the string $PATH) Also, the non-master job says: [EnvInject] - Unset unresolved 'PATH' variable. The master job doesn't print this. Environment: Jenkins 1.472 EnvInject 1.60 Project: Jenkins Priority: Major Reporter: Jørgen Tjernø This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14332) Repeated channel/timeout errors from Jenkins slave
Richard Mortimer commented on JENKINS-14332 Repeated channel/timeout errors from Jenkins slave Similar symptoms at JENKINS-14307 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14348) Multi-configuration projects don't load properly in 1.473
Brett Clouser created JENKINS-14348 Multi-configuration projects don't load properly in 1.473 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: matrix Created: 06/Jul/12 11:15 PM Description: We had several multi-configuration projects which were working properly on 1.472. Upon upgrading to 1.473 these projects no longer appeared. I noticed the following in the Jenkins logs: SEVERE: Failed Loading job foo_bar java.lang.NullPointerException at hudson.matrix.MatrixProject.updateTransientActions(MatrixProject.java:431) at hudson.model.AbstractProject.onLoad(AbstractProject.java:296) at hudson.matrix.MatrixProject.onLoad(MatrixProject.java:466) at hudson.model.Items.load(Items.java:115) at jenkins.model.Jenkins$17.run(Jenkins.java:2492) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:878) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) Let me know if I can provide any further information. Environment: Ubuntu 11.04 Jenkins 1.473 Java Runtime Version 1.6.0_22-b22 Project: Jenkins Labels: exception matrix Priority: Major Reporter: Brett Clouser This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
