[JIRA] [core] (JENKINS-32797) Access to check for unprotected/never secured paths
Title: Message Title Bryson Gibbons edited a comment on JENKINS-32797 Re: Access to check for unprotected/never secured paths You made me question my solution... I'm assuming the Kerberos-SSO plugin doesn't have a problem with wanting authentication on paths that shouldn't be authenticated? (actually, it looks like they had some, given that they specifically check for the "/userContent" path in the filter). I need to perform some more testing on my plugin before deciding if this is truly needed for my situation. Currently I have duplicated portions of the Jenkins.getTarget() code, since previous solutions involved maintaining an internal list of all paths that should not be authenticated (something I didn't want to maintain). 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-32797) Access to check for unprotected/never secured paths
Title: Message Title Bryson Gibbons commented on JENKINS-32797 Re: Access to check for unprotected/never secured paths You made me question my solution... I'm assuming the Kerberos-SSO plugin doesn't have a problem with wanting authentication on paths that shouldn't be authenticated? I need to perform some more testing on my plugin before deciding if this is truly needed for my situation. Currently I have duplicated portions of the Jenkins.getTarget() code, since previous solutions involved maintaining an internal list of all paths that should not be authenticated (something I didn't want to maintain). 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-33334) Out of the Box: Restart -button is barely visible on 1280 x 800 screen
Title: Message Title Jyrki Puttonen created an issue Jenkins / JENKINS-4 Out of the Box: Restart -button is barely visible on 1280 x 800 screen Issue Type: Bug Assignee: Unassigned Attachments: Screenshot 2016-03-05 06.26.52.png Components: core Created: 05/Mar/16 4:29 AM Labels: 2.0 Priority: Minor Reporter: Jyrki Puttonen After installing Plugins on first run, the "Restart Jenkins" (or something, can't see it right now) is barely visible, see attached screenshot.
[JIRA] [packaging] (JENKINS-33333) Unable to uninstall Jenkins 1.642.2 on Ubuntu 14.04 latest
Title: Message Title Jonathan Davis closed an issue as Cannot Reproduce Jenkins / JENKINS-3 Unable to uninstall Jenkins 1.642.2 on Ubuntu 14.04 latest Change By: Jonathan Davis Status: Open Closed Resolution: Cannot Reproduce 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] [jenkins-tracker] (JENKINS-33333) Unable to uninstall Jenkins 1.642.2 on Ubuntu 14.04 latest
Title: Message Title Jonathan Davis created an issue Jenkins / JENKINS-3 Unable to uninstall Jenkins 1.642.2 on Ubuntu 14.04 latest Issue Type: Bug Assignee: Unassigned Components: jenkins-tracker Created: 05/Mar/16 4:06 AM Priority: Major Reporter: Jonathan Davis Unpacking replacement jenkins ... dpkg-deb: file `/var/cache/apt/archives/jenkins_1.642.2_all.deb' contains ununderstood data member data.tar.xz , giving up dpkg: error processing /var/cache/apt/archives/jenkins_1.642.2_all.deb (--unpack): subprocess dpkg-deb --fsys-tarfile returned error exit status 2 Errors were encountered while processing: /var/cache/apt/archives/jenkins_1.642.2_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Add Comment
[JIRA] [packaging] (JENKINS-33333) Unable to uninstall Jenkins 1.642.2 on Ubuntu 14.04 latest
Title: Message Title Jonathan Davis updated an issue Jenkins / JENKINS-3 Unable to uninstall Jenkins 1.642.2 on Ubuntu 14.04 latest Change By: Jonathan Davis Component/s: packaging Component/s: jenkins-tracker 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] [poll-mailbox-trigger-plugin] (JENKINS-27575) Please add possibility to handle the attachment of mail to this plugin
Title: Message Title Nick Grealy edited a comment on JENKINS-27575 Re: Please add possibility to handle the attachment of mail to this plugin Hi [~balakumarpg] [~jswager1] [~someguy],I've just added functionality to download email attachments to a temporary folder identified by the `*pmt_attachmentsDirectory*` job parameter. *Is anyone interested in beta testing the changes?*I've tested locally against gmail with two JPEG attachments - seems to work fine. I was looking for general testing "in the wild" and feedback/suggestions.*e.g. Test using:*- your email provider- your attachment types- your email formats- ???*Caveats:*- I don't think jobs running on a Jenkins slaves will have access the attachments - is someone able to test/confirm this? (Workaround: [you could copy them from the master|https://wiki.jenkins-ci.org/display/JENKINS/Copy+To+Slave+Plugin]?)- There is (currently) no integration with the [File Parameter|https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Build#ParameterizedBuild-Fileparameter] job parameter*Downloading:*- You can either checkout the [source code|https://github.com/jenkinsci/poll-mailbox-trigger-plugin], and run the plugin locallly locally with the command `[gradlew clean server|https://github.com/jenkinsci/poll-mailbox-trigger-plugin#building]`or- You can download a version I've [prebuilt here|https://bintray.com/artifact/download/nickgrealy/Jenkins_Plugin_Snapshots/poll-mailbox-trigger-plugin.hpi], and then upload the plugin to your Jenkins instance (e.g. http://localhost:8080/pluginManager/advanced > Upload Plugin)I think that's it, let me know if you have an any questions.Kind regards,Nick Grealy 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] [powershell-plugin] (JENKINS-31069) Error after 1.3 Powershell Plugin Update
Title: Message Title Alex Earl commented on JENKINS-31069 Re: Error after 1.3 Powershell Plugin Update I just tested with that version and am not seeing the issue. Can you give more info on what you are seeing specifically and how you have the plugin configured? 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-33332) add itemBlocked extension point to QueueTaskDispatcher
Title: Message Title Jim Carrothers created an issue Jenkins / JENKINS-2 add itemBlocked extension point to QueueTaskDispatcher Issue Type: Improvement Assignee: Unassigned Components: core Created: 05/Mar/16 2:25 AM Priority: Minor Reporter: Jim Carrothers Some plugins may place a reservation on some internal resources as part of their implementation of .QueueTaskDispatcher.canRun() clearing a queue item as runnable. A new callack in QueueTaskDispatcher would be useful to allow a plugin to be notified whenever the Queue decides an item is blocked so that it can free such resources for other purposes in the meantime. Add Comment
[JIRA] [core] (JENKINS-33332) add itemBlocked extension point to QueueTaskDispatcher
Title: Message Title Jim Carrothers commented on JENKINS-2 Re: add itemBlocked extension point to QueueTaskDispatcher I'm submitted a patch to implement this request in https://github.com/jenkinsci/jenkins/pull/2084 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] [dynamic-search-view-plugin] (JENKINS-33331) Dynamic-search-view is not supported under multi-branch-project
Title: Message Title Rick Liu created an issue Jenkins / JENKINS-1 Dynamic-search-view is not supported under multi-branch-project Issue Type: Bug Assignee: Oleg Nenashev Components: dynamic-search-view-plugin, multi-branch-project-plugin Created: 05/Mar/16 1:32 AM Environment: Ubuntu 14.04 x86_64 Jenkins 1.642.1 Oracle 1.7 Dynamic Search View Plugin 0.2.2 Multi-Branch Project Plugin 0.4.1 Priority: Major Reporter: Rick Liu Under multi-branch project, the dynamic-search-view is not supported. The multi-branch project plugin and dynamic-search-view plugin are not compatible. Add Comment
[JIRA] [doclinks-plugin] (JENKINS-30776) Jenkins exception in project configuration page when enabling doclinks
Title: Message Title ikedam closed an issue as Fixed Released 0.6.1 fixing this issue. It will be available in the update center in a day. Please try that. Jenkins / JENKINS-30776 Jenkins exception in project configuration page when enabling doclinks Change By: ikedam Status: Resolved Closed 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-33330) Cron hashing syntax is ignored in Poll SCM
Title: Message Title Christopher Orr created an issue Jenkins / JENKINS-0 Cron hashing syntax is ignored in Poll SCM Issue Type: Bug Assignee: Unassigned Attachments: poll-scm-cron-hashing.png Components: core Created: 05/Mar/16 1:26 AM Priority: Major Reporter: Christopher Orr Entering a hashable cron value like @midnight, @daily, or H 4 * * * in the "Poll SCM" field of a job seems to ignore the hashable part, and the value 0 is used instead. i.e. Jobs scheduled to poll @midnight actually do occur at midnight (according to the text in the config page; see screenshot), and polling scheduled as H 4 * * * is shown to always start at minute zero of that hour. I would expect these to happen — as documented, and as works for "Build periodically" — at pseudo-randomly chosen times. I've seen this across various different jobs, so it wasn't just luck that I happened to see 12:00 come up as the "midnight" time.
[JIRA] [robot-plugin] (JENKINS-33329) Robot-plugin incorrectly recognized CloudBees Folder project to display Robot results column
Title: Message Title Rick Liu created an issue Jenkins / JENKINS-33329 Robot-plugin incorrectly recognized CloudBees Folder project to display Robot results column Issue Type: Bug Assignee: jpiironen Attachments: Selection_004.png Components: robot-plugin Created: 05/Mar/16 1:08 AM Environment: Ubuntu 14.04 x86_64 Jenkins 1.642.1 Oracle JDK 1.7 Robot Framework plugin 1.6.2 CloudBees Folders Plugin 5.1 Priority: Major Reporter: Rick Liu I'm using CloudBees Folder plugin to organize my Jenkins projects. Robot framework plugin incorrectly recognizes the CloudBees Folder as a project contains Robot framework results and display " / passed ". Please refer to the screenshot.
[JIRA] [doclinks-plugin] (JENKINS-30776) Jenkins exception in project configuration page when enabling doclinks
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30776 Re: Jenkins exception in project configuration page when enabling doclinks Code changed in jenkins User: ikedam Path: src/main/java/hudson/plugins/doclinks/DocLinksPublisher.java src/main/java/hudson/plugins/doclinks/m2/DocLinksMavenReporter.java http://jenkins-ci.org/commit/doclinks-plugin/9876b4c6c9c5e291769fd0b53d338e68333f8a88 Log: Merge pull request #4 from ikedam/feature/ JENKINS-30776 _OptionalDependencyToMaven JENKINS-30776 The dependency to maven-plugin should be optional. Compare: https://github.com/jenkinsci/doclinks-plugin/compare/3369f4cfaa24...9876b4c6c9c5 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] [doclinks-plugin] (JENKINS-30776) Jenkins exception in project configuration page when enabling doclinks
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-30776 Jenkins exception in project configuration page when enabling doclinks Change By: SCM/JIRA link daemon Status: In Progress 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] [doclinks-plugin] (JENKINS-30776) Jenkins exception in project configuration page when enabling doclinks
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30776 Re: Jenkins exception in project configuration page when enabling doclinks Code changed in jenkins User: ikedam Path: src/main/java/hudson/plugins/doclinks/DocLinksPublisher.java src/main/java/hudson/plugins/doclinks/m2/DocLinksMavenReporter.java http://jenkins-ci.org/commit/doclinks-plugin/c9f43211892b6f3c15729c5ea1e2937b5eac7cc4 Log: [FIXED JENKINS-30776] The dependency to maven-plugin should be optional. 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-branch-source-plugin] (JENKINS-33228) GitHub server configuration undocumented / duplicated
Title: Message Title Manuel Jesús Recena Soto assigned an issue to Manuel Jesús Recena Soto Jenkins / JENKINS-33228 GitHub server configuration undocumented / duplicated Change By: Manuel Jesús Recena Soto Assignee: Jesse Glick Manuel Jesús Recena Soto 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-branch-source-plugin] (JENKINS-33228) GitHub server configuration undocumented / duplicated
Title: Message Title Manuel Jesús Recena Soto started work on JENKINS-33228 Change By: Manuel Jesús Recena Soto 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] [github-branch-source-plugin] (JENKINS-33318) GitHub Enterprise Server validation does not work when private mode is enabled
Title: Message Title
Manuel Jesús Recena Soto updated an issue
Jenkins / JENKINS-33318
GitHub Enterprise Server validation does not work when private mode is enabled
Change By:
Manuel Jesús Recena Soto
The method {{checkApiUrlValidity()}} does not work fine when a GitHub Enterprise instace instance is configured in {{private mode}}.When I've added this method in [GitHub API|https://github.com/kohsuke/github-api] forget to check with this configuration:{noformat}public void checkApiUrlValidity() throws IOException {retrieve().to("/", GHApiInfo.class).check(apiUrl);}{noformat}Probably, we need to do changes in this plugin (to handle the error) and in *GitHub API*.
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-branch-source-plugin] (JENKINS-33318) GitHub Enterprise Server validation does not work when private mode is enabled
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-33318 Re: GitHub Enterprise Server validation does not work when private mode is enabled Christopher Orr I did not have time to solve this bug but I'll work on it this weekend. Thanks for you feedback. 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-branch-source-plugin] (JENKINS-33228) GitHub server configuration undocumented / duplicated
Title: Message Title Jesse Glick commented on JENKINS-33228 Re: GitHub server configuration undocumented / duplicated Yes, this should be fixed. My general preference would be to move APIs and global configuration options into a separate plugin that could be reused by various feature plugins, but just properly using the existing APIs in the github plugin is the first step. 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-branch-source-plugin] (JENKINS-33228) GitHub server configuration undocumented / duplicated
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-33228 Re: GitHub server configuration undocumented / duplicated Christopher Orr Thanks for your feedback. 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-branch-source-plugin] (JENKINS-33318) GitHub Enterprise Server validation does not work when private mode is enabled
Title: Message Title
Christopher Orr commented on JENKINS-33318
Re: GitHub Enterprise Server validation does not work when private mode is enabled
This seems to be what I'm talking about here and here.
For info, from my GitHub Enterprise instance:
Mar 05, 2016 12:37:50 AM org.jenkinsci.plugins.github_branch_source.Endpoint$DesciptorImpl doCheckApiUri
WARNING: Server returned HTTP response code: 401 for URL: https://github.example.com/api/v3/
$ curl -i https://github.example.com/api/v3/
HTTP/1.1 401 Unauthorized
Server: GitHub.com
Date: Fri, 04 Mar 2016 23:56:42 GMT
Content-Type: application/json; charset=utf-8
Content-Length: 130
Status: 401 Unauthorized
X-GitHub-Media-Type: github.v3
X-XSS-Protection: 1; mode=block
X-Frame-Options: deny
Content-Security-Policy: default-src 'none'
Access-Control-Allow-Credentials: true
Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval
Access-Control-Allow-Origin: *
X-GitHub-Request-Id: 3f457a05-16e9-490f-b28e-175cdffa45b8
Strict-Transport-Security: max-age=31536000; includeSubdomains; preload
X-Content-Type-Options: nosniff
{
"message": "Must authenticate to access this API.",
"documentation_url": "https://developer.github.com/enterprise/2.5/v3"
}
The 401 response throws an IOException, which the plugin turns into a generic error message.
This is also why the GitHub Plugin's UI, where I can enter credentials and click the "Verify credentials" is way more user-friendly
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [github-branch-source-plugin] (JENKINS-33228) GitHub server configuration undocumented / duplicated
Title: Message Title Christopher Orr commented on JENKINS-33228 Re: GitHub server configuration undocumented / duplicated Global configuration provided for this plugin to handle GitHub Entreprise instances, IMO, it is enough. Yeah... if the existing UI was good enough, then I wouldn't have filed this issue, and Cyrille Le Clerc wouldn't have submitted PR #25! Firstly, someone seeing "API endpoint" as a configuration option won't magically know that this is supposed to be a URL pointing to the base path of the API on the GitHub Enteprise server. Even if they do enter a URL, they will probably see "This does not look like a GitHub Enterprise API URL". What should they do when they see this? What should a GH Enterprise API URL look like? Again, there is zero inline documentation. There are even three different code paths which show this same message at the moment — one of which is wrong, since if the GH Enterprise instance has anonymous access disabled, you'll get an IOException: "WARNING: Server returned HTTP response code: 401 for URL: https://github.example.de/api/v3/" Anyway, aside from the fact that every config option should be clearly named and clearly documented, it misses the main point — the needless duplication. As a user, I don't really care which dependency this plugin uses, so long as the UI is consistent. If relying on the github-plugin makes it more consistent, then great. If this plugin and the github-plugin both end up relying on some new github-library-ui plugin, also great. But right now, the duplication of UI here makes no sense. 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
[JIRA] [workflow-plugin] (JENKINS-29711) Snippet Generator: missing attribute names in single-entry forms
Title: Message Title Jesse Glick commented on JENKINS-29711 Re: Snippet Generator: missing attribute names in single-entry forms Reported to affect properties too. 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-25440) Failed to create Guice container from all the plugins
Title: Message Title dogfood commented on JENKINS-25440 Re: Failed to create Guice container from all the plugins Integrated in jenkins_main_trunk #4480 [FIXED JENKINS-25440] Recursively resolve @Inject’ed extensions, too, (Revision 1a2d82275c078ca3f651d9924a53acd2b6210a93) Result = SUCCESS jesse glick : 1a2d82275c078ca3f651d9924a53acd2b6210a93 Files : core/src/main/java/hudson/ExtensionFinder.java 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] [scripttrigger-plugin] (JENKINS-33328) Cannot run trigger script on a slave node
Title: Message Title Christopher Orr commented on JENKINS-33328 Re: Cannot run trigger script on a slave node Were there any nodes with the label android-dev online at the time the polling ran? 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] [offlineonfailure-plugin] (JENKINS-19518) "Take node offline on failure is waiting for a checkpoint on ... - the same build, on a different node
Title: Message Title Leah Zagreus commented on JENKINS-19518 Re: "Take node offline on failure is waiting for a checkpoint on ... - the same build, on a different node Any word on the pull request? 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-25440) Failed to create Guice container from all the plugins
Title: Message Title SCM/JIRA link daemon commented on JENKINS-25440 Re: Failed to create Guice container from all the plugins Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/ExtensionFinder.java http://jenkins-ci.org/commit/jenkins/1a2d82275c078ca3f651d9924a53acd2b6210a93 Log: [FIXED JENKINS-25440] Recursively resolve @Inject’ed extensions, too, looking for LinkageError’s. 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-25440) Failed to create Guice container from all the plugins
Title: Message Title SCM/JIRA link daemon commented on JENKINS-25440 Re: Failed to create Guice container from all the plugins Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/ExtensionFinder.java http://jenkins-ci.org/commit/jenkins/290af8dd1f196815c703a1761fc8a884516f2879 Log: JENKINS-25440 Merged #2072. Compare: https://github.com/jenkinsci/jenkins/compare/ec95aa5b21ab...290af8dd1f19 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-25440) Failed to create Guice container from all the plugins
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-25440 Failed to create Guice container from all the plugins Change By: SCM/JIRA link daemon Status: In Progress 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] [core] (JENKINS-32478) Test harness split
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32478 Re: Test harness split Code changed in jenkins User: Jesse Glick Path: plugins/pom.xml pom.xml test-harness-tools/pom.xml test-harness-tools/src/main/java/org/jvnet/hudson/test/ToolInstallations.java test-harness-tools/src/main/resources/apache-ant-1.8.1-bin.zip test-harness-tools/src/main/resources/apache-maven-2.2.1-bin.zip test-harness-tools/src/main/resources/apache-maven-3.0.1-bin.zip test-harness-tools/src/main/resources/apache-maven-3.1.0-bin.zip test-harness-tools/src/main/resources/maven-2.0.7-bin.zip test-harness/pom.xml test-harness/src/main/java/com/gargoylesoftware/htmlunit/README.md test-harness/src/main/java/com/gargoylesoftware/htmlunit/WebClientUtil.java test-harness/src/main/java/com/gargoylesoftware/htmlunit/WebResponseListener.java test-harness/src/main/java/com/gargoylesoftware/htmlunit/html/DomNodeUtil.java test-harness/src/main/java/com/gargoylesoftware/htmlunit/html/HtmlElementUtil.java test-harness/src/main/java/com/gargoylesoftware/htmlunit/html/HtmlFormUtil.java test-harness/src/main/java/hudson/cli/CLICommandInvoker.java test-harness/src/main/java/hudson/util/SecretHelper.java test-harness/src/main/java/jenkins/model/JenkinsAdaptor.java test-harness/src/main/java/jenkins/model/WorkspaceWriter.java test-harness/src/main/java/org/jvnet/hudson/test/BuildWatcher.java test-harness/src/main/java/org/jvnet/hudson/test/CaptureEnvironmentBuilder.java test-harness/src/main/java/org/jvnet/hudson/test/ChannelShutdownListener.java test-harness/src/main/java/org/jvnet/hudson/test/ClosureExecuterAction.java test-harness/src/main/java/org/jvnet/hudson/test/ComputerConnectorTester.java test-harness/src/main/java/org/jvnet/hudson/test/CreateFileBuilder.java test-harness/src/main/java/org/jvnet/hudson/test/DefaultConstructorChecker.java test-harness/src/main/java/org/jvnet/hudson/test/EndOfTestListener.java test-harness/src/main/java/org/jvnet/hudson/test/ExtractChangeLogParser.java test-harness/src/main/java/org/jvnet/hudson/test/ExtractChangeLogSet.java test-harness/src/main/java/org/jvnet/hudson/test/ExtractResourceSCM.java test-harness/src/main/java/org/jvnet/hudson/test/ExtractResourceWithChangesSCM.java test-harness/src/main/java/org/jvnet/hudson/test/FailureBuilder.java test-harness/src/main/java/org/jvnet/hudson/test/FakeChangeLogSCM.java test-harness/src/main/java/org/jvnet/hudson/test/FakeLauncher.java test-harness/src/main/java/org/jvnet/hudson/test/GroovyHudsonTestCase.java test-harness/src/main/java/org/jvnet/hudson/test/GroovyJenkinsRule.java test-harness/src/main/java/org/jvnet/hudson/test/HudsonHomeLoader.java test-harness/src/main/java/org/jvnet/hudson/test/HudsonPageCreator.java test-harness/src/main/java/org/jvnet/hudson/test/HudsonTestCase.java test-harness/src/main/java/org/jvnet/hudson/test/JavaNetReverseProxy.java test-harness/src/main/java/org/jvnet/hudson/test/JellyTestSuiteBuilder.java test-harness/src/main/java/org/jvnet/hudson/test/JenkinsComputerConnectorTester.java test-harness/src/main/java/org/jvnet/hudson/test/JenkinsMatchers.java test-harness/src/main/java/org/jvnet/hudson/test/JenkinsRecipe.java test-harness/src/main/java/org/jvnet/hudson/test/JenkinsRule.java test-harness/src/main/java/org/jvnet/hudson/test/LenientRunnable.java test-harness/src/main/java/org/jvnet/hudson/test/MemoryAssert.java test-harness/src/main/java/org/jvnet/hudson/test/MilliSecLogFormatter.java test-harness/src/main/java/org/jvnet/hudson/test/MockBuilder.java test-harness/src/main/java/org/jvnet/hudson/test/MockFolder.java test-harness/src/main/java/org/jvnet/hudson/test/MockQueueItemAuthenticator.java test-harness/src/main/java/org/jvnet/hudson/test/NoListenerConfiguration.java test-harness/src/main/java/org/jvnet/hudson/test/PluginAutomaticTestBuilder.java test-harness/src/main/java/org/jvnet/hudson/test/PretendSlave.java
[JIRA] [workflow-plugin] (JENKINS-32925) StackOverflow when trying to get Pipeline GDSL file
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-32925 StackOverflow when trying to get Pipeline GDSL file Change By: SCM/JIRA link daemon Status: In Progress 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] [workflow-plugin] (JENKINS-32925) StackOverflow when trying to get Pipeline GDSL file
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32925 Re: StackOverflow when trying to get Pipeline GDSL file Code changed in jenkins User: Jesse Glick Path: CHANGES.md step-api/src/main/java/org/jenkinsci/plugins/workflow/structs/DescribableHelper.java step-api/src/test/java/org/jenkinsci/plugins/workflow/structs/DescribableHelperTest.java http://jenkins-ci.org/commit/workflow-plugin/e51ddbbe6ec954dc4bccefb123528ddf28162d5e Log: [FIXED JENKINS-32925] Merged #351. Compare: https://github.com/jenkinsci/workflow-plugin/compare/0b0b2aa0c5e9...e51ddbbe6ec9 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] [aws-lambda-plugin] (JENKINS-33198) add Pipeline support to aws-lambda-plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33198 Re: add Pipeline support to aws-lambda-plugin Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/workflow-plugin/f66308082191e764b55447d5bc1cc40f8d0914ca Log: JENKINS-33198 Merging #353 with touch-ups. 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] [js-modules] (JENKINS-33245) jquery-detached creates directory structure with 21 webapp subdirectories
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33245 Re: jquery-detached creates directory structure with 21 webapp subdirectories Code changed in jenkins User: tfennelly Path: cps/pom.xml http://jenkins-ci.org/commit/workflow-plugin/c83b2cc9f1759c0efd02ca39be4e110c197986f7 Log: Use repackaged jQuery HPI The jQuery plugin was bloated due to a bad assembly. See JENKINS-33245. 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] [scripttrigger-plugin] (JENKINS-33328) Cannot run trigger script on a slave node
Title: Message Title luper rouch updated an issue Jenkins / JENKINS-33328 Cannot run trigger script on a slave node Change By: luper rouch If I check "Restrict where the polling can be run" and add a label, I see this error in the polling log:Polling started on Mar 4, 2016 8:26:00 PMPolling for the job bundle-builder-develop-androidLooking nodes where the poll can be run.Looking for a node to the restricted label android-dev.Can't find any eligible slave nodes.Trying to poll on master node. And the script is executed on the master. 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] [scripttrigger-plugin] (JENKINS-33328) Cannot run trigger script on a slave node
Title: Message Title
luper rouch updated an issue
Jenkins / JENKINS-33328
Cannot run trigger script on a slave node
Change By:
luper rouch
If I check "Restrict where the polling can be run" and add a label, I see this error in the polling log: {{Polling started on Mar 4, 2016 8:26:00 PMPolling for the job bundle-builder-develop-androidLooking nodes where the poll can be run.Looking for a node to the restricted label android-dev.Can't find any eligible slave nodes.Trying to poll on master node.}}
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] [scripttrigger-plugin] (JENKINS-33328) Cannot run trigger script on a slave node
Title: Message Title
luper rouch updated an issue
Jenkins / JENKINS-33328
Cannot run trigger script on a slave node
Change By:
luper rouch
If I check "Restrict where the polling can be run" and add a label, I see this error in the polling log:{{ Polling started on Mar 4, 2016 8:26:00 PMPolling for the job bundle-builder-develop-androidLooking nodes where the poll can be run.Looking for a node to the restricted label android-dev.Can't find any eligible slave nodes.Trying to poll on master node. }}
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] [scripttrigger-plugin] (JENKINS-33328) Cannot run trigger script on a slave node
Title: Message Title
luper rouch created an issue
Jenkins / JENKINS-33328
Cannot run trigger script on a slave node
Issue Type:
Bug
Assignee:
Gregory Boissinot
Components:
scripttrigger-plugin
Created:
04/Mar/16 8:28 PM
Labels:
plugin
Priority:
Minor
Reporter:
luper rouch
If I check "Restrict where the polling can be run" and add a label, I see this error in the polling log: {{Polling started on Mar 4, 2016 8:26:00 PM Polling for the job bundle-builder-develop-android Looking nodes where the poll can be run. Looking for a node to the restricted label android-dev. Can't find any eligible slave nodes. Trying to poll on master node.}}
Add Comment
[JIRA] [core] (JENKINS-33327) Order of post-build plugins graphs not respected anymore
Title: Message Title Chris J created an issue Jenkins / JENKINS-33327 Order of post-build plugins graphs not respected anymore Issue Type: Bug Assignee: Unassigned Attachments: config.PNG, job result.PNG Components: core Created: 04/Mar/16 8:08 PM Priority: Minor Reporter: Chris J In Jenkins 1.625.3, the graph produced by post-build publish plugins such as "coverage" or "junit" were following the order displayed in job configuration page. If I had "publish coverage" post-build action on top of "publish junit", then the graph of coverage would be on top of junit graph. If I changed the order of post-build actions, then immediately the graph order was changed. +Since I upgraded to version 1.642.1, the UI order is not respected anymore +and the coverage graph is always on top of junit for instance. Could you revert back to the previous behaviour please? Thank you
[JIRA] [monitoring-plugin] (JENKINS-32441) SEVERE: Failed Loading plugin monitoring
Title: Message Title evernat resolved as Not A Defect ok, thanks Jenkins / JENKINS-32441 SEVERE: Failed Loading plugin monitoring Change By: evernat Status: Open 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] [github-branch-source-plugin] (JENKINS-33228) GitHub server configuration undocumented / duplicated
Title: Message Title Kanstantsin Shautsou commented on JENKINS-33228 Re: GitHub server configuration undocumented / duplicated github-plugin provides API for hooks registration and GH connection with credentials UI. It kept as generic functionality plugin (plus very annoying push->git-poll trigger that can't be removed). User configures GH connection and then plugins reusing it. As i see branch-source fully rewrote this functionality with allowing totally bad things like using user+password logins and anonymous connections. Excluding `github-plugin` for github plugins unfortunately would mean that CloudBees doesn't want to use community produced code and APIs. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-choices-plugin] (JENKINS-33326) Programmatic changes to Reactive Reference value do not cascade
Title: Message Title Ioannis Moutsatsos created an issue Jenkins / JENKINS-33326 Programmatic changes to Reactive Reference value do not cascade Issue Type: Bug Assignee: Bruno P. Kinoshita Components: active-choices-plugin Created: 04/Mar/16 6:54 PM Environment: Jenkins 1.596.1, Active-choices v 1.4 Priority: Minor Reporter: Ioannis Moutsatsos I have two AC-Reactive Reference parameters. The first (A) is an input text box. The second (B) references the value of A and cascades when A-value is changed by user input. However, when A-value is changed programmatically by a _javascript_ function, its value does not cascade to B, even after I force the A-input text box to fire an onchange() event. The only way to cascade the A-value is for the user to click in the input text box and change something. Upon exit the A.value cascades to parameter B. An onchange() event in the input text box should cascade the A-value to parameters that reference it.
[JIRA] [remoting] (JENKINS-31735) Remoting : NioChannelHub is not currently running
Title: Message Title Vinay Shah commented on JENKINS-31735 Re: Remoting : NioChannelHub is not currently running We are using Jenkins version 1.579, and intermittently observing similar issue. <===[JENKINS REMOTING CAPACITY]===>Failed to establish the connection java.io.IOException: NioChannelHub is not currently running at org.jenkinsci.remoting.nio.NioChannelHub$1.makeTransport(NioChannelHub.java:446) .. Do we know the root cause of it? And how to address it without restarting the Jenkins server. Thanks, Vinay 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-branch-source-plugin] (JENKINS-33183) Anonymous scan credentials causes checkout to fail
Title: Message Title Manuel Jesús Recena Soto resolved as Fixed Jenkins / JENKINS-33183 Anonymous scan credentials causes checkout to fail Change By: Manuel Jesús Recena Soto Status: In Progress 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] [packaging] (JENKINS-33285) Old jenkins versions are not listed in Debian repository Packages.gz
Title: Message Title Kohsuke Kawaguchi commented on JENKINS-33285 Re: Old jenkins versions are not listed in Debian repository Packages.gz This seems like a regression, because I remember writing some code that handles this. I need to look it up. 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-name-setter-plugin] (JENKINS-33167) Build Name Setter Plugin doesn't update the build name during the build
Title: Message Title Chris Hillery edited a comment on JENKINS-33167 Re: Build Name Setter Plugin doesn't update the build name during the build The separate build steps in a Jenkins job are executed sequentially, not in parallel. Adding an "Update build name" build step to set the build name from a file doesn't tell Jenkins to start monitoring that file for changes and immediately reflect them in the Jenkins GUI. The update won't happen until that build step is executed, which will be after your "Execute shell" step completes.If you want this to happen "during" your shell script build, you'll need to split the script into two parts. The first part could initialize things and put the desired build name into the file. Then you'd add an "Execute shell" step to run that part; add an "Update build name" step to set the build name in Jenkins; and finally add another "Execute shell" step to run the second script.Meanwhile this ticket can problem probably be closed as "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] [github-branch-source-plugin] (JENKINS-33183) Anonymous scan credentials causes checkout to fail
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33183 Re: Anonymous scan credentials causes checkout to fail Code changed in jenkins User: Manuel Recena Path: src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMSource.java http://jenkins-ci.org/commit/github-branch-source-plugin/e3784380a29f020468e28b251ae7e3b3ee9c6273 Log: Merge pull request #23 from Andne/ghe-anon JENKINS-33183 Allow anon credentials when retrieving commit Compare: https://github.com/jenkinsci/github-branch-source-plugin/compare/b407e671c88a...e3784380a29f 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-33325) Rename workflow job to pipeline job
Title: Message Title Neil Hunt created an issue Jenkins / JENKINS-33325 Rename workflow job to pipeline job Issue Type: Improvement Assignee: Daniel Spilker Components: job-dsl-plugin Created: 04/Mar/16 5:52 PM Labels: job-dsl-plugin Priority: Minor Reporter: Neil Hunt Since Jenkins has renamed "Workflow" suite of plugins to "Pipeline", ideally the type in Job DSL would be renamed from workflowJob to pipelineJob (or similar) Add Comment
[JIRA] [monitoring-plugin] (JENKINS-32441) SEVERE: Failed Loading plugin monitoring
Title: Message Title Samuel Lopez commented on JENKINS-32441 Re: SEVERE: Failed Loading plugin monitoring Hello and thanks for the update. We did find a third party log4j .jar file that was causing the problem. Once removed the monitoring plugin loaded successfully 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] [jacoco-plugin] (JENKINS-28652) JaCoCo 0.7.5 incorrectly shows 0% coverage in Jenkins summary
Title: Message Title Samuel Lopez commented on JENKINS-28652 Re: JaCoCo 0.7.5 incorrectly shows 0% coverage in Jenkins summary Thanks, On my side it looks like using the Mvn plugin at 0.7.5 fixes my 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] [maven-metadata-plugin] (JENKINS-17717) Plugin should use authentication from settings.xml
Title: Message Title Marc Rohlfs closed an issue as Not A Defect Jenkins / JENKINS-17717 Plugin should use authentication from settings.xml Change By: Marc Rohlfs Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-metadata-plugin] (JENKINS-21743) Enable/Implement CLI parameter submission for Maven Metadata Plugin
Title: Message Title Marc Rohlfs closed an issue as Fixed Jenkins / JENKINS-21743 Enable/Implement CLI parameter submission for Maven Metadata Plugin Change By: Marc Rohlfs Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-metadata-plugin] (JENKINS-23206) ARTIFACT_URL is not correctly resolved for SNAPSHOT artifacts
Title: Message Title Marc Rohlfs closed an issue as Fixed Jenkins / JENKINS-23206 ARTIFACT_URL is not correctly resolved for SNAPSHOT artifacts Change By: Marc Rohlfs Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-metadata-plugin] (JENKINS-32953) Classifier support in Maven Metadata Plugin
Title: Message Title Marc Rohlfs edited a comment on JENKINS-32953 Re: Classifier support in Maven Metadata Plugin Release Released with plugin version 1.4.0 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-metadata-plugin] (JENKINS-32953) Classifier support in Maven Metadata Plugin
Title: Message Title Marc Rohlfs commented on JENKINS-32953 Re: Classifier support in Maven Metadata Plugin Release with plugin version 1.4.0 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] [msbuild-plugin] (JENKINS-33321) Upgrade msbuild-plugin to new parent pom
Title: Message Title Armando Fernandez commented on JENKINS-33321 Re: Upgrade msbuild-plugin to new parent pom PR here 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] [docker-commons-plugin] (JENKINS-32792) Unable to push Docker images due to failing image ID length check
Title: Message Title Taylor Patton commented on JENKINS-32792 Re: Unable to push Docker images due to failing image ID length check Can bypass the failure if I uncheck "Create fingerprints" in Docker Build Advanced section 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-oauth-plugin] (JENKINS-33258) Error on every Jenkins page: java.lang.RuntimeException: java.io.IOException: Server returned HTTP response code: 401 for URL: https://api.github.com/user
Title: Message Title Leandro Lucarella commented on JENKINS-33258 Re: Error on every Jenkins page: java.lang.RuntimeException: java.io.IOException: Server returned HTTP response code: 401 for URL: https://api.github.com/user Anyway, I'm fine if you want to close this as invalid or cantreproduce, as once the browser was restarted I never experienced this again. 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-oauth-plugin] (JENKINS-33258) Error on every Jenkins page: java.lang.RuntimeException: java.io.IOException: Server returned HTTP response code: 401 for URL: https://api.github.com/user
Title: Message Title Leandro Lucarella commented on JENKINS-33258 Re: Error on every Jenkins page: java.lang.RuntimeException: java.io.IOException: Server returned HTTP response code: 401 for URL: https://api.github.com/user But thanks for the link, I've made my own gitignore rules, I'll check if I missed anything. 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-oauth-plugin] (JENKINS-33258) Error on every Jenkins page: java.lang.RuntimeException: java.io.IOException: Server returned HTTP response code: 401 for URL: https://api.github.com/user
Title: Message Title Leandro Lucarella commented on JENKINS-33258 Re: Error on every Jenkins page: java.lang.RuntimeException: java.io.IOException: Server returned HTTP response code: 401 for URL: https://api.github.com/user I am This was very early in the stage of the move, I just copied a couple of jobs to make sure I installed all the necessary plugins, etc. Once everything looked fine, I checked out the whole config files I have in git, and then it happened. 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-32451) Collection.find returns boolean
Title: Message Title
Mitya Kononchuk edited a comment on JENKINS-32451
Re: Collection.find returns boolean
` {{ find ` }} method as many others using closures are not supported in workflow code. You should put such code in ` {{ NonCPS ` }} blocks. See [best practices ]( | https://github.com/jenkinsci/pipeline-examples/blob/master/docs/BEST_PRACTICES.md ) ] .
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-32451) Collection.find returns boolean
Title: Message Title Mitya Kononchuk commented on JENKINS-32451 Re: Collection.find returns boolean `find` method as many others using closures are not supported in workflow code. You should put such code in `NonCPS` blocks. See [best practices](https://github.com/jenkinsci/pipeline-examples/blob/master/docs/BEST_PRACTICES.md). 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] [nodelabelparameter-plugin] (JENKINS-32002) Build is sheduled on one node and not all of them for node parameter
Title: Message Title Oleg Nenashev commented on JENKINS-32002 Re: Build is sheduled on one node and not all of them for node parameter Antonio Muñiz I've fixed the link direction Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-metadata-plugin] (JENKINS-32953) Classifier support in Maven Metadata Plugin
Title: Message Title Marc Rohlfs edited a comment on JENKINS-32953 Re: Classifier support in Maven Metadata Plugin Great job, [~dromie]. Many 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] [maven-metadata-plugin] (JENKINS-32953) Classifier support in Maven Metadata Plugin
Title: Message Title Marc Rohlfs resolved as Fixed Jenkins / JENKINS-32953 Classifier support in Maven Metadata Plugin Change By: Marc Rohlfs Status: In Progress 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] [workflow-plugin] (JENKINS-27039) Option for input or stage step to cancel older executions
Title: Message Title Antonio Muñiz commented on JENKINS-27039 Re: Option for input or stage step to cancel older executions Proposed PR: https://github.com/jenkinsci/workflow-plugin/pull/355 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-branch-source-plugin] (JENKINS-33183) Anonymous scan credentials causes checkout to fail
Title: Message Title Jesse Glick commented on JENKINS-33183 Re: Anonymous scan credentials causes checkout to fail should retrieve(SCMHead, TaskListener) be using the checkout credentials instead of the scan credentials? No, all GitHub API operations use the scan credentials. it appears to me that anonymous access was intentionally left unusable No, it is intended to work to the extent possible. You might run into rate limiting issues, if you have a lot of repositories/branches, but that is your problem. 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-21750) Promoted Builds Plugin
Title: Message Title Chris Z edited a comment on JENKINS-21750 Re: Promoted Builds Plugin Great success finally PR is in master !Plugin for tests:https://jenkins.ci.cloudbees.com/job/plugins/job/promoted-builds-plugin/251/org.jenkins-ci.plugins$promoted-builds/Description how [edit] removed due to use it:https://github.com/denschu/promoted-builds-plugin/blob/master/README.mdSection Job DSL support misleading information 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-21750) Promoted Builds Plugin
Title: Message Title Chris Z commented on JENKINS-21750 Re: Promoted Builds Plugin Yes, you are right. I have no idea how I have seen it in master branch. My bad 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] [integrity-plugin] (JENKINS-32677) Don't see labels applied to the codebase
Title: Message Title Cletus D'Souza resolved as Not A Defect Jenkins / JENKINS-32677 Don't see labels applied to the codebase Change By: Cletus D'Souza Status: Open 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] [integrity-plugin] (JENKINS-32677) Don't see labels applied to the codebase
Title: Message Title Cletus D'Souza assigned an issue to PTC ALM Jenkins / JENKINS-32677 Don't see labels applied to the codebase Change By: Cletus D'Souza Assignee: PTC ALM Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-metadata-plugin] (JENKINS-32953) Classifier support in Maven Metadata Plugin
Title: Message Title Marc Rohlfs commented on JENKINS-32953 Re: Classifier support in Maven Metadata Plugin Many 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] [subversion-plugin] (JENKINS-31455) Build instability with "ISVNAuthentication provider did not provide credentials"
Title: Message Title Martin Kaiser commented on JENKINS-31455 Re: Build instability with "ISVNAuthentication provider did not provide credentials" Same problem here: most of the time it works when the build is triggered manually if build is triggered by svn-polling, every access every nested/external svn. The projects "main" repo can be accessed successfully. Jenkins ver. 1.642.2 Subversion Plug-in: 2.5.7 Ubuntu 14.04 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] [integrity-plugin] (JENKINS-31836) Restarting PTC server during Polling does not time out
Title: Message Title Cletus D'Souza assigned an issue to PTC ALM Jenkins / JENKINS-31836 Restarting PTC server during Polling does not time out Change By: Cletus D'Souza Assignee: Cletus D'Souza PTC ALM 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] [integrity-plugin] (JENKINS-31836) Restarting PTC server during Polling does not time out
Title: Message Title Cletus D'Souza commented on JENKINS-31836 Re: Restarting PTC server during Polling does not time out Please reproduce with latest version. No updates will be performed on the older releases 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] [integrity-plugin] (JENKINS-27217) Replace Derby DB by MapDB
Title: Message Title Cletus D'Souza assigned an issue to PTC ALM Jenkins / JENKINS-27217 Replace Derby DB by MapDB Change By: Cletus D'Souza Assignee: Cletus D'Souza PTC ALM 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] [integrity-plugin] (JENKINS-31739) NPE from IntegritySCM.checkout from Workflow
Title: Message Title Cletus D'Souza commented on JENKINS-31739 Re: NPE from IntegritySCM.checkout from Workflow Please reproduce with latest version. No updates will be released for older versions 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] [integrity-plugin] (JENKINS-31739) NPE from IntegritySCM.checkout from Workflow
Title: Message Title Cletus D'Souza assigned an issue to PTC ALM Jenkins / JENKINS-31739 NPE from IntegritySCM.checkout from Workflow Change By: Cletus D'Souza Assignee: Cletus D'Souza PTC ALM 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] [integrity-plugin] (JENKINS-32826) Polling failure on jobs with same name in different folders
Title: Message Title Cletus D'Souza assigned an issue to PTC ALM Jenkins / JENKINS-32826 Polling failure on jobs with same name in different folders Change By: Cletus D'Souza Assignee: Cletus D'Souza PTC ALM 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] [integrity-plugin] (JENKINS-32826) Polling failure on jobs with same name in different folders
Title: Message Title Cletus D'Souza commented on JENKINS-32826 Re: Polling failure on jobs with same name in different folders Please reproduce with latest version. No release updates will be made for older releases 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] [integrity-plugin] (JENKINS-32085) PTC sandbox creation takes too long
Title: Message Title Cletus D'Souza resolved as Not A Defect Jenkins / JENKINS-32085 PTC sandbox creation takes too long Change By: Cletus D'Souza Status: Open 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] [integrity-plugin] (JENKINS-27140) Workflow support for Integrity SCM Plugin
Title: Message Title Cletus D'Souza resolved as Fixed Workflow support was added for the latest version at the time. No older versions will be back-ported and issues with the latest version should be tracked separately. Jenkins / JENKINS-27140 Workflow support for Integrity SCM Plugin Change By: Cletus D'Souza Status: Reopened 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] [integrity-plugin] (JENKINS-33077) checkPointBeforeBuild fails for projects on development path
Title: Message Title Cletus D'Souza commented on JENKINS-33077 Re: checkPointBeforeBuild fails for projects on development path Please reproduce this behavior with the latest version of the plugin. No updates are going to be release for the older version. 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] [integrity-plugin] (JENKINS-33077) checkPointBeforeBuild fails for projects on development path
Title: Message Title Cletus D'Souza assigned an issue to PTC ALM Jenkins / JENKINS-33077 checkPointBeforeBuild fails for projects on development path Change By: Cletus D'Souza Assignee: Cletus D'Souza PTC ALM 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] [bitbucket-build-status-notifier-plugin] (JENKINS-32940) Aborted builds remain in progress in BitBucket
Title: Message Title Antonio Mansilla resolved as Fixed Jenkins / JENKINS-32940 Aborted builds remain in progress in BitBucket Change By: Antonio Mansilla Status: In Progress 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] [integrity-plugin] (JENKINS-33079) Handling prebuild checkpoint results in Pipeline
Title: Message Title Cletus D'Souza assigned an issue to PTC ALM Jenkins / JENKINS-33079 Handling prebuild checkpoint results in Pipeline Change By: Cletus D'Souza Assignee: Cletus D'Souza PTC ALM Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-metadata-plugin] (JENKINS-32953) Classifier support in Maven Metadata Plugin
Title: Message Title Marc Rohlfs assigned an issue to Marc Rohlfs Jenkins / JENKINS-32953 Classifier support in Maven Metadata Plugin Change By: Marc Rohlfs Assignee: Gesh Markov Marc Rohlfs Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory-plugin] (JENKINS-26737) AD can not log on with email address (regression in 1.39)
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-26737 AD can not log on with email address (regression in 1.39) Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory-plugin] (JENKINS-26737) AD can not log on with email address (regression in 1.39)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26737 Re: AD can not log on with email address (regression in 1.39) Code changed in jenkins User: Felix Belzunce Arcos Path: src/main/java/hudson/plugins/active_directory/ActiveDirectoryUnixAuthenticationProvider.java http://jenkins-ci.org/commit/active-directory-plugin/3a5ee3bf2007beabcde04844e8fba57bacad2255 Log: Merge pull request #12 from nieuwtje/upn-login-double-domain [FIXED JENKINS-26737] AD can not log on with email address Compare: https://github.com/jenkinsci/active-directory-plugin/compare/5372151110a5...3a5ee3bf2007 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory-plugin] (JENKINS-26737) AD can not log on with email address (regression in 1.39)
Title: Message Title James Nord edited a comment on JENKINS-26737 Re: AD can not log on with email address (regression in 1.39) most likely fixed by [PR #12 | https://github.com/jenkinsci/active-directory-plugin/pull/12]Build for testing [here | https://jenkins.ci.cloudbees.com/job/plugins/job/active-directory-plugin/158/org.jenkins-ci.plugins$active-directory/artifact/org.jenkins-ci.plugins/active-directory/1.43-SNAPSHOT/active-directory-1.43-SNAPSHOT.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] [git-client-plugin] (JENKINS-33324) Old git versions (git 1.7.1 on CentOS 6.7) report git config error from --local parameter
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-33324 Old git versions (git 1.7.1 on CentOS 6.7) report git config error from --local parameter Change By: Mark Waite Summary: Older Old git versions ( like git 1.7.1 from on CentOS 6.7) report git config error from --local parameter Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory-plugin] (JENKINS-25485) Unable to login with standard Jenkins users when Active Directory plugin is in use
Title: Message Title James Nord closed an issue as Duplicate Jenkins / JENKINS-25485 Unable to login with standard Jenkins users when Active Directory plugin is in use Change By: James Nord Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory-plugin] (JENKINS-25485) Unable to login with standard Jenkins users when Active Directory plugin is in use
Title: Message Title James Nord commented on JENKINS-25485 Re: Unable to login with standard Jenkins users when Active Directory plugin is in use This is as you guessed by design. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory-plugin] (JENKINS-26603) Active Directory trying to connect to AD server every 15 seconds with a user ID
Title: Message Title James Nord commented on JENKINS-26603 Re: Active Directory trying to connect to AD server every 15 seconds with a user ID something is hitting jenkins with some username. I would suggest sniffing the tcp traffic and looking at the requests to identify the source. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory-plugin] (JENKINS-26603) Active Directory trying to connect to AD server every 15 seconds with a user ID
Title: Message Title
James Nord updated an issue
Jenkins / JENKINS-26603
Active Directory trying to connect to AD server every 15 seconds with a user ID
Change By:
James Nord
When activating the Active directory plugin i am able to connect to the domain via the test button. I see the user groups are available as the red boxes beside them go away once active. However in the log file i see the following error every 15 seconds and I am currently unable to log into jenkins via my AD credentials. {noformat} Jan 26, 2015 7:00:24 AM WARNING hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl bindFailed to authenticate while binding to server.domain.com:3268javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C0903A9, comment: AcceptSecurityContext error, data 52e, v1db1] at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3032) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2978) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2780) at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2694) at com.sun.jndi.ldap.LdapCtx.ensureOpen(LdapCtx.java:2580) at com.sun.jndi.ldap.LdapCtx.ensureOpen(LdapCtx.java:2567) at com.sun.jndi.ldap.LdapCtx.reconnect(LdapCtx.java:2563) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:514) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:430) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:273) 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 jenkins.security.BasicHeaderRealPasswordAuthenticator.authenticate(BasicHeaderRealPasswordAuthenticator.java:55) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:79) 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:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at
[JIRA] [github-branch-source-plugin] (JENKINS-33228) GitHub server configuration undocumented / duplicated
Title: Message Title Kirill Merkushev edited a comment on JENKINS-33228 Re: GitHub server configuration undocumented / duplicated Think it should reuse github-plugin's credentials storage and not use own . I can help on how to do so - it requires only few lines of code Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory-plugin] (JENKINS-26737) AD can not log on with email address (regression in 1.39)
Title: Message Title James Nord commented on JENKINS-26737 Re: AD can not log on with email address (regression in 1.39) most likely fixed by PR #12 Build for testing Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
