[JIRA] [performance-plugin] (JENKINS-28426) JMeterCSV always reports 100% 0f errors
Title: Message Title Mayank Saini commented on JENKINS-28426 Re: JMeterCSV always reports 100% 0f errors Is there any update on the issue? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23120) FATAL: hudson.remoting.RequestAbortedException on Windows Slaves
Title: Message Title Greg Byrne commented on JENKINS-23120 Re: FATAL: hudson.remoting.RequestAbortedException on Windows Slaves I had a similar issue after upgrading Jenkins to 1.614 on my Windows 7 (64 bit) slaves. Similar to Fernando, they were running JDK 1.6 (32 bits). As soon as I downgraded back to the previous version, all the slaves came back online. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-pullrequest-plugin] (JENKINS-28515) Always require ok to test from admin
Title: Message Title Kanstantsin Shautsou commented on JENKINS-28515 Re: Always require ok to test from admin Please confirm what exactly PR plugin do you use. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-28515) Always require ok to test from admin
Title: Message Title Kanstantsin Shautsou assigned an issue to Honza Brzdil Jenkins / JENKINS-28515 Always require ok to test from admin Change By: Kanstantsin Shautsou Assignee: KanstantsinShautsou HonzaBrzdil Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-28515) Always require ok to test from admin
Title: Message Title Kanstantsin Shautsou updated an issue Jenkins / JENKINS-28515 Always require ok to test from admin Change By: Kanstantsin Shautsou Component/s: ghprb-plugin Component/s: github-pullrequest-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-pullrequest-plugin] (JENKINS-28515) Always require ok to test from admin
Title: Message Title Thomas Diesler commented on JENKINS-28515 Re: Always require ok to test from admin ghprb-1.20 https://wiki.jenkins-ci.org/display/JENKINS/GitHub+pull+request+builder+plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-pullrequest-plugin] (JENKINS-28515) Always require ok to test from admin
Title: Message Title Thomas Diesler created an issue Jenkins / JENKINS-28515 Always require ok to test from admin Issue Type: Improvement Assignee: Kanstantsin Shautsou Components: github-pullrequest-plugin Created: 21/May/15 7:42 AM Priority: Minor Reporter: Thomas Diesler We like to use a model for wildfly-camel where it is always required to have second pair of eyes on a given pull request. An admin should be able to ok to tests his own PRs. However, no PR should automatically be executed and merged. Add Comment
[JIRA] [clearcase-ucm-plugin] (JENKINS-28514) Failure to recommend created baseline with poll rebase (case 13049)
Title: Message Title Mads Nielsen created an issue Jenkins / JENKINS-28514 Failure to recommend created baseline with poll rebase (case 13049) Issue Type: Bug Assignee: Praqma Support Components: clearcase-ucm-plugin Created: 21/May/15 7:16 AM Priority: Major Reporter: Mads Nielsen Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are
[JIRA] [exclusion-plugin] (JENKINS-12399) Dynamic exclusion resourced based on parameter name
Title: Message Title Tim Rule commented on JENKINS-12399 Re: Dynamic exclusion resourced based on parameter name Hello, I have a similar situation with Template Jobs which can run on any number of Slaves however the exact Slave is specified in an upstream Job (its actually stored in a Properties File and loaded as an Environment Variable). These Jobs use the Exclusion plugin to access various resources on the Slave. It would be great if the Slave could be specified as an Environment Variable (loaded by Inject Env plugin) or as a Parameter. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-28511) Trigger builds remotely is started but nothing changes
Title: Message Title kean Luke commented on JENKINS-28511 Re: Trigger builds remotely is started but nothing changes 1.In Stash, install the Stash Webhook for Jenkins plugin 2.add the AuthenticationToken name in Trigger build remotely field 3.developers merge their code to Stash. 4.Jenkins detect the commit action via Trigger build remotely function and build action is started Expect: http://jenkins_server/job/git_project/build_seq_number/changes show the changes log Summary Merge pull request #1in project from feature/user/feature to master (details) or developer's comments (details) actually: please check my uploaded attachments. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-28446) UnlabeledLoad.computeQueueLength() includes labeled jobs
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-28446 UnlabeledLoad.computeQueueLength() includes labeled jobs Change By: Oleg Nenashev Labels: cloudloadstatistics lts-candidate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-28511) Trigger builds remotely is started but nothing changes
Title: Message Title kean Luke updated an issue Jenkins / JENKINS-28511 Trigger builds remotely is started but nothing changes Change By: kean Luke Attachment: upload002.JPG Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26854) EC2 slave launch stops working after a while with AmazonServiceException Request has expired
Title: Message Title martinfr62 commented on JENKINS-26854 Re: EC2 slave launch stops working after a while with AmazonServiceException Request has expired James - just an fyi the message about pending spot instances is actually n othing to do with spot instances. Weird I know - it just means that you have a pending queue size of 23, after all spot instances have been launched - as you dont have any spot instances - you just have a queue size of 23. That's all the message means. Nothing to do really with spot instances. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-blocker-plugin] (JENKINS-28513) Build-Blocker-Plugin blocks on builds queued leading to deadlock
Title: Message Title Thomas Schweikle created an issue Jenkins / JENKINS-28513 Build-Blocker-Plugin blocks on builds queued leading to deadlock Issue Type: Bug Assignee: Unassigned Components: build-blocker-plugin Created: 21/May/15 7:11 AM Labels: blocking Priority: Major Reporter: Thomas Schweikle Assume two projects that never shall be build in parallel. You may build project A, then project B or vice versa, but never project A and B together. In Project A you define project B as blocker. In Project B you define project A as blocker. All will be fine: Project A builds, Project B is blocked. Project B builds, Project A is blocked. ... until when Project A is queued, because no available slots to build, and then Project B is queued to. Now Project A blocks Project B, while Project B blocks Project A. Both will never be build! Cause: Build-Blocker-Plugin does not only take running projects in to account to block other projects, it takes the queue too! This leads to deadlocks as soon as both projects are queued. The plugin should only take running projects into account blocking other projects.
[JIRA] [git-client-plugin] (JENKINS-26417) Allow to customize refspec/tags of the clone/fetch commands
Title: Message Title
Daniel Geiler edited a comment on JENKINS-26417
Re: Allow to customize refspec/tags of the clone/fetch commands
Asfarasicanseetherefspecisnotusedontheinitialclone.Hereistherelevantextractfromabuildwithacleanedworkspace:{noformat}CloningtheremoteGitrepositoryCloningrepositorygitserver:/data/git/MyProject.git/usr/bin/gitinit/data/jenkins/workspace/myjob.checkoutrefspec#timeout=10Fetchingupstreamchangesfromgitserver:/data/git/MyProject.git/usr/bin/git--version#timeout=10usingGIT_SSHtosetcredentialsJenkinsprivatekey/usr/bin/gitfetch--tags--progressgitserver:/data/git/MyProject.git+refs/heads/*:refs/remotes/origin/*/usr/bin/gitconfigremote.origin.urlgitserver:/data/git/MyProject.git#timeout=10/usr/bin/gitconfig--addremote.origin.fetch+refs/heads/*:refs/remotes/origin/*#timeout=10/usr/bin/gitconfigremote.origin.urlgitserver:/data/git/MyProject.git#timeout=10{noformat}thisisdirectlyfollowedby{noformat}Fetchingupstreamchangesfromgitserver:/data/git/MyProject.gitusingGIT_SSHtosetcredentialsJenkinsprivatekey/usr/bin/gitfetch--tags--progressgitserver:/data/git/MyProject.git+refs/heads/development:refs/remotes/origin/development/usr/bin/gitrev-parseorigin/development^{commit}#timeout=10CheckingoutRevisionc5280c05a01a61f2ae43e46a1ee398be27cdc14e(origin/development)/usr/bin/gitconfigcore.sparsecheckout#timeout=10/usr/bin/gitcheckout-fc5280c05a01a61f2ae43e46a1ee398be27cdc14eFirsttimebuild.Skippingchangelog.{noformat}wichisthesameforlaterBuilds.Itestedwith:*JenkinsLatestandgreatest(1.614)*JenkinsOlderbutstable(1.596.3)*git-client1.17.1*git-client1.16.1 *Gitplugin2.3.5 Anyonecanconfirmthis?Wehavesomeoldandheavybranches(withsomebinaries)thatwedonotwanttogetfetchedatanytime.Asoftodaythisisonlypossiblewithsparsecheckouts,buttheyhavethedrawbackthatwecannotpushtagsbacktoremoteafterthebuild.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-plugin] (JENKINS-26417) Allow to customize refspec/tags of the clone/fetch commands
Title: Message Title
Daniel Geiler edited a comment on JENKINS-26417
Re: Allow to customize refspec/tags of the clone/fetch commands
Asfarasicanseetherefspecisnotusedontheinitialclone.Hereistherelevantextractfromabuildwithacleanedworkspace:{noformat}CloningtheremoteGitrepositoryCloningrepositorygitserver:/data/git/MyProject.git/usr/bin/gitinit/data/jenkins/workspace/myjob.checkoutrefspec#timeout=10Fetchingupstreamchangesfromgitserver:/data/git/MyProject.git/usr/bin/git--version#timeout=10usingGIT_SSHtosetcredentialsJenkinsprivatekey/usr/bin/gitfetch--tags--progressgitserver:/data/git/MyProject.git+refs/heads/*:refs/remotes/origin/*/usr/bin/gitconfigremote.origin.urlgitserver:/data/git/MyProject.git#timeout=10/usr/bin/gitconfig--addremote.origin.fetch+refs/heads/*:refs/remotes/origin/*#timeout=10/usr/bin/gitconfigremote.origin.urlgitserver:/data/git/MyProject.git#timeout=10{noformat}thisisdirectlyfollowedby{noformat}Fetchingupstreamchangesfromgitserver:/data/git/MyProject.gitusingGIT_SSHtosetcredentialsJenkinsprivatekey/usr/bin/gitfetch--tags--progressgitserver:/data/git/MyProject.git+refs/heads/development:refs/remotes/origin/development/usr/bin/gitrev-parseorigin/development^{commit}#timeout=10CheckingoutRevisionc5280c05a01a61f2ae43e46a1ee398be27cdc14e(origin/development)/usr/bin/gitconfigcore.sparsecheckout#timeout=10/usr/bin/gitcheckout-fc5280c05a01a61f2ae43e46a1ee398be27cdc14eFirsttimebuild.Skippingchangelog.{noformat}wichisthesameforlaterBuilds.Itestedwith:*JenkinsLatestandgreatest(1.614)*JenkinsOlderbutstable(1.596.3)*git-client1.17.1*git-client1.16.1*Gitplugin2.3.5 and2.3.4 Anyonecanconfirmthis?Wehavesomeoldandheavybranches(withsomebinaries)thatwedonotwanttogetfetchedatanytime.Asoftodaythisisonlypossiblewithsparsecheckouts,buttheyhavethedrawbackthatwecannotpushtagsbacktoremoteafterthebuild. Hopethisistherightplace,orshouldthatbereportedtothegitplugin?
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
[JIRA] [git-client-plugin] (JENKINS-26417) Allow to customize refspec/tags of the clone/fetch commands
Title: Message Title Vincent Latombe closed an issue as Fixed Jenkins / JENKINS-26417 Allow to customize refspec/tags of the clone/fetch commands Change By: Vincent Latombe Status: Reopened Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-26417) Allow to customize refspec/tags of the clone/fetch commands
Title: Message Title Vincent Latombe edited a comment on JENKINS-26417 Re: Allow to customize refspec/tags of the clone/fetch commands Itisadifferentissue,pleaseopenaseparateticket . onthegitplugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-26417) Allow to customize refspec/tags of the clone/fetch commands
Title: Message Title Vincent Latombe commented on JENKINS-26417 Re: Allow to customize refspec/tags of the clone/fetch commands It is a different issue, please open a separate ticket. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-28516) refsec is not applied on clone (initial fetch)
Title: Message Title Daniel Geiler created an issue Jenkins / JENKINS-28516 refsec is not applied on clone (initial fetch) Issue Type: Bug Assignee: Nicolas De Loof Components: git-plugin Created: 21/May/15 9:37 AM Environment: Jenkins Latest and greatest (1.614) / Older but stable (1.596.3) git-client 1.17.1 / 1.16.1 git-plugin 2.3.5 / 2.3.4 Labels: git Priority: Major Reporter: Daniel Geiler As far as i can see the refspec is not used on the initial clone. Here is the relevant extract from a build with a cleaned workspace: Cloning the remote Git repository Cloning repository gitserver:/data/git/MyProject.git /usr/bin/git init /data/jenkins/workspace/myjob.checkoutrefspec # timeout=10 Fetching upstream changes from gitserver:/data/git/MyProject.git /usr/bin/git --version # timeout=10 using GIT_SSH to set credentials Jenkins private key /usr/bin/git fetch --tags --progress
[JIRA] [p4-plugin] (JENKINS-28498) Null Pointer when publishing assets and server is down
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28498 Re: Null Pointer when publishing assets and server is down Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/asset/AssetNotifier.java src/main/java/org/jenkinsci/plugins/p4/client/ClientHelper.java src/main/java/org/jenkinsci/plugins/p4/client/ConnectionHelper.java src/main/java/org/jenkinsci/plugins/p4/tasks/AbstractTask.java http://jenkins-ci.org/commit/p4-plugin/efe25d4cb794e2b48e876ab5eeb9d0803d78355d Log: Improved Error for Publish step when connection is down. JENKINS-28498 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-26417) Allow to customize refspec/tags of the clone/fetch commands
Title: Message Title
Daniel Geiler reopened an issue
As far as i can see the refspec is not used on the initial clone.
Here is the relevant extract from a build with a cleaned workspace:
Cloning the remote Git repository
Cloning repository gitserver:/data/git/MyProject.git
/usr/bin/git init /data/jenkins/workspace/myjob.checkoutrefspec # timeout=10
Fetching upstream changes from gitserver:/data/git/MyProject.git
/usr/bin/git --version # timeout=10
using GIT_SSH to set credentials Jenkins private key
/usr/bin/git fetch --tags --progress gitserver:/data/git/MyProject.git +refs/heads/*:refs/remotes/origin/*
/usr/bin/git config remote.origin.url gitserver:/data/git/MyProject.git # timeout=10
/usr/bin/git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
/usr/bin/git config remote.origin.url gitserver:/data/git/MyProject.git # timeout=10
this is directly followed by
Fetching upstream changes from gitserver:/data/git/MyProject.git
using GIT_SSH to set credentials Jenkins private key
/usr/bin/git fetch --tags --progress gitserver:/data/git/MyProject.git +refs/heads/development:refs/remotes/origin/development
/usr/bin/git rev-parse origin/development^{commit} # timeout=10
Checking out Revision c5280c05a01a61f2ae43e46a1ee398be27cdc14e (origin/development)
/usr/bin/git config core.sparsecheckout # timeout=10
/usr/bin/git checkout -f c5280c05a01a61f2ae43e46a1ee398be27cdc14e
First time build. Skipping changelog.
wich is the same for later Builds.
I tested with:
Jenkins Latest and greatest (1.614)
Jenkins Older but stable (1.596.3)
git-client 1.17.1
git-client 1.16.1
Anyone can confirm this?
We have some old and heavy branches (with some binaries) that we do not want to get fetched at any time. As of today this is only possible with sparse checkouts, but they have the drawback that we can not push tags back to remote after the build.
Jenkins / JENKINS-26417
Allow to customize refspec/tags of the clone/fetch commands
[JIRA] [p4-plugin] (JENKINS-28498) Null Pointer when publishing assets and server is down
Title: Message Title Paul Allen commented on JENKINS-28498 Re: Null Pointer when publishing assets and server is down Thanks for raising this, I had missed the Publish failure case (only checked for Populate/Poll). In an ideal world I should throw this in the ClientHelper/ConnectionHelper class, but for slight behaviour differences with remote slave execution I delay the throw. There are a few minor fixes, but the new error looks like this... P4: Unable to connect: com.perforce.p4java.exception.ConnectionException: Unable to connect to Perforce server at localhost:1888 P4: Connection retry: 1 P4: Unable to connect: com.perforce.p4java.exception.ConnectionException: Unable to connect to Perforce server at localhost:1888 P4: Connection retry: 2 P4: Unable to connect: com.perforce.p4java.exception.ConnectionException: Unable to connect to Perforce server at localhost:1888 P4: Connection retry: 3 P4: Connection retry giving up... P4 Task: establishing connection. P4: Server connection error: localhost:1888 P4: Abort, no server connection. ERROR: Publisher org.jenkinsci.plugins.p4.asset.AssetNotifier aborted due to exception hudson.AbortException: P4: Abort, no server connection. at org.jenkinsci.plugins.p4.tasks.AbstractTask.setWorkspace(AbstractTask.java:57) at org.jenkinsci.plugins.p4.asset.AssetNotifier.perform(AssetNotifier.java:88) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:772) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:736) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:685) at hudson.model.Run.execute(Run.java:1757) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:234) Finished: FAILURE Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-28531) Out of memory
Title: Message Title Demitrius Nelon commented on JENKINS-28531 Re: Out of memory https://github.com/jenkinsci/docker-plugin/issues/221 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cucumber-testresult-plugin] (JENKINS-25203) support embedded content in json
Title: Message Title James Nord commented on JENKINS-25203 Re: support embedded content in json 1.580 is needed for JENKINS-25280 if you don't care about that it should be possible to back port if you as a dependency on security-144-compat But you should upgrade Jenkins instead Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudbees-folder-plugin] (JENKINS-28538) CCE after Upgrade to 1.6 Jenkins
Title: Message Title Darko Palic created an issue Jenkins / JENKINS-28538 CCE after Upgrade to 1.6 Jenkins Issue Type: Bug Assignee: Jesse Glick Attachments: jenkins.log Components: cloudbees-folder-plugin Created: 21/May/15 6:21 PM Environment: Ubuntu 14.04 LTS x64 Oracle JDK 1.7 Jenkins 1.614 Labels: exception Priority: Critical Reporter: Darko Palic We have used jenkins for a while successfully, but now we are facing a issue, we cannot handle anymore ourself. Also the Jenkins takes roughly 10 minutes to load now the pages. So we are nearly lost now with the jenkins... basically I am getting similar issues like this (see the attached logfile) WARNING: Caught exception evaluating:
Ваш E-mail ID выиграл один миллион долларов от Объединенных Нация премии Грант Связаться Mr.robin Стивеном за Претензии
-- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-19939) Discard Old Builds I/O Performance Issue
Title: Message Title Daniel Beck edited a comment on JENKINS-19939 Re: Discard Old Builds I/O Performance Issue bq.Hi,I'mhopingthisbugcanberevisited.Consideraddressingmycommentstoclarifywhattheissueis.bq.Somesortofinfointheloginfobeverywelcome.I'lllookintothat.bq.Someotherpluginsthatdoworkafterabuildcompletes,suchasCalculationofdiskusageofworkspace,dologthetimetheytook.Ithinkthispluginshoulddosoaswell.It'sincore,notinaplugin. Thatsaid,theproblemwiththeBuildDiscarderAPIisthatitdoesnotsupporthavingauser-visiblelogatallatthemoment.It'snotstrictlyrelatedtoabuild,andthereforenotreallyexpectedtowritetothebuildlog.Afterabuildfinishesissimplyagoodtimetodicardoldbuilds. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [accelerated-build-now-plugin] (JENKINS-28539) InvocationTargetException after Upgrade to 1.6 Jenkins
Title: Message Title Darko Palic created an issue Jenkins / JENKINS-28539 InvocationTargetException after Upgrade to 1.6 Jenkins Issue Type: Bug Assignee: Anthony Dahanne Attachments: jenkins.log Components: accelerated-build-now-plugin Created: 21/May/15 6:34 PM Environment: Ubuntu 14.04 LTS x64 Jenkins 1.614 Labels: exception Priority: Critical Reporter: Darko Palic We are facing this issue if we restart the jenkins. Since the jenkins is not working properly anymore, we are not sure where this error comes from. Please see for the detailed view the attached logfile Similar issues: May 21, 2015 7:38:14 PM hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception
[JIRA] [_test] (JENKINS-28521) Poll SCM
Title: Message Title
Tavant Grubhub created an issue
Jenkins / JENKINS-28521
Poll SCM
Issue Type:
Task
Assignee:
Oleg Nenashev
Components:
_test
Created:
21/May/15 11:48 AM
Priority:
Minor
Reporter:
Tavant Grubhub
javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class hudson.triggers.SCMTrigger from {scmpoll_spec:H/5,ignorePostCommitHooks:false}
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) 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:123) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at
[JIRA] [gitlab-hook-plugin] (JENKINS-28452) Push event web hook triggers all jobs regardless of Branch Specifier
Title: Message Title Javier Palacios resolved as Fixed If you want to give another chance, try the latest snapshot. It allows to configure whether triggering is done also for merged branches, and defaults to false, which should cause less surprises. I've done a fast test and seems to work, although it is not yet fully merged because I want to add some acceptance test for this. Jenkins / JENKINS-28452 Push event web hook triggers all jobs regardless of Branch Specifier Change By: Javier Palacios Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory-plugin] (JENKINS-28523) AD authentication for trusted domain users
Title: Message Title Ankan Saha created an issue Jenkins / JENKINS-28523 AD authentication for trusted domain users Issue Type: Improvement Assignee: Unassigned Components: active-directory-plugin Created: 21/May/15 1:10 PM Environment: Windows 2008, Windows 2003 or all windows Platform Jenkins version 1.598 Active Directory Plugin version 1.39 Priority: Minor Reporter: Ankan Saha In Linux when using Active Directory Plugin I get options for Domain,Domain Controller and Even Bind User and passwd where I specified a common account which will be used to search the account for user to login. In windows I do not get option to set Bind user and passwd. Only Domain name and Domain Controller. As a result I cannot authenticate to Jenkins through Active Directory. The Windows uses the default domain as per your Wiki document. However we use trusted domain for our setup. How can I get the BindUser and Bind Passwd setting which is essential to authenticate for trusted domain The Jenkins server is in one domain but we are authenticating account from another domain which is a trusted domain for the server
[JIRA] [xfpanel-plugin] (JENKINS-19044) Would like to have a third column of jobs as an option in the eXtreme Feedback panel
Title: Message Title Tomasz Bech assigned an issue to Tomasz Bech Jenkins / JENKINS-19044 Would like to have a third column of jobs as an option in the eXtreme Feedback panel Change By: Tomasz Bech Assignee: JulienRENAUT TomaszBech Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [performance-plugin] (JENKINS-28426) JMeterCSV always reports 100% 0f errors
Title: Message Title
Mayank Saini commented on JENKINS-28426
Re: JMeterCSV always reports 100% 0f errors
I think the issue is with the constructor of JMeterCsvParser.I checked the option skipFirstLine in jenkins and print field names is also set to true in jmeter.properties file.
In jtl file field name timeStamp is written with capital S while in the constructor if condition is applied with smaller s if (timestamp.equals(field)) { timestampIdx = i; }
I unchecked the option and set print field names to false everything works fine
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-19939) Discard Old Builds I/O Performance Issue
Title: Message Title Tomasz Śniatowski commented on JENKINS-19939 Re: Discard Old Builds I/O Performance Issue Hi, I'm hoping this bug can be revisited. We just spent an unpleasant amount of time trying to figure out why finished builds sometimes seem stuck on a spinner for a random amount of time, turns out it's often the discard old builds step. Some sort of info in the log info be very welcome. It's not very user friendly when jobs are stuck and it's not obvious what's going on. Some other plugins that do work after a build completes, such as Calculation of disk usage of workspace, do log the time they took. I think this plugin should do so as well. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-28522) masked variable in p4 passwd causes labelling problem
Title: Message Title
Ankan Saha created an issue
Jenkins / JENKINS-28522
masked variable in p4 passwd causes labelling problem
Issue Type:
Bug
Assignee:
Rob Petti
Components:
perforce-plugin
Created:
21/May/15 12:21 PM
Environment:
Jenkins version 1.598 Perforce Plugin version - 1.3.31 and 1.3.34 Mask Passwords Plugin - 2.7.2 OS - Windows2008R2 x64, Ubuntu details are NAME=Ubuntu VERSION=12.04.5 LTS, Precise Pangolin ID=ubuntu ID_LIKE=debian PRETTY_NAME=Ubuntu precise (12.04.5 LTS) VERSION_ID=12.04
Priority:
Minor
Reporter:
Ankan Saha
When we are using masked plugin with Perforce plugin 1.3.31 or 1.3.34 though the sync happens on the common variable labeling files. I define a variable P4USR, P4PWD P4PWD is masked passwd defined in Global Configuration and in Build job we enable the mask plugin checkbox. The sync happens properly but the labeling fails Labelling Build in Perforce using $ {JOB_NAME}
_$ {BUILD_ID}
16:00:11 $ {P4PWD}: Found unresolved macro at '${P4PWD}
' 16:00:11 Build step 'Create or Update Label in Perforce' marked build as failure
However instead of P4PWD if I use unmasked variables there is no problem. I wanted to use the Mask Plugin and majority of jobs are configured to use
[JIRA] [performance-plugin] (JENKINS-28426) JMeterCSV always reports 100% 0f errors
Title: Message Title
Mayank Saini edited a comment on JENKINS-28426
Re: JMeterCSV always reports 100% 0f errors
IthinktheissueiswiththeconstructorofJMeterCsvParser.IcheckedtheoptionskipFirstLineinjenkinsandprintfieldnamesisalsosettotrueinjmeter.propertiesfile.InjtlfilefieldnametimeStampiswrittenwithcapitalSwhileintheconstructorifconditionisappliedwithsmallersif(timestamp.equals(field)){timestampIdx=i;}Iuncheckedtheoptionandsetprintfieldnamestofalse injmeter.properties everythingworksfine
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [dependency-check-jenkins-plugin] (JENKINS-28395) java.lang.NullPointerException after upgrade to v1.2.11
Title: Message Title Shawn Crain commented on JENKINS-28395 Re: java.lang.NullPointerException after upgrade to v1.2.11 Happening for us as well. Jenkins 1.609 on Windows Server 2008 R2 (x86) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-28540) git publisher fails if user.email and user.name
Title: Message Title martinfr62 commented on JENKINS-28540 Re: git publisher fails if user.email and user.name So I tested - the email doesnt seem to be recorded - atleast not in stash. But the username is - it even tho we might use the credentials with the name 'bill', if the username is set to fred - that's who will appear to have performed the work. As for use case - it allows someone to 'forge' who made a change. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy-plugin] (JENKINS-28502) Install from http://groovy.codehaus.org installer method failing
Title: Message Title Arnaud Hritier commented on JENKINS-28502 Re: Install from http://groovy.codehaus.org installer method failing The groovy team forgot to move its distributions All of them aren't on bintray They are waiting that Ben Walding give them back a copy of groovy distros to deploy them on Bintray Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [coverity-plugin] (JENKINS-28541) [COMMAND LINE ERROR] Undefined option 'dir /bms/tools/jenkins/coverity/temp-3643448916814087209.tmp
Title: Message Title Shoban Cheekuru updated an issue Jenkins / JENKINS-28541 [COMMAND LINE ERROR] Undefined option 'dir /bms/tools/jenkins/coverity/temp-3643448916814087209.tmp Change By: Shoban Cheekuru HiIhaveinstalledcoverityjekinspluginandcreatedcoverityjobwithcoverityinstancemanagerwiththegiveninstructioninthejenkinspluginsiteHereistheconsollogCheckingCoverityconfiguration...[Stream]Testcoverity/TestProjectforShoban/NewStream-1106:OK(version:7.5.1)[Node]rtp-wasl-bldex:version7.5.1Configurationisvalid.[EnvInject]-Loadingnodeenvironmentvariables.Buildingremotelyonslave1linux ) inworkspace/bms/tools/jenkins/workspace/TestCoverity[Coverity]cmdsofaris:[/bms/tools/coverity/7.5.1/cov-analysis-linux64-7.5.1_csco/bin/cov-analyze,--dir,/bms/tools/jenkins/coverity/temp-3643448916814087209.tmp,--java,--all,--ticker-mode,none,--enable-constraint-fpp,--enable-callgraph-metrics,--force,--hfa][TestCoverity]$/bms/tools/coverity/7.5.1/cov-analysis-linux64-7.5.1_csco/bin/cov-analyze--dir/bms/tools/jenkins/coverity/temp-3643448916814087209.tmp--java--all--ticker-modenone--enable-constraint-fpp--enable-callgraph-metrics--force--hfa[COMMANDLINEERROR]Undefinedoption'dir/bms/tools/jenkins/coverity/temp-3643448916814087209.tmp--java--all--ticker-modenone--enable-constraint-fpp--enable-callgraph-metrics--force--hfa'Specify--helpforassistance.[Coverity]/bms/tools/coverity/7.5.1/cov-analysis-linux64-7.5.1_csco/bin/cov-analyzereturned2,aborting...Buildstep'Coverity'changedbuildresulttoFAILUREFinished:FAILURE Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You
[JIRA] [snsnotify-plugin] (JENKINS-28542) SNS notifier plugin missing httpcore dependency
Title: Message Title Milo Hyson updated an issue Jenkins / JENKINS-28542 SNS notifier plugin missing httpcore dependency Change By: Milo Hyson Installingthereleasedsnsnotify-pluginv1.9onacompletelystockJenkinsv1.614doesnotwork.Buildsusingthepluginfailwiththefollowingexception onstdout :java.lang.NoClassDefFoundError:org/apache/http/util/Args atorg.apache.http.conn.scheme.Scheme.init(Scheme.java:90) atorg.apache.http.impl.conn.SchemeRegistryFactory.createDefault(SchemeRegistryFactory.java:50) atcom.amazonaws.http.ConnectionManagerFactory.createPoolingClientConnManager(ConnectionManagerFactory.java:29) atcom.amazonaws.http.HttpClientFactory.createHttpClient(HttpClientFactory.java:104) atcom.amazonaws.http.AmazonHttpClient.init(AmazonHttpClient.java:198) atcom.amazonaws.AmazonWebServiceClient.init(AmazonWebServiceClient.java:132) atcom.amazonaws.AmazonWebServiceClient.init(AmazonWebServiceClient.java:116) atcom.amazonaws.services.sns.AmazonSNSClient.init(AmazonSNSClient.java:147) atcom.amazonaws.services.sns.AmazonSNSClient.init(AmazonSNSClient.java:128) atorg.jenkinsci.plugins.snsnotify.AmazonSNSNotifier.send(AmazonSNSNotifier.java:156) atorg.jenkinsci.plugins.snsnotify.AmazonSNSNotifier.sendSafe(AmazonSNSNotifier.java:102) atorg.jenkinsci.plugins.snsnotify.AmazonSNSNotifier.onStarted(AmazonSNSNotifier.java:79) atorg.jenkinsci.plugins.snsnotify.BuildListener.onStarted(BuildListener.java:19) atorg.jenkinsci.plugins.snsnotify.BuildListener.onStarted(BuildListener.java:8) athudson.model.listeners.RunListener.fireStarted(RunListener.java:215) athudson.model.Run.execute(Run.java:1740) athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) athudson.model.ResourceController.execute(ResourceController.java:98) athudson.model.Executor.run(Executor.java:374)Causedby:java.lang.ClassNotFoundException:org.apache.http.util.Args atjenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1376) atjenkins.util.AntClassLoader.findClass(AntClassLoader.java:1326) atjenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1079) atjava.lang.ClassLoader.loadClass(ClassLoader.java:358) ...19moreAneasyfixistoaddthefollowingtothepom.xmlandrebuild:dependencygroupIdorg.apache.httpcomponents/groupIdartifactIdhttpcore/artifactIdversion4.4.1/version/dependency Add Comment
[JIRA] [coverity-plugin] (JENKINS-28541) [COMMAND LINE ERROR] Undefined option 'dir /bms/tools/jenkins/coverity/temp-3643448916814087209.tmp
Title: Message Title Shoban Cheekuru created an issue Jenkins / JENKINS-28541 [COMMAND LINE ERROR] Undefined option 'dir /bms/tools/jenkins/coverity/temp-3643448916814087209.tmp Issue Type: Bug Assignee: Ken Dang Components: coverity-plugin Created: 21/May/15 8:37 PM Environment: jenkins version : Jenkins ver. 1.580.3 Coverity Plugin :1.5.0 OS: Linux Browser: Firefox Java: JDK1.7 Coverity Instance: 7.5.x Coverity Analysis tool : 7.5.x Priority: Critical Reporter: Shoban Cheekuru Hi I have installed coverity jekins plugin and created coverity job with coverity instance manager with the given instruction in the jenkins plugin site Here is the consol log Checking Coverity configuration... [Stream] Testcoverity/Test Project for Shoban/New Stream - 1106 : OK (version: 7.5.1) [Node] rtp-wasl-bldex : version 7.5.1 Configuration is valid. [EnvInject] - Loading node environment variables. Building remotely on rtp-wasl-bldex (vm5 rtp slave1 linux) in workspace /bms/tools/jenkins/workspace/TestCoverity [Coverity] cmd so far is: [/bms/tools/coverity/7.5.1/cov-analysis-linux64-7.5.1_csco/bin/cov-analyze, --dir, /bms/tools/jenkins/coverity/temp-3643448916814087209.tmp, --java, --all, --ticker-mode, none, --enable-constraint-fpp, --enable-callgraph-metrics,
[JIRA] [snsnotify-plugin] (JENKINS-28542) SNS notifier plugin missing httpcore dependency
Title: Message Title Milo Hyson updated an issue Jenkins / JENKINS-28542 SNS notifier plugin missing httpcore dependency Change By: Milo Hyson Priority: Blocker Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [snsnotify-plugin] (JENKINS-28542) SNS notifier plugin missing httpcore dependency
Title: Message Title Milo Hyson created an issue Jenkins / JENKINS-28542 SNS notifier plugin missing httpcore dependency Issue Type: Bug Assignee: Unassigned Components: snsnotify-plugin Created: 21/May/15 9:22 PM Environment: Stock Jenkins v1.614 snsnotify-plugin v1.9 Priority: Blocker Reporter: Milo Hyson Installing the released snsnotify-plugin v1.9 on a completely stock Jenkins v1.614 does not work. Builds using the plugin fail with the following exception: java.lang.NoClassDefFoundError: org/apache/http/util/Args at org.apache.http.conn.scheme.Scheme.init(Scheme.java:90) at org.apache.http.impl.conn.SchemeRegistryFactory.createDefault(SchemeRegistryFactory.java:50) at com.amazonaws.http.ConnectionManagerFactory.createPoolingClientConnManager(ConnectionManagerFactory.java:29) at com.amazonaws.http.HttpClientFactory.createHttpClient(HttpClientFactory.java:104) at com.amazonaws.http.AmazonHttpClient.init(AmazonHttpClient.java:198) at com.amazonaws.AmazonWebServiceClient.init(AmazonWebServiceClient.java:132) at com.amazonaws.AmazonWebServiceClient.init(AmazonWebServiceClient.java:116) at com.amazonaws.services.sns.AmazonSNSClient.init(AmazonSNSClient.java:147) at com.amazonaws.services.sns.AmazonSNSClient.init(AmazonSNSClient.java:128) at
[JIRA] [groovy-plugin] (JENKINS-28502) Install from http://groovy.codehaus.org installer method failing
Title: Message Title Christopher Orr commented on JENKINS-28502 Re: Install from http://groovy.codehaus.org installer method failing aheritier said on IRC that he checked with the Groovy team, and they're going to try and get the old downloads on bintray too at some point. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-28540) git publisher fails if user.email and user.name
Title: Message Title Mark Waite commented on JENKINS-28540 Re: git publisher fails if user.email and user.name I don't think that using a globally defined user.name and user.email for git allows someone to forge who made a change any more (or less) than git already allows anyone to forge who made a change. Git allows any value to be assigned to the git user.name and user.email. As far as I can tell, Git relies on operating system permissions to defend its repositories, and it relies on human beings (web of trust) to prevent forgery of change authorship. There was a 2009 discussion of using GPG signed commits, but Linus doesn't see value in them. Jenkins provides a place for you to assign the git user.name and user.email which will be used for commits performed by the Jenkins server. You configure that information in the Configure System page (for example http://localhost:8080/configure). In my case, I specifically want the commit to be listed as being performed by the Jenkins user, even if I've allowed the Jenkins user to perform certain operations (like git push) with my credentials. Use of my credentials for the push does not mean that I want my user.name or my user.email placed in the commit message. In a specific case I use at the office, I have the Git Publisher push from a single job to multiple repositories using different credentials for each destination repository. If that job wanted to apply a tag prior to that collection of push operations, which credential should it choose? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-23826) Allow automatic install of Maven 3.2.2
Title: Message Title Arnaud Hritier resolved as Fixed Duplicates INFRA-181 Jenkins / JENKINS-23826 Allow automatic install of Maven 3.2.2 Change By: Arnaud Hritier Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-28506) [REGRESSION] Git fails to trigger from polling for refs/heads/ style branch name
Title: Message Title Mark Waite commented on JENKINS-28506 Re: [REGRESSION] Git fails to trigger from polling for refs/heads/ style branch name I believe the breaking change between 2.3.4 and 2.3.5 is 85463e9. More investigation is needed. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-28506) [REGRESSION] Git fails to trigger from polling for refs/heads/ style branch name
Title: Message Title Mark Waite assigned an issue to Mark Waite Jenkins / JENKINS-28506 [REGRESSION] Git fails to trigger from polling for refs/heads/ style branch name Change By: Mark Waite Assignee: NicolasDeLoof MarkWaite Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-28506) [REGRESSION] Git fails to trigger from polling for refs/heads/ style branch name
Title: Message Title Mark Waite started work on JENKINS-28506 Change By: Mark Waite Status: Open InProgress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xfpanel-plugin] (JENKINS-20749) Some jobs are missing in Available jobs multichoice window
Title: Message Title Tomasz Bech assigned an issue to Tomasz Bech Jenkins / JENKINS-20749 Some jobs are missing in Available jobs multichoice window Change By: Tomasz Bech Assignee: JulienRENAUT TomaszBech Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xunit-plugin] (JENKINS-28497) xUnit does not check for activation status of JUnit
Title: Message Title Jennifer Hofmeister updated an issue Jenkins / JENKINS-28497 xUnit does not check for activation status of JUnit Change By: Jennifer Hofmeister Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xfpanel-plugin] (JENKINS-28520) standard header and left side panel shown on top of panel
Title: Message Title
Tomasz Bech created an issue
Jenkins / JENKINS-28520
standard header and left side panel shown on top of panel
Issue Type:
Bug
Assignee:
Tomasz Bech
Components:
xfpanel-plugin
Created:
21/May/15 11:04 AM
Priority:
Major
Reporter:
Tomasz Bech
After upgrading to newer Jenkins standard header and left side panel shown on top of panel
Workaround: in description field put style type=text/css #side-panel, #page-head { display: none; visibility: hidden; height: 0px; }
/style
Add Comment
[JIRA] [ssh-slaves-plugin] (JENKINS-28519) Upgrade to 1.614 from 1.605 breaks connectivity with slaves
Title: Message Title Alexandr Alexandrov created an issue Jenkins / JENKINS-28519 Upgrade to 1.614 from 1.605 breaks connectivity with slaves Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: ssh-slaves-plugin Created: 21/May/15 11:02 AM Environment: Jenkins v. 1.605, CentOS 6.6, Oracle JDK 1.8.0_45, SSH Slaves plugin v. 1.9 Priority: Major Reporter: Alexandr Alexandrov I tried to upgrade from 1.605 to 1.614 by downloading .war and restarting. After restart Jenkins is unable to connect to most slaves. /var/log/secure on the slaves shows after upgrade: May 21 13:20:32 as8 sshd[15563]: Connection from 10.2.7.121 port 61748 May 21 13:20:35 as8 sshd[15563]: Accepted password for sadm from 10.2.7.121 port 61748 ssh2 May 21 13:20:35 as8 sshd[15933]: subsystem request for sftp May 21 13:27:43 as8 sshd[19718]: Received disconnect from 10.2.6.3: 11: Closed due to user request. May 21 13:29:03 as8 sshd[21939]: Connection from 10.2.6.3 port 49943 May 21 13:29:05 as8 sshd[21939]: Accepted password for sadm from 10.2.6.3 port 49943 ssh2 May 21 13:29:06 as8 sshd[22160]: subsystem request for sftp May 21 13:29:11 as8 sshd[22160]: Received disconnect from 10.2.6.3: 11: Closed due to user request. May 21 13:29:18 as8 sshd[25679]: Connection from 10.2.6.3 port 50042 May 21 13:29:18 as8 sshd[25679]: Accepted password for sadm from 10.2.6.3 port 50042
[JIRA] [junit-plugin] (JENKINS-28479) Latest Test Result text and Test Result Trend plot do not appear for projects which always fail
Title: Message Title Alexander Ost updated an issue Jenkins / JENKINS-28479 Latest Test Result text and Test Result Trend plot do not appear for projects which always fail patch for junit-1.6 that works around the issue Change By: Alexander Ost Attachment: patch.txt Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mstest-plugin] (JENKINS-28517) [MSTEST] XML coverage report file not found
Title: Message Title Daniel Wagner created an issue Jenkins / JENKINS-28517 [MSTEST] XML coverage report file not found Issue Type: Bug Assignee: Ivo Bellin Salarin Components: mstest-plugin Created: 21/May/15 10:14 AM Environment: Jenkins 1.614 MSTest Plugin 0.18 VSTest Runner plugin 1.0.4 Priority: Minor Reporter: Daniel Wagner MSTest Plugin reports the following error after a successful build with MSBuild and test run with VSTest Runner. The mentioned file TestResults\vstest.coveragexml exists (I generate it with C:\Program Files (x86)\Microsoft Visual Studio 12.0\Team Tools\Dynamic Code Coverage Tools\CodeCoverage.exe analyze /output:%WORKSPACE%\TestResults\vstest.coveragexml %VSTEST_RESULT_COVERAGE% MSTest: Processing tests results in file(s) E:\jenkins\data\jobs\ProjectX\workspace\TestResults\jenkins_ARIEL 2015-05-21 10_16_33.trx MSTest: E:\jenkins\data\jobs\ProjectX\workspace\TestResults\jenkins_ARIEL 2015-05-21 10_16_33.trx [MSTEST] XML coverage report file not found: E:\jenkins\data\jobs\ProjectX\workspace\TestResults\vstest.coveragexml [MSTEST] XML coverage report file not found: E:\jenkins\data\jobs\ProjectX\workspace\TestResults\jenkins_ARIEL 2015-05-21 10_16_33.coveragexml
[JIRA] [mstest-plugin] (JENKINS-28517) [MSTEST] XML coverage report file not found
Title: Message Title Ivo Bellin Salarin commented on JENKINS-28517 Re: [MSTEST] XML coverage report file not found Thanks for your feedback, Daniel. I am sorry, the mstest-plugin message you point out is slightly wrong. It should state something different: [MSTEST] XML coverage report file not found or its format is not supported [..] The problem you experience is due to the fact that .coveragexml files content may differ according to the tool which has produced them. The mstest-plugin reads the format produced by Visual Studio (or by an handmade tool written according to the instructions gave on MSDN). SonarQube reads the format produced by CodeCoverage.exe uniquely. Visual Studio is able to read both formats. I hope to have the time to produce an XSLT which converts the CodeCoverage.exe format to the format produced by Visual Studio. Until then, I suggest you to use a different tool to produce the .coveragexml file.. I have updated the wiki for the MSTest-plugin according to the above text. It could take a while before the wiki changes get published. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-12610) Util.deleteRecursive fails for files using unmappable characters
Title: Message Title Johannes Villmow commented on JENKINS-12610 Re: Util.deleteRecursive fails for files using unmappable characters I have the same problem. A unicode character in the filename was causing it. Once i deleted this file manually it worked. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [swarm-plugin] (JENKINS-28518) Slaves not discovering when Maven is not enabled on the master
Title: Message Title Srini Sundaram created an issue Jenkins / JENKINS-28518 Slaves not discovering when Maven is not enabled on the master Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: swarm-plugin Created: 21/May/15 10:47 AM Environment: OS - Centos 6.5 64 bit Jenkins - 1.614 Swarm - 1.24 Slave - swarm-client-1.24-jar-with-dependencies.jar Java (Master Slave) - OpenJDK Runtime Environment (build 1.8.0_45-b13) Labels: jenkins plugin slave Priority: Minor Reporter: Srini Sundaram Hi, This is not a blocker. I was trying the slave auto discovery in the above mentioned scenario. Without having the Maven installed on the master when I tried: java -jar swarm-client-1.24-jar-with-dependencies.jar -autoDiscoveryAddress 192.168.55.22 -name Slave1
[JIRA] [junit-plugin] (JENKINS-28479) Latest Test Result text and Test Result Trend plot do not appear for projects which always fail
Title: Message Title Alexander Ost commented on JENKINS-28479 Re: Latest Test Result text and Test Result Trend plot do not appear for projects which always fail The issue is really caused by the SimpleBuildStep migration. The description of the SimpleBuildStep.LastBuildAction interface states Marker for explicitly added build actions (as Run.addAction(hudson.model.Action)) which should imply a transient project action (Actionable.getActions()) when present on the Job.getLastSuccessfulBuild(). As getProjectActions() was moved from class JUnitResultArchiver to that interface, the project actions will never become active for jobs that do not contain at least one successful build. The attached patch.txt (for junit-1.6) moves getProjectActions() back to class JUnitResultArchiver, and this fixes the issue. I am not aware of the side-effects of this change, though. Plugin tests are passing as before, but we're not using all features of the plugin. Please, kindly review. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xfpanel-plugin] (JENKINS-28064) 'Replace nr. of failed test cases' option doesn't work
Title: Message Title Tomasz Bech assigned an issue to Tomasz Bech Jenkins / JENKINS-28064 'Replace nr. of failed test cases' option doesn't work Change By: Tomasz Bech Assignee: JulienRENAUT TomaszBech Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-28527) Configuring mailer via groovy script via CLI fails with spurious 'missing jar' error.
Title: Message Title Alex Earl updated an issue Jenkins / JENKINS-28527 Configuring mailer via groovy script via CLI fails with spurious 'missing jar' error. Doesn't look like an issue with email-ext itself, so should be assigned to someone else. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ldap-plugin] (JENKINS-4895) AD and LDAP fail due to Referrals
Title: Message Title
Andy Pemberton edited a comment on JENKINS-4895
Re: AD and LDAP fail due to Referrals
Ibelievethedescriptionofthisissueisincorrect(atleastitistoday).Thisvaluecanbeconfiguredbysettinganenvironmentvariable:{{java.naming.referral=ignore}}Willcausethereferralstoignored.Thetroubleisthatyouwillstillreceivea{{PartialResultException}}ifADattemptstoreturnanentrywithreferralswhenreferralsareignored(seehereforexplanation:http://docs.spring.io/spring-ldap/docs/current/apidocs/org/springframework/ldap/core/LdapTemplate.html). OneotherworkaroundmaybetochangetheADportsfrom389to3268(ldap)orfrom636to3269(ldaps)[perthisSOthread|http://stackoverflow.com/questions/16412236/how-to-resolve-javax-naming-partialresultexception]. Ibelievetheproperfixistoleveragefunctionalitylikeavailableinthemorerecentspring-ldapframework'sLdapTemplate.ignorePartialResultExceptionproperty,perhapssettingthatpropertytotruefortheJenkinsldap-plugin'sLdapTemplate(oratleastsettotrueifthejava.naming.referralpropertyissettoignore).
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [unity3d-plugin] (JENKINS-23958) Pipe Broken
Title: Message Title lacostej commented on JENKINS-23958 Re: Pipe Broken Thanks Charles for the logs. I don't know what's happening yet but this should help us a bit. I am surprised to not see more communication. What can I see: Pipe.Chunks are seen up to May 21, 2015 9:26:15 followed by lots of hudson.remoting.UnexportCommand a PingThread kicks in at May 21, 2015 9:27:40 AM a PingThread kicks in at May 21, 2015 9:28:11 AM nothing during 2 min a Pipe.Chunk is sent a Dead is received instead of an Ack Here's a patch to apply to your remoting.jar https://github.com/lacostej/remoting/commit/02969e1271443afc933dcb8e0d472c1dfc9e8856 that could help knowing why the Death. Maybe worth a shot ? This also should help a bit: https://wiki.jenkins-ci.org/display/JENKINS/Remoting+issue although Charles said he couldn't find any specific info in his slaves logs. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [subversion-plugin] (JENKINS-28525) Subversion plugin doesn't do cleanup
Title: Message Title Pawel Grzegrzolka created an issue Jenkins / JENKINS-28525 Subversion plugin doesn't do cleanup Issue Type: Bug Assignee: Unassigned Components: subversion-plugin Created: 21/May/15 2:32 PM Environment: subversion-plugin: 2.5 Jenkins: 1.609 OS: Windows Server 2013 R2 Labels: plugin svn subversion Priority: Major Reporter: Pawel Grzegrzolka I had an issue quite a few time that checkout has been broken (interrupted during update, etc.) To fix it it's sufficient to do 'svn cleanup'. However subversion-plugin doesn't support it. In case of a broken checkout poll-scm triggers a new build https://repo/svn/project/trunk is at revision 3,211 (changed from 3,210) but SVN doesn't update this repository:
[JIRA] [workflow-plugin] (JENKINS-26761) WorkflowJob.getSCMs throws NullPointerException from notifyCommit hooks after Jenkins Restart
Title: Message Title Kenneth Baltrinic commented on JENKINS-26761 Re: WorkflowJob.getSCMs throws NullPointerException from notifyCommit hooks after Jenkins Restart FYI, this problem has yet again disappeared for us, but I will add the loggers and take the other debug steps mentioned should it re-appear. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial-plugin] (JENKINS-28526) Build emails reference unrelated changesets
Title: Message Title Kent Johnson created an issue Jenkins / JENKINS-28526 Build emails reference unrelated changesets Issue Type: Bug Assignee: Jesse Glick Components: mercurial-plugin Created: 21/May/15 2:44 PM Environment: Jenkins 1.614, mercurial-plugin 1.52, mercurial 3.4, Windows 64 Priority: Minor Reporter: Kent Johnson Mercurial 3.4 changed the behavior of the log command as used by this plugin. A command such as hg log --rev default:0 --follow --prune 5029 now will show unrelated changesets on other branches (specifically the head of an active branch other than default). This results in build logs and emails that show unrelated changesets and build emails being sent to the authors of unrelated changesets. AFAICT the mercurial changeset is http://hg.intevation.org/mercurial/crew/rev/c260887cdbcd. There is related discussion here: http://thread.gmane.org/gmane.comp.version-control.mercurial.general/36471. I'm not sure why the hg log behaviour changed or even if it is correct, but from the discussion it seems like the command used by this plugin is not correct either. The --follow flag is used to follow changes to a particular file, not to follow the ancestor relationships of changesets. A better command seems to be hg log --rev descendents(5029)::default which directly asks for all the
[JIRA] [cli] (JENKINS-28527) Configuring mailer via groovy script via CLI fails with spurious 'missing jar' error.
Title: Message Title
Kenneth Baltrinic created an issue
Jenkins / JENKINS-28527
Configuring mailer via groovy script via CLI fails with spurious 'missing jar' error.
Issue Type:
Bug
Assignee:
Alex Earl
Components:
cli, core, email-ext-plugin
Created:
21/May/15 2:58 PM
Environment:
This is occurring on various machines running 1.596.3 LTS on Centos 6.6. They have various plugins installed, however the likely relevant plugins, (mailer, email-ext) are the latest and greatest on each machine.
Priority:
Minor
Reporter:
Kenneth Baltrinic
We manage our Jenkins infrastructure via Chef which is configured to automatically upgrade the machines to the latest LTS version when it comes out. Chef runs on each machine every 30 min. Immediately following the latest LTS release to 1.596.3, our chef runs started failing frequently but intermittently (about 50% of the time). The run fails at the point where we use the jenkins-cli groovy to configure certain properties of the mailer by means of running a script.
The script template looks like the following:
import jenkins.model.*
def inst = Jenkins.getInstance()
def desc = inst.getDescriptor('hudson.tasks.Mailer')
[JIRA] [cli] (JENKINS-28527) Configuring mailer via groovy script via CLI fails with spurious 'missing jar' error.
Title: Message Title Alex Earl assigned an issue to Unassigned Jenkins / JENKINS-28527 Configuring mailer via groovy script via CLI fails with spurious 'missing jar' error. Change By: Alex Earl Assignee: AlexEarl Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-25385) Jenkins EC2 plugin is not able to launch Windows Slaves in AWS
Title: Message Title Tom FENNELLY commented on JENKINS-25385 Re: Jenkins EC2 plugin is not able to launch Windows Slaves in AWS Hi guys. So is this working or not? I just tried it and just sits there waiting: Waiting for WinRM to come up. Sleeping 10s. Connecting to ec2-52-17-36-66.eu-west-1.compute.amazonaws.com(52.17.36.66) with WinRM as Waiting for WinRM to come up. Sleeping 10s. Connecting to ec2-52-17-36-66.eu-west-1.compute.amazonaws.com(52.17.36.66) with WinRM as Waiting for WinRM to come up. Sleeping 10s. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobconfighistory-plugin] (JENKINS-28129) Default exclusions should be more precise
Title: Message Title Julien Carsique resolved as Fixed Resolved in version 2.12. Jenkins / JENKINS-28129 Default exclusions should be more precise Change By: Julien Carsique Status: Open Resolved Assignee: MirkoFriedenhagen JulienCarsique Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [neoload-jenkins] (JENKINS-28524) The Neoload Performance Test Result link does not appear on a successful build although the report is getting created at expected location
Title: Message Title Sayantani Das created an issue Jenkins / JENKINS-28524 The Neoload Performance Test Result link does not appear on a successful build although the report is getting created at expected location Issue Type: Bug Assignee: Unassigned Attachments: NeoloadDashboardGraphsAvailable.png, NeoloadPerformanceResultLinkNotAvailable.png, neoload_PostBuildSteps.png Components: neoload-jenkins Created: 21/May/15 1:54 PM Environment: Jenkins 1.612, Neoload plugin v 1.0.1 Labels: plugin performance neoload Priority: Major Reporter: Sayantani Das 1. I have installed the Neoload plugin. 2. Created a build step as below: (Execute Windows Batch Command) D:\Program Files\NeoLoad
[JIRA] [unity3d-plugin] (JENKINS-23958) Pipe Broken
Title: Message Title Charles Bouchard-Lgar commented on JENKINS-23958 Re: Pipe Broken Here are some logs extracted using the loggers as you suggested. May 21, 2015 9:25:40 AM FINE hudson.remoting.Channel Send Pipe.Chunk(7806,227) May 21, 2015 9:25:40 AM FINER hudson.remoting.PipeWindow decrease(7806,227)-1048349 May 21, 2015 9:25:40 AM FINE hudson.remoting.Channel Received ProxyOutputStream.Ack(7806,227) May 21, 2015 9:25:40 AM FINER hudson.remoting.PipeWindow increase(7806,227)-1048576 May 21, 2015 9:25:40 AM FINE hudson.remoting.Channel Send Pipe.Chunk(7806,111) May 21, 2015 9:25:40 AM FINER hudson.remoting.PipeWindow decrease(7806,111)-1048465 May 21, 2015 9:25:40 AM FINE hudson.remoting.Channel Received ProxyOutputStream.Ack(7806,111) May 21, 2015 9:25:40 AM FINER hudson.remoting.PipeWindow increase(7806,111)-1048576 May 21, 2015 9:25:44 AM FINE hudson.remoting.Channel Send Pipe.Chunk(7806,1395) May 21, 2015 9:25:44 AM FINER hudson.remoting.PipeWindow decrease(7806,1395)-1047181 May 21, 2015 9:25:44 AM FINE hudson.remoting.Channel Received ProxyOutputStream.Ack(7806,1395) May 21, 2015 9:25:44 AM FINER hudson.remoting.PipeWindow increase(7806,1395)-1048576 May 21, 2015 9:25:46 AM FINE hudson.remoting.Channel Send Pipe.Chunk(7806,39) May 21, 2015 9:25:46 AM FINER hudson.remoting.PipeWindow decrease(7806,39)-1048537 May 21, 2015 9:25:46 AM FINE hudson.remoting.Channel Received ProxyOutputStream.Ack(7806,39) May 21, 2015 9:25:46 AM FINER hudson.remoting.PipeWindow increase(7806,39)-1048576 May 21, 2015 9:25:46 AM FINE hudson.remoting.Channel Send Pipe.Chunk(7806,358) May 21, 2015 9:25:46 AM FINER hudson.remoting.PipeWindow decrease(7806,358)-1048218 May 21, 2015 9:25:46 AM FINE hudson.remoting.Channel Received ProxyOutputStream.Ack(7806,358) May 21, 2015 9:25:46 AM FINER hudson.remoting.PipeWindow increase(7806,358)-1048576 May 21, 2015 9:25:46 AM FINE hudson.remoting.Channel Send Pipe.Chunk(7806,776) May 21, 2015 9:25:46 AM FINER hudson.remoting.PipeWindow decrease(7806,776)-1047800 May 21, 2015 9:25:46 AM FINE hudson.remoting.Channel Received ProxyOutputStream.Ack(7806,776) May 21, 2015 9:25:46 AM FINER hudson.remoting.PipeWindow increase(7806,776)-1048576 May 21, 2015 9:25:48 AM FINE hudson.remoting.Channel Send Pipe.Chunk(7806,39) May 21, 2015 9:25:48 AM FINER hudson.remoting.PipeWindow decrease(7806,39)-1048537 May 21, 2015 9:25:48 AM FINE hudson.remoting.Channel Received ProxyOutputStream.Ack(7806,39) May 21, 2015 9:25:48 AM FINER hudson.remoting.PipeWindow increase(7806,39)-1048576 May 21, 2015 9:25:48 AM FINE hudson.remoting.Channel Send Pipe.Chunk(7806,352) May 21, 2015 9:25:48 AM FINER hudson.remoting.PipeWindow decrease(7806,352)-1048224 May 21, 2015 9:25:48 AM FINE hudson.remoting.Channel Received ProxyOutputStream.Ack(7806,352) May 21, 2015 9:25:48 AM FINER hudson.remoting.PipeWindow increase(7806,352)-1048576 May 21, 2015 9:25:50 AM FINE hudson.remoting.Channel Send Pipe.Chunk(7806,390) May 21, 2015 9:25:50 AM FINER hudson.remoting.PipeWindow decrease(7806,390)-1048186 May 21, 2015 9:25:50 AM FINE hudson.remoting.Channel Received ProxyOutputStream.Ack(7806,390) May 21, 2015 9:25:50 AM FINER hudson.remoting.PipeWindow increase(7806,390)-1048576 May 21, 2015 9:25:50 AM FINE hudson.remoting.Channel Send Pipe.Chunk(7806,388) May 21, 2015 9:25:50 AM FINER hudson.remoting.PipeWindow decrease(7806,388)-1048188 May 21, 2015 9:25:50 AM FINE hudson.remoting.Channel Received ProxyOutputStream.Ack(7806,388) May 21, 2015 9:25:50 AM FINER hudson.remoting.PipeWindow increase(7806,388)-1048576 May 21, 2015 9:25:50 AM FINE hudson.remoting.Channel Send Pipe.Chunk(7806,388) May 21, 2015 9:25:50 AM FINER hudson.remoting.PipeWindow decrease(7806,388)-1048188 May 21, 2015 9:25:50 AM
[JIRA] [build-flow-plugin] (JENKINS-20843) build flow plugin does not properly initialize workspace but supports options (SCM) that require a workspace
Title: Message Title Philipp Strobel commented on JENKINS-20843 Re: build flow plugin does not properly initialize workspace but supports options (SCM) that require a workspace build-flow-plugin 0.17 does not prepare the workspace after SCM checkout. The workspace stays empty. I use the SCM to check for changes on the SCM and to trigger a new Job-Run. However, since the workspace is always empty, each time the SCM is checked for changes it will trigger a new Job-Run. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [prioritysorter-plugin] (JENKINS-22267) Upgrade to advanced mode is somehow not persisted to disk
Title: Message Title Julien Carsique commented on JENKINS-22267 Re: Upgrade to advanced mode is somehow not persisted to disk Same issue with Jenkins 1.590 and Priority Sorter 2.9. I was not yet able to determine when it happens, nor why. I submitted JENKINS-28129 to get change history on the Priority Sorter configuration files... I've set an absolute priority up to 10 and created two JobGroups (one based on regexp, one based on view). On disk, I can see 7 jobs with priority 100, obviously not updated. I also found 3 jobs templates setting similar legacy values. Maybe that could be the cause of the issue? What happens when a job is created with a legacy priority value after migration from legacy to absolute? After manual fix of the templates job, I now have: 267 jobs with priority-2147483647/priority. What means that value? Equivalent to unset? 208 jobs with priority-1/priority 161 jobs with priority between 1 and 10 as expected. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-28504) Add Folder Support To the Parameterized Remote Trigger Plugin
Title: Message Title Steven Christou updated an issue Jenkins / JENKINS-28504 Add Folder Support To the Parameterized Remote Trigger Plugin Change By: Steven Christou URL: https://cloudbees.zendesk.com/agent/tickets/26401 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [update-sites-manager-plugin] (JENKINS-28544) Update Center Permission Denied
Title: Message Title
Alex Shafer updated an issue
Jenkins / JENKINS-28544
Update Center Permission Denied
Change By:
Alex Shafer
WhenattemptingtoinstallpluginsusingtheUpdateCenter,pluginscannotbewrittento/var/lib/jenkins/pluginsduetoinvalidpermissions. {{ hudson.util.IOException2:Failedtodownloadfromhttp://updates.jenkins-ci.org/download/plugins/ssh/2.4/ssh.hpi(redirectedto:http://ftp-nyc.osuosl.org/pub/jenkins/plugins/ssh/2.4/ssh.hpi) athudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:797) athudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1148) athudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1309) athudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1126) atjava.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) atjava.util.concurrent.FutureTask.run(FutureTask.java:266) athudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110) atjava.lang.Thread.run(Thread.java:744)Causedby:java.io.FileNotFoundException:/var/lib/jenkins/plugins/ssh.jpi.tmp(Permissiondenied) atjava.io.FileOutputStream.open(NativeMethod) atjava.io.FileOutputStream.init(FileOutputStream.java:206) atjava.io.FileOutputStream.init(FileOutputStream.java:156) athudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:763) ...7more }} {{***@***/var/lib/jenkins$ls-altotal80drwxr-xr-x11jenkinsjenkins4096May2119:27.drwxr-xr-x48rootroot4096May218:23..-rw-r--r--1systemd-timesyncsambashare0Apr1019:04atomic3320745316088279947.tmp-rw-r--r--1jenkinsjenkins1715May2119:15config.xml-rw-r--r--1jenkinsjenkins0May2119:10Downloadmetadata.log-rw-r--r--1systemd-timesyncsambashare0Apr1104:16Fingerprintcleanup.log-rw-r--r--1jenkinsjenkins160May2119:27hudson.model.UpdateCenter.xml-rw---1systemd-timesyncsambashare1675Apr1019:09identity.keydrwxr-xr-x3jenkinsjenkins4096May2119:09.java-rw-r--r--1jenkinsjenkins138May2119:14jenkins.model.DownloadSettings.xml-rw-r--r--1jenkinsjenkins169May2119:14jenkins.security.QueueItemAuthenticatorConfiguration.xmldrwxr-xr-x2jenkinsjenkins4096May2119:13jenkins.security.RekeySecretAdminMonitordrwxr-xr-x2systemd-timesyncsambashare4096Apr1018:56jobs-rw-r--r--1jenkinsjenkins907May2119:10nodeMonitors.xmldrwxr-xr-x2jenkinsjenkins4096May2119:09nodes-rw-r--r--1systemd-timesyncsambashare51Apr1115:56.ownerdrwxr-xr-x2systemd-timesyncsambashare4096Apr1018:56plugins-rw-r--r--1systemd-timesyncsambashare46Apr1116:18queue.xml.bak-rw-r--r--1systemd-timesyncsambashare64Apr1018:56secret.keydrwxr-xr-x4jenkinsjenkins4096May2119:15secretsdrwxr-xr-x2jenkinsjenkins4096May2119:28updatesdrwxr-xr-x2systemd-timesyncsambashare4096Apr1019:09userContentdrwxr-xr-x3jenkinsjenkins4096May2119:15users}}Canbefixedbyissuing:{{sudochownjenkinspluginssudochownjenkinsuserContentsudochgrpjenkinsuserContentsudochgrpjenkinsplugins}}
[JIRA] [update-sites-manager-plugin] (JENKINS-28544) Update Center Permission Denied
Title: Message Title
Alex Shafer updated an issue
Jenkins / JENKINS-28544
Update Center Permission Denied
Change By:
Alex Shafer
WhenattemptingtoinstallpluginsusingtheUpdateCenter,pluginscannotbewrittento/var/lib/jenkins/pluginsduetoinvalidpermissions.{ { quote} hudson.util.IOException2:Failedtodownloadfromhttp://updates.jenkins-ci.org/download/plugins/ssh/2.4/ssh.hpi(redirectedto:http://ftp-nyc.osuosl.org/pub/jenkins/plugins/ssh/2.4/ssh.hpi) athudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:797) athudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1148) athudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1309) athudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1126) atjava.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) atjava.util.concurrent.FutureTask.run(FutureTask.java:266) athudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110) atjava.lang.Thread.run(Thread.java:744)Causedby:java.io.FileNotFoundException:/var/lib/jenkins/plugins/ssh.jpi.tmp(Permissiondenied) atjava.io.FileOutputStream.open(NativeMethod) atjava.io.FileOutputStream.init(FileOutputStream.java:206) atjava.io.FileOutputStream.init(FileOutputStream.java:156) athudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:763) ...7more {quote } } { { quote} ***@***/var/lib/jenkins$ls-altotal80drwxr-xr-x11jenkinsjenkins4096May2119:27.drwxr-xr-x48rootroot4096May218:23..-rw-r--r--1systemd-timesyncsambashare0Apr1019:04atomic3320745316088279947.tmp-rw-r--r--1jenkinsjenkins1715May2119:15config.xml-rw-r--r--1jenkinsjenkins0May2119:10Downloadmetadata.log-rw-r--r--1systemd-timesyncsambashare0Apr1104:16Fingerprintcleanup.log-rw-r--r--1jenkinsjenkins160May2119:27hudson.model.UpdateCenter.xml-rw---1systemd-timesyncsambashare1675Apr1019:09identity.keydrwxr-xr-x3jenkinsjenkins4096May2119:09.java-rw-r--r--1jenkinsjenkins138May2119:14jenkins.model.DownloadSettings.xml-rw-r--r--1jenkinsjenkins169May2119:14jenkins.security.QueueItemAuthenticatorConfiguration.xmldrwxr-xr-x2jenkinsjenkins4096May2119:13jenkins.security.RekeySecretAdminMonitordrwxr-xr-x2systemd-timesyncsambashare4096Apr1018:56jobs-rw-r--r--1jenkinsjenkins907May2119:10nodeMonitors.xmldrwxr-xr-x2jenkinsjenkins4096May2119:09nodes-rw-r--r--1systemd-timesyncsambashare51Apr1115:56.ownerdrwxr-xr-x2systemd-timesyncsambashare4096Apr1018:56plugins-rw-r--r--1systemd-timesyncsambashare46Apr1116:18queue.xml.bak-rw-r--r--1systemd-timesyncsambashare64Apr1018:56secret.keydrwxr-xr-x4jenkinsjenkins4096May2119:15secretsdrwxr-xr-x2jenkinsjenkins4096May2119:28updatesdrwxr-xr-x2systemd-timesyncsambashare4096Apr1019:09userContentdrwxr-xr-x3jenkinsjenkins4096May2119:15users {quote } } Canbefixedbyissuing:{ { quote} sudochownjenkinspluginssudochownjenkinsuserContentsudochgrpjenkinsuserContentsudochgrpjenkinsplugins {quote } }
[JIRA] [parameterized-remote-trigger-plugin] (JENKINS-28504) Add Folder Support To the Parameterized Remote Trigger Plugin
Title: Message Title Steven Christou closed an issue as Duplicate Jenkins / JENKINS-28504 Add Folder Support To the Parameterized Remote Trigger Plugin Change By: Steven Christou Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-28540) Set git publisher user.name from credentials instead of using global setting
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-28540 Set git publisher user.name from credentials instead of using global setting Change By: Mark Waite Summary: Set gitpublisher failsif user. emailanduser. name fromcredentialsinsteadofusingglobalsetting Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-28529) Git polling deletes files in workspace if clean and ignore commits in path are both enabled
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-28529 Git polling deletes files in workspace if clean and ignore commits in path are both enabled Change By: Mark Waite Summary: Gitpollingdeletesfilesinworkspaceif clean and ignorecommitsinpath are bothenabled Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials when running as a service
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-20356 Git CLI cannot clone on Windows using GIT_SSH to set credentials when running as a service Change By: Mark Waite Assignee: MarkWaite Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-28540) git publisher fails if user.email and user.name
Title: Message Title martinfr62 commented on JENKINS-28540 Re: git publisher fails if user.email and user.name So thanks for the hint about the global configuration - and this does work both for the artifactory plugin and the git publisher. That said I believe the name of the user in the commit should be the owner of the credentials used. Not a generic username called jenkins. From a SOX compliance issue - allowing the username to not match the credentials used is a 'really bad thing'. Being able to trace who made a change to a system and when they did it - and proof that only they could do so (ie they had access to the credentials) is of primary importance where the SOX compliance is required. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-token-root-plugin] (JENKINS-28543) Additional parameters not being passed
Title: Message Title Jay Kah created an issue Jenkins / JENKINS-28543 Additional parameters not being passed Issue Type: Bug Assignee: Jesse Glick Components: build-token-root-plugin Created: 21/May/15 11:46 PM Environment: Jenkins latest, all plugins up-to-date Priority: Minor Reporter: Jay Kah The documentation states that: Trigger the RevolutionTest job with the token TacoTuesday and parameter Type supplied with the value Mexican buildByToken/buildWithParameters?job=RevolutionTesttoken=TacoTuesdayType=Mexican However, when I add the Type parameter with value it is nowhere to be seen. I have tried printing it, passing it, and checking the env variables for it - to no avail. Now I might be looking in the wrong place, and if I am, would appreciate if someone could shed some light on the matter. Thanks!
[JIRA] [update-sites-manager-plugin] (JENKINS-28544) Update Center Permission Denied
Title: Message Title
Alex Shafer created an issue
Jenkins / JENKINS-28544
Update Center Permission Denied
Issue Type:
Bug
Assignee:
Unassigned
Components:
update-sites-manager-plugin
Created:
21/May/15 11:57 PM
Environment:
Oracle JDK 8 Debian 8 Installed via Jenkins Deb Package Repository
Priority:
Major
Reporter:
Alex Shafer
When attempting to install plugins using the Update Center, plugins can not be written to /var/lib/jenkins/plugins due to invalid permissions.
{{hudson.util.IOException2: Failed to download from http://updates.jenkins-ci.org/download/plugins/ssh/2.4/ssh.hpi (redirected to: http://ftp-nyc.osuosl.org/pub/jenkins/plugins/ssh/2.4/ssh.hpi) at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:797) at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1148) at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1309) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1126) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110) at java.lang.Thread.run(Thread.java:744) Caused by: java.io.FileNotFoundException: /var/lib/jenkins/plugins/ssh.jpi.tmp
[JIRA] [update-sites-manager-plugin] (JENKINS-28544) Update Center Permission Denied
Title: Message Title
Alex Shafer updated an issue
Jenkins / JENKINS-28544
Update Center Permission Denied
Change By:
Alex Shafer
WhenattemptingtoinstallpluginsusingtheUpdateCenter,pluginscannotbewrittento/var/lib/jenkins/pluginsduetoinvalidpermissions. {{ hudson.util.IOException2:Failedtodownloadfromhttp://updates.jenkins-ci.org/download/plugins/ssh/2.4/ssh.hpi(redirectedto:http://ftp-nyc.osuosl.org/pub/jenkins/plugins/ssh/2.4/ssh.hpi) athudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:797) athudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1148) athudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1309) athudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1126) atjava.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) atjava.util.concurrent.FutureTask.run(FutureTask.java:266) athudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110) atjava.lang.Thread.run(Thread.java:744)Causedby:java.io.FileNotFoundException:/var/lib/jenkins/plugins/ssh.jpi.tmp(Permissiondenied) atjava.io.FileOutputStream.open(NativeMethod) atjava.io.FileOutputStream.init(FileOutputStream.java:206) atjava.io.FileOutputStream.init(FileOutputStream.java:156) athudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:763) ...7more }} {{***@***/var/lib/jenkins$ls-altotal80drwxr-xr-x11jenkinsjenkins4096May2119:27.drwxr-xr-x48rootroot4096May218:23..-rw-r--r--1systemd-timesyncsambashare0Apr1019:04atomic3320745316088279947.tmp-rw-r--r--1jenkinsjenkins1715May2119:15config.xml-rw-r--r--1jenkinsjenkins0May2119:10Downloadmetadata.log-rw-r--r--1systemd-timesyncsambashare0Apr1104:16Fingerprintcleanup.log-rw-r--r--1jenkinsjenkins160May2119:27hudson.model.UpdateCenter.xml-rw---1systemd-timesyncsambashare1675Apr1019:09identity.keydrwxr-xr-x3jenkinsjenkins4096May2119:09.java-rw-r--r--1jenkinsjenkins138May2119:14jenkins.model.DownloadSettings.xml-rw-r--r--1jenkinsjenkins169May2119:14jenkins.security.QueueItemAuthenticatorConfiguration.xmldrwxr-xr-x2jenkinsjenkins4096May2119:13jenkins.security.RekeySecretAdminMonitordrwxr-xr-x2systemd-timesyncsambashare4096Apr1018:56jobs-rw-r--r--1jenkinsjenkins907May2119:10nodeMonitors.xmldrwxr-xr-x2jenkinsjenkins4096May2119:09nodes-rw-r--r--1systemd-timesyncsambashare51Apr1115:56.ownerdrwxr-xr-x2systemd-timesyncsambashare4096Apr1018:56plugins-rw-r--r--1systemd-timesyncsambashare46Apr1116:18queue.xml.bak-rw-r--r--1systemd-timesyncsambashare64Apr1018:56secret.keydrwxr-xr-x4jenkinsjenkins4096May2119:15secretsdrwxr-xr-x2jenkinsjenkins4096May2119:28updatesdrwxr-xr-x2systemd-timesyncsambashare4096Apr1019:09userContentdrwxr-xr-x3jenkinsjenkins4096May2119:15users}}Canbefixedbyissuing:{{sudochownjenkinspluginssudochownjenkinsuserContentsudochgrpjenkinsuserContentsudochgrpjenkinsplugins}}
[JIRA] [aws-lambda-plugin] (JENKINS-28441) refactor project for future feature additions
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28441 Re: refactor project for future feature additions Code changed in jenkins User: cast Path: src/main/java/com/xti/jenkins/plugin/awslambda/invoke/LambdaInvokeBuildStep.java src/main/java/com/xti/jenkins/plugin/awslambda/invoke/LambdaInvokeVariables.java src/main/java/com/xti/jenkins/plugin/awslambda/service/LambdaService.java src/main/java/com/xti/jenkins/plugin/awslambda/upload/LambdaUploadBuildStep.java src/main/resources/com/xti/jenkins/plugin/awslambda/invoke/LambdaInvokeVariables/config.jelly http://jenkins-ci.org/commit/aws-lambda-plugin/0d68c974f1f718f9048e0291cd259042d3b51a7c Log: JENKINS-28441 Fixed Lambda invoke as a build step, awaiting testing Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-28540) git publisher fails if user.email and user.name
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-28540 git publisher fails if user.email and user.name Change By: Mark Waite Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-28540) git publisher fails if user.email and user.name
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-28540 git publisher fails if user.email and user.name Change By: Mark Waite Issue Type: Bug NewFeature Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-28540) git publisher fails if user.email and user.name
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-28540 git publisher fails if user.email and user.name Change By: Mark Waite Component/s: git-client-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [update-sites-manager-plugin] (JENKINS-28544) Update Center Permission Denied
Title: Message Title Alex Shafer commented on JENKINS-28544 Re: Update Center Permission Denied Other directories also needed to be fixed to inorder for jobs to work correctly Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-28544) Update Center and Jobs Permission Denied
Title: Message Title Alex Shafer updated an issue Jenkins / JENKINS-28544 Update Center and Jobs Permission Denied Change By: Alex Shafer Summary: UpdateCenter andJobs PermissionDenied Component/s: core Labels: core exceptionjenkins plugins jobpluginupdate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26854) EC2 slave launch stops working after a while with AmazonServiceException Request has expired
Title: Message Title
James Judd edited a comment on JENKINS-26854
Re: EC2 slave launch stops working after a while with AmazonServiceException Request has expired
ThanksfortheinfoMartin.IspentsomemoretimelookingintothistonightandIthinkIfoundthecause.Evenbetter,Ithinkthefixisquitesimple.Atthemoment,inEC2Cloud:wecreateanAmazonEC2Clientlikeso{code:Java}AmazonEC2client=newAmazonEC2Client(credentialsProvider.getCredentials(),config);{code}Accordingtothe[AmazonSDKsource|https://github.com/aws/aws-sdk-java/blob/84adaca80ee2b974f76816f5d4d9be90a5aa8543/aws-java-sdk-ec2/src/main/java/com/amazonaws/services/ec2/AmazonEC2Client.java#L134-138]thiscreatesa[StaticCredentialsProvider|https://github.com/puppetlabs/aws-sdk-for-java/blob/master/src/main/java/com/amazonaws/internal/StaticCredentialsProvider.java]usingthegivencredentials.FromwhatIcantell,StaticCredentialsProviderneverrefreshesitscredentials,leadingtoexpiration.Instead,youcancreatean[AmazonEC2Clientwithacredentialsproviderdirectly|https://github.com/aws/aws-sdk-java/blob/84adaca80ee2b974f76816f5d4d9be90a5aa8543/aws-java-sdk-ec2/src/main/java/com/amazonaws/services/ec2/AmazonEC2Client.java#L172-174].Thisshould,asfarasIcantell,refreshthecredentialsasneeded.{code:Java}AmazonEC2client=newAmazonEC2Client(credentialsProvider,config);{code}Thisisfurthersupportedby[thisamazondocumentation|http://docs.aws.amazon.com/AWSSdkDocsJava/latest/DeveloperGuide/java-dg-roles.html],whichstates{quote}*Important*Theautomaticcredentialsrefreshhappensonlywhenyouusethedefaultclientconstructor,whichcreatesitsownInstanceProfileCredentialsProvideraspartofthedefaultproviderchain, _or _or whenyoupassanInstanceProfileCredentialsProviderinstancedirectlytotheclientconstructor_.Ifyouuseanothermethodtoobtainorpassinstanceprofilecredentials,youareresponsibleforcheckingforandrefreshingexpiredcredentials.{quote}[emphasismine]IjustuploadedaversionofthepluginwiththischangetoourJenkinsserver.I'llletitrunandreportbacktomorrowifIseeanyerrors.Ifitworks,I'llcreateapullrequest.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group
[JIRA] [ec2-plugin] (JENKINS-26854) EC2 slave launch stops working after a while with AmazonServiceException Request has expired
Title: Message Title James Judd commented on JENKINS-26854 Re: EC2 slave launch stops working after a while with AmazonServiceException Request has expired Thanks for the info Martin. I spent some more time looking into this tonight and I think I found the cause. Even better, I think the fix is quite simple. At the moment, in EC2Cloud: we create an AmazonEC2Client like so AmazonEC2 client = new AmazonEC2Client(credentialsProvider.getCredentials(), config); According to the Amazon SDK source this creates a StaticCredentialsProvider using the given credentials. From what I can tell, StaticCredentialsProvider never refreshes its credentials, leading to expiration. Instead, you can create an AmazonEC2Client with a credentials provider directly. This should, as far as I can tell, refresh the credentials as needed. AmazonEC2 client = new AmazonEC2Client(credentialsProvider, config); This is further supported by this amazon documentation, which states Important The automatic credentials refresh happens only when you use the default client constructor, which creates its own InstanceProfileCredentialsProvider as part of the default provider chain,_ or when you pass an InstanceProfileCredentialsProvider instance directly to the client constructor_. If you use another method to obtain or pass instance profile credentials, you are responsible for checking for and refreshing expired credentials. [emphasis mine] I just uploaded a version of the plugin with this change to our Jenkins server. I'll let it run and report back tomorrow if I see any errors. If it works, I'll create a pull request. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [git-client-plugin] (JENKINS-28540) git publisher fails if user.email and user.name
Title: Message Title martinfr62 created an issue Jenkins / JENKINS-28540 git publisher fails if user.email and user.name Issue Type: Bug Assignee: Nicolas De Loof Components: git-client-plugin, git-plugin Created: 21/May/15 7:19 PM Environment: Jenkins 1.611, git 2.1.0, git-plugin 2.3.5, git-client-plugin 1.7.1 Priority: Major Reporter: martinfr62 Attempting to use git publisher with command line git - get following error when attempt to use git-plugin with ssh credentials (seems to also happen with username/password). Adding commands git config --global user.email yy...@.com git config --global user.name username from credentials as a build step made this work. git publisher/git-client should preset these locally using the ssh-credentials so we dont need to duplicate them by adding a build step or adding to the build slaves - should be provided from the credentials. ERROR: Failed to push merge to origin repository hudson.plugins.git.GitException: Could not apply tag jenkins-ZipManagerTag-12-SUCCESS at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.tag(CliGitAPIImpl.java:1201) at hudson.plugins.git.GitAPI.tag(GitAPI.java:274) at
[JIRA] [core] (JENKINS-19939) Discard Old Builds I/O Performance Issue
Title: Message Title Daniel Beck commented on JENKINS-19939 Re: Discard Old Builds I/O Performance Issue Hi, I'm hoping this bug can be revisited. Consider addressing my comments to clarify what the issue is. Some sort of info in the log info be very welcome. I'll look into that. Some other plugins that do work after a build completes, such as Calculation of disk usage of workspace, do log the time they took. I think this plugin should do so as well. It's in core, not in a plugin. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [findbugs-plugin] (JENKINS-28537) Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.0:sonar (default-cli) on project XXXXX: Can not execute Sonar: Can not execute Findbugs: TimeoutE
Title: Message Title Antonio Garca created an issue Jenkins / JENKINS-28537 Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.0:sonar (default-cli) on project X: Can not execute Sonar: Can not execute Findbugs: TimeoutException Issue Type: Bug Assignee: Ulli Hafner Components: findbugs-plugin, sonar Created: 21/May/15 6:01 PM Labels: exception plugins jenkins Priority: Major Reporter: Antonio Garca I am working with jenkins 1.515, SonarSource v.3.2.1, Maven 3.0.4, with SonarQube Plugin 2.0.1. configured on Jenkins: I had not applied any kind of upgrade Recently when construction process job start, it takes more time than previous construcctions. I noticed this when SonarSource Plugin start to analyzing code, i.e. FindBugs,Java AST Scan, etc., and finally an exception is thrown due to: [ERROR] Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.0:sonar (default-cli) on project X: Can not execute Sonar: Can not execute Findbugs: TimeoutException - [Help 1]
[JIRA] [accelerated-build-now-plugin] (JENKINS-28539) InvocationTargetException after Upgrade to 1.6 Jenkins
Title: Message Title Darko Palic commented on JENKINS-28539 Re: InvocationTargetException after Upgrade to 1.6 Jenkins maybe related, since they show up after a upgrade from 1.5 to 1.6 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-28532) Jobs get stuck in the queue
Title: Message Title Magnus Sandberg commented on JENKINS-28532 Re: Jobs get stuck in the queue PrioritySorter will only order the Jobs in the Queue and will not interfere with execution/scheduling (if you do not use Run Exclusive) so this does look like a problem somewhere else. Totally of the topic: You are the first one I see that uses anything else besides Absolute sorting - I would be happy if you can share your thought on the Queueing strategy, feel free to email me. Thanks, Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
