[JIRA] [git] (JENKINS-24082) Be able to force push for branch on git publisher
SCM/JIRA link daemon resolved JENKINS-24082 as Fixed Be able to force push for branch on git publisher Change By: SCM/JIRA link daemon (17/Sep/14 6:20 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24082) Be able to force push for branch on git publisher
SCM/JIRA link daemon commented on JENKINS-24082 Be able to force push for branch on git publisher Code changed in jenkins User: Wannes Sels Path: src/test/java/hudson/plugins/git/GitPublisherTest.java http://jenkins-ci.org/commit/git-plugin/b14f6f4398c0ccfb88392dfda8baaf2ef9e3a2c8 Log: added testcase for force push JENKINS-24082 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-24082) Be able to force push for branch on git publisher
SCM/JIRA link daemon commented on JENKINS-24082 Be able to force push for branch on git publisher Code changed in jenkins User: Wannes Sels Path: src/main/java/hudson/plugins/git/GitPublisher.java src/main/resources/hudson/plugins/git/GitPublisher/config.jelly src/test/java/hudson/plugins/git/GitPublisherTest.java http://jenkins-ci.org/commit/git-plugin/cebb9da131fa6c9e07ec9e6ff71ec89aa58fdd6f Log: Merge pull request #248 from guilhem/forceOption FIXED JENKINS-24082 Add a force option to push command Compare: https://github.com/jenkinsci/git-plugin/compare/adc96942cd67...cebb9da131fa This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-24082) Be able to force push for branch on git publisher
SCM/JIRA link daemon commented on JENKINS-24082 Be able to force push for branch on git publisher Code changed in jenkins User: Guilhem Lettron Path: src/test/java/hudson/plugins/git/GitPublisherTest.java http://jenkins-ci.org/commit/git-plugin/ef6bc1856202a8d7a936ce881b083517bc1e28a3 Log: Merge pull request #1 from wannessels/forceOption added testcase for force push JENKINS-24082 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-24703) Search box background color (white) not matching navbar backround (black)
Tom FENNELLY commented on JENKINS-24703 Search box background color (white) not matching navbar backround (black) Assuming it works, I would go with the later of your two fixes listed above i.e. remove the setting of the font color on the input. I was not able to test this the other day because I did not know how you were changing your colour scheme to cause the original problem you were trying to fix. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24082) Be able to force push for branch on git publisher
SCM/JIRA link daemon commented on JENKINS-24082 Be able to force push for branch on git publisher Code changed in jenkins User: Wannes Sels Path: src/test/java/hudson/plugins/git/GitPublisherTest.java http://jenkins-ci.org/commit/git-plugin/db14f9f5659794a146ee4850e7f63795f6b10e77 Log: fixed GitPublisherTest.testForcePush , was not deterministic JENKINS-24082 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [android-emulator] (JENKINS-24736) Android emulator plugin does not use all available executors on a slave
JY Hsu commented on JENKINS-24736 Android emulator plugin does not use all available executors on a slave ok I found that for existing emulators, if two jobs are asking to launch the same emulator, one will be blocked. So that looks like the right behavior. However, for creating new emulators, it still blocks all other create new emulator jobs on the same node. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-24458) SomeAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions
herve_colliaux commented on JENKINS-24458 SomeAction doesnt have @ExportedBean so cannot write hudson.model.Actionable.actions I had also this issue on Windows 7 with Jenkins 1.580. resolved by deactivating EzWall 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] [core] (JENKINS-24737) updateCenter fails to restart Jenkins
Daniel Beck commented on JENKINS-24737 updateCenter fails to restart Jenkins Make sure your Jenkins.exe is up to date the integrated updater does (did?) not update it. Then try again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-24112) git-client does not support authentication proxy
OHTAKE Tomohiro closed JENKINS-24112 as Fixed git-client does not support authentication proxy Change By: OHTAKE Tomohiro (17/Sep/14 7:23 AM) 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] [parameterized-remote-trigger] (JENKINS-24731) Using Remote Trigger Plugin and properties files can get job into a weird state where it cannot be aborted
Daniel Beck updated JENKINS-24731 Using Remote Trigger Plugin and properties files can get job into a weird state where it cannot be aborted Not a core issue. There's little core can do about a plugin that catches InterruptedException in what's effectively a 'while(true)' loop. Change By: Daniel Beck (17/Sep/14 7:30 AM) 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] [ghprb] (JENKINS-24592) ghprb does not support proxies
OHTAKE Tomohiro updated JENKINS-24592 ghprb does not support proxies Change By: OHTAKE Tomohiro (17/Sep/14 7:30 AM) Environment: ghprb1. 15 16 - 1 0 Jenkins1. 578 580 OpenJDK7u65-2.5. 1 2 - 4ubuntu1 3 ~ 0. 14.04 .2 Ubuntu14.04.1LTSx86_64 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-24737) updateCenter fails to restart Jenkins
Daniel Beck resolved JENKINS-24737 as Duplicate updateCenter fails to restart Jenkins Assuming this is a duplicate of JENKINS-22685. Change By: Daniel Beck (17/Sep/14 7:32 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24734) JenkinsLocationConfiguration does not get reloaded from disk
Daniel Beck resolved JENKINS-24734 as Duplicate JenkinsLocationConfiguration does not get reloaded from disk Duplicates JENKINS-8217 (just a different affected extension point). Change By: Daniel Beck (17/Sep/14 7:34 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-8217) Ant Settings aren't reloaded from hudson.tasks.Ant.xml
Daniel Beck commented on JENKINS-8217 Ant Settings arent reloaded from hudson.tasks.Ant.xml JENKINS-24734 notes that this also affects jenkins.model.JenkinsLocationConfiguration.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] [build-pipeline] (JENKINS-22146) Infinite recursion when the pipeline involves joined jobs triggering the same child job
Ville Hartikainen commented on JENKINS-22146 Infinite recursion when the pipeline involves joined jobs triggering the same child job Ran into this with latest Jenkins version 1.580. Fortunately, I was able to navigate myself via proper URL to the cyclic configuration. Is there any update when this fix will be available? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-import] (JENKINS-24739) import additional job properties
Tobias Hartmann created JENKINS-24739 import additional job properties Issue Type: New Feature Assignee: Unassigned Components: job-import Created: 17/Sep/14 7:49 AM Description: When importing a job from another instance also make it possible to import other job properties than the configuration xml. Being able to conveniently import the job history information and the nextBuildNumber file would ease the process of moving jobs without breaking existing environments. Project: Jenkins Labels: job Priority: Minor Reporter: Tobias Hartmann This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-24703) Search box background color (white) not matching navbar backround (black)
Ceesjan Luiten commented on JENKINS-24703 Search box background color (white) not matching navbar backround (black) Thanks for the feedback Tom. I've implemented your suggestion: https://github.com/quinox/jenkins/commit/78d222c607d31bdcfd5df7c20dbefe3ec937f3de The differences for most people will be subtle, instead of #333-on-white you get default text color (#000)-on-white. You shouldn't see any other changes. For me the change is significant, I get usable input fields again. I looked at a few CSS frameworks yesterday, some follow the road of color-style-everything (fe. Bootstrap) while others don't color-style input elements at all (fe. Yahoo!'s Pure CSS) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-14744) java.lang.OutOfMemoryError: GC overhead limit exceeded
Daniel Beck commented on JENKINS-14744 java.lang.OutOfMemoryError: GC overhead limit exceeded What's the output of org.tmatesoft.svn.core.wc.DefaultSVNRepositoryPool.ourInstanceCount in script console? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [perforce] (JENKINS-24740) Expose duration of sync in ENV
Morne Joubert created JENKINS-24740 Expose duration of sync in ENV Issue Type: New Feature Assignee: Rob Petti Components: perforce Created: 17/Sep/14 8:31 AM Description: It would be very good to expose the time the perforce plugin took to perform its actions as env variables. We can then track down clients specs that are taking too long to sync (because they are too big) or proxies that have not been set up currently etc. I can then take these variables and post process them. Project: Jenkins Priority: Minor Reporter: Morne Joubert This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-14744) java.lang.OutOfMemoryError: GC overhead limit exceeded
Daniel Beck commented on JENKINS-14744 java.lang.OutOfMemoryError: GC overhead limit exceeded Also, a thread dump could be interesting. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-24741) Expose duration of plugin
Morne Joubert created JENKINS-24741 Expose duration of plugin Issue Type: New Feature Assignee: Unassigned Components: p4 Created: 17/Sep/14 8:35 AM Description: It would be good to expose the duration of the actions (in env variables if possible) so i can track how long it took for cleanup,sync etc. I can then track syncs that take too long etc. Project: Jenkins Priority: Minor Reporter: Morne Joubert This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [perforce] (JENKINS-24740) Expose duration of sync in ENV
Daniel Beck commented on JENKINS-24740 Expose duration of sync in ENV Timestamper plugin might help, assuming there's sufficient build log output by the plugin. Also, should be easy to write a plugin that lists time spent per build phase/step, similar to Metrics Plugin's waiting in queue/executing info. (What is it about Perforce that requires weird features like this?) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-import] (JENKINS-24739) import additional job properties
Daniel Beck commented on JENKINS-24739 import additional job properties 'job history information' refers to Job Config History Plugin's data? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-import] (JENKINS-24739) import additional job properties
Tobias Hartmann commented on JENKINS-24739 import additional job properties I refer to the actual build history of the imported job. Currently the job-import plugin only imports the job configuration xml, but there is no option to import the complete job history or at least the number of the next build that should be performed. We are currently moving some old jobs to a brand new build server it'd be a big improvement if it was possible for the moved jobs to just continue the old job's history or at least give it the next build number the old job would have used without editing the files manually and having to reload the 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] [job-import] (JENKINS-24739) import additional job properties
Tobias Hartmann edited a comment on JENKINS-24739 import additional job properties I refer to the actual build history of the imported job. Currently the job-import plugin only imports the job configuration xml, but there is no option to import the complete job history or at least the number of the next build that should be performed. We are currently moving some old jobs to a brand new build server. It'd be a big improvement if it was possible for the moved jobs to just continue the old job's history or at least give it the next build number the old job would have used without editing the files manually and having to reload the 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] [job-import] (JENKINS-24739) import additional job properties
Tobias Hartmann edited a comment on JENKINS-24739 import additional job properties I refer to the actual build history of the imported job. Currently the job-import plugin only imports the job configuration xml, but there is no option to import the complete job history or at least the number of the next build that should be performed. We are currently moving some old jobs to a brand new build server. It'd be a big improvement if it was possible for the moved jobs to just continue the old job's history or at least give it the next build number the old job would have used without editing the files manually and having to reload the configuration. Edit: We had independent Jenkins instances running that were added with increasing demands, but are now moving to a better scalable master-slave setup. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-import] (JENKINS-24739) import additional job properties
Tobias Hartmann edited a comment on JENKINS-24739 import additional job properties I refer to the actual build history of the imported job. Currently the job-import plugin only imports the job configuration xml, but there is no option to import the complete job history or at least the number of the next build that should be performed. We are currently moving some old jobs to a brand new build server. It'd be a big improvement if it was possible for the moved jobs to just continue the old job's history or at least give it the next build number the old job would have used without editing the files manually and having to reload the configuration. Edit: We independent Jenkins instances running that were added with increasing demands, but are now moving to a better scalable master-slave setup. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-import] (JENKINS-24739) import additional job properties
Daniel Beck commented on JENKINS-24739 import additional job properties Given that you'd also want or need build logs, artifacts, etc., and for some projects this is easily tens or hundreds of GB of data, this could well be very time consuming, requiring considering things like retries and resuming transfers. (Granted, maybe not for you, but generally speaking.) Also, since build.xml files aren't exposed like a job's config.xml is, this will require massive changes in the plugin. Note that some plugins also store data in additional files (Promoted Builds and Subversion come to mind) which would also need to be considered to result in perfect replica. In comparison, it's trivial to just transfer the job folder over (+ Reload Config on the receiving side, delete project on the sending side) to get the same result. While I'm not a job import plugin dev, I have serious doubts about the feasibility of this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-24740) Expose duration of sync in ENV
Morne Joubert commented on JENKINS-24740 Expose duration of sync in ENV The timestamper seems a bit intrusive and a lot of fixes have been done that are not in the latest LTS version. If i have a big build across multiple sites then i would want to upload the time the Perforce actions ( sync) takes to determine how long does a full sync of stream X takes on site A,B,C,D I can then get IT to look at optimizing the distributed Perforce proxies around our sites. A stream or client specs might be too wide or someone might have added a very large file in a wrong place causing a knock on effect. I know i could write a groovy script to post process the log to pull the durations but it seems a lot of work if the plugin could just expose this This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24458) SomeAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions
Craig Phillips commented on JENKINS-24458 SomeAction doesnt have @ExportedBean so cannot write hudson.model.Actionable.actions I can't believe you closed the issue, that is such a cop out. We are not using any wall plugin, we just happen to be accessing the REST API from a _javascript_ web service, completely separate from Jenkins. So what you are saying is that as an unauthenticated user, I can hammer jenkins REST API's with requests that will fill it's logs and take the server down. Sounds like a DoS attack waiting to happen 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] [scm-sync-configuration] (JENKINS-22666) No popup window when committing changes to job config for putting in commit message
Torben Knerr commented on JENKINS-22666 No popup window when committing changes to job config for putting in commit message Donwgraded to 0.0.7.4 as suggested by @colonelcoder above. The popup now appears, but the commits are not being pushed to the remote repo anymore... any ideas? P.S.: the log looks fine, though: Sep 17, 2014 11:09:54 AM FINE hudson.plugins.scm_sync_configuration.SCMManipulator Checked in SCM files ! Sep 17, 2014 11:09:54 AM FINEST hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness Commit Commit hudson.plugins.scm_sync_configuration.model.Commit@268189ca : Author : Torben Knerr Comment : Job [maven.dummy] configuration updated by torben.knerr with following comment : NAUA-25 yes we can! (now add commit messages to build plan changes :-)) Changeset : A jobs/maven.dummy/config.xml pushed to SCM ! Sep 17, 2014 11:14:05 AM FINEST hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness Queuing commit Commit hudson.plugins.scm_sync_configuration.model.Commit@5a1ab9cb : Author : Torben Knerr Comment : Jenkins configuration files updated by torben.knerr Changeset : A hudson.plugins.groovy.Groovy.xml A hudson.plugins.jira.JiraProjectProperty.xml A hudson.plugins.emailext.ExtendedEmailPublisher.xml A hudson.maven.MavenModuleSet.xml A hudson.plugins.git.GitSCM.xml A hudson.triggers.SCMTrigger.xml A hudson.plugins.git.GitTool.xml A scm-sync-configuration.xml A hudson.plugins.gradle.Gradle.xml A hudson.tasks.Mailer.xml A config.xml A hudson.tasks.Maven.xml A hudson.tasks.Shell.xml to SCM ... Sep 17, 2014 11:14:05 AM FINEST hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [_test] (JENKINS-24742) [FlowDock] Use global proxy configuration (including proxy authentication)
Baptiste Mathus created JENKINS-24742 [FlowDock] Use global proxy configuration (including proxy authentication) Issue Type: Bug Assignee: Oleg Nenashev Components: _test Created: 17/Sep/14 9:29 AM Description: Currently, seems like the flowdock-jenkins-plugin is only able to push notification if there's no proxy in the middle. If there's one, then nothing goes out. Here's essentially the corresponding code I guess: https://github.com/jenkinsci/flowdock-plugin/blob/master/src/main/java/com/flowdock/jenkins/FlowdockAPI.java#L65 Thanks PS : put _test as component since "flowdock" does not seem to exist yet. Will update as soon as the new component is created. Environment: Jenkins 1.559 Project: Jenkins Priority: Blocker Reporter: Baptiste Mathus This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-import] (JENKINS-24739) import additional job properties
Tobias Hartmann commented on JENKINS-24739 import additional job properties I don't wanna copy the whole workspace. I was more thinking in terms of build result reports and logs but this also is a massive amount of data for longer running jobs. At least an option to import the nextBuildNumber would be nice to be able to build the connection between an old job and its copy on a new system. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-20725) maven build creates symlinkd files that Windows OS does not understand
Thomas Pilz commented on JENKINS-20725 maven build creates symlinkd files that Windows OS does not understand Hi there, i still hope that there will be some Progress on this Issue as this Problem is a real Blocker for Windows backed Jenkins Installations with Maven Projects. Backups via ZIP/TAR and also Job Migration via copy of Jobs Folder to different Host is not working at the moment due to wrong generated symbolic links. 09.09.2014 14:17SYMLINKD com.foo.acme$acmeCore ../../modules/com.foo.acme$acmeCore/builds/2014-09-09_14-16-18 should be 09.09.2014 14:17SYMLINKD com.foo.acme$acmeCore ..\..\modules\com.foo.acme$acmeCore\builds\2014-09-09_14-16-18 Environment: Windows 2008 R2 / Jenkins 1.532.2 LTS / Maven Project Plugin 2.0.3 / Maven 3.2.1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-import] (JENKINS-24739) import additional job properties
Tobias Hartmann updated JENKINS-24739 import additional job properties Change By: Tobias Hartmann (17/Sep/14 9:33 AM) Description: Whenimportingajobfromanotherinstancealsomakeitpossibletoimportotherjobpropertiesthantheconfigurationxml.BeingabletoconvenientlyimportthejobhistoryinformationandthenextBuildNumberfilewouldeasetheprocessofmovingjobswithoutbreakingexistingenvironments. Edit:AsanimportofacompletejobhistoryisatooheavytaskbetterperformedseparatelyjusthavingtheoptiontoimportpartsofitlikethenextBuildNumberfilewouldbeveryconvenient. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-import] (JENKINS-24739) import additional job properties
Daniel Beck commented on JENKINS-24739 import additional job properties Not workspace (temporary build data) archived artifacts. Those are build records just like the log is. Or e.g. old builds' file parameters all files uploaded as parameters are archived for older builds, and would also need to be transferred. Hundreds of MB per build in some cases. Of course, just nextBuildNumber should be fairly easy (speaking as someone who's not a dev of the plugin). Workaround until then: Set Next Buildnumber 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] [android-emulator] (JENKINS-24736) Android emulator plugin does not use all available executors on a slave
Christopher Orr commented on JENKINS-24736 Android emulator plugin does not use all available executors on a slave If multiple jobs try to use the same existing named emulator on the same slave, only one build can use the emulator at at time, blocking the other builds. If two jobs have the same emulator properties, the same will happen. What do your 10 jobs look like? Are they 10 separate Jenkins jobs, or are you trying to run multiple builds of the same job? Do they all have completely unique OS/density/resolution/locale/ABI? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-import] (JENKINS-24739) import additional job properties
Tobias Hartmann commented on JENKINS-24739 import additional job properties Did not have all this data in mind when opening this issue. Also didn't find the next build number plugin before. Will use this now 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] [subversion] (JENKINS-24554) Builds get triggered multiple times when the SCM URL contains variables that change on each node
Alex Ouzounis commented on JENKINS-24554 Builds get triggered multiple times when the SCM URL contains variables that change on each node Pull request: https://github.com/jenkinsci/subversion-plugin/commit/6496d7fa3623408a7af571601deac75c8cc29dcb When comparing builds make sure the environment used is based on the system env vars otherwise the comparison is not fair. Use the incoming build's system environment variables. Please review and merge This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-15331) Workaround Windows unpredictable file locking in Util.deleteContentsRecursive
apgray commented on JENKINS-15331 Workaround Windows unpredictable file locking in Util.deleteContentsRecursive This is affecting the Allure Reports plugin as well. Is this any closer to a fix? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24458) SomeAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions
Craig Phillips commented on JENKINS-24458 SomeAction doesnt have @ExportedBean so cannot write hudson.model.Actionable.actions Oh, and btw. I updated all the API calls to use the 'tree' parameter and made sure depth isn't used. This made no difference whatsoever. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-24458) SomeAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions
Craig Phillips commented on JENKINS-24458 SomeAction doesnt have @ExportedBean so cannot write hudson.model.Actionable.actions I'd be inclined to say, the Jenkins CLI is what is causing this, rather than the rest API. I just disabled all the dashboards that point to Jenkins and I was still seeing the errors. There was a build running that was updating job configuration using the CLI. Calls to this, seem to be generating these errors. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-24458) SomeAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions
Daniel Beck commented on JENKINS-24458 SomeAction doesnt have @ExportedBean so cannot write hudson.model.Actionable.actions I can't believe you closed the issue, that is such a cop out. Jesse already wrote that logging level will be reduced in a future release, and that level (FINE) is hidden by default. No more messages logged. ... Sounds like a DoS attack waiting to happen to me. Don't allow anonymous read access to Jenkins (and remove any malicious users who have read access). Jenkins CLI is what is causing this, rather than the rest API. Provide a full stack trace that does not contain Api.doJson or Api.doXml (or both that and a call to CLI.execute), and confirm in the access logs that nobody calls .../api/json, .../api/xml, or .../api/python, and I'll look into it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds] (JENKINS-15820) JClouds plugin deadlock
SCM/JIRA link daemon commented on JENKINS-15820 JClouds plugin deadlock Code changed in jenkins User: Kei YAMAZAKI Path: jclouds-plugin/src/main/java/jenkins/plugins/jclouds/compute/JCloudsRetentionStrategy.java http://jenkins-ci.org/commit/jclouds-plugin/363f3cef682aa2ee4bb34ada46384168989ae2a8 Log: JENKINS-15820 Avoid deadlocks by using RentrantLock#tryLock() instead of synchronized This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [jclouds] (JENKINS-15820) JClouds plugin deadlock
SCM/JIRA link daemon commented on JENKINS-15820 JClouds plugin deadlock Code changed in jenkins User: Marat Mavlyutov Path: jclouds-plugin/src/main/java/jenkins/plugins/jclouds/compute/JCloudsRetentionStrategy.java http://jenkins-ci.org/commit/jclouds-plugin/ab755ddd10fdbe43b84ff08ad6a05aa0e358e59b Log: Merge pull request #72 from kei-yamazaki/avoid-deadlock JENKINS-15820 Avoid deadlocks by using RentrantLock#tryLock() instead of synchronized Compare: https://github.com/jenkinsci/jclouds-plugin/compare/6bab23d09c3d...ab755ddd10fd This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [show-build-parameters] (JENKINS-24698) ShowParametersBuildAction doesn't have @ExportedBean so cannot write hudson.model.Actionabl
Per Arnold Blaasmo commented on JENKINS-24698 ShowParametersBuildAction doesnt have @ExportedBean so cannot write hudson.model.Actionabl I was a little to hasty, the warnings did not disappear So I get I have to follow https://wiki.jenkins-ci.org/display/JENKINS/Exposing+data+to+the+remote+API and add @ExportedBean for the class. I will try that. I am not sure though what provokes the warning? When running it isolated it does not seem to trigger the warning, but when running it on the production server it gets 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] [flowdock] (JENKINS-24742) [FlowDock] Use global proxy configuration (including proxy authentication)
Baptiste Mathus updated JENKINS-24742 [FlowDock] Use global proxy configuration (including proxy authentication) Change By: Baptiste Mathus (17/Sep/14 12:20 PM) Component/s: flowdock Component/s: _test This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-24640) File modes are wrong after git checkout
Mark Waite closed JENKINS-24640 as Not A Defect File modes are wrong after git checkout Change By: Mark Waite (17/Sep/14 12:22 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-client] (JENKINS-24640) File modes are wrong after git checkout
Mark Waite resolved JENKINS-24640 as Not A Defect File modes are wrong after git checkout According to the git wiki, git does not track file modes, except the executable bit and whether a file is a symbolic link. Since git does not track file modes, it seems reasonable that there may be file mode differences between git implementations (like command line git and JGit). The file mode is not adjusted in any way by either the git plugin, or the git client plugin. If there is a difference between the two, as far as I understand, it would need to be reported as bugs to those projects. Change By: Mark Waite (17/Sep/14 12:22 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-remote-trigger] (JENKINS-24731) Using Remote Trigger Plugin and properties files can get job into a weird state where it cannot be aborted
Lorelei McCollum commented on JENKINS-24731 Using Remote Trigger Plugin and properties files can get job into a weird state where it cannot be aborted Ahh Thanks for the information, I didn't know if core would allow things like this or not. Not good though. Hopefully the plugin team can get a fix out for this This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [flowdock] (JENKINS-24742) [FlowDock] Use global proxy configuration (including proxy authentication)
Baptiste Mathus updated JENKINS-24742 [FlowDock] Use global proxy configuration (including proxy authentication) Change By: Baptiste Mathus (17/Sep/14 12:21 PM) Assignee: OlegNenashev AnttiPitkänen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
Pradeepto Bhattacharya commented on JENKINS-23641 Builds are failing due to GitHubCommitNotifier exception I was just bitten by this issue. I am using GitHub Pull Request Builder (1.16-0) along with Github plugin (1.9.1). I am trying build a PR using GHPRB. ERROR: Publisher com.cloudbees.jenkins.GitHubCommitNotifier aborted due to exception java.lang.NullPointerException at com.cloudbees.jenkins.GitHubCommitNotifier.perform(GitHubCommitNotifier.java:53) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:756) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720) at hudson.model.Build$BuildExecution.post2(Build.java:182) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:669) at hudson.model.Run.execute(Run.java:1731) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:232) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-22252) Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap
Stefan Cordes edited a comment on JENKINS-22252 Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap Can this be fixed in https://wiki.jenkins-ci.org/display/JENKINS/Task+Scanner+Plugin ? When switching off hudson.plugins.tasks.TasksReporter plugin="tasks@4.40" we no longer receive: 2014-09-17T13:26:10.115 [INFO] Building xx-jenkins-test-ejb 2014.3.1-15-SNAPSHOT 2014-09-17T13:26:10.117 [INFO] 2014-09-17T13:26:10.236 [INFO] 2014-09-17T13:26:10.236 [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ xx-jenkins-test-ejb --- [TASKS] Scanning folder 'D:\jenkins-TEST-Slave1\workspace\xx-jenkins-test\xx\xx-jenkins-test\xx-jenkins-test-ejb' for files matching the pattern '**/*.java, **/*.xml' - excludes: [TASKS] Found 9 files to scan for tasks Found 0 open tasks. java.io.IOException: Remote call on channel failed at hudson.remoting.Channel.call(Channel.java:731) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:167) at $Proxy4.execute(Unknown Source) at hudson.maven.MavenBuildProxy$Filter.execute(MavenBuildProxy.java:206) at hudson.plugins.analysis.core.HealthAwareReporter.registerResultsOnMaster(HealthAwareReporter.java:325) at hudson.plugins.analysis.core.HealthAwareReporter.postExecute(HealthAwareReporter.java:316) at hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoEnded(Maven3Builder.java:628) at hudson.maven.Maven3Builder$MavenExecutionListener.mojoSucceeded(Maven3Builder.java:610) at hudson.maven.Maven3Builder$JenkinsEventSpy.onEvent(Maven3Builder.java:306) at org.apache.maven.eventspy.internal.EventSpyDispatcher.onEvent(EventSpyDispatcher.java:108) at org.apache.maven.eventspy.internal.EventSpyExecutionListener.mojoSucceeded(EventSpyExecutionListener.java:131) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:87) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:227) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154) at org.jvnet.hudson.maven3.launcher.Maven31Launcher.main(Maven31Launcher.java:132) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:600) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:330) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:238) at jenkins.maven3.agent.Maven31Main.launch(Maven31Main.java:181) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:600) at hudson.maven.Maven3Builder.call(Maven3Builder.java:134) at hudson.maven.Maven3Builder.call(Maven3Builder.java:69) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:315) at java.util.concurrent.FutureTask.run(FutureTask.java:150) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:898) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:920) at
[JIRA] [findbugs] (JENKINS-24743) Findbug and PMD are broken in Jenkins 1.565.2
bhanu pathak created JENKINS-24743 Findbug and PMD are broken in Jenkins 1.565.2 Issue Type: Bug Assignee: Ulli Hafner Components: findbugs, pmd Created: 17/Sep/14 12:35 PM Description: I have upgraded Jenkins to version 1.565.2 and after that when we are running Findbugs and PMD jobs they are failing with nullpointer exception code snippet is shown below FINDBUGS Collecting findbugs analysis files... ERROR: Publisher hudson.plugins.findbugs.FindBugsPublisher aborted due to exception java.lang.NullPointerException at org.apache.commons.digester3.Digester.getXMLReader(Digester.java:799) at org.apache.commons.digester3.Digester.parse(Digester.java:1642) at org.apache.commons.digester3.Digester.parse(Digester.java:1701) at hudson.plugins.findbugs.parser.FindBugsParser.preParse(FindBugsParser.java:229) at hudson.plugins.findbugs.parser.FindBugsParser.parse(FindBugsParser.java:187) at hudson.plugins.findbugs.parser.FindBugsParser.parse(FindBugsParser.java:172) at hudson.plugins.findbugs.parser.FindBugsParser.parse(FindBugsParser.java:140) at hudson.plugins.analysis.core.FilesParser.parseFile(FilesParser.java:300) at hudson.plugins.analysis.core.FilesParser.parseFiles(FilesParser.java:258) at hudson.plugins.analysis.core.FilesParser.parserCollectionOfFiles(FilesParser.java:209) at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:178) at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:31) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2474) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 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 hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Unknown Source) PMD Collecting PMD analysis files... ERROR: Publisher hudson.plugins.pmd.PmdPublisher aborted due to exception java.lang.NullPointerException at org.apache.commons.digester3.Digester.getXMLReader(Digester.java:799) at org.apache.commons.digester3.Digester.parse(Digester.java:1642) at org.apache.commons.digester3.Digester.parse(Digester.java:1701) at hudson.plugins.pmd.parser.PmdParser.parse(PmdParser.java:70) at hudson.plugins.analysis.core.AbstractAnnotationParser.parse(AbstractAnnotationParser.java:53) at hudson.plugins.analysis.core.FilesParser.parseFile(FilesParser.java:300) at hudson.plugins.analysis.core.FilesParser.parseFiles(FilesParser.java:258) at hudson.plugins.analysis.core.FilesParser.parserCollectionOfFiles(FilesParser.java:209) at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:178) at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:31) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2474) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 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 hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Unknown Source) Environment: windows server 2012 R2 and windows7 Project: Jenkins Priority:
[JIRA] [github] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
Pradeepto Bhattacharya edited a comment on JENKINS-23641 Builds are failing due to GitHubCommitNotifier exception I was just bitten by this issue. I am using GitHub Pull Request Builder (1.16-0) along with Github plugin (1.9.1). I am trying build a PR using GHPRB. ERROR: Publisher com.cloudbees.jenkins.GitHubCommitNotifier aborted due to exception java.lang.NullPointerException at com.cloudbees.jenkins.GitHubCommitNotifier.perform(GitHubCommitNotifier.java:53) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:756) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720) at hudson.model.Build$BuildExecution.post2(Build.java:182) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:669) at hudson.model.Run.execute(Run.java:1731) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:232) Is there anything else I can provide to help with this error? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-24744) Build Pipeline view refreshes DOM for the entire page when a build finishes
Kasper Jacobsen created JENKINS-24744 Build Pipeline view refreshes DOM for the entire page when a build finishes Issue Type: Bug Assignee: Unassigned Components: build-pipeline Created: 17/Sep/14 12:39 PM Description: When a job is finished in a pipeline and you're viewing it the build pipeline plugin updates every job step. This causes the user to experience a lot of flashing elements on the page. Environment: Ubuntu server 14.04 on AWS EC2 Happens in all browsers Project: Jenkins Priority: Trivial Reporter: Kasper Jacobsen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-18426) When repository URL contains variable causes checkout from wrong SVN path
rzanner commented on JENKINS-18426 When repository URL contains variable causes checkout from wrong SVN path I have the same issue here. Jenkins reports checking out the desired tag (which contains a variable, that by itself contains the build number of the triggering build), but uses trunk instead (checked with svn info in file system). Is there some default, that falls back to trunk? I would rather let this build fail, when the checkout of the tag fails. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24745) hundson failed to create symlink cause incorrect function
Dominika Tomaszewska created JENKINS-24745 hundson failed to create symlink cause incorrect function Issue Type: Bug Assignee: Dominika Tomaszewska Components: subversion Created: 17/Sep/14 1:12 PM Description: The communicates being thrown in the console at the top of every build are kind of: ln 2014-09-17_14-23-26 T:\jenkins\jobs\Bootloader\builds\11 failed hudson.util.jna.WinIOException: Failed to create a symlink T:\jenkins\jobs\Bootloader\builds\11 to 2014-09-17_14-23-26 error=1:Incorrect function at hudson.util.jna.Kernel32Utils.createSymbolicLink(Kernel32Utils.java:93) at hudson.Util.createSymlink(Util.java:1078) at hudson.model.Run.updateSymlinks(Run.java:1792) at hudson.model.Run.execute(Run.java:1704) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:232) ln builds\lastSuccessfulBuild T:\jenkins\jobs\Bootloader\lastSuccessful failed hudson.util.jna.WinIOException: Failed to create a symlink T:\jenkins\jobs\Bootloader\lastSuccessful to builds\lastSuccessfulBuild error=1:Incorrect function at hudson.util.jna.Kernel32Utils.createSymbolicLink(Kernel32Utils.java:93) at hudson.Util.createSymlink(Util.java:1078) at hudson.model.Run.createSymlink(Run.java:1812) at hudson.model.Run.updateSymlinks(Run.java:1793) at hudson.model.Run.execute(Run.java:1704) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:232) ln builds\lastStableBuild T:\jenkins\jobs\Bootloader\lastStable failed hudson.util.jna.WinIOException: Failed to create a symlink T:\jenkins\jobs\Bootloader\lastStable to builds\lastStableBuild error=1:Incorrect function at hudson.util.jna.Kernel32Utils.createSymbolicLink(Kernel32Utils.java:93) at hudson.Util.createSymlink(Util.java:1078) at hudson.model.Run.createSymlink(Run.java:1812) at hudson.model.Run.updateSymlinks(Run.java:1794) at hudson.model.Run.execute(Run.java:1704) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:232) Building in workspace T:\jenkins\jobs\Bootloader\workspace Reverting T:\jenkins\jobs\Bootloader\workspace\. to depth infinity with ignoreExternals: false an then everything is getting normal and build is finished as success. Project: Jenkins Priority: Minor Reporter: Dominika Tomaszewska This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-20725) maven build creates symlinkd files that Windows OS does not understand
Joe Knudsen updated JENKINS-20725 maven build creates symlinkd files that Windows OS does not understand Change By: Joe Knudsen (17/Sep/14 1:25 PM) Description: Afterupgradingto1.509.4ourMavenbuildscreatefilesthatWindowscannotbackup.The UIseemstoworking.The invalid filesareSYMLINKDoneforeachmodule.The none maven builds buildandUI seem towork fine.Thefilesareunderthejobs/projectname/builds/buildnumberorbuilddatedirectory.11/19/201304:47PMSYMLINKDus.mn.state.education.sfin.automation$sfin-post-processor[../../modules/us.mn.state.education.sfin.automation$sfin-post-processor/builds/2013-11-19_16-40-46]4File(s)3,881,255bytes34Dir(s)20,236,365,824bytesfreeE:\jenkins\.jenkins\jobs\SFIN-OB\builds\56typeus.mn.state.education.sfin$configsAccessisdenied.E:\jenkins\.jenkins\jobs\SFIN-OB\builds\56cdus.mn.state.education.sfin$configsThefilename,directoryname,orvolumelabelsyntaxisincorrect.E:\jenkins\.jenkins\jobs\SFIN-OB\builds\56 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-20725) maven build creates symlinkd files that Windows OS does not understand
Joe Knudsen commented on JENKINS-20725 maven build creates symlinkd files that Windows OS does not understand Thomas we ended up excluding the build folders from our backups. Would like to see this resolved and be able to do a complete Jenkins backup. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24745) hundson failed to create symlink cause incorrect function
Daniel Beck updated JENKINS-24745 hundson failed to create symlink cause incorrect function Change By: Daniel Beck (17/Sep/14 1:40 PM) Status: Reopened 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] [subversion] (JENKINS-24745) hundson failed to create symlink cause incorrect function
Daniel Beck reopened JENKINS-24745 hundson failed to create symlink cause incorrect function Sorry, didn't see you assigned this to yourself. Reopening. Change By: Daniel Beck (17/Sep/14 1:40 PM) Resolution: Incomplete Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24745) hundson failed to create symlink cause incorrect function
Daniel Beck resolved JENKINS-24745 as Incomplete hundson failed to create symlink cause incorrect function Please read the guidelines how to report an issue, especially regarding what information to include. This report does not contain enough information to investigate any further. Change By: Daniel Beck (17/Sep/14 1:39 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10442) RestartNotSupportedException when trying to do safeRestart
Pierre-Nicolas Mougel commented on JENKINS-10442 RestartNotSupportedException when trying to do safeRestart I'm running Ubuntu 14.04 with Jenkins 1.580 and OpenJDK and I'm still having this problem with restart javax.servlet.ServletException: hudson.lifecycle.RestartNotSupportedException: Failed to obtain the command line arguments of the process at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) 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.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.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:960) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1021) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:865) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:240) at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668) at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: hudson.lifecycle.RestartNotSupportedException: Failed to obtain the command line arguments of the process at hudson.lifecycle.UnixLifecycle.verifyRestartable(UnixLifecycle.java:98) at jenkins.model.Jenkins.restart(Jenkins.java:3345) at jenkins.model.Jenkins.doRestart(Jenkins.java:3316) 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) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at
[JIRA] [maven] (JENKINS-20725) maven build creates symlinkd files that Windows OS does not understand
Thomas Pilz commented on JENKINS-20725 maven build creates symlinkd files that Windows OS does not understand Our Jenkins Instance is growing and we would like to move from VM to Hardware. This Bug makes it impossible to transfer the Jobs to the new Instance without Data loss. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-7478) Wrong EOL (UNIX type: LF) in Windows batch files executed for build steps of type Execute Windows batch command
SCM/JIRA link daemon resolved JENKINS-7478 as Fixed Wrong EOL (UNIX type: LF) in Windows batch files executed for build steps of type Execute Windows batch command Change By: SCM/JIRA link daemon (17/Sep/14 2:23 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7478) Wrong EOL (UNIX type: LF) in Windows batch files executed for build steps of type Execute Windows batch command
SCM/JIRA link daemon commented on JENKINS-7478 Wrong EOL (UNIX type: LF) in Windows batch files executed for build steps of type Execute Windows batch command Code changed in jenkins User: David Ruhmann Path: core/src/main/java/hudson/tasks/BatchFile.java core/src/main/java/hudson/tasks/Shell.java core/src/main/java/hudson/tools/AbstractCommandInstaller.java core/src/main/java/hudson/tools/BatchCommandInstaller.java core/src/main/java/hudson/tools/CommandInstaller.java core/src/main/java/hudson/util/LineEndingConversion.java test/src/test/java/hudson/tasks/BatchFileTest.java test/src/test/java/hudson/tasks/ShellTest.java test/src/test/java/hudson/tools/BatchCommandInstallerTest.java test/src/test/java/hudson/tools/CommandInstallerTest.java test/src/test/java/hudson/util/LineEndingConversionTest.java http://jenkins-ci.org/commit/jenkins/67ac47af0709dde6297dffeb210b03d8b65f6033 Log: FIXED JENKINS-7478 Create Line Ending Conversion utility to convert scripts to proper OS line ending type. Tests included. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-7478) Wrong EOL (UNIX type: LF) in Windows batch files executed for build steps of type Execute Windows batch command
SCM/JIRA link daemon commented on JENKINS-7478 Wrong EOL (UNIX type: LF) in Windows batch files executed for build steps of type Execute Windows batch command Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/tasks/BatchFile.java core/src/main/java/hudson/tasks/Shell.java core/src/main/java/hudson/tools/AbstractCommandInstaller.java core/src/main/java/hudson/tools/BatchCommandInstaller.java core/src/main/java/hudson/tools/CommandInstaller.java core/src/main/java/hudson/util/LineEndingConversion.java test/src/test/java/hudson/tasks/BatchFileTest.java test/src/test/java/hudson/tasks/ShellTest.java test/src/test/java/hudson/tools/BatchCommandInstallerTest.java test/src/test/java/hudson/tools/CommandInstallerTest.java test/src/test/java/hudson/util/LineEndingConversionTest.java http://jenkins-ci.org/commit/jenkins/3d25f57aa1352359331675c05cd387e6bc536a3a Log: Merge pull request #1370 from DavidRuhmann/JENKINS-7478 FIXED JENKINS-7478 Correct Line Endings for Batch Files Compare: https://github.com/jenkinsci/jenkins/compare/8bb88be27ec4...3d25f57aa135 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-remote-trigger] (JENKINS-24731) Using Remote Trigger Plugin and properties files can get job into a weird state where it cannot be aborted
Lorelei McCollum
commented on JENKINS-24731
Using Remote Trigger Plugin and properties files can get job into a weird state where it cannot be aborted
This is the issue in the code
while (preCheckResponse.getBoolean("building") == true || preCheckResponse.getString("result") == null) {
listener.getLogger().println("Remote build is currently running - waiting for it to finish.");
preCheckResponse = sendHTTPCall(preCheckUrlString, "POST", build, listener);
listener.getLogger().println("Waiting for " + this.pollInterval + " seconds until next retry.");
// Sleep for 'pollInterval' seconds.
// Sleep takes miliseconds so need to convert this.pollInterval to milisecopnds (x 1000)
try {
Thread.sleep(this.pollInterval * 1000);
} catch (InterruptedException e) {
this.failBuild(e, listener);
}
}
failBuild never is allowed to get into the abort exception because the boolean variable that would allow that is never modified after instance created
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-15576) LoadStatistics queue length and Cloud provisioning not working in conjunction with Node and Label parameter plugin
dogfood commented on JENKINS-15576 LoadStatistics queue length and Cloud provisioning not working in conjunction with Node and Label parameter plugin Integrated in jenkins_main_trunk #3686 FIXED JENKINS-15576 Label's Load Statistics queue length based on (Revision b47f527ce9427218aecde544e0d5a196925cb892) Test cases for FIXED JENKINS-15576 (Revision c49420e622facb8cc98e5f4447c0fc8ad6660990) Result = SUCCESS laurence.hey : b47f527ce9427218aecde544e0d5a196925cb892 Files : core/src/main/java/hudson/model/LoadStatistics.java changelog.html laurence.hey : c49420e622facb8cc98e5f4447c0fc8ad6660990 Files : core/src/main/java/hudson/model/LoadStatistics.java test/src/test/java/hudson/model/LabelLoadStatisticsQueueLengthTest.java changelog.html test/pom.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] [perforce] (JENKINS-24740) Expose duration of sync in ENV
Rob Petti assigned JENKINS-24740 to Unassigned Expose duration of sync in ENV Change By: Rob Petti (17/Sep/14 3:31 PM) Assignee: RobPetti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [perforce] (JENKINS-24740) Expose duration of sync in ENV
Kanstantsin Shautsou commented on JENKINS-24740 Expose duration of sync in ENV Additionally, you can create separate tool that will just analyze build logs with existed timestamps and then provide any info you want for your it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-14744) java.lang.OutOfMemoryError: GC overhead limit exceeded
Bryce Schober updated JENKINS-14744 java.lang.OutOfMemoryError: GC overhead limit exceeded It seems like something has changed for me, since now at least it isn't getting hung up in what feels like a GC spiral. I've attached a memory usage graph and thread dump, compliments of the JavaMelody Monitoring plugin. Change By: Bryce Schober (17/Sep/14 3:35 PM) Attachment: jenkins_thread_dump.txt Attachment: usedMemory.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] [maven] (JENKINS-21330) java.nio.file.DirectoryNotEmptyException: /home/dev/.jenkins/jobs/MyBuild/lastSuccessful
Michael Pereira
updated JENKINS-21330
java.nio.file.DirectoryNotEmptyException: /home/dev/.jenkins/jobs/MyBuild/lastSuccessful
Change By:
Michael Pereira
(17/Sep/14 3:40 PM)
Description:
Hello,Onthelatestversion1.546foramavenbuildIgetthiserror:
{noformat}
Startedbyuseranonymouslnbuilds/lastSuccessfulBuild/home/dev/.jenkins/jobs/MyBuild/lastSuccessfulfailedjava.nio.file.DirectoryNotEmptyException:/home/dev/.jenkins/jobs/MyBuild/lastSuccessful atsun.nio.fs.UnixFileSystemProvider.implDelete(UnixFileSystemProvider.java:241) atsun.nio.fs.AbstractFileSystemProvider.deleteIfExists(AbstractFileSystemProvider.java:108) atjava.nio.file.Files.deleteIfExists(Files.java:1116) atsun.reflect.GeneratedMethodAccessor313.invoke(UnknownSource) atsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) atjava.lang.reflect.Method.invoke(Method.java:601) athudson.Util.createSymlinkJava7(Util.java:1146) athudson.Util.createSymlink(Util.java:1064) athudson.model.Run.createSymlink(Run.java:1783) athudson.model.Run.updateSymlinks(Run.java:1764) athudson.model.Run.execute(Run.java:1676) athudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519) athudson.model.ResourceController.execute(ResourceController.java:88) athudson.model.Executor.run(Executor.java:231)lnbuilds/lastStableBuild/home/dev/.jenkins/jobs/MyBuild/lastStablefailedjava.nio.file.DirectoryNotEmptyException:/home/dev/.jenkins/jobs/MyBuild/lastStable atsun.nio.fs.UnixFileSystemProvider.implDelete(UnixFileSystemProvider.java:241) atsun.nio.fs.AbstractFileSystemProvider.deleteIfExists(AbstractFileSystemProvider.java:108) atjava.nio.file.Files.deleteIfExists(Files.java:1116) atsun.reflect.GeneratedMethodAccessor313.invoke(UnknownSource) atsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) atjava.lang.reflect.Method.invoke(Method.java:601) athudson.Util.createSymlinkJava7(Util.java:1146) athudson.Util.createSymlink(Util.java:1064) athudson.model.Run.createSymlink(Run.java:1783) athudson.model.Run.updateSymlinks(Run.java:1765) athudson.model.Run.execute(Run.java:1676) athudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519) athudson.model.ResourceController.execute(ResourceController.java:88) athudson.model.Executor.run(Executor.java:231)Buildinginworkspace/home/dev/.jenkins/jobs/MyBuild/workspaceUpdatingsvn://myweb.com/repos/Events/trunkatrevision2014-01-10T15:06:09.745+Atrevision1974WARNING:clockofthesubversionserverappearstobeoutofsync.Thiscanresultininconsistentcheckoutbehavior.nochangeforsvn://myweb.com/repos/Events/trunksincethepreviousbuildParsingPOMs
{noformat}
Itdoesnotseemtogetthelatestupdatefromthesvn.Switchingbackto1.544fixedtheissue.CheersGreg
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [valgrind] (JENKINS-13745) Valgrind Plugin: Any Configuration of the publish valgrind results part triggers exception
Artem Popov updated JENKINS-13745 Valgrind Plugin: Any Configuration of the publish valgrind results part triggers exception Change By: Artem Popov (17/Sep/14 3:47 PM) Attachment: Overview.png Attachment: graph.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] [valgrind] (JENKINS-13745) Valgrind Plugin: Any Configuration of the publish valgrind results part triggers exception
Artem Popov commented on JENKINS-13745 Valgrind Plugin: Any Configuration of the publish valgrind results part triggers exception @Johannes, thank you for the fix, it works fine for me now. Bug happened because I use my own valgrind version with some extra functionality, and I did not add some field to the report which I considered as not mandatory, but it was. Reports looks like correct now, but I am worried about performance. Jenkins need to many time for display reports. It take about 45 seconds for each request. I attached screenshot of timing. It is not related to this story, but will be interesting to know your opinion about performance 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] [maven] (JENKINS-21330) java.nio.file.DirectoryNotEmptyException: /home/dev/.jenkins/jobs/MyBuild/lastSuccessful
Swapnil Mate commented on JENKINS-21330 java.nio.file.DirectoryNotEmptyException: /home/dev/.jenkins/jobs/MyBuild/lastSuccessful After cleaning up the last stable and lastsuccessful folder i'm not getting this error. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-24746) Support a way to retrigger part of matrix job
Roland Schulz created JENKINS-24746 Support a way to retrigger part of matrix job Issue Type: New Feature Assignee: rsandell Components: gerrit-trigger Created: 17/Sep/14 3:49 PM Description: It would be nice if one could retrigger only part of matrix job. This would avoid having to rerun the whole matrix because of some temporary problem for a single matrix job. Possible interface options: Add a menu item "Retrigger unsuccessful" under "Retrigger" on the main matrix page. It would retrigger all jobs which either failed or were unstable. If the Matrix Reloaded Plugin plugin is installed also, support their matrix view as a way to retrigger Add a "Retrigger" menu item on the individual matrix job (currently only the main job contains a link). If that link is clicked only the individual job is retriggered not the whole matrix. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-23929) Cannot use 'WORKSPACE' variable when creating custom workspace to *modify* the auto-generated workspace
Rob Petti commented on JENKINS-23929 Cannot use WORKSPACE variable when creating custom workspace to *modify* the auto-generated workspace I fail to see the need for checking out each branch into it's own workspace. I perform similar branch selection at build time without any issues simply by using a build parameter in the client view spec. I suggest you do the same. Also, if the clean functionality doesn't work for your use-case, then simply don't use it. Fix your build scripts so they clean up after themselves and you won't have to wipe the workspace at all. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7478) Wrong EOL (UNIX type: LF) in Windows batch files executed for build steps of type Execute Windows batch command
dogfood commented on JENKINS-7478 Wrong EOL (UNIX type: LF) in Windows batch files executed for build steps of type Execute Windows batch command Integrated in jenkins_main_trunk #3687 FIXED JENKINS-7478 (Revision 67ac47af0709dde6297dffeb210b03d8b65f6033) Result = SUCCESS david.ruhmann : 67ac47af0709dde6297dffeb210b03d8b65f6033 Files : test/src/test/java/hudson/util/LineEndingConversionTest.java test/src/test/java/hudson/tools/BatchCommandInstallerTest.java core/src/main/java/hudson/tools/BatchCommandInstaller.java test/src/test/java/hudson/tools/CommandInstallerTest.java core/src/main/java/hudson/tasks/Shell.java test/src/test/java/hudson/tasks/ShellTest.java core/src/main/java/hudson/util/LineEndingConversion.java core/src/main/java/hudson/tasks/BatchFile.java core/src/main/java/hudson/tools/CommandInstaller.java core/src/main/java/hudson/tools/AbstractCommandInstaller.java test/src/test/java/hudson/tasks/BatchFileTest.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] [android-emulator] (JENKINS-24736) Android emulator plugin does not use all available executors on a slave
JY Hsu commented on JENKINS-24736 Android emulator plugin does not use all available executors on a slave Yes the launch existing emulators isn't a problem now. The problem now is that when running more than one jobs that creates new emulator on the same slave node, only one will be run. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [valgrind] (JENKINS-13745) Valgrind Plugin: Any Configuration of the publish valgrind results part triggers exception
Artem Popov edited a comment on JENKINS-13745 Valgrind Plugin: Any Configuration of the publish valgrind results part triggers exception @Johannes, thank you for the fix, it works fine for me now. Bug happened because I use my own valgrind version with some extra functionality, and I did not add some field to the report which I considered as not mandatory, but it was. Reports looks like correct now, but I am worried about performance. Jenkins need to many time for display reports. It take about 45 seconds for each request. I attached screenshot of timing. It is not related to this story, but will be interesting to know your opinion about performance issues. P.S. Job contain ~250 valgrind report files, with 1Mb data in the each file. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [rvm] (JENKINS-24747) RVM plugin manipulations via script console
Serghei Anicheev created JENKINS-24747 RVM plugin manipulations via script console Issue Type: Task Assignee: Unassigned Components: rvm Created: 17/Sep/14 4:44 PM Description: I want to be able to create jobs via script console and enable RVM environment for them. Actually don't know how to implement it.Tried to find from jenkins sources but no luck. I'm creating job with this command: job = Jenkins.getInstance().createProject(FreeStyleProject.class, "test123") The next i found from jenkins sources should be something like : job.getBuildWrappersList().add(wrapper) And here is the problem. How should i initialize wrapper correctly for RVM plugin? Please clarify this aspect. Project: Jenkins Priority: Trivial Reporter: Serghei Anicheev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [rvm] (JENKINS-24747) RVM plugin manipulations via script console
Serghei Anicheev updated JENKINS-24747 RVM plugin manipulations via script console Change By: Serghei Anicheev (17/Sep/14 4:46 PM) Description: IwanttobeabletocreatejobsviascriptconsoleandenableRVMenvironmentforthem.Actuallydontknowhowtoimplementit.Triedtofindfromjenkinssourcesbutnoluck.Imcreatingjobwiththiscommand:job=Jenkins.getInstance().createProject(FreeStyleProject.class,test123)Thenextifoundfromjenkinssourcesshouldbesomethinglike:job.getBuildWrappersList().add(wrapper)Andhereistheproblem.HowshouldiinitializewrappercorrectlyforRVMplugin? IntestsisawthisTestBuildWrapperwrapper=newTestBuildWrapper();.Butwhatsarealimplementationonthis? Pleaseclarifythisaspect. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [rvm] (JENKINS-24747) RVM plugin manipulations via script console
Daniel Beck resolved JENKINS-24747 as Not A Defect RVM plugin manipulations via script console Jira is not a support site. Ask on the jenkinsci-users (or even jenkinsci-dev) mailing list, or in #jenkins on Freenode. Change By: Daniel Beck (17/Sep/14 4:48 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [envinject] (JENKINS-24287) EnvInject exposes password hashes
Daniel Beck commented on JENKINS-24287 EnvInject exposes password hashes Jesse Glick: No, this is about variables recognized by Env-Inject as passwords. They're only shown in encrypted form on the Injected Env Vars page, but that can be reused in another job in the same instance the malicious user has config access to: Just run env there and you "decrypted" the password. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-22675) Jenkins GIT Plugin unable to access repository using HTTPS with self-signed certificate
Jim Colton commented on JENKINS-22675 Jenkins GIT Plugin unable to access repository using HTTPS with self-signed certificate The access is working for me if I use select to have Jenkins use JGit in the "Configure System" section, use the ssh protocol when specifying the git repo (git@gitHost/repo) and also using ssh keys so that ssh works without asking for password. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-22675) Jenkins GIT Plugin unable to access repository using HTTPS with self-signed certificate
Jim Colton edited a comment on JENKINS-22675 Jenkins GIT Plugin unable to access repository using HTTPS with self-signed certificate The access is working for me if I select to have Jenkins use JGit in the "Configure System" section, use the ssh protocol when specifying the git repo (git@gitHost/repo) and also using ssh keys so that ssh works without asking for password. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-24640) File modes are wrong after git checkout
Gustavo Chaves commented on JENKINS-24640 File modes are wrong after git checkout I'd say that reasonableness is in the eye of the beholder. But you're absolutely right in that the bug/misfeature isn't a Jenkins problem. I've been able to reproduce it with the JGit command line tool and opened an issue in their Bugzilla. Thank you! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [customtools-plugin] (JENKINS-14515) Malformed PATH environment variable on Windows slave (unix syntax used)
Jesse Glick reopened JENKINS-14515 Malformed PATH environment variable on Windows slave (unix syntax used) Behavior may have been changed, but not actually fixed in 0.4.2. You now get Path=C:\slave\tools\something;C:\slave\tools\something\bin;:C:\WINDOWS\system32;… Note the : separating the path addition from the original path, causing the first entry in the original path to be unusable. Change By: Jesse Glick (17/Sep/14 7:14 PM) Resolution: Fixed Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [customtools-plugin] (JENKINS-14515) Malformed PATH environment variable on Windows slave (unix syntax used)
Jesse Glick updated JENKINS-14515 Malformed PATH environment variable on Windows slave (unix syntax used) Change By: Jesse Glick (17/Sep/14 7:14 PM) Status: Reopened 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] [customtools-plugin] (JENKINS-14515) Malformed PATH environment variable on Windows slave (unix syntax used)
Jesse Glick started work on JENKINS-14515 Malformed PATH environment variable on Windows slave (unix syntax used) Change By: Jesse Glick (17/Sep/14 7:14 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-flow] (JENKINS-24748) If running build is aborted, other concurrent and future builds don't run in executors.
Charles Stephens created JENKINS-24748 If running build is aborted, other concurrent and future builds dont run in executors. Issue Type: Bug Assignee: Nicolas De Loof Components: build-flow Created: 17/Sep/14 7:40 PM Description: When a build flow job is started on a node that was previously idle, then additional concurrent builds are started. If the first build is aborted, then the other builds, and all subsequent concurrent builds no longer run in an executor on that node. Steps to Reproduce Create a node which: has four or more executors, and the availability is set to "Take this slave on-line when in demand and off-line when idle." Create a free-style project job with a build step that calls "sleep 180" Create a build flow project which: has the "Flow run needs a workspace" set, starts a build of the job from the previous step, has "Execute concurrent builds if necessary" set, and is restricted to the node created in the first step. Confirm that the node created in the first step is idle and the slave agent has not started. Start a build. Observe that it runs on one of the executors. Start another build. Observe that it too runs on one of the executors. Cancel the first build. Observe that the second build is no longer running on an executor Start one or more jobs while the second job is also running and continue to observe them not running on any of the executors. The builds no longer are returned when Computer.getExecutors() is called, but they are with Computer.getOneOffExecutors(). Environment: core: 1.565.2 build flow plugin: 0.15 Project: Jenkins Priority: Minor Reporter: Charles Stephens This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-flow] (JENKINS-24748) If running build flow job is aborted, other concurrent and future builds don't run a node's executors.
Charles Stephens updated JENKINS-24748 If running build flow job is aborted, other concurrent and future builds dont run a nodes executors. Change By: Charles Stephens (17/Sep/14 7:41 PM) Summary: Ifrunningbuild flowjob isaborted,otherconcurrentandfuturebuildsdontrun in anodes executors. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gui] (JENKINS-24749) please change the font back - the helvetica font is messing up the whole gui under folders
marlene cote created JENKINS-24749 please change the font back - the helvetica font is messing up the whole gui under folders Issue Type: Improvement Assignee: Unassigned Components: gui Created: 17/Sep/14 8:28 PM Description: The latest version of Jenkins has a Helvetica font and no way to resize the columns or delete columns inside of folders. it is displaying my job names in a very narrow column. I can shrink the whole window with ctrl -, but then things are too small to read. Not sure why you changed the default font, but it was fine before. Environment: windows Project: Jenkins Priority: Major Reporter: marlene cote This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-23665) Parameter to select alias of SSL/TLS certificate for Jenkins Web UI, private key password
SCM/JIRA link daemon commented on JENKINS-23665 Parameter to select alias of SSL/TLS certificate for Jenkins Web UI, private key password Code changed in jenkins User: Kohsuke Kawaguchi Path: src/java/winstone/HttpsConnectorFactory.java src/java/winstone/cmdline/Option.java http://jenkins-ci.org/commit/winstone/a9cd71255b74637f1d0bc227e8d4dee907f3fe0b Log: Merge pull request #16 from TorstenS73/master FIXED JENKINS-23665 Parameter to select alias ... Compare: https://github.com/jenkinsci/winstone/compare/52e94ad4669d...a9cd71255b74 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-23665) Parameter to select alias of SSL/TLS certificate for Jenkins Web UI, private key password
SCM/JIRA link daemon resolved JENKINS-23665 as Fixed Parameter to select alias of SSL/TLS certificate for Jenkins Web UI, private key password Change By: SCM/JIRA link daemon (17/Sep/14 8:54 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-23665) Parameter to select alias of SSL/TLS certificate for Jenkins Web UI, private key password
SCM/JIRA link daemon commented on JENKINS-23665 Parameter to select alias of SSL/TLS certificate for Jenkins Web UI, private key password Code changed in jenkins User: TorstenS73 Path: src/java/winstone/HttpsConnectorFactory.java src/java/winstone/cmdline/Option.java http://jenkins-ci.org/commit/winstone/e3434028033c31269157229ff43391a8b29ea828 Log: JENKINS-23665 Parameter to select alias of SSL/TLS certificate for Jenkins Web UI, private key password This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [ssh-agent] (JENKINS-24750) Cannot find user credentials when job is triggered with parameters
Ole Christian Langfjæran created JENKINS-24750 Cannot find user credentials when job is triggered with parameters Issue Type: Bug Assignee: Unassigned Components: ssh-agent Created: 17/Sep/14 9:07 PM Description: Given I have a job A And job A has Credentials Parameter And job A triggers job B sending job A's parameters And job B has Credentials Parameter And job B uses ssh-agent And job B uses Authorize Project plugin And job B uses Run as user who triggered the build When I build job A And choose a credential from logged in user Then job B should find the credentials The result unfortunately is this: Started by upstream project "jobA" build number 4 originally caused by: Started by user Superman Running as Superman Building in workspace /app/jenkins/jobs/jobB/workspace FATAL: [ssh-agent] Could not find specified credentials [ssh-agent] Looking for ssh-agent implementation... [ssh-agent] Java/JNR ssh-agent [ssh-agent] Started. Project: Jenkins Priority: Major Reporter: Ole Christian Langfjæran This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
