[JIRA] (JENKINS-36135) cannot get CHANGES BUILD_LOG BUILD_STATUS variables' value
Title: Message Title David van Laatum closed an issue as Cannot Reproduce Closing due to no response Jenkins / JENKINS-36135 cannot get CHANGES BUILD_LOG BUILD_STATUS variables' value Change By: David van Laatum Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-36572) Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build
Title: Message Title David van Laatum assigned an issue to Alex Earl Jenkins / JENKINS-36572 Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build Change By: David van Laatum Assignee: David van Laatum Alex Earl Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36572) Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build
Title: Message Title David van Laatum commented on JENKINS-36572 Re: Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build I have just attempted to replicate without success (using git scm). Based on the screen shots I assume you just have the default triggers configured under advanced? But after some hunting the problem is more likely to be in the token-macro plugin. I had a look at the code but can't see anything obvious unless the p4 plugin is behaving drastically different to other SCM modules. Alex Earl any thoughts? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36572) Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build
Title: Message Title David van Laatum updated an issue Jenkins / JENKINS-36572 Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build Change By: David van Laatum Component/s: token-macro-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27084) SVN authentication fails using subversion plugin v.2.5
Title: Message Title
Ilguiz Latypov edited a comment on JENKINS-27084
Re: SVN authentication fails using subversion plugin v.2.5
Setting the svnkit.http.methods property to Basic in both the master and the slave did not make a difference for me. The source code of svnkit authentication looks like a maze of protocols, managers and special cases. So I followed someone else's work-around by setting the Jenkins project's SCM to None and using the Cygwin's svn command in the first build step to check out the code. I had to add "--username USER --password PASSWORD" in a one-off invocation of the job to get svn store the credentials in the Jenkins agent's home.{code:none}set svn_opts=--non-interactive --trust-server-cert-failures unknown-ca,cn-mismatch,expiredif exist .svn\nul ( %cygbinslash%svn.exe update %svn_opts%) else (%cygbinslash%svn.exe co %svn_opts% https://SERVER:PORT/svn/REPO/trunk/DIR .){code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27084) SVN authentication fails using subversion plugin v.2.5
Title: Message Title Ilguiz Latypov commented on JENKINS-27084 Re: SVN authentication fails using subversion plugin v.2.5 The source code of svnkit authentication looks like a maze of protocols, managers and special cases. So I followed someone else's work-around by setting the Jenkins project's SCM to None and using the Cygwin's svn command in the first build step to check out the code. I had to add "--username USER --password PASSWORD" in a one-off invocation of the job to get svn store the credentials in the Jenkins agent's home. set svn_opts=--non-interactive --trust-server-cert-failures unknown-ca,cn-mismatch,expired if exist .svn\nul ( %cygbinslash%svn.exe update %svn_opts% ) else ( %cygbinslash%svn.exe co %svn_opts% https://SERVER:PORT/svn/REPO/trunk/DIR . ) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36733) Performance Plugin upload failures
Title: Message Title Seshu Babu nagalla created an issue Jenkins / JENKINS-36733 Performance Plugin upload failures Issue Type: Bug Assignee: Andrey Pokhilko Components: performance-plugin Created: 2016/Jul/16 4:08 AM Environment: Jenkins Version : 2.7.1 Plugin : Performance Plugin Version :1.14 Priority: Minor Reporter: Seshu Babu nagalla Hi Download the performance plugin and trying to import the plugin through upload plugin option . The upload is failed java.io.IOException: Failed to dynamically deploy this plugin at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1867) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1624) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110) at java.lang.Thread.run(Thread.java:745) Caused by: java.util.zip.ZipException: error in opening zip file at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.(ZipFile.java:220) at java.util.zip.ZipFile.(ZipFile.java:150) at java.util.jar.JarFile.(JarFile.java:166) at java.util.jar.JarFile.(JarFile.java:145) at hudson.ClassicPluginStrategy.getShortName(ClassicPluginStrategy.java:114) at hudson.PluginManager.dynamicLoad(PluginManager.java:787) at hudson.PluginManager.dynamicLoad(PluginManager.java:775) at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1863
[JIRA] (JENKINS-30821) Include comment text as an environmental variable in comment-added Gerrit trigger event
Title: Message Title Teemu Murtola resolved as Fixed Merged in https://github.com/jenkinsci/gerrit-trigger-plugin/pull/295 Jenkins / JENKINS-30821 Include comment text as an environmental variable in comment-added Gerrit trigger event Change By: Teemu Murtola Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
[JIRA] (JENKINS-30821) Include comment text as an environmental variable in comment-added Gerrit trigger event
Title: Message Title Teemu Murtola assigned an issue to Teemu Murtola Jenkins / JENKINS-30821 Include comment text as an environmental variable in comment-added Gerrit trigger event Change By: Teemu Murtola Assignee: rsandell Teemu Murtola Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36732) Timestamps in Build History widget (BuildTimelineWidget) is wrong
Title: Message Title ikedam commented on JENKINS-36732 Re: Timestamps in Build History widget (BuildTimelineWidget) is wrong https://github.com/jenkinsci/jenkins/pull/2460 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36732) Timestamps in Build History widget (BuildTimelineWidget) is wrong
Title: Message Title ikedam started work on JENKINS-36732 Change By: ikedam Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34309) git-client-plugin: StringIndexOutOfBoundsException when parsing branches
Title: Message Title Mark Waite resolved as Fixed Fixed in git client plugin 1.19.7 released 15 Jul 2016 Jenkins / JENKINS-34309 git-client-plugin: StringIndexOutOfBoundsException when parsing branches Change By: Mark Waite Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-36255) git-client-plugin doesn’t work under NixOS
Title: Message Title Mark Waite resolved as Fixed Fixed in git client plugin 1.19.7, 15 Jul 2016 Jenkins / JENKINS-36255 git-client-plugin doesn’t work under NixOS Change By: Mark Waite Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26895) Exception if Dashboard View plugin is not installed
Title: Message Title Leandro Kersting de Freitas commented on JENKINS-26895 Re: Exception if Dashboard View plugin is not installed +1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36732) Timestamps in Build History widget (BuildTimelineWidget) is wrong
Title: Message Title ikedam created an issue Jenkins / JENKINS-36732 Timestamps in Build History widget (BuildTimelineWidget) is wrong Issue Type: Bug Assignee: ikedam Attachments: Screen Shot 2016-07-16 at 11.12.07.png, Screen Shot 2016-07-16 at 11.12.16.png Components: core Created: 2016/Jul/16 2:32 AM Environment: Jenkins 2.17 Priority: Minor Reporter: ikedam Consider a following build: (Added comments) admin 1 1 146863080 146863440 SUCCESS 180 windows-31j false C:\Users\ikedam\.jenkins\workspace\test 2.13 This means: Scheduled at 2016-07-16 10:00:00+0900 Started at 2016-07-16 11:00:00+0900 Finished at 2016-07-16 11:30:00+0900 for this build, `BuildTimelineWidget` in the build history page displays a build as "Sta, 16 Jul 2016 10:00:00 - Sat, 16 Jul 2016 10:30:00", which is completely wrong.
[JIRA] (JENKINS-36502) compatibility with snipper generator
Title: Message Title Liam Newman commented on JENKINS-36502 Re: compatibility with snipper generator I'm working on a fix for this. It has to do with getting the databound paramters just right. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36731) Sorting results by column should be stable
Title: Message Title Richard created an issue Jenkins / JENKINS-36731 Sorting results by column should be stable Issue Type: Bug Assignee: Gregory Boissinot Components: cppcheck-plugin Created: 2016/Jul/16 12:35 AM Priority: Minor Reporter: Richard If I sort first by line, then by file, I should see all the results ordered by file first and line number second. Currently, the sorting isn't stable, so I can either sort by line number (useless across files), or I can sort by file with the line results in some random order by line number. A stable sort would make the table much more useful when there are many results as is the case when you first begin running cppcheck on a large code base. Add Comment
[JIRA] (JENKINS-34377) job-restrictions does not support Pipeline Plugin
Title: Message Title Oleg Nenashev commented on JENKINS-34377 Re: job-restrictions does not support Pipeline Plugin Dominik Ruf Actually this change can be solved by more or less hackish code in the plugin. Maybe upstream user retrieval works out of the box, but I'm not 100% sure. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36700) Steps open and close on load
Title: Message Title James Dumay commented on JENKINS-36700 Re: Steps open and close on load For #2, if there are zero steps add a "empty state" JDL component with text inside that says "There are no steps" We use the same pattern on the tests tab when there are no tests for the run Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36582) Developer can see the dashboard update in real time
Title: Message Title James Dumay commented on JENKINS-36582 Re: Developer can see the dashboard update in real time Not built should get grouped in with the failures Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35837) Developer can view the dashboard
Title: Message Title James Dumay commented on JENKINS-35837 Re: Developer can view the dashboard Display short name and full name via tooltip sounds good to me. Secondary sort by most recently run (in all cases you should see the most recent successful runs grouped together with the newest at the top) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36728) Pipeline job _class appears as BranchImpl
Title: Message Title Vivek Pandey edited a comment on JENKINS-36728 Re: Pipeline job _class appears as BranchImpl [~cliffmeyers] yes I know. This fix exactly fixes that problem . It was problem in general , not specific to Favorite alone. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36728) Pipeline job _class appears as BranchImpl
Title: Message Title Vivek Pandey commented on JENKINS-36728 Re: Pipeline job _class appears as BranchImpl Cliff Meyers yes I know. This fix exactly fixes that problem, Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36728) Pipeline job _class appears as BranchImpl
Title: Message Title Cliff Meyers commented on JENKINS-36728 Re: Pipeline job _class appears as BranchImpl Hey Vivek, I actually saw this in the /users/:userID/favorites API. Not sure if the root cause is the same as /pipelines/. Sorry if I was unclear on that when we originally chatted Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36730) Need to allow full sem versions like Nuget
Title: Message Title Jon Starbird created an issue Jenkins / JENKINS-36730 Need to allow full sem versions like Nuget Issue Type: Improvement Assignee: Andrew Sumner Components: inedo-proget-plugin Created: 2016/Jul/15 11:07 PM Priority: Blocker Reporter: Jon Starbird Need to allow version like Nuget with the pre-release tags. Only having one version of the package isn't useful if you use Proget for daily build artifact storage. Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-36717) FindBugs: Major issues are reported for the Jenkins core
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-36717 FindBugs: Major issues are reported for the Jenkins core Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36717) FindBugs: Major issues are reported for the Jenkins core
Title: Message Title Oleg Nenashev started work on JENKINS-36717 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35783) REST API must only be authenticated using JWT
Title: Message Title Vivek Pandey started work on JENKINS-35783 Change By: Vivek Pandey Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36728) Pipeline job _class appears as BranchImpl
Title: Message Title Vivek Pandey commented on JENKINS-36728 Re: Pipeline job _class appears as BranchImpl PR submitted https://github.com/jenkinsci/blueocean-plugin/pull/358 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36690) New Item doesn't show anything
Title: Message Title Oleg Nenashev commented on JENKINS-36690 Re: New Item doesn't show anything Yes, I can see the form. Works well in latest versions of Safari, Chrome and Mozilla. Which browser do you use? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36502) compatibility with snipper generator
Title: Message Title Liam Newman edited a comment on JENKINS-36502 Re: compatibility with snipper generator [~daspilker] This doesn wouldn 't effect a custom build steps step exposed via "org.jenkinsci.plugins.workflow.steps.AbstractStepDescriptorImpl", right? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36502) compatibility with snipper generator
Title: Message Title Liam Newman commented on JENKINS-36502 Re: compatibility with snipper generator Daniel Spilker This doesn't effect custom build steps exposed via "org.jenkinsci.plugins.workflow.steps.AbstractStepDescriptorImpl", right? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36587) Investigate: Split of BlueOcean Workflow Pipeline implementation in to it's own module
Title: Message Title Vivek Pandey commented on JENKINS-36587 Re: Investigate: Split of BlueOcean Workflow Pipeline implementation in to it's own module Michael Neale James Dumay Not sure if It's ready for PR yet. Can one of you try https://github.com/jenkinsci/blueocean-plugin/tree/task/JENKINS-36587, see if it works to your satisfaction or maybe have others look at it. Just in case something is broken that I missed during my testing. Also once we have this PR up, I would like to put hold on commit to blueocean-rest-impl otherwise merging in to this branch is going to be painful. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36729) Plugin update available page have stack overflow errors.
Title: Message Title Chuan He created an issue Jenkins / JENKINS-36729 Plugin update available page have stack overflow errors. Issue Type: Bug Assignee: Unassigned Attachments: stacktrace.txt Components: core Created: 2016/Jul/15 9:35 PM Environment: win2012R2 jenkins 1.588 Priority: Major Reporter: Chuan He in manage plugin page, update and available both have big oops demon face jenkins, with this huge stack trace (attached), and below that are actual context i expect to see on the page, of course i will not risk install anything now. Add Comment
[JIRA] (JENKINS-36728) Pipeline job _class appears as BranchImpl
Title: Message Title Vivek Pandey started work on JENKINS-36728 Change By: Vivek Pandey Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36728) Pipeline job _class appears as BranchImpl
Title: Message Title Vivek Pandey created an issue Jenkins / JENKINS-36728 Pipeline job _class appears as BranchImpl Issue Type: Bug Assignee: Vivek Pandey Components: blueocean-plugin Created: 2016/Jul/15 9:27 PM Priority: Minor Reporter: Vivek Pandey As reported by Cliff Meyers, .../pipelines/:id is returning _class with BranchImpl. This should be PipelineImpl. This can cause confusion in UI layer and pipeline might get treated as branches with current ongoing work. Add Comment This message
[JIRA] (JENKINS-36728) Pipeline job _class appears as BranchImpl
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-36728 Pipeline job _class appears as BranchImpl Change By: Vivek Pandey Sprint: 1.0-m11 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36711) JobDsl pipeline snippet generator produces invalid code
Title: Message Title Daniel Spilker closed an issue as Duplicate Jenkins / JENKINS-36711 JobDsl pipeline snippet generator produces invalid code Change By: Daniel Spilker Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36690) New Item doesn't show anything
Title: Message Title Nicolas de Marqué commented on JENKINS-36690 Re: New Item doesn't show anything For the security, i know and securize access when problem will corrected. For the page, i see the page, but it's a blank page whith just herder and footer. Can you see the form to add a new item ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36727) NullPointerException when using GitPublisher in post build actions
Title: Message Title Michael Fowler assigned an issue to Nicolas De Loof Jenkins / JENKINS-36727 NullPointerException when using GitPublisher in post build actions Change By: Michael Fowler Assignee: Nicolas De Loof Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31678) NullPointerException when using GitPublisher in release post build actions
Title: Message Title
Michael Fowler updated an issue
Jenkins / JENKINS-31678
NullPointerException when using GitPublisher in release post build actions
Change By:
Michael Fowler
Comment:
On Jenkins 1.625.1 with git plugin 2.5.2 on a multi branch project when trying to add the git publisher in the config screen:{code:java}javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:201) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:178) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:102) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:129) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at
[JIRA] (JENKINS-36727) NullPointerException when using GitPublisher in post build actions
Title: Message Title Michael Fowler updated an issue Jenkins / JENKINS-36727 NullPointerException when using GitPublisher in post build actions Change By: Michael Fowler Environment: On Jenkins 1. 638 625.1 with git - plugin 2. 4 5 . 0. 2 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36727) NullPointerException when using GitPublisher in post build actions
Title: Message Title
Michael Fowler updated an issue
Jenkins / JENKINS-36727
NullPointerException when using GitPublisher in post build actions
Change By:
Michael Fowler
On Jenkins 1.625.1 with git plugin 2.5.2 on a multi branch project when trying to add the git publisher in the config screen:{code:java}javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:201) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:178) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:102) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:129) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at
[JIRA] (JENKINS-36727) NullPointerException when using GitPublisher in post build actions
Title: Message Title Michael Fowler updated an issue Jenkins / JENKINS-36727 NullPointerException when using GitPublisher in post build actions Change By: Michael Fowler Environment: Debian Wheezy running Jenkins 1.638 with git-plugin 2.4.0. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36727) NullPointerException when using GitPublisher in post build actions
Title: Message Title Michael Fowler updated an issue Jenkins / JENKINS-36727 NullPointerException when using GitPublisher in post build actions Change By: Michael Fowler Configure a job to use the Jenkins release plugin and use the Git publisher as release step after a successful release build. Tick the checkbox "Push only If Build Succeeds". Then a release build failes with the following NullPointerException:FATAL: nulljava.lang.NullPointerException at hudson.plugins.git.GitPublisher.perform(GitPublisher.java:203) at hudson.plugins.release.ReleaseWrapper.executeBuildSteps(ReleaseWrapper.java:423) at hudson.plugins.release.ReleaseWrapper.access$300(ReleaseWrapper.java:99) at hudson.plugins.release.ReleaseWrapper$4.tearDown(ReleaseWrapper.java:370) at hudson.model.Build$BuildExecution.doRun(Build.java:173) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)This is caused by the null derefenced buildResult of AbstractBuild.getResult(). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36727) NullPointerException when using GitPublisher in post build actions
Title: Message Title Michael Fowler updated an issue Jenkins / JENKINS-36727 NullPointerException when using GitPublisher in post build actions Change By: Michael Fowler Labels: exception git plugin publisher Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36727) NullPointerException when using GitPublisher in post build actions
Title: Message Title Michael Fowler created an issue Jenkins / JENKINS-36727 NullPointerException when using GitPublisher in post build actions Issue Type: Bug Assignee: Unassigned Components: git-plugin Created: 2016/Jul/15 8:31 PM Environment: Debian Wheezy running Jenkins 1.638 with git-plugin 2.4.0. Labels: exception git plugin Priority: Major Reporter: Michael Fowler Configure a job to use the Jenkins release plugin and use the Git publisher as release step after a successful release build. Tick the checkbox "Push only If Build Succeeds". Then a release build failes with the following NullPointerException: FATAL: null java.lang.NullPointerException at hudson.plugins.git.GitPublisher.perform(GitPublisher.java:203) at hudson.plugins.release.ReleaseWrapper.executeBuildSteps(ReleaseWrapper.java:423) at hudson.plugins.release.ReleaseWrapper.access$300(ReleaseWrapper.java:99) at hudson.plugins.release.ReleaseWrapper$4.tearDown(ReleaseWrapper.java:370) at hudson.model.Build$BuildExecution.doRun(Build.java:173) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) This is caused by the null derefenced buildResult of AbstractBuild.getResult().
[JIRA] (JENKINS-31678) NullPointerException when using GitPublisher in release post build actions
Title: Message Title
Michael Fowler edited a comment on JENKINS-31678
Re: NullPointerException when using GitPublisher in release post build actions
On Jenkins 1.625.1 with git plugin 2.5.2 on a multi branch project when trying to add the git publisher in the config screen :{code:java}javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:201) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:178) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:102) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:129) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87){code}
[JIRA] (JENKINS-31678) NullPointerException when using GitPublisher in release post build actions
Title: Message Title Michael Fowler commented on JENKINS-31678 Re: NullPointerException when using GitPublisher in release post build actions On Jenkins 1.625.1 with git plugin 2.5.2 on a multi branch project: javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:201) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:178) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:102) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:129) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
[JIRA] (JENKINS-36549) Parameterized Trigger Plugin - doesn't pass parameters after upgrating jenkins to 2.7
Title: Message Title Kyle Nehring commented on JENKINS-36549 Re: Parameterized Trigger Plugin - doesn't pass parameters after upgrating jenkins to 2.7 This is from the SECURITY-170 update.. the current work around to fix this is add the system property to your java_opts -Dhudson.model.ParametersAction.keepUndefinedParameters=true https://wiki.jenkins-ci.org/display/JENKINS/Plugins+affected+by+fix+for+SECURITY-170 also looks like this plugin wont be fixed according to the page above. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36726) Plugin comments on subsequent successful builds
Title: Message Title Jay Kah assigned an issue to Radek Antoniuk Jenkins / JENKINS-36726 Plugin comments on subsequent successful builds Change By: Jay Kah Assignee: Radek Antoniuk Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36726) Plugin comments on subsequent successful builds
Title: Message Title Jay Kah created an issue Jenkins / JENKINS-36726 Plugin comments on subsequent successful builds Issue Type: Task Assignee: Unassigned Components: jira-plugin Created: 2016/Jul/15 7:39 PM Priority: Minor Reporter: Jay Kah My use case involves creating JIRA tickets for failed Jenkins builds, which the plugin handles correctly. However, when a subsequent build succeeds (and a comment is therefore posted to the ticket) the issue does not get closed, but instead is accumulating all further successful builds in comments. Is that the intended behavior? Is there a way to NOT create a comment when the build succeeds for the second time in a row? Thanks! Add Comment
[JIRA] (JENKINS-35837) Developer can view the dashboard
Title: Message Title Cliff Meyers commented on JENKINS-35837 Re: Developer can view the dashboard James Dumay Couple more q's: 1: should the full name be displayed after the organization name? Or just the name? Realize that if two jobs with the same name are in different folders, that part of the card will appear identical unless we show the full name. 2. beyond the status-based sorting from JENKINS-36582, should there be any secondary sort applied? Gets a little trickier to decide what to do if we include folders, too. If we really want to avoid showing full name, we could also show short name but offer full name via a tooltip. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23895) does not respect http_proxy variables
Title: Message Title Steven Proctor commented on JENKINS-23895 Re: does not respect http_proxy variables And looking at the Similar Issues link, there seem to be a few others that are there, one of which is even labeld core and remoting, and is resolved (https://issues.jenkins-ci.org/browse/JENKINS-32326). Would any of those help resolve this issue if it has been fixed in core and remoting? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23895) does not respect http_proxy variables
Title: Message Title
Steven Proctor commented on JENKINS-23895
Re: does not respect http_proxy variables
Is accessing Jenkin's environment variables not just the same as accessing any environment variable? System.out.println("http_proxy=" + env.get("http_proxy")); We would like to get this moved forward at work, and I have gotten some availability for now to help drive this forward. Is there any approach that you would need, or anything that I can do to help get this issue resolved? Thanks in advance! --Proctor
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36725) Not able to travese XML in pipeline project
Title: Message Title Smithesh Purushothaman created an issue Jenkins / JENKINS-36725 Not able to travese XML in pipeline project Issue Type: Bug Assignee: Sam Van Oort Attachments: node.docx Components: pipeline-stage-view-plugin Created: 2016/Jul/15 7:15 PM Priority: Minor Reporter: Smithesh Purushothaman Please see the attachment and kindly help Add Comment
[JIRA] (JENKINS-36509) 'Active Choices Reactive Reference Parameter' type variable is empty
Title: Message Title
Rick Liu commented on JENKINS-36509
Re: 'Active Choices Reactive Reference Parameter' type variable is empty
i found a solution to make it read-only using HTML
return "value\" value=\"${reactRefParam}\" class=\"setting-input\" type=\"text\" readonly>"
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36509) 'Active Choices Reactive Reference Parameter' type variable is empty
Title: Message Title
Rick Liu commented on JENKINS-36509
Re: 'Active Choices Reactive Reference Parameter' type variable is empty
Thanks~ This code is working. But is it possible to make the field to be READ-ONLY? This field is more like the conclusion field based upon other Active-Choice selections. It will display to inform the user's final selection, and it will be used inside the Jenkins build.
return "value\" value=\"${reactRefParam}\" class=\"setting-input\" type=\"text\">"
This code fulfills my requirement. It just after Active-Choice updates the field, the user might still accidentally changed the text.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36582) Developer can see the dashboard update in real time
Title: Message Title Cliff Meyers commented on JENKINS-36582 Re: Developer can see the dashboard update in real time James Dumay where should "NOT_BUILT" go? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36724) Branch indexing hangs
Title: Message Title Shauvik Roy Choudhary created an issue Jenkins / JENKINS-36724 Branch indexing hangs Issue Type: Bug Assignee: Jesse Glick Attachments: branch_indexing_hangs.png Components: github-branch-source-plugin Created: 2016/Jul/15 6:07 PM Priority: Minor Reporter: Shauvik Roy Choudhary We've been noticing problems with our jenkins branch indexing, which seems to hang from several minutes to hours. We see a lot of Branch indexing jobs on the queue and in the Branch indexing log itself, it shows (what we believe) a complete log with a loading spinner gif at the end. Not sure what the error is. Would be happy to dig in and provide more info if needed. Jenkins version: 2.7.1 Installed Plugins: Ant Plugin - 1.3 Authentication Tokens API Plugin - 1.3 Branch API Plugin - 1.10 build timeout plugin - 1.17 CloudBees Docker Pipeline - 1.6 Credentials Plugin - 2.1.4 CVS Plug-in - 2.12 Docker Commons Plugin - 1.4.0 Durable Task Plugin - 1.11 External Monitor Job Type Plugin - 1.5 Folders Plugin - 5.12 Git client plugin - 1.19.6 Git plugin - 2.5.2 GIT server Plugin - 1.7 GitHub API Plugin - 1.76 GitHub Branch Source Plugin - 1.8.1 GitHub Organization Folder Plugin - 1.3 GitHub plugin - 1.19.2 Google Login Plugin - 1.2.1 Icon Shim Plugin - 2.0.3 Javadoc Plugin - 1.4 _javascript_ GUI Lib: ACE Editor bundle plugin - 1.1 _javascript_ GUI Lib: Handlebars bundle plugin - 1.1.1 _javascript_ GUI Lib: jQuery bundles (jQuery and jQuery UI) plugin - 1.2.1 _javascript_ GUI Lib: Moment.js bundle plugin - 1.1.1 JUnit Plugin - 1.15 LDAP Plugin - 1.12 Mailer Plugin - 1.17 MapDB API Plugin - 1.0.9.0 Matrix Authorization Strategy Plugin - 1.4 Matrix Project Plugin - 1.7.1 Maven Integration plugin - 2.13 OWASP Markup Formatter Plugin - 1.5 PAM Authentication plugin - 1.3 Pipeline -
[JIRA] (JENKINS-36723) Snapshots are not unique
Title: Message Title Daniel Martin created an issue Jenkins / JENKINS-36723 Snapshots are not unique Issue Type: Task Assignee: Deluan Quintão Components: rtc-plugin Created: 2016/Jul/15 5:44 PM Labels: plugins Priority: Minor Reporter: Daniel Martin When using the rtc workspace to look for changes in your pipeline the snapshot is simply the Jenkins build number. This means that the snapshots are not unique with an instance of RTC. The bug makes it difficult to promote a snapshot to a stream at the end of your pipeline, unless you retrieve the alias. The snapshot should include the jenkins job name to help ensure no two snapshots are exactly the same Add Comment
[JIRA] (JENKINS-31939) The top value is better to be chosed by default of to have such option
Title: Message Title Boguslaw Klimas started work on JENKINS-31939 Change By: Boguslaw Klimas Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31939) The top value is better to be chosed by default of to have such option
Title: Message Title Boguslaw Klimas updated JENKINS-31939 Jenkins / JENKINS-31939 The top value is better to be chosed by default of to have such option Change By: Boguslaw Klimas Status: Reopened Open Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35314) p4 Plugin does not trigger Pipeline builds
Title: Message Title Kyle Mott commented on JENKINS-35314 Re: p4 Plugin does not trigger Pipeline builds I think this can be resolved. I did some tweaks to my config, and it appears to be working correctly now. The main adjustment I did was instead of configuring the base workspace as the source for the pipeline script from SCM, I pointed it directly at the Jenkins file so instead of this: //depot/project1/tip/... //client_workspace_project1/... It ended up looking like this: //depot/project1/tip/Jenkinsfile... //client_workspace_project1/Jenkinsfile... I also changed the Populate options to "Forced clean & sync", and added a few polling build filters for sub-projects checkins I didn't want to trigger the main parent build. This seems to work now as I would expect, and is quite smooth. Thanks for the pointers Paul Allen. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving
[JIRA] (JENKINS-36716) Automatic FindBugs Static Analysis in the Jenkins core
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-36716 Automatic FindBugs Static Analysis in the Jenkins core Change By: Oleg Nenashev Summary: Automatic FindBugs Static Analysis in the Jenkins core Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36673) MissingMethodException When Calling Pipeline Library Function
Title: Message Title Mark Bidewell updated an issue Jenkins / JENKINS-36673 MissingMethodException When Calling Pipeline Library Function Change By: Mark Bidewell Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36721) Create a Jenkins FindBugs Detectors library with specific checks
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-36721 Create a Jenkins FindBugs Detectors library with specific checks Change By: Oleg Nenashev The library should contain Jenkins-specific checks. It would be great to start from several critical cases we commonly experience in Jenkins-specific codebase.TODO: define the final listExamples:* Definition of extensionPoint implementation without @Extension in the class/descriptor* Usage of the Restricted method coming from the external library* Usage of do*() methods in the code without RequirePost* Nice2have: Method may return null, but there is no CheckForNull annotation* ... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36721) Create a Jenkins FindBugs Detectors library with specific checks
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-36721 Create a Jenkins FindBugs Detectors library with specific checks Change By: Oleg Nenashev Issue Type: Task New Feature Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36721) Create a Jenkins FindBugs Detectors library with specific checks
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-36721 Create a Jenkins FindBugs Detectors library with specific checks Change By: Oleg Nenashev Summary: Create a Jenkins FindBugs Detectors library with specific checks Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36722) Include Jenkins FindBugs Detectors lib into the core build process
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-36722 Include Jenkins FindBugs Detectors lib into the core build process Issue Type: Improvement Assignee: Unassigned Components: core Created: 2016/Jul/15 4:48 PM Priority: Minor Reporter: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the
[JIRA] (JENKINS-36721) Create a Jenkins FindBugs Detectors library
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-36721 Create a Jenkins FindBugs Detectors library Issue Type: Task Assignee: Unassigned Components: core Created: 2016/Jul/15 4:47 PM Priority: Minor Reporter: Oleg Nenashev The library should contain Jenkins-specific checks. It would be great to start from several critical cases we commonly experience in Jenkins-specific codebase. TODO: define the final list Examples: Definition of extensionPoint implementation without @Extension in the class/descriptor Usage of the Restricted method coming from the external library Usage of do*() methods in the code without RequirePost ... Add Comment
[JIRA] (JENKINS-36691) Pipeline project giving error for sample script.
Title: Message Title Sam Van Oort closed an issue as Not A Defect Sure thing, glad to help. Jenkins / JENKINS-36691 Pipeline project giving error for sample script. Change By: Sam Van Oort Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36720) Investigate/cleanup medium-severity FindBugs issues in the Jenkins core
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-36720 Investigate/cleanup medium-severity FindBugs issues in the Jenkins core Issue Type: Task Assignee: Unassigned Components: core Created: 2016/Jul/15 4:39 PM Priority: Minor Reporter: Oleg Nenashev Currently FindBugs settings ignore all medium-priority issues. It's bad, because this level contains NPE checks and other serious issues. TODOs: Remove filtering of medium-priority issues Investigate error codes, add low-important once to the ignore list Fix important issues Add Comment
[JIRA] (JENKINS-36549) Parameterized Trigger Plugin - doesn't pass parameters after upgrating jenkins to 2.7
Title: Message Title Kyle Nehring commented on JENKINS-36549 Re: Parameterized Trigger Plugin - doesn't pass parameters after upgrating jenkins to 2.7 I have exactly the same problem, just recently upgraded from 1.625.2 to v2.9 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36719) Enable FindBugs reporting in the Jenkins core PR builder
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-36719 Enable FindBugs reporting in the Jenkins core PR builder Issue Type: Improvement Assignee: Unassigned Components: core Created: 2016/Jul/15 4:34 PM Priority: Minor Reporter: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups
[JIRA] (JENKINS-36718) FindBugs: DM_DEFAULT_ENCODING issues in the core
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-36718 FindBugs: DM_DEFAULT_ENCODING issues in the core Change By: Oleg Nenashev Summary: FindBugs: DM_DEFAULT_ENCODING issues in the core Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36718) FindBugs: DM_DEFAULT_ENCODING issues
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-36718 FindBugs: DM_DEFAULT_ENCODING issues Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Jul/15 4:33 PM Priority: Minor Reporter: Oleg Nenashev FindBugs records about 50 DM_DEFAULT_ENCODING issues in different core components. These issues are commonly safe, but it would be great to cleanup them Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36715) Jenkins Core build should invoke FindBugs by default
Title: Message Title Oleg Nenashev started work on JENKINS-36715 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36717) FindBugs: Major issues are reported for the Jenkins core
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-36717 FindBugs: Major issues are reported for the Jenkins core Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Jul/15 4:32 PM Priority: Major Reporter: Oleg Nenashev It would be great to fix the issues and to enable FindBugs by default after it. [INFO] BugInstance size is 26 [INFO] Error size is 0 [INFO] Total bugs: 26 [INFO] Possible null pointer dereference of ExtensionList.jenkins in hudson.DescriptorExtensionList.load() [hudson.DescriptorExtensionList, hudson.DescriptorExtensionList] Dereferenced at DescriptorExtensionList.java:[line 185]Known null at DescriptorExtensionList.java:[line 185] NP_NULL_ON_SOME_PATH [INFO] hudson.PluginManager.addDependencies(URL, String, Set) is or uses a map or set of URLs, which can be a performance hog [hudson.PluginManager] At PluginManager.java:[lines 631-663] DMI_COLLECTION_OF_URLS [INFO] hudson.PluginManager.addDependencies(URL, String, Set) is or uses a map or set of URLs, which can be a performance hog [hudson.PluginManager] At PluginManager.java:[line 631] DMI_COLLECTION_OF_URLS [INFO] hudson.PluginManager.loadPluginsFromWar(String, FilenameFilter) is or uses a map or set of URLs, which can be a performance hog [hudson.PluginManager, hudson.PluginManager] At PluginManager.java:[line 599]Another occurrence at PluginManager.java:[line 621] DMI_COLLECTION_OF_URLS [INFO] hudson.PluginManager.loadPluginsFromWar(String, FilenameFilter) is or uses a map or set of URLs, which can be a performance hog [hudson.PluginManager] At PluginManager.java:[line 612] DMI_COLLECTION_OF_URLS [INFO] hudson.PluginManager.loadPluginsFromWar(String, FilenameFilter) is or uses a map or set of URLs, which can be a performance hog [hudson.PluginManager] At PluginManager.java:[line 612]
[JIRA] (JENKINS-36716) Automatic Static Analysis in the Jenkins core
Title: Message Title Oleg Nenashev started work on JENKINS-36716 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36716) Automatic Static Analysis in the Jenkins core
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-36716 Automatic Static Analysis in the Jenkins core Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36716) Automatic Static Analysis in the Jenkins core
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-36716 Automatic Static Analysis in the Jenkins core Issue Type: Epic Assignee: Unassigned Components: core Created: 2016/Jul/15 4:29 PM Priority: Minor Reporter: Oleg Nenashev Jenkins core lacks automatic code quality checks. It would be great to fix it. FindBugs automation would be a great first baby step. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36715) Jenkins Core build should invoke FindBugs by default
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-36715 Jenkins Core build should invoke FindBugs by default Issue Type: Improvement Assignee: Unassigned Components: core Created: 2016/Jul/15 4:27 PM Priority: Major Reporter: Oleg Nenashev In the Jenkins core we suffer from the missing automatic FindBugs run in pull requests. It should be enabled at least to discover serious issues being introduced by PRs. I would like to enable automatic runs and to enable generation/reporting of FindBugs issues like we do in plugins. Add Comment
[JIRA] (JENKINS-36715) Jenkins Core build should invoke FindBugs by default
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-36715 Jenkins Core build should invoke FindBugs by default Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26259) hudson.util.IOException2: Could not copy slave.jar into '/home/jenkins-build' on slave
Title: Message Title Pravin Mundra commented on JENKINS-26259 Re: hudson.util.IOException2: Could not copy slave.jar into '/home/jenkins-build' on slave I faced the similar issue and lack of space was the actual problem. I had to delete the old workspaces created under /apps/jenkins/workspace and then it worked. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34377) job-restrictions does not support Pipeline Plugin
Title: Message Title Dominik Ruf commented on JENKINS-34377 Re: job-restrictions does not support Pipeline Plugin I looked at at code (AbstractUserCauseRestriction.java canTake(Queue.BuildableItem item)) and the problem is this : In case the task of the BuildableItem object is of type org.jenkinsci.plugins.workflow.support.steps.ExecutorStepExecution getActions() returns an empty list. AFAIS this problem can not be solved without changes in the workflow/pipeline plugin. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35837) Developer can view the dashboard
Title: Message Title Cliff Meyers updated an issue Jenkins / JENKINS-35837 Developer can view the dashboard Change By: Cliff Meyers Summary: Developer can view the dashboard and see the cards update in realtime Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34377) job-restrictions does not support Pipeline Plugin
Title: Message Title Dominik Ruf updated an issue Jenkins / JENKINS-34377 job-restrictions does not support Pipeline Plugin Change By: Dominik Ruf Component/s: workflow-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36689) Windows Power Shell - Trying to execute SQL server Query using Windows Power shell Plugin and its throwing error as
Title: Message Title Vamsi Kalyan assigned an issue to luther orea Can you please assign it to respective user as this is unassigned from yesterday Jenkins / JENKINS-36689 Windows Power Shell - Trying to execute SQL server Query using Windows Power shell Plugin and its throwing error as Change By: Vamsi Kalyan Assignee: luther orea Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36712) Test Results screen throws "unique keys" error
Title: Message Title Cliff Meyers commented on JENKINS-36712 Re: Test Results screen throws "unique keys" error UI behaves correctly when all tests are passing, except for error. Not sure how it will respond they're failing. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36712) Test Results screen throws "unique keys" error
Title: Message Title
Cliff Meyers updated an issue
Jenkins / JENKINS-36712
Test Results screen throws "unique keys" error
Change By:
Cliff Meyers
To repro:# Navigate to a pipeline that publishes test results (I used the JDL)# Choose a Run# Select the "Tests" tab Should be able to open and view test results, instead console error is thrown and results cannot be expanded. Each child in an array or iterator should have a unique "key" prop. Check the render method of `TestResult`. See https://fb.me/react-warning-keys for more information.JSON from endpoint:{code}"_class": "hudson.tasks.junit.TestResult","testActions": [],"duration": 0.151,"empty": false,"failCount": 0,"passCount": 26,"skipCount": 0,"suites": [{"cases": [{"testActions": [],"age": 0,"className": "PhantomJS_2_1_1_(Linux_0_0_0).CommitHash","duration": 0.049,"errorDetails": null,"errorStackTrace": null,"failedSince": 0,"name": "CommitHash renders dash with no data","skipped": false,"skippedMessage": null,"status": "PASSED","stderr": "","stdout": "\n\n\n "}, {"testActions": [],"age": 0,"className": "PhantomJS_2_1_1_(Linux_0_0_0).CommitHash","duration": 0.003,"errorDetails": null,"errorStackTrace": null,"failedSince": 0,"name": "CommitHash renders dash with invalid data","skipped": false,"skippedMessage": null,"status": "PASSED","stderr": "","stdout": "\n\n\n "}, {"testActions": [],"age": 0,"className": "PhantomJS_2_1_1_(Linux_0_0_0).CommitHash","duration": 0.006,"errorDetails": null,"errorStackTrace": null,"failedSince": 0,"name": "CommitHash renders sha-1 char hash with proper length","skipped": false,"skippedMessage": null,"status": "PASSED","stderr": "","stdout": "\n\n\n "}, {"testActions": [],"age": 0,"className": "PhantomJS_2_1_1_(Linux_0_0_0).FileSize","duration": 0.006,"errorDetails": null,"errorStackTrace": null,"failedSince": 0,"name": "FileSize renders dash with no data","skipped": false,"skippedMessage": null,"status": "PASSED","stderr": "","stdout": "\n\n\n "}, {"testActions": [],"age": 0,"className": "PhantomJS_2_1_1_(Linux_0_0_0).FileSize","duration": 0.003,"errorDetails": null,"errorStackTrace": null,"failedSince": 0,"name": "FileSize renders dash with invalid data","skipped": false,"skippedMessage":
[JIRA] (JENKINS-36689) Windows Power Shell - Trying to execute SQL server Query using Windows Power shell Plugin and its throwing error as
Title: Message Title Vamsi Kalyan started work on JENKINS-36689 Change By: Vamsi Kalyan Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36689) Windows Power Shell - Trying to execute SQL server Query using Windows Power shell Plugin and its throwing error as
Title: Message Title Vamsi Kalyan commented on JENKINS-36689 Re: Windows Power Shell - Trying to execute SQL server Query using Windows Power shell Plugin and its throwing error as But if i execute same in windows powershell command prompt its working fine Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36710) SVN authorization issue
Title: Message Title Rafael Pestano resolved as Fixed fixed by https://github.com/jenkinsci/last-changes-plugin/commit/8a5d8ecc2e6c367d0fe7e959099c42f9f927a972 Jenkins / JENKINS-36710 SVN authorization issue Change By: Rafael Pestano Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-36714) MemoryMonitor No suitable implementation found: os.name=HP-UX os.arch=IA64N sun.arch.data.model=32
Title: Message Title Oliver Gondža created an issue Jenkins / JENKINS-36714 MemoryMonitor No suitable implementation found: os.name=HP-UX os.arch=IA64N sun.arch.data.model=32 Issue Type: Improvement Assignee: Unassigned Components: core Created: 2016/Jul/15 3:27 PM Priority: Minor Reporter: Oliver Gondža java.util.concurrent.ExecutionException: java.io.IOException: No suitable implementation found: os.name=HP-UX os.arch=IA64N sun.arch.data.model=32 at hudson.remoting.Channel$2.adapt(Channel.java:810) at hudson.remoting.Channel$2.adapt(Channel.java:805) at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59) at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMonitorDescriptor.java:97) at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:302) Caused by: java.io.IOException: No suitable implementation found: os.name=HP-UX os.arch=IA64N sun.arch.data.model=32 at org.jvnet.hudson.MemoryMonitor.obtain(MemoryMonitor.java:91) at org.jvnet.hudson.MemoryMonitor.get(MemoryMonitor.java:57) at hudson.node_monitors.SwapSpaceMonitor$MonitorTask.call(SwapSpaceMonitor.java:107) at hudson.node_monitors.SwapSpaceMonitor$MonitorTask.call(SwapSpaceMonitor.java:103) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) at
[JIRA] (JENKINS-36092) Pipeline Syntax Generator throws 500 on merge before build
Title: Message Title Oleg Nenashev resolved as Duplicate Duplicates JENKINS-34070 Jenkins / JENKINS-36092 Pipeline Syntax Generator throws 500 on merge before build Change By: Oleg Nenashev Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36712) Test Results screen throws "unique keys" error
Title: Message Title
Cliff Meyers created an issue
Jenkins / JENKINS-36712
Test Results screen throws "unique keys" error
Issue Type:
Bug
Assignee:
Unassigned
Components:
blueocean-plugin
Created:
2016/Jul/15 3:22 PM
Priority:
Minor
Reporter:
Cliff Meyers
To repro:
Navigate to a pipeline that publishes test results (I used the JDL)
Choose a Run
Select the "Tests" tab
Should be able to open and view test results, instead console error is thrown and results cannot be expanded. Each child in an array or iterator should have a unique "key" prop. Check the render method of `TestResult`. See https://fb.me/react-warning-keys for more information. JSON from endpoint:
"_class": "hudson.tasks.junit.TestResult",
"testActions": [],
"duration": 0.151,
"empty": false,
"failCount": 0,
"passCount": 26,
"skipCount": 0,
"suites": [{
"cases": [{
"testActions": [],
"age": 0,
"className": "PhantomJS_2_1_1_(Linux_0_0_0).CommitHash",
"duration": 0.049,
"errorDetails": null,
"errorStackTrace": null,
"failedSince": 0,
"name": "CommitHash renders dash with no data",
"skipped": false,
"skippedMessage": null,
"status": "PASSED",
"stderr": "",
"stdout": "\n\n\n "
}, {
"testActions": [],
"age": 0,
"className": "PhantomJS_2_1_1_(Linux_0_0_0).CommitHash",
"duration": 0.003,
[JIRA] (JENKINS-36713) Jenkins upgrade is failing
Title: Message Title Smithesh Purushothaman created an issue Jenkins / JENKINS-36713 Jenkins upgrade is failing Issue Type: Bug Assignee: Jesse Glick Attachments: 1.PNG, 2.PNG Components: workflow-plugin Created: 2016/Jul/15 3:22 PM Labels: jenkins Priority: Minor Reporter: Smithesh Purushothaman Jenkins 2.7 upgrade is failing. Please look at the screen shots Add Comment
[JIRA] (JENKINS-36092) Pipeline Syntax Generator throws 500 on merge before build
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-36092 Pipeline Syntax Generator throws 500 on merge before build Change By: Oleg Nenashev Component/s: git-client-plugin Component/s: core Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36256) "java.net.SocketTimeoutException: Read timed out" error during jenkins upgrade automatically
Title: Message Title Oleg Nenashev commented on JENKINS-36256 Re: "java.net.SocketTimeoutException: Read timed out" error during jenkins upgrade automatically Maybe default Socket timeout on your system is not high enough. Could you provide the full stacktrace? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
