[JIRA] [s3-plugin] (JENKINS-25509) When a build is aborted, publishing to s3 should not be attempted
Title: Message Title Eli Oxman commented on JENKINS-25509 Re: When a build is aborted, publishing to s3 should not be attempted Hello, I've opened this PR which should fix the issue: https://github.com/jenkinsci/s3-plugin/pull/59 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-28367) perforce plugin don't support P4 ticket authentication
Title: Message Title Bin Yin commented on JENKINS-28367 Re: perforce plugin don't support P4 ticket authentication Thanks Rob for the comment. The command "p4 login -a -p" don't support my P4 ticket auth(as below). But I can use "p4 login" to login P4. C:\Users\xxx>p4 login -a -p User not allowed to create a ticket that is valid on all host machines. 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-28367) perforce plugin don't support P4 ticket authentication
Title: Message Title Bin Yin edited a comment on JENKINS-28367 Re: perforce plugin don't support P4 ticket authentication Thanks Rob for the comment.The command "p4 login -a -p" don't support my P4 ticket auth(as below). But I can use "p4 login" to login P4. --- C:\Users\xxx>p4 login -a -pUser not allowed to create a ticket that is valid on all host machines. 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] [copyartifact-plugin] (JENKINS-14999) Copy Artifact plugin: Unable to find project for artifact copy when using a build parameter
Title: Message Title Or Shachar reopened an issue Hi, The issue reoccurs with Jenkins core 1.596.2 and copy-artifacts version 1.35. Tested it with any of the parameters and I still get same issue. Jenkins / JENKINS-14999 Copy Artifact plugin: Unable to find project for artifact copy when using a build parameter Change By: Or Shachar Resolution: Fixed Status: Closed Reopened 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] [svn-release-mgr-plugin] (JENKINS-28396) Cannot tag code from SubversionReleaseSCM
Title: Message Title HeadLess HeadLess created an issue Jenkins / JENKINS-28396 Cannot tag code from SubversionReleaseSCM Issue Type: Improvement Assignee: k2nakamura Components: svn-release-mgr-plugin, svn-tag-plugin Created: 14/May/15 8:39 AM Environment: svn-release-mgr ver.1.2 svn-tag-plugin ver.1.17 Jenkins ver.1.562 on win8 Labels: svn release tag plugin Priority: Major Reporter: HeadLess HeadLess Attempt to tag code checked out using Subversion Release Manager results in log: ... Starting to tag SvnTag plugin does not support tagging for SCM hudson.scm.SubversionReleaseSCM@54db9e58. ... Since they're not much different implementations (I think) - could support for this be added? One would think that some releases should be tagged Keep up great work!
[JIRA] [copyartifact-plugin] (JENKINS-14999) Copy Artifact plugin: Unable to find project for artifact copy when using a build parameter
Title: Message Title Or Shachar updated JENKINS-14999 Jenkins / JENKINS-14999 Copy Artifact plugin: Unable to find project for artifact copy when using a build parameter Change By: Or Shachar Status: Reopened Open 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] [copyartifact-plugin] (JENKINS-14999) Copy Artifact plugin: Unable to find project for artifact copy when using a build parameter
Title: Message Title Or Shachar closed an issue as Fixed It seems like now you need to give special permissions at the source job to allow specific jobs to copy artifacts. Jenkins / JENKINS-14999 Copy Artifact plugin: Unable to find project for artifact copy when using a build parameter Change By: Or Shachar Status: Open 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] [robot-plugin] (JENKINS-28338) IO Exception: Truncated TAR archive during copy step in robot-plugin
Title: Message Title jpiironen resolved as Duplicate Okay, I'm closing this as a duplicate. If the problem reappears, you can reopen this or report another issue. Thanks for the report! Jenkins / JENKINS-28338 IO Exception: Truncated TAR archive during copy step in robot-plugin Change By: jpiironen Status: Open Resolved 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] [svn-release-mgr-plugin] (JENKINS-28396) Cannot tag code from SubversionReleaseSCM
Title: Message Title HeadLess HeadLess commented on JENKINS-28396 Re: Cannot tag code from SubversionReleaseSCM Upon adding post Build "Trigger parameterized build on other projects" with param Subversion revision: Starting to tag SvnTag plugin does not support tagging for SCM hudson.scm.SubversionReleaseSCM@2dcb8d80. Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered [parameterizedtrigger] no SubversionTagAction found – is this project an SVN project ? [parameterized-trigger] Downstream builds will not be triggered as no parameter is set. So, maybe using SubversionReleaseSCM as drop-in replacement of SubversionSCM is not-so- easy.. 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] [svn-release-mgr-plugin] (JENKINS-28396) Cannot tag code from SubversionReleaseSCM
Title: Message Title
HeadLess HeadLess commented on JENKINS-28396
Re: Cannot tag code from SubversionReleaseSCM
triggering next tagging job with params: SVN_REVISION=$ {SVN_REVISION} SVN_URL=${SVN_URL} and checkingOut this ${SVN_REVISION}
finishes tagging succesfully.
Building in workspace C:\Users\jpodpora\.jenkins\jobs\tagPrerealease1\workspace Checking out a fresh workspace because there's no workspace at C:\Users\jpodpora\.jenkins\jobs\tagPrerealease1\workspace Cleaning local Directory . Checking out svn://localhost/D:/myNewSvnTestRepo/trunk@205 at revision 205 A nowy5.txt A nowy8.txt A nowy9.txt A addOneChange.bat A nowy.txt A nowy10.txt A nowy11.txt A nowy2.txt A nowy3.txt A build.xml A nowyZZ.txt At revision 205 no change for svn://localhost/D:/myNewSvnTestRepo/trunk since the previous build [workspace] $ cmd /c call C:\Users\jpodpora\AppData\Local\Temp\hudson8386110393862585076.bat build Starting to tag Tagging svn://localhost/D:/myNewSvnTestRepo/trunk Remote Module Location: svn://localhost/D:/myNewSvnTestRepo/trunk@205. Tag Base URL: svn://localhost/D:/myNewSvnTestRepo/tags/dev/preRelease_rev_205. There was no old tag at svn://localhost/D:/myNewSvnTestRepo/tags/dev/preRelease_rev_205. Tagged as Revision 206
Propably will work in post-release trigger too. Ugly - but works..
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] [svn-release-mgr-plugin] (JENKINS-28396) Cannot tag code from SubversionReleaseSCM
Title: Message Title
HeadLess HeadLess edited a comment on JENKINS-28396
Re: Cannot tag code from SubversionReleaseSCM
triggering next tagging job with params:SVN_REVISION=${SVN_REVISION}SVN_URL=${SVN_URL}and checkingOut this ${SVN_REVISION} finishes tagging succesfully.{quote}Building in workspace C:\Users\jpodpora\.jenkins\jobs\tagPrerealease1\workspaceChecking out a fresh workspace because there's no workspace at C:\Users\jpodpora\.jenkins\jobs\tagPrerealease1\workspaceCleaning local Directory .Checking out svn://localhost/D:/myNewSvnTestRepo/trunk@205 at revision 205A nowy5 new .txt A nowy8.txtA nowy9.txtA addOneChange.batA nowy.txtA nowy10.txtA nowy11.txtA nowy2.txtA nowy3.txtA build.xmlA nowyZZ.txt At revision 205no change for svn://localhost/D:/myNewSvnTestRepo/trunk since the previous build[workspace] $ cmd /c call C:\Users\jpodpora\AppData\Local\Temp\hudson8386110393862585076.batbuildStarting to tagTagging svn://localhost/D:/myNewSvnTestRepo/trunkRemote Module Location: svn://localhost/D:/myNewSvnTestRepo/trunk@205.Tag Base URL: svn://localhost/D:/myNewSvnTestRepo/tags/dev/preRelease_rev_205.There was no old tag at svn://localhost/D:/myNewSvnTestRepo/tags/dev/preRelease_rev_205.Tagged as Revision 206{quote}Propably will work in post-release trigger too.Ugly - but works..
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] [svn-release-mgr-plugin] (JENKINS-28396) Cannot tag code from SubversionReleaseSCM
Title: Message Title
HeadLess HeadLess edited a comment on JENKINS-28396
Re: Cannot tag code from SubversionReleaseSCM
triggering next tagging job with params:SVN_REVISION=${SVN_REVISION}SVN_URL=${SVN_URL}and checkingOut this ${SVN_REVISION} finishes tagging succesfully.{quote}Building in workspace C:\Users\jpodpora\.jenkins\jobs\tagPrerealease1\workspaceChecking out a fresh workspace because there's no workspace at C:\Users\jpodpora\.jenkins\jobs\tagPrerealease1\workspaceCleaning local Directory .Checking out svn://localhost/D:/myNewSvnTestRepo/trunk@205 at revision 205A new.txtAt revision 205no change for svn://localhost/D:/myNewSvnTestRepo/trunk since the previous build[workspace] $ cmd /c call C:\Users\ jpodpora user \AppData\Local\Temp\hudson8386110393862585076.batbuildStarting to tagTagging svn://localhost/D:/myNewSvnTestRepo/trunkRemote Module Location: svn://localhost/D:/myNewSvnTestRepo/trunk@205.Tag Base URL: svn://localhost/D:/myNewSvnTestRepo/tags/dev/preRelease_rev_205.There was no old tag at svn://localhost/D:/myNewSvnTestRepo/tags/dev/preRelease_rev_205.Tagged as Revision 206{quote}Propably will work in post-release trigger too.Ugly - but works..
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] [svn-release-mgr-plugin] (JENKINS-28396) Cannot tag code from SubversionReleaseSCM
Title: Message Title
HeadLess HeadLess edited a comment on JENKINS-28396
Re: Cannot tag code from SubversionReleaseSCM
triggering next tagging job with params:SVN_REVISION=${SVN_REVISION}SVN_URL=${SVN_URL}and checkingOut this ${SVN_REVISION} finishes tagging succesfully.{quote}Building in workspace C:\Users\ jpodpora user \.jenkins\jobs\tagPrerealease1\workspaceChecking out a fresh workspace because there's no workspace at C:\Users\ jpodpora user \.jenkins\jobs\tagPrerealease1\workspaceCleaning local Directory .Checking out svn://localhost/D:/myNewSvnTestRepo/trunk@205 at revision 205A new.txtAt revision 205no change for svn://localhost/D:/myNewSvnTestRepo/trunk since the previous build[workspace] $ cmd /c call C:\Users\user\AppData\Local\Temp\hudson8386110393862585076.batbuildStarting to tagTagging svn://localhost/D:/myNewSvnTestRepo/trunkRemote Module Location: svn://localhost/D:/myNewSvnTestRepo/trunk@205.Tag Base URL: svn://localhost/D:/myNewSvnTestRepo/tags/dev/preRelease_rev_205.There was no old tag at svn://localhost/D:/myNewSvnTestRepo/tags/dev/preRelease_rev_205.Tagged as Revision 206{quote}Propably will work in post-release trigger too.Ugly - but works..
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] [svn-release-mgr-plugin] (JENKINS-28396) Cannot tag code from SubversionReleaseSCM
Title: Message Title
HeadLess HeadLess edited a comment on JENKINS-28396
Re: Cannot tag code from SubversionReleaseSCM
triggering next tagging job with params:SVN_REVISION=${SVN_REVISION} SVN_URL= *Warning - ${SVN_URL} is not resolved - is passed as string.* and checkingOut CheckingOut this ${SVN_REVISION} finishes tagging succesfully. If SVN_URL will change - needs to change in both jobs manually. {quote}Building in workspace C:\Users\user\.jenkins\jobs\tagPrerealease1\workspaceChecking out a fresh workspace because there's no workspace at C:\Users\user\.jenkins\jobs\tagPrerealease1\workspaceCleaning local Directory .Checking out svn://localhost/D:/myNewSvnTestRepo/trunk@205 at revision 205A new.txtAt revision 205no change for svn://localhost/D:/myNewSvnTestRepo/trunk since the previous build[workspace] $ cmd /c call C:\Users\user\AppData\Local\Temp\hudson8386110393862585076.batbuildStarting to tagTagging svn://localhost/D:/myNewSvnTestRepo/trunkRemote Module Location: svn://localhost/D:/myNewSvnTestRepo/trunk@205.Tag Base URL: svn://localhost/D:/myNewSvnTestRepo/tags/dev/preRelease_rev_205.There was no old tag at svn://localhost/D:/myNewSvnTestRepo/tags/dev/preRelease_rev_205.Tagged as Revision 206{quote}Propably will work in post-release trigger too.Ugly - but works..
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] [svn-release-mgr-plugin] (JENKINS-28396) Cannot tag code from SubversionReleaseSCM
Title: Message Title
HeadLess HeadLess edited a comment on JENKINS-28396
Re: Cannot tag code from SubversionReleaseSCM
triggering next tagging job with params:SVN_REVISION=${SVN_REVISION} *Warning - ${SVN_URL} is not resolved - it is passed as string.*CheckingOut this ${SVN_REVISION} finishes tagging succesfully.If SVN_URL will change - needs to change in both jobs manually.{quote}Building in workspace C:\Users\user\.jenkins\jobs\tagPrerealease1\workspaceChecking out a fresh workspace because there's no workspace at C:\Users\user\.jenkins\jobs\tagPrerealease1\workspaceCleaning local Directory .Checking out svn://localhost/D:/myNewSvnTestRepo/trunk@205 at revision 205A new.txtAt revision 205no change for svn://localhost/D:/myNewSvnTestRepo/trunk since the previous build[workspace] $ cmd /c call C:\Users\user\AppData\Local\Temp\hudson8386110393862585076.batbuildStarting to tagTagging svn://localhost/D:/myNewSvnTestRepo/trunkRemote Module Location: svn://localhost/D:/myNewSvnTestRepo/trunk@205.Tag Base URL: svn://localhost/D:/myNewSvnTestRepo/tags/dev/preRelease_rev_205.There was no old tag at svn://localhost/D:/myNewSvnTestRepo/tags/dev/preRelease_rev_205.Tagged as Revision 206{quote}Propably will work in post-release trigger too.Ugly - but works..
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-plugin] (JENKINS-28397) GitHub plugin only re-registers a subset of webhooks
Title: Message Title Graham Hay created an issue Jenkins / JENKINS-28397 GitHub plugin only re-registers a subset of webhooks Issue Type: Bug Assignee: Unassigned Components: github-plugin Created: 14/May/15 9:44 AM Environment: Jenkins ver 1.601, GH plugin 1.11.3 Priority: Minor Reporter: Graham Hay I set up jenkins to "auto-manage" hook urls, but if I click the re-register button it only processes the hooks for 4 projects. There is at least one more with the "build when a change is pushed" box ticked. Is it possible that cloning projects could cause problems? Is there any to force the hook to be created? I've tried ticking and unticking that box without any change Add Comment
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-28398) Error Message : Error during Analysis run. See output console for details
Title: Message Title nikhi kamboj created an issue Jenkins / JENKINS-28398 Error Message : Error during Analysis run. See output console for details Issue Type: Bug Assignee: nikhi kamboj Components: hp-application-automation-tools-plugin Created: 14/May/15 9:49 AM Environment: i am getting the below mention error in load runner when executing with jenkins. can anybody help me out in this. Priority: Minor Reporter: nikhi kamboj Error Message Error during Analysis run. See output console for detailsStandard Output 14/05/2015 12:30:54 Running: C:\Program Files (x86)\HP\LoadRunner\scenario\Scenario1.lrs Cleaning up the environment... Preparing scenario C:\Program Files (x86)\HP\LoadRunner\scenario\Scenario1.lrs for execution. Load Generator localhost connected Starting scenario... Analyzing results... closing Controller Controller closed calling analysis report generator Error: Error during Analysis run. See output console for details Analysis Results: starting analysis launcher HP LoadRunner Analysis Command Line Executer Usage: LRAnalysisLauncher.exe[.lrr file location] [.lra output location] [html report output folder] analysis report generator finished Error(s) summary: 0 ignored , 0 errors
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-28398) Error Message : Error during Analysis run. See output console for details
Title: Message Title nikhi kamboj started work on JENKINS-28398 Change By: nikhi kamboj Status: Open In Progress 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] [hp-application-automation-tools-plugin] (JENKINS-28398) Error Message : Error during Analysis run. See output console for details
Title: Message Title nikhi kamboj stopped work on JENKINS-28398 Change By: nikhi kamboj Status: In Progress Open 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-28335) Be able to use GitPublisher in a workflow description
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-28335 Be able to use GitPublisher in a workflow description Change By: Jesse Glick Labels: workflow 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-28335) Be able to use GitPublisher in a workflow
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-28335 Be able to use GitPublisher in a workflow I already considered this possibility but do not consider it straightforward. GitPublisher relies on obtaining the single GitSCM configured for the project; there is no equivalent concept for Workflow. Anyway the extensive hardcoded logic in this publisher probably does not make sense in an otherwise flexible script. More useful would be an independent Step which lets you run arbitrary git commands, integrates with Credentials for authentication, and lets you pick a GitTool (certainly CLI, perhaps also JGit). Change By: Jesse Glick Summary: Be able to use GitPublisher in a workflow description Issue Type: Improvement New Feature Priority: Trivial Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [git-plugin] (JENKINS-28335) Be able to use GitPublisher in a workflow
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28335 Re: Be able to use GitPublisher in a workflow Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/workflow-plugin/26beaf00bff3fc235cb73d53c77bf64b632fdc75 Log: JENKINS-28335 Noting. 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-28383) Infrequent "ERROR: Error cloning remote repo 'origin'"
Title: Message Title Tony Zedar commented on JENKINS-28383 Re: Infrequent "ERROR: Error cloning remote repo 'origin'" The version of git we are using is: git-gui version 0.19.GITGUI git version 1.9.4.msysgit.0 We are not currently monitoring the git server but I will check more into this. I was not thinking it was the git server because a second job just minutes after the failed job can pass without the same issue. I was thinking this info would rule out the git server. We were discussing upgrading the git plugins. If you think this could help we will do it asap. Most of our tests run at night when no one is around so there shouldn't be much happening but the failures do also happen during the day. It is definitely not time of day specific. It is hard to figure out because it is completely random and can happen at any time. 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-26781) regression resolving Descriptor using "$class" vs "kind"
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26781 Re: regression resolving Descriptor using "$class" vs "kind" Code changed in jenkins User: Jesse Glick Path: test/src/test/java/hudson/model/DescriptorTest.java http://jenkins-ci.org/commit/jenkins/00cbb2823187df7efcf8c9de33907f0f58c77729 Log: JENKINS-26781 Reproduced problem in test. Besides failing in master, it also fails in 4e0af43 (merge of #1443), but passes in the 1.598-SNAPSHOT parent 239caf8. (cherry picked from commit 33041903ab67c3e32959b7b78e557ffb7d4ecd16) 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-26781) regression resolving Descriptor using "$class" vs "kind"
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26781 Re: regression resolving Descriptor using "$class" vs "kind" Code changed in jenkins User: Nicolas De Loof Path: core/src/main/java/hudson/model/Descriptor.java core/src/main/resources/lib/form/class-entry.jelly http://jenkins-ci.org/commit/jenkins/dfa17c4a18cb9585681102770db8b7117eab9531 Log: JENKINS-26781 lookup descriptor by ID, then by class if explicitly set to match some specific use cases. (cherry picked from commit 8881703f7c7351695c5d5b2662faefae60de68e8) 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] [copyartifact-plugin] (JENKINS-28011) Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job
Title: Message Title
SCM/JIRA link daemon commented on JENKINS-28011
Re: Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job
Code changed in jenkins User: Jesse Glick Path: core/src/main/resources/lib/form/class-entry.jelly http://jenkins-ci.org/commit/jenkins/ecc848b20dd3d972c76f9435e83908e419111fe2 Log: [FIXED JENKINS-28011] Amending #1563, $ {descriptor}
is not necessarily $ {attrs.descriptor}
! (cherry picked from commit 343382b9ff8a978f6914cc64714a5c16bd9b511a)
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-28093) 404 on jenkins.plugins.nodejs.tools.NodeJSInstaller.json.html
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28093 Re: 404 on jenkins.plugins.nodejs.tools.NodeJSInstaller.json.html Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/tools/DownloadFromUrlInstaller.java http://jenkins-ci.org/commit/jenkins/83c7f8467c15e10b18833acae1154bdf285a589a Log: [FIXED JENKINS-28093] Reverting getDownloadableId from #1563. Not compatible. (cherry picked from commit 972db2a593fc978b8fb16a8d14cf485b8679c6e2) 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-28110) 1.610 “Failed to instantiate” error
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28110 Re: 1.610 “Failed to instantiate” error Code changed in jenkins User: Jesse Glick Path: core/src/main/resources/lib/form/class-entry.jelly http://jenkins-ci.org/commit/jenkins/2e51740fbeef363a888446846b497550d4d2981b Log: [FIXED JENKINS-28110] Always generate stapler-class, even when generating kind. (cherry picked from commit ef2b6580a8621a4a627ef015481d58bf4c83a682) 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-28110) 1.610 “Failed to instantiate” error
Title: Message Title
SCM/JIRA link daemon commented on JENKINS-28110
Re: 1.610 “Failed to instantiate” error
Code changed in jenkins User: Jesse Glick Path: test/src/test/java/hudson/model/DescriptorTest.java test/src/test/resources/hudson/model/DescriptorTest/B1/config.jelly test/src/test/resources/hudson/model/DescriptorTest/B2/config.jelly test/src/test/resources/hudson/model/DescriptorTest/D1/config.jelly test/src/test/resources/hudson/model/DescriptorTest/D2/config.jelly test/src/test/resources/hudson/model/DescriptorTest/D3/config.jelly http://jenkins-ci.org/commit/jenkins/11d46ad639943feb9f17da5d4d1529cdfbd87495 Log:
JENKINS-28110
Reproduced problem in test. Starting in 4f24a02 (1.587-SNAPSHOT, before #1443 or stapler #39), nestedDescribableOverridingId passes. nestedDescribableSharingClass fails given {stapler-class: D3, kind: d3a}
. (Stapler has no way of interpreting kind since it knows nothing of Descriptor, only implementation class names.) In master (3080573), both fail in the way reported (only kind is passed in). After adding stapler-class back, nestedDescribableOverridingId passes again. (cherry picked from commit 1f41bec8ef656da014b7145fdff82563c030ca29)
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-26781) regression resolving Descriptor using "$class" vs "kind"
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26781 Re: regression resolving Descriptor using "$class" vs "kind" Code changed in jenkins User: Oliver Gondža Path: core/src/main/java/hudson/DescriptorExtensionList.java core/src/main/java/hudson/model/ComputerSet.java core/src/main/java/hudson/model/Descriptor.java core/src/main/java/hudson/model/Items.java core/src/main/java/hudson/tools/ToolLocationNodeProperty.java core/src/main/java/hudson/util/DescriptorList.java core/src/main/resources/lib/form/class-entry.jelly test/src/test/java/hudson/model/DescriptorTest.java test/src/test/resources/hudson/model/DescriptorTest/B1/config.jelly test/src/test/resources/hudson/model/DescriptorTest/B2/config.jelly test/src/test/resources/hudson/model/DescriptorTest/D1/config.jelly test/src/test/resources/hudson/model/DescriptorTest/D2/config.jelly test/src/test/resources/hudson/model/DescriptorTest/D3/config.jelly http://jenkins-ci.org/commit/jenkins/0f0047a17d04aa0111e76046b5d3c8b1208e8385 Log: Merge pull request #1701 from jglick/backport- JENKINS-26781 JENKINS-26781 Backport to 1.609 Compare: https://github.com/jenkinsci/jenkins/compare/aadc9914ff34...0f0047a17d04 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] [credentials-binding-plugin] (JENKINS-28399) Support for SSHUserPrivateKey
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-28399 Support for SSHUserPrivateKey Issue Type: New Feature Assignee: Jesse Glick Components: credentials-binding-plugin Created: 14/May/15 12:22 PM Priority: Major Reporter: Jesse Glick Would be useful to have a Binding for SSHUserPrivateKey. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [credentials-binding-plugin] (JENKINS-27389) credentials set via 'withCredentials' block isn't accesible from 'env'
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27389 Re: credentials set via 'withCredentials' block isn't accesible from 'env' Code changed in jenkins User: Jesse Glick Path: CHANGES.md http://jenkins-ci.org/commit/workflow-plugin/8aba4d5b6c7236aaddbda7c69e89807c872add4f Log: JENKINS-27389 Noting. 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] [credentials-binding-plugin] (JENKINS-27386) Access credentials value from workflow Groovy script
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-27386 Access credentials value from workflow Groovy script Change By: Jesse Glick Issue Type: Bug New Feature 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] [durable-task-plugin] (JENKINS-28400) Not timing when launch pid fails to appear
Title: Message Title Tom FENNELLY created an issue Jenkins / JENKINS-28400 Not timing when launch pid fails to appear Issue Type: Bug Assignee: Jesse Glick Components: durable-task-plugin Created: 14/May/15 12:35 PM Priority: Major Reporter: Tom FENNELLY ShellController.exitStatus if more than a minute has elapsed since doLaunch, and still _pid == 0, return -2 Also consider uncommenting ps.stdout(listener) under some conditions. Add Comment
[JIRA] [durable-task-plugin] (JENKINS-28400) Not timing out when launch pid fails to appear
Title: Message Title Tom FENNELLY updated an issue Jenkins / JENKINS-28400 Not timing out when launch pid fails to appear Change By: Tom FENNELLY Summary: Not timing out when launch pid fails to 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] [core] (JENKINS-28093) 404 on jenkins.plugins.nodejs.tools.NodeJSInstaller.json.html
Title: Message Title Ireneusz Makowski commented on JENKINS-28093 Re: 404 on jenkins.plugins.nodejs.tools.NodeJSInstaller.json.html It is related to following message: "You currently are using browser-based download to retrieve metadata for Jenkins plugins and tools. This has reliability issues and is not considered fully secure. Consider switching to server-based download." If I go with this suggestion plugin update center is broken. 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-28093) 404 on jenkins.plugins.nodejs.tools.NodeJSInstaller.json.html
Title: Message Title Daniel Beck commented on JENKINS-28093 Re: 404 on jenkins.plugins.nodejs.tools.NodeJSInstaller.json.html Ireneusz Makowski Are you saying the fix in 1.612 does not work? 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] [p4-plugin] (JENKINS-26486) Workspace fails to update when Replace missing/modified files is checked
Title: Message Title amit yedidia commented on JENKINS-26486 Re: Workspace fails to update when Replace missing/modified files is checked Hi, Any progress on this issue? I run into it myself. was able to fix it on WIN7 machine by installing java1.7r80. now I got it on my linux slave as well Thanks. Amit 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-28383) Infrequent "ERROR: Error cloning remote repo 'origin'"
Title: Message Title Mark Waite commented on JENKINS-28383 Re: Infrequent "ERROR: Error cloning remote repo 'origin'" Tony Zedar I don't think an upgrade of the git plugin will change the behavior. The timeout is happening inside the command line git program (at least according to the log). It is possible that the upgrade will help, but I would truly be surprised. If I were you, I'd be more likely to evaluate updating the command line git from 1.9.4 to the latest version of msysgit 1.9.5. I believe it included an update to the "ssh" program which might help in your case. 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-28401) More disable/enable button to sidepanel
Title: Message Title Oliver Gondža created an issue Jenkins / JENKINS-28401 More disable/enable button to sidepanel Issue Type: Improvement Assignee: Oliver Gondža Components: core Created: 14/May/15 1:12 PM Priority: Minor Reporter: Oliver Gondža Improve the appearance of project page (disabled or not) moving the button where it belongs. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-28384) NPE from LoadStatistics$LoadStatisticsSnapshot$Builder.with
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28384 Re: NPE from LoadStatistics$LoadStatisticsSnapshot$Builder.with Code changed in jenkins User: Jesse Glick Path: changelog.html http://jenkins-ci.org/commit/jenkins/6966f33d3db7e7308a201580c9c842f30f7245c9 Log: JENKINS-28384 Noting merge of #1700. 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] [email-ext-plugin] (JENKINS-28402) Email-ext plugin 2.40.2 warns of a circular dependency error
Title: Message Title davida2009 created an issue Jenkins / JENKINS-28402 Email-ext plugin 2.40.2 warns of a circular dependency error Issue Type: Bug Assignee: Alex Earl Components: email-ext-plugin Created: 14/May/15 1:22 PM Environment: Jenkins 1.607 Priority: Major Reporter: davida2009 I updated the Email-ext plugin from 2.40.1 to 2.40.2 and now see the following error in the Jenkins log at startup: May 14, 2015 11:08:07 AM INFO jenkins.InitReactorRunner$1 onAttained Listed all plugins May 14, 2015 11:08:09 AM INFO jenkins.InitReactorRunner$1 onAttained Prepared all plugins May 14, 2015 11:08:17 AM WARNING hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 error Failed to instantiate Key[type=hudson.plugins.emailext.ExtendedEmailPublisherDescriptor, annotation=[none]]; skipping this component com.google.inject.ProvisionException: Guice provision errors: 1) Tried proxying hudson.plugins.emailext.ExtendedEmailPublisherDescriptor to support a circular dependency, but it is not an interface. 1 error at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52) at com.google.inject.Scopes$1$1.get(Scopes.java:65) at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(Extensio
[JIRA] [perforce-plugin] (JENKINS-28367) perforce plugin don't support P4 ticket authentication
Title: Message Title Rob Petti commented on JENKINS-28367 Re: perforce plugin don't support P4 ticket authentication That looks like an issue with the configuration of your server. Unfortunately there's nothing I can do about that. 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] [durable-task-plugin] (JENKINS-28400) Not timing out when launch pid fails to appear
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-28400 Not timing out when launch pid fails to appear Change By: Jesse Glick Labels: workflow 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] [email-ext-plugin] (JENKINS-28402) Email-ext plugin 2.40.2 warns of a circular dependency error
Title: Message Title Alex Earl commented on JENKINS-28402 Re: Email-ext plugin 2.40.2 warns of a circular dependency error Oh, good. Another one I can't replicate... 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-28361) Queue.Task has no ExportedBean attribute, but it's being exported to API
Title: Message Title
Jesse Glick updated an issue
Jenkins / JENKINS-28361
Queue.Task has no ExportedBean attribute, but it's being exported to API
Change By:
Jesse Glick
REST API use-case: {{ Queue. Item. Task Issue example: https://github.com/cloudbees/cloudbees-long-running-build-plugin/pull/5 }}
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] [email-ext-plugin] (JENKINS-28402) Email-ext plugin 2.40.2 warns of a circular dependency error
Title: Message Title Alex Earl commented on JENKINS-28402 Re: Email-ext plugin 2.40.2 warns of a circular dependency error Do you have the Mailer plugin enabled? 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] [email-ext-plugin] (JENKINS-28357) Cannot use Jelly Template after recent 2.40 fix
Title: Message Title Alex Earl commented on JENKINS-28357 Re: Cannot use Jelly Template after recent 2.40 fix I tried with 1.596.2 as well with your jpi, and I didn't have any issues still. 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] [email-ext-plugin] (JENKINS-28402) Email-ext plugin 2.40.2 warns of a circular dependency error
Title: Message Title davida2009 commented on JENKINS-28402 Re: Email-ext plugin 2.40.2 warns of a circular dependency error Yes, Mailer is enabled. I guess that means I should disable it? 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] [subversion-plugin] (JENKINS-22542) Subversion polling not work with externals or variables in URL - E200015: No credential to try.
Title: Message Title Jiri Pergl commented on JENKINS-22542 Re: Subversion polling not work with externals or variables in URL - E200015: No credential to try. Hi, we have a similar problem with the latest Subversion plugin 2.5 version. We have a project which has svn:external dependency. If we do the commit to this external and then executed the job, the svn update is failed. This problem is only for the first execution of the job, next repeating of the job is successful. We have received this stacktrace: hudson.util.IOException2: revision check failed on http://externalUrl/project.Foo/trunk/xxx/ at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:196) at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:137) at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:725) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:860) at hudson.scm.SCM.checkout(SCM.java:484) at hudson.model.AbstractProject.checkout(AbstractProject.java:1270) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:609) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:531) at hudson.model.Run.execute(Run.java:1718) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:60) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:759) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:371) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:359) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:710) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1032) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:175) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:184) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:160) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1259) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:968) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:873) at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:184) ... 12 more Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. at org.tmat
[JIRA] [core] (JENKINS-28110) 1.610 “Failed to instantiate” error
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-28110 1.610 “Failed to instantiate” error Change By: Oliver Gondža Labels: 1.609.1-fixed form-data regression stapler 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] [email-ext-plugin] (JENKINS-28402) Email-ext plugin 2.40.2 warns of a circular dependency error
Title: Message Title Alex Earl commented on JENKINS-28402 Re: Email-ext plugin 2.40.2 warns of a circular dependency error No, it should be enabled. Let me look into it some more. 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-26781) regression resolving Descriptor using "$class" vs "kind"
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-26781 regression resolving Descriptor using "$class" vs "kind" Change By: Oliver Gondža Labels: api lts 1.609.1 - candidate fixed api regression stapler 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] [ssh-slaves-plugin] (JENKINS-28403) SSH-slaves fails because Windows VM did not start yet on OpenStack
Title: Message Title Abdul Charif created an issue Jenkins / JENKINS-28403 SSH-slaves fails because Windows VM did not start yet on OpenStack Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: ssh-slaves-plugin Created: 14/May/15 2:12 PM Environment: Open Stack Jenkins 1613 Labels: plugin slave windows openstack Priority: Major Reporter: Abdul Charif When Open-stack cloud plugin dynamically provisions a VM, it uses SSH-slaves plugins to install the slave agent. Similar to this case https://issues.jenkins-ci.org/browse/JENKINS-20921 but i used Cygwin as suggested by arazauci. The problem is that it takes a windows VM a little bit more time to start the SSH daemon, so the ssh-slaves plugin fails to start the SSH connection since windows did not start just yet. 5 seconds later when the VM launches, i can connect the slave node. However, i would have to do this manually to trigger a job every time. Can we add an a time out for the ssh slaves configuration in openstack provisioning ?
[JIRA] [core] (JENKINS-28093) 404 on jenkins.plugins.nodejs.tools.NodeJSInstaller.json.html
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-28093 404 on jenkins.plugins.nodejs.tools.NodeJSInstaller.json.html Change By: Oliver Gondža Labels: 1.609.1-fixed regression tools 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] [email-ext-plugin] (JENKINS-28402) Email-ext plugin 2.40.2 warns of a circular dependency error
Title: Message Title davida2009 commented on JENKINS-28402 Re: Email-ext plugin 2.40.2 warns of a circular dependency error There is a later error but I assume that is unrelated: May 14, 2015 12:26:52 PM WARNING hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider retrieveUser Credential exception trying to authenticate against uktm.eu.nec.com domain org.acegisecurity.BadCredentialsException: Empty password at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:254) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:219) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:163) at org.acegisecurity.providers.dao.AbstractUserDetailsAuthenticationProvider.authenticate(AbstractUserDetailsAuthenticationProvider.java:122) at org.acegisecurity.providers.ProviderManager.doAuthentication(ProviderManager.java:200) at org.acegisecurity.AbstractAuthenticationManager.authenticate(AbstractAuthenticationManager.java:47) at org.acegisecurity.ui.webapp.AuthenticationProcessingFilter.attemptAuthentication(AuthenticationProcessingFilter.java:74) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:252) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:168) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:
[JIRA] [core] (JENKINS-28401) Move disable/enable button to sidepanel
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-28401 Move disable/enable button to sidepanel Change By: Oliver Gondža Summary: More Move disable/enable button to sidepanel 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-commander-plugin] (JENKINS-27881) Use user's identity to perform the command
Title: Message Title Oliver Gondža resolved as Fixed Fixed in 0.2 Jenkins / JENKINS-27881 Use user's identity to perform the command Change By: Oliver Gondža 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] [email-ext-plugin] (JENKINS-28402) Email-ext plugin 2.40.2 warns of a circular dependency error
Title: Message Title davida2009 commented on JENKINS-28402 Re: Email-ext plugin 2.40.2 warns of a circular dependency error Restarted Jenkins and got the same error: "1) Tried proxying hudson.plugins.emailext.ExtendedEmailPublisherDescriptor to support a circular dependency..." but did not get the second error: "WARNING hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider retrieveUser Credential exception trying to authenticate against uktm.eu.nec.com domain". 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] [email-ext-plugin] (JENKINS-28402) Email-ext plugin 2.40.2 warns of a circular dependency error
Title: Message Title Alex Earl commented on JENKINS-28402 Re: Email-ext plugin 2.40.2 warns of a circular dependency error Yeah, the second error is not related. What version of Jenkins? What version of Mailer? 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-28404) Failing test age not set properly
Title: Message Title Charles Beaudin created an issue Jenkins / JENKINS-28404 Failing test age not set properly Issue Type: Bug Assignee: Ivo Bellin Salarin Attachments: results.trx Components: mstest-plugin Created: 14/May/15 2:31 PM Environment: Jenkins 1.611 mstest-plugin 0.18 Labels: plugin jenkins Priority: Minor Reporter: Charles Beaudin When two or more tests have the same method name but in different classes then the "failedSince" node in the junit.xml file is never set properly. In fact the value is always the currect build id. I attached a sample of a ".trx" generated with vstest.console.exe. If you build more than once then you will always get an Age of "1".
[JIRA] [email-ext-plugin] (JENKINS-28402) Email-ext plugin 2.40.2 warns of a circular dependency error
Title: Message Title davida2009 commented on JENKINS-28402 Re: Email-ext plugin 2.40.2 warns of a circular dependency error Jenkins 1.607, Mailer 1.15. 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] [vsphere-cloud-plugin] (JENKINS-25955) Restart (and revert) Guest before build
Title: Message Title Jason Swager commented on JENKINS-25955 Re: Restart (and revert) Guest before build Would the following solution work? Assumptions: Disable the slave's revert after X builds feature. As either the first build steps, or as a job that runs prior to your list of build steps, do the following - must be done from a slave OTHER than the target VM slave: Power on target VM slave if necessary. Execute a job on the target VM slave - update the software as necessary. Power the target VM slave down (may need to use the Jenkins CLI to temporarily disable the slave to prevent Jenkins from restarting it once powered down) Take a new snapshot, delete the old revert snapshot. (If necessary, enable the slave via Jenkins CLI), power on the target VM slave Run your normal build steps or job with those build steps Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [email-ext-plugin] (JENKINS-28402) Email-ext plugin 2.40.2 warns of a circular dependency error
Title: Message Title davida2009 commented on JENKINS-28402 Re: Email-ext plugin 2.40.2 warns of a circular dependency error Upgraded to Jenkins 1.613 and the error is still there. 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] [subversion-plugin] (JENKINS-22542) Subversion polling not work with externals or variables in URL - E200015: No credential to try.
Title: Message Title Alexey Larsky edited a comment on JENKINS-22542 Re: Subversion polling not work with externals or variables in URL - E200015: No credential to try. Suppose it because only ferst first time you really getting externals. After you will get them (and got error) if them was changed. 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] [subversion-plugin] (JENKINS-22542) Subversion polling not work with externals or variables in URL - E200015: No credential to try.
Title: Message Title Alexey Larsky commented on JENKINS-22542 Re: Subversion polling not work with externals or variables in URL - E200015: No credential to try. Suppose it because only ferst time you really getting externals. After you will get them (and got error) if them was changed. 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] [vsphere-cloud-plugin] (JENKINS-25955) Restart (and revert) Guest before build
Title: Message Title Alexey Larsky commented on JENKINS-25955 Re: Restart (and revert) Guest before build I believe I can workaround my scenario with additional job. For example just turn off VM in the first job and start in second, which revert VM to snapshot/reset changes and start it. But second job for that is too much overhead. If you for example will add checkbox like "Revert to snapshot/reset changes even VM was powered on" it will cover rollback to snapshot before build steps (and will enough just one job). 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] [email-ext-plugin] (JENKINS-28402) Email-ext plugin 2.40.2 warns of a circular dependency error
Title: Message Title Alex Earl commented on JENKINS-28402 Re: Email-ext plugin 2.40.2 warns of a circular dependency error As a workaround, you can edit the hudson.plugins.emailext.ExtendedEmailPublisher.xml (I think that's the name) in JENKINS_HOME and set overrideGlobalSettings to true and restart Jenkins. You will need to reconfigure your mail server information in the Email-ext global config area. 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] [email-ext-plugin] (JENKINS-28402) Email-ext plugin 2.40.2 warns of a circular dependency error
Title: Message Title davida2009 commented on JENKINS-28402 Re: Email-ext plugin 2.40.2 warns of a circular dependency error Rolled back email-ext plugin to 2.40.1. Error is still there. 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-27708) Concurrent build limits not honored on Jenkins 1.607
Title: Message Title Andrei Costescu commented on JENKINS-27708 Re: Concurrent build limits not honored on Jenkins 1.607 I added my vote to it. 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.
[JIRA] [build-blocker-plugin] (JENKINS-28376) jobs get stuck in queue from time to time
Title: Message Title Daniel Beck commented on JENKINS-28376 Re: jobs get stuck in queue from time to time Our instance here runs on german, so actually I do not know the exact descriptions in english The UI uses whatever your browser is set to send as Accept-Language (unless something like the Locale Plugin is installed). 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] [cloudfoundry-plugin] (JENKINS-28210) FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype
Title: Message Title Aidan Killeen commented on JENKINS-28210 Re: FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype Hi, I have experienced an almost identical error. A HelloWorld web application that has a single index.jsp page. It deploys properly using cf push. The job fails in Jenkins and this is the console output: [JENKINS] Archiving /home/smartretail/.jenkins/jobs/HelloWorldWeb/workspace/pom.xml to ie.huawei.helloworld/HelloWorldWeb/0.0.1-SNAPSHOT/HelloWorldWeb-0.0.1-SNAPSHOT.pom [JENKINS] Archiving /home/smartretail/.jenkins/jobs/HelloWorldWeb/workspace/target/HelloWorldWeb.war to ie.huawei.helloworld/HelloWorldWeb/0.0.1-SNAPSHOT/HelloWorldWeb-0.0.1-SNAPSHOT.war channel stopped Pushing HelloWorldWeb app to http://api.117.78.6.213.xip.io App already exists, resetting. App deleted. Creating new app. Pushing app bits. Starting application. FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype java.util.ServiceConfigurationError: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype at java.util.ServiceLoader.fail(ServiceLoader.java:239) at java.util.ServiceLoader.access$300(ServiceLoader.java:185) at java.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:376) at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:404) at java.util.ServiceLoader$1.next(ServiceLoader.java:480) at javax.websocket.ContainerProvider.getWebSocketContainer(ContainerProvider.java:43) at org.cloudfoundry.client.lib.rest.LoggregatorClient.connectToLoggregator(LoggregatorClient.java:65) at org.cloudfoundry.client.lib.rest.CloudControllerClientImpl.streamLoggregatorLogs(CloudControllerClientImpl.java:2040) at org.cloudfoundry.client.lib.rest.CloudControllerClientImpl.streamLogs(CloudControllerClientImpl.java:244) at org.cloudfoundry.client.lib.CloudFoundryClient.streamLogs(CloudFoundryClient.java:356) at com.activestate.cloudfoundryjenkins.CloudFoundryPushPublisher.printStagingLogs(CloudFoundryPushPublisher.java:372) at com.activestate.cloudfoundryjenkins.CloudFoundryPushPublisher.processOneApp(CloudFoundryPushPublisher.java:222) at com.activestate.cloudfoundryjenkins.CloudFoundryPushPublisher.perform(CloudFoundryPushPublisher.java:119) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:721) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1037) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:670) at hudson.model.Run.execute(Run.java:1766) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374) Finished: FAILURE The app is created but doesn't start. This is a company internal cloud foundry implementation rather than the pivotal one but cf push and the cf plugin for eclipse can both deploy this project while the jenkins cf plugin fails. If I can supply more info I would be happy to do so. best regards Aidan
[JIRA] [cloudfoundry-plugin] (JENKINS-28210) FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype
Title: Message Title Aidan Killeen edited a comment on JENKINS-28210 Re: FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype Hi, I have experienced an almost identical error. A HelloWorld web application that has a single index.jsp page. It deploys properly using cf push. The job fails in Jenkins and this is the console output:[JENKINS] Archiving /home/smartretail/.jenkins/jobs/HelloWorldWeb/workspace/pom.xml to ie.huawei.helloworld/HelloWorldWeb/0.0.1-SNAPSHOT/HelloWorldWeb-0.0.1-SNAPSHOT.pom[JENKINS] Archiving /home/smartretail/.jenkins/jobs/HelloWorldWeb/workspace/target/HelloWorldWeb.war to ie.huawei.helloworld/HelloWorldWeb/0.0.1-SNAPSHOT/HelloWorldWeb-0.0.1-SNAPSHOT.warchannel stoppedPushing HelloWorldWeb app to http://api.117.78.6.213.xip.ioApp already exists, resetting.App deleted.Creating new app.Pushing app bits.Starting application.FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtypejava.util.ServiceConfigurationError: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype at java.util.ServiceLoader.fail(ServiceLoader.java:239) at java.util.ServiceLoader.access$300(ServiceLoader.java:185) at java.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:376) at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:404) at java.util.ServiceLoader$1.next(ServiceLoader.java:480) at javax.websocket.ContainerProvider.getWebSocketContainer(ContainerProvider.java:43) at org.cloudfoundry.client.lib.rest.LoggregatorClient.connectToLoggregator(LoggregatorClient.java:65) at org.cloudfoundry.client.lib.rest.CloudControllerClientImpl.streamLoggregatorLogs(CloudControllerClientImpl.java:2040) at org.cloudfoundry.client.lib.rest.CloudControllerClientImpl.streamLogs(CloudControllerClientImpl.java:244) at org.cloudfoundry.client.lib.CloudFoundryClient.streamLogs(CloudFoundryClient.java:356) at com.activestate.cloudfoundryjenkins.CloudFoundryPushPublisher.printStagingLogs(CloudFoundryPushPublisher.java:372) at com.activestate.cloudfoundryjenkins.CloudFoundryPushPublisher.processOneApp(CloudFoundryPushPublisher.java:222) at com.activestate.cloudfoundryjenkins.CloudFoundryPushPublisher.perform(CloudFoundryPushPublisher.java:119) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:721) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1037) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:670) at hudson.model.Run.execute(Run.java:1766) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374)Finished: FAILUREThe app is created but doesn't start.This is a company internal cloud foundry implementation rather than the pivotal one but cf push and the cf plugin for eclipse can both deploy this project while the jenkins cf plugin fails. I am using Jenkins 1.610 and tomcat 7.0.47 If I can supply more info I would be happy to do so.best regardsAidan
[JIRA] [vsphere-cloud-plugin] (JENKINS-25955) Restart (and revert) Guest before build
Title: Message Title Jason Swager commented on JENKINS-25955 Re: Restart (and revert) Guest before build That's the problem. I can't touch the slave once the job begins. Jenkins will only allow the job to run on a slave if the slave is running and can take the job. If the job starts running on the slave and the slave does a revert, the Jenkins-slave connection is broken and Jenkins will abort the slave. I tried a feature like this early on, but it won't work with Jenkins. Only at the end of the job - when the job is no longer running on the slave, can the plugin do something drastic like revert the VM. 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] [fitnesse-plugin] (JENKINS-27940) Consider using jUnit output from FitNesse
Title: Message Title Serge Zukov updated an issue Jenkins / JENKINS-27940 Consider using jUnit output from FitNesse Change By: Serge Zukov Issue Type: New Feature Improvement 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] [fitnesse-plugin] (JENKINS-12380) Display results whilst build is in progress
Title: Message Title Serge Zukov commented on JENKINS-12380 Re: Display results whilst build is in progress Just to thrown an idea: In theory this could be achieved by using text format when querying test execution. The problem is that FitNesse does not support REST calls for retrieving latest test result therefore showing current nice report will not be possible. 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] [fitnesse-plugin] (JENKINS-12380) Display results whilst build is in progress
Title: Message Title Serge Zukov edited a comment on JENKINS-12380 Re: Display results whilst build is in progress Just to thrown throw an idea:In theory this could be achieved by using text format when querying test execution.The problem is that FitNesse does not support REST calls for retrieving latest test result therefore showing current nice report will not be possible. 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] [fitnesse-plugin] (JENKINS-27936) When few FitNesse test results being published in a single job they renamed into Summary
Title: Message Title Serge Zukov updated an issue Jenkins / JENKINS-27936 When few FitNesse test results being published in a single job they renamed into Summary Change By: Serge Zukov Priority: Minor 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] [job-dsl-plugin] (JENKINS-28405) Add support for all code browser for the Git plugin
Title: Message Title Jean-Philippe BOLATRE created an issue Jenkins / JENKINS-28405 Add support for all code browser for the Git plugin Issue Type: Improvement Assignee: Daniel Spilker Components: job-dsl-plugin Created: 14/May/15 3:48 PM Labels: plugin git enhancement Priority: Minor Reporter: Jean-Philippe BOLATRE Actually, only stash is supported, please add support for all others code browser supported by the Git plugin . Add Comment
[JIRA] [job-dsl-plugin] (JENKINS-28405) Add support for all code browser for the Git plugin
Title: Message Title Jean-Philippe BOLATRE commented on JENKINS-28405 Re: Add support for all code browser for the Git plugin I'll post a PR soon. 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-28401) Move disable/enable button to sidepanel
Title: Message Title Oliver Gondža started work on JENKINS-28401 Change By: Oliver Gondža Status: Open In Progress 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] [cloudfoundry-plugin] (JENKINS-28210) FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype
Title: Message Title Aidan Killeen edited a comment on JENKINS-28210 Re: FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype Hi, I have experienced an almost identical error. A HelloWorld web application that has a single index.jsp page. It deploys properly using cf push. The job fails in Jenkins and this is the console output:[JENKINS] Archiving /home/smartretail/.jenkins/jobs/HelloWorldWeb/workspace/pom.xml to ie.huawei.helloworld/HelloWorldWeb/0.0.1-SNAPSHOT/HelloWorldWeb-0.0.1-SNAPSHOT.pom[JENKINS] Archiving /home/smartretail/.jenkins/jobs/HelloWorldWeb/workspace/target/HelloWorldWeb.war to ie.huawei.helloworld/HelloWorldWeb/0.0.1-SNAPSHOT/HelloWorldWeb-0.0.1-SNAPSHOT.warchannel stoppedPushing HelloWorldWeb app to http://api.117.78.6.213.xip.ioApp already exists, resetting.App deleted.Creating new app.Pushing app bits.Starting application.FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtypejava.util.ServiceConfigurationError: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype at java.util.ServiceLoader.fail(ServiceLoader.java:239) at java.util.ServiceLoader.access$300(ServiceLoader.java:185) at java.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:376) at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:404) at java.util.ServiceLoader$1.next(ServiceLoader.java:480) at javax.websocket.ContainerProvider.getWebSocketContainer(ContainerProvider.java:43) at org.cloudfoundry.client.lib.rest.LoggregatorClient.connectToLoggregator(LoggregatorClient.java:65) at org.cloudfoundry.client.lib.rest.CloudControllerClientImpl.streamLoggregatorLogs(CloudControllerClientImpl.java:2040) at org.cloudfoundry.client.lib.rest.CloudControllerClientImpl.streamLogs(CloudControllerClientImpl.java:244) at org.cloudfoundry.client.lib.CloudFoundryClient.streamLogs(CloudFoundryClient.java:356) at com.activestate.cloudfoundryjenkins.CloudFoundryPushPublisher.printStagingLogs(CloudFoundryPushPublisher.java:372) at com.activestate.cloudfoundryjenkins.CloudFoundryPushPublisher.processOneApp(CloudFoundryPushPublisher.java:222) at com.activestate.cloudfoundryjenkins.CloudFoundryPushPublisher.perform(CloudFoundryPushPublisher.java:119) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:721) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1037) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:670) at hudson.model.Run.execute(Run.java:1766) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374)Finished: FAILUREThe app is created but doesn't start.This is a company internal cloud foundry implementation rather than the pivotal one but cf push and the cf plugin for eclipse can both deploy this project while the jenkins cf plugin fails.I am using upgraded to Jenkins 1. 613 from 1. 610 and to no avail. And am using tomcat 7.0.47If I can supply more info I would be happy to do so.best regardsAidan
[JIRA] [fitnesse-plugin] (JENKINS-27936) When few FitNesse test results being published in a single job they renamed into Summary
Title: Message Title Serge Zukov commented on JENKINS-27936 Re: When few FitNesse test results being published in a single job they renamed into Summary Apparently publishing multiple test results under a single build using plugin 1.12 is broken. If you publish two XML files then you will have two SUMMARY entries in FitNesse result with exact same content under each of the summaries. I believe the latest published XML takes precedence. I increased priority from minor to 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] [job-dsl-plugin] (JENKINS-28405) Add support for all code browser for the Git plugin
Title: Message Title Jean-Philippe BOLATRE commented on JENKINS-28405 Re: Add support for all code browser for the Git plugin PR submitted 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-27708) Concurrent build limits not honored on Jenkins 1.607
Title: Message Title stephenconnolly assigned an issue to Oleg Nenashev This is fundamentally an issue in t-c-b-p making incorrect assumptions Jenkins / JENKINS-27708 Concurrent build limits not honored on Jenkins 1.607 Change By: stephenconnolly Assignee: stephenconnolly Oleg Nenashev 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-28093) 404 on jenkins.plugins.nodejs.tools.NodeJSInstaller.json.html
Title: Message Title Jesse Glick commented on JENKINS-28093 Re: 404 on jenkins.plugins.nodejs.tools.NodeJSInstaller.json.html Ireneusz Makowski I think your issue is unrelated and should not be discussed here. Anyway if you see a problem using the CloudBees update center because you are a CloudBees customer then you should file a support ticket 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] [core] (JENKINS-28384) NPE from LoadStatistics$LoadStatisticsSnapshot$Builder.with
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-28384 NPE from LoadStatistics$LoadStatisticsSnapshot$Builder.with Change By: Jesse Glick Labels: lts 1.609.1 - candidate fixed queue regression 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] [workflow-plugin] (JENKINS-28392) Ability to evaluate a script in the repository where the workflow script is executed from
Title: Message Title Jesse Glick resolved as Won't Fix Using CpsScmFlowDefinition? Yes just check out the repository and use load. (Or in such a case it probably makes more sense to use plain CpsFlowDefinition to begin with, so there is only one checkout.) Jenkins / JENKINS-28392 Ability to evaluate a script in the repository where the workflow script is executed from Change By: Jesse Glick Status: Open Resolved Resolution: Won't Fix 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] [workflow-plugin] (JENKINS-28392) Ability to evaluate a script in the repository where the workflow script is executed from
Title: Message Title Jesse Glick commented on JENKINS-28392 Re: Ability to evaluate a script in the repository where the workflow script is executed from (In the longer term it is likely cps-global-lib will be expanded to allow external SCM sources.) 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] [email-ext-plugin] (JENKINS-28357) Cannot use Jelly Template after recent 2.40 fix
Title: Message Title Jon Starbird commented on JENKINS-28357 Re: Cannot use Jelly Template after recent 2.40 fix I'm not sure where to go next either. Unfortunately company policy prevents me from sharing desktop to an outside entity. I can provide any additional info you think might help. Java version is 1.7, OS is recently updated - like in the last 2 months, do you want a list of all the other plugins? One question, you mentioned before that 2.40 was having the issue of needing the extension but that was for only Groovy, correct? Just wondering why my other system running 2.40 and was never upgraded to 2.40.1, doesn't see 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] [email-ext-plugin] (JENKINS-28402) Email-ext plugin 2.40.2 warns of a circular dependency error
Title: Message Title Alex Earl updated an issue Jenkins / JENKINS-28402 Email-ext plugin 2.40.2 warns of a circular dependency error If you are willing, would you try this version of the plugin? You'd have to install via the advanced tab in the plugin manager. Change By: Alex Earl Attachment: email-ext.hpi 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-28364) Polling does not work concurrently
Title: Message Title Jesse Glick resolved as Not A Defect Max # of concurrent polling in global configuration. If this does not work provide a thread dump or test case to reproduce. Jenkins / JENKINS-28364 Polling does not work concurrently Change By: Jesse Glick Status: Reopened Resolved Resolution: Not A Defect 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] [email-ext-plugin] (JENKINS-28357) Cannot use Jelly Template after recent 2.40 fix
Title: Message Title Alex Earl commented on JENKINS-28357 Re: Cannot use Jelly Template after recent 2.40 fix Yes, there was a change that went into 2.40 that would have caused the issue for either Jelly or Groovy. The fix went into 2.40.1. I decompiled the plugin file you uploaded, and the code is correct, it wouldn't require the .jelly to be added at the end, so I don't know how it's causing you an issue, unless somehow your plugin versions are showing up incorrectly, but I don't know how that is possible either. Are you running Jenkins in Tomcat or anything like that, or just as java -jar jenkins.war? 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] [email-ext-plugin] (JENKINS-28357) Cannot use Jelly Template after recent 2.40 fix
Title: Message Title Jon Starbird commented on JENKINS-28357 Re: Cannot use Jelly Template after recent 2.40 fix It's running as java -jar . Interestingly on both of these machines I was no longer getting the Upgrade message for Jenkins itself within Jenkins for this last update to 1.596.2 so I had to manually download the war files and upgrade that way. After that I upgraded all the plugins that needed upgrading, but I did that the normal way from within Jenkins. My point is that the upgrade to 2.40 happened at the time I did that. No idea what connection could be there but just wanted to mention it since it was an odd situation for the Upgrade notice to not show up in Jenkins. 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 Fernando Boaglio commented on JENKINS-23120 Re: FATAL: hudson.remoting.RequestAbortedException on Windows Slaves Hello, After upgrading to Jenkins 1.613 I got this error on all my Windows 2003/2008 slaves (64bits). They were running JDK 1.6 (32 bits). I moved up to JDK 1.8.0 (64 bits) and updated the jenkins-slave.xml to the new path, restarted the Jenkins Service and everything went 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] [email-ext-plugin] (JENKINS-28357) Cannot use Jelly Template after recent 2.40 fix
Title: Message Title Alex Earl commented on JENKINS-28357 Re: Cannot use Jelly Template after recent 2.40 fix Wait, I think I misunderstood something, is the file named mod1.template.jelly on the file system itself? 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] [email-ext-plugin] (JENKINS-28357) Cannot use Jelly Template after recent 2.40 fix
Title: Message Title
Jon Starbird commented on JENKINS-28357
Re: Cannot use Jelly Template after recent 2.40 fix
Yes. Then I was entering in the email settings as $ {JELLY_SCRIPT, template="mod1.template"}
until I updated to 2.40.1 but the file in email-templates folder has always had the full name with extension.
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] [email-ext-plugin] (JENKINS-28357) Cannot use Jelly Template after recent 2.40 fix
Title: Message Title Alex Earl commented on JENKINS-28357 Re: Cannot use Jelly Template after recent 2.40 fix Ok, I had misunderstood that part. I know why this is happening and can reproduce the problem and should have a fix soon. Sorry for the runaround! 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] [credentials-plugin] (JENKINS-28407) Create Credentials through CLI
Title: Message Title Steven Christou created an issue Jenkins / JENKINS-28407 Create Credentials through CLI Issue Type: Improvement Assignee: stephenconnolly Components: credentials-plugin Created: 14/May/15 5:36 PM Priority: Minor Reporter: Steven Christou Credentials plugin should have a CLI(or rest api) operation to create credentials. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [email-ext-plugin] (JENKINS-28357) Cannot use Jelly Template after recent 2.40 fix
Title: Message Title Jon Starbird commented on JENKINS-28357 Re: Cannot use Jelly Template after recent 2.40 fix No problem. Glad it got figured out. 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.
