[JIRA] [jira-plugin] (JENKINS-32491) Rename Workflow Plugin to Pipeline
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32491 Re: Rename Workflow Plugin to Pipeline Code changed in jenkins User: Radek Antoniuk Path: COMPATIBILITY.md README.md pom.xml http://jenkins-ci.org/commit/jira-plugin/ea4deb1fabe92cb89736d432cef6d8b36e3b19db Log: JENKINS-32491 - Workflow references renamed to Pipeline JENKINS-34661 - Bump LTS to 1.642.3 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] [jira-plugin] (JENKINS-34661) Bump LTS to 1.642.3
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34661 Re: Bump LTS to 1.642.3 Code changed in jenkins User: Radek Antoniuk Path: COMPATIBILITY.md README.md pom.xml http://jenkins-ci.org/commit/jira-plugin/ea4deb1fabe92cb89736d432cef6d8b36e3b19db Log: JENKINS-32491 - Workflow references renamed to Pipeline JENKINS-34661 - Bump LTS to 1.642.3 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] [jira-plugin] (JENKINS-34661) Bump LTS to 1.642.3
Title: Message Title Radek Antoniuk resolved as Fixed Jenkins / JENKINS-34661 Bump LTS to 1.642.3 Change By: Radek Antoniuk 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] [jira-plugin] (JENKINS-34661) Bump LTS to 1.642.3
Title: Message Title Radek Antoniuk created an issue Jenkins / JENKINS-34661 Bump LTS to 1.642.3 Issue Type: Task Assignee: Unassigned Components: jira-plugin Created: 2016/May/07 4:25 AM Labels: jira-plugin-2.3 Priority: Minor Reporter: Radek Antoniuk Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [jira-plugin] (JENKINS-32491) Rename Workflow Plugin to Pipeline
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-32491 Rename Workflow Plugin to Pipeline Change By: Radek Antoniuk Labels: jira-plugin-2.3 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] [jira-plugin] (JENKINS-32491) Rename Workflow Plugin to Pipeline
Title: Message Title Radek Antoniuk resolved as Fixed Jenkins / JENKINS-32491 Rename Workflow Plugin to Pipeline Change By: Radek Antoniuk 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] [core] (JENKINS-34660) Latest LTS plugin pom not available
Title: Message Title Radek Antoniuk created an issue Jenkins / JENKINS-34660 Latest LTS plugin pom not available Issue Type: Task Assignee: Unassigned Components: core Created: 2016/May/07 3:32 AM Priority: Minor Reporter: Radek Antoniuk http://repo.jenkins-ci.org/public/org/jenkins-ci/plugins/plugin/1.651.1/ does not exist for the latest LTS release. Add Comment This message was sent by Atlassian
[JIRA] [jira-plugin] (JENKINS-16292) Set Release date to now() for Post Build Step 'Mark a JIRA Version as Released'
Title: Message Title Radek Antoniuk resolved as Duplicate Jenkins / JENKINS-16292 Set Release date to now() for Post Build Step 'Mark a JIRA Version as Released' Change By: Radek Antoniuk Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-plugin] (JENKINS-23229) Add support of rebuild actions (Rebuild Plugin)
Title: Message Title Radek Antoniuk resolved as Cannot Reproduce Jenkins / JENKINS-23229 Add support of rebuild actions (Rebuild Plugin) Change By: Radek Antoniuk Status: Open Resolved 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] [jira-plugin] (JENKINS-25135) JIRA Plugin should expose built JIRAs via Token Macro
Title: Message Title Radek Antoniuk commented on JENKINS-25135 Re: JIRA Plugin should expose built JIRAs via Token Macro This should be possible via pipeline plugin and environment variables in v. 2.3. 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] [jira-plugin] (JENKINS-25135) JIRA Plugin should expose built JIRAs via Token Macro
Title: Message Title Radek Antoniuk assigned an issue to Radek Antoniuk Jenkins / JENKINS-25135 JIRA Plugin should expose built JIRAs via Token Macro Change By: Radek Antoniuk Assignee: Radek Antoniuk 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] [jira-plugin] (JENKINS-750) Possibility to update custom fields
Title: Message Title Radek Antoniuk commented on JENKINS-750 Re: Possibility to update custom fields Martin, I think your request is different from this JIRA. You want to specify additional field while creating new issues not updating, is that correct? 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] [jira-plugin] (JENKINS-750) Possibility to update custom fields
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-750 Possibility to update custom fields Change By: Radek Antoniuk Summary: JIRA plugin: put build number in Possibility to update custom field? fields 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] [jira-plugin] (JENKINS-1489) JIRA plugin - security level for comment
Title: Message Title Radek Antoniuk commented on JENKINS-1489 Re: JIRA plugin - security level for comment Anyone still getting this on plugin 2.x via REST 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] [jira-plugin] (JENKINS-2792) Support for HTTP basic authentication on Jira server
Title: Message Title Radek Antoniuk commented on JENKINS-2792 Re: Support for HTTP basic authentication on Jira server So is this still the case in via JIRA REST 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] [jira-plugin] (JENKINS-13773) Perform Jira release based on user action or certain plugin usage - Maven
Title: Message Title Radek Antoniuk resolved as Won't Fix As Jan mentioned this could be now achieved via pipeline plugin. Jenkins / JENKINS-13773 Perform Jira release based on user action or certain plugin usage - Maven Change By: Radek Antoniuk Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-plugin] (JENKINS-32491) Rename Workflow Plugin to Pipeline
Title: Message Title Radek Antoniuk assigned an issue to Radek Antoniuk Jenkins / JENKINS-32491 Rename Workflow Plugin to Pipeline Change By: Radek Antoniuk Assignee: Jan Zajíc Radek Antoniuk 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] [jira-plugin] (JENKINS-32602) jira-plugin missing License
Title: Message Title Radek Antoniuk commented on JENKINS-32602 Re: jira-plugin missing License Cc Antonio Muñiz, olamy ARTEM KOSHELEV should we go with Jenkins' MIT license? https://github.com/jenkinsci/jenkins/blob/master/LICENSE.txt Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-plugin] (JENKINS-32602) jira-plugin missing License
Title: Message Title Radek Antoniuk assigned an issue to Radek Antoniuk Jenkins / JENKINS-32602 jira-plugin missing License Change By: Radek Antoniuk Assignee: Radek Antoniuk 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] [jira-plugin] (JENKINS-33222) Concurrent builds are blocking with jira-plugin
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-33222 Concurrent builds are blocking with jira-plugin Change By: Radek Antoniuk Issue Type: Improvement Bug 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] [jira-plugin] (JENKINS-33222) Concurrent builds are blocking with jira-plugin
Title: Message Title Radek Antoniuk commented on JENKINS-33222 Re: Concurrent builds are blocking with jira-plugin Are there any logs you could attach for this bug? 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] [jira-plugin] (JENKINS-33752) Parse branch name for JIRA issue
Title: Message Title Radek Antoniuk commented on JENKINS-33752 Re: Parse branch name for JIRA issue I would say this is correct behavior - it is a standard and good practice to put the JIRA ID in the commit message. Branch naming is often different from actual JIRA IDs - i've seen XXX-123_xx, XXX_123_xx etc, which will create a mess in terms of regex matching. Additionally, the commit message can actually perform workflow actions (see JIRA's SmartCommits). For this reason I would say - "as designed" 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] [jira-plugin] (JENKINS-33996) Add a new Pipeline step that find all JIRA issues referenced by the commit logs of this build
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-33996 Add a new Pipeline step that find all JIRA issues referenced by the commit logs of this build Change By: Radek Antoniuk Labels: jira-plugin-2.3 workflow Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-34573) Running out of Heap Memory (2048m)
Title: Message Title Raymond Accary commented on JENKINS-34573 Re: Running out of Heap Memory (2048m) Hey Daniel Beck, I just want to make sure that we're not handling two different issues here. Despite the common symptoms, it might be a totally different issue. I have a generated heap dump (.hprof); will that be of equivalent value to providing a threadDump? (it's ~ 1.8GB) I have already added an attachment which shows the memory profile (memory.png). I will be enabling the support plugin and performing the action item you asked for. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-34350) CSRF breaks generic polling skipper /git/notifyCommit?url=
Title: Message Title Daniel Beck commented on JENKINS-34350 Re: CSRF breaks generic polling skipper /git/notifyCommit?url=""> What container is this running on? IIRC I've seen a case of a borked Tomcat config before that caused something similar to break. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-34659) Add support for "Dedicated Host" option
Title: Message Title Mike Dougherty created an issue Jenkins / JENKINS-34659 Add support for "Dedicated Host" option Issue Type: New Feature Assignee: Francis Upton Components: ec2-plugin Created: 2016/May/06 11:36 PM Priority: Major Reporter: Mike Dougherty I see in JENKINS-22141 "Dedicated Tenancy" was added, but there is also a "Dedicated Host" option when creating a host on EC2, which is (as I understand it) physical hardware. It would be helpful if the EC2 plugin supported this as well. Note: In the EC2 web UI, this is offered as a drop-down list option with values "Shared", "Dedicated" and "Dedicated Host". It would be great if the Jenkins UI used a similar UI element and wording. This effectively means the checkbox from JENKINS-22141 would be replaced with the drop-down list. Add Comment
[JIRA] [security] (JENKINS-31612) Stack trace shown with suppress-stack-trace plugin installed
Title: Message Title Daniel Beck commented on JENKINS-31612 Re: Stack trace shown with suppress-stack-trace plugin installed I used the URL shown in the screenshot (doUninstall) rather than the credentials store, due to less dependencies (Credentials Plugin 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] [security] (JENKINS-31612) Stack trace shown with suppress-stack-trace plugin installed
Title: Message Title Daniel Beck commented on JENKINS-31612 Re: Stack trace shown with suppress-stack-trace plugin installed I am unable to reproduce this problem in Jenkins 1.642.2 using a user with Overall/Read permission only. The page just shows "username is missing the Overall/Administer permission", with or without the Suppress Stacktrace Plugin. Security realm is PAM, authorization strategy is Matrix Auth. 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-34573) Running out of Heap Memory (2048m)
Title: Message Title Daniel Beck commented on JENKINS-34573 Re: Running out of Heap Memory (2048m) Alexandr Bykov Thanks, looking. Unfortunately the plugins haven't had time to collect interesting looking data, the heap stats also look rather healthy. Will be more informative once there's the first OOM error. Please note that the support bundle contains the Jenkins admin password, as well as the HTTP keystore password, as they're command line arguments to Jenkins that get logged, so I recommend you consider changing those. 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] [script-security-plugin] (JENKINS-34658) Whitelist more Functions for trivial operations on builtin types
Title: Message Title Norbert Lange created an issue Jenkins / JENKINS-34658 Whitelist more Functions for trivial operations on builtin types Issue Type: Improvement Assignee: Jesse Glick Components: script-security-plugin Created: 2016/May/06 11:08 PM Priority: Minor Reporter: Norbert Lange I have problems writing pipeline Scripts without having to approve several functions that are rather trivial operations of the most basic types. List of approvals follows, and some short fragments showing some code fragments using them. method java.lang.Object clone method java.util.Map putAll java.util.Map new java.util.AbstractMap$SimpleImmutableEntry java.lang.Object java.lang.Object new java.util.AbstractMap$SimpleEntry java.lang.Object java.lang.Object staticMethod org.codehaus.groovy.runtime.DefaultGroovyMethods minus java.lang.String java.lang.Object staticMethod org.codehaus.groovy.runtime.DefaultGroovyMethods plus java.util.Map java.util.Map // String minus operator def file = "foo.exe" def base = file - ".exe" Cloning a Map, so you can have a template and change fields without modifying the original.
[JIRA] [git-plugin] (JENKINS-32023) %d returns timestamp 0000 as of Jenkins 1.625.1
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-32023 %d returns timestamp as of Jenkins 1.625.1 Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-34165) Null pointer exception polling from git job to bitbucket repo
Title: Message Title Mark Waite commented on JENKINS-34165 Re: Null pointer exception polling from git job to bitbucket repo Looking at the code, it might be that the slave which last built that job has ceased to exist. Any chance in your use case that you have slaves which exist for a build, but then are deleted before the next build of that job? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-34350) CSRF breaks generic polling skipper /git/notifyCommit?url=
Title: Message Title Mark Waite edited a comment on JENKINS-34350 Re: CSRF breaks generic polling skipper /git/notifyCommit?url=""> [~jieryn] I don't think there is anything to roll back. When I check the latest LTS release of Jenkins 1 (1.651.*), it behaved the same as Jenkins 2.0. In both cases, CSRF protection did not stop my jobs from being run when the notifyCommit was called.What Jenkins version are you running?Can you see anything different about how you're using notifyCommit in your environment, compared to how I used it in my test case (described [above|https://issues.jenkins-ci.org/browse/JENKINS-34350?focusedCommentId=255977=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-255977])? If you have different steps which show the failure, please include them in a comment and reopen this bug. 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-34309) git-client-plugin: StringIndexOutOfBoundsException when parsing branches
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-34309 git-client-plugin: StringIndexOutOfBoundsException when parsing branches Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-34350) CSRF breaks generic polling skipper /git/notifyCommit?url=
Title: Message Title Mark Waite edited a comment on JENKINS-34350 Re: CSRF breaks generic polling skipper /git/notifyCommit?url=""> [~jieryn] I don't think there is anything to roll back. When I check the latest LTS release of Jenkins 1 (1.651.*), it behaved the same as Jenkins 2.0. In both cases, CSRF protection did not stop my jobs from being run when the notifyCommit was called.What Jenkins version are you running?Can you see anything different about how you're using notifyCommit in your environment, compared to how I used it in my test case (described [above|https://issues.jenkins-ci.org/browse/JENKINS-34350?focusedCommentId=255977=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-255977]) ? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-34350) CSRF breaks generic polling skipper /git/notifyCommit?url=
Title: Message Title Mark Waite commented on JENKINS-34350 Re: CSRF breaks generic polling skipper /git/notifyCommit?url=""> jieryn I don't think there is anything to roll back. When I check the latest LTS release of Jenkins 1 (1.651.*), it behaved the same as Jenkins 2.0. In both cases, CSRF protection did not stop my jobs from being run when the notifyCommit was called. What Jenkins version are you running? Can you see anything different about how you're using notifyCommit in your environment, compared to how I used it in my test case (described above) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-34350) CSRF breaks generic polling skipper /git/notifyCommit?url=
Title: Message Title
Mark Waite edited a comment on JENKINS-34350
Re: CSRF breaks generic polling skipper /git/notifyCommit?url="">
I don't see any failure related to honoring http requests submitted to Jenkins through http://debian8.markwaite.net:8080/git/notifyCommit?url="" />Steps I used to try to duplicate the problem:# Run jenkins 2.0 from docker commit e77dae5{code}docker run -p 8080:8080 -p 5:5 jenkins{code}# Install only the git plugin (assuming other plugins might inadvertently provide a CrumbExclusion)# Configure a job which uses a git repo and polls SCM with no schedule# Use curl to "prod" that server {code:java}curl -s http://debian8.markwaite.net:8080/git/notifyCommit?url="" />{code}When I do that, the job is consistently started the first time (no build available), and on each change that I make to the test repository after I run that curl command. As far as I can tell, CSRF for the git/notfiyCommit is already excluded for Jenkins 2.0. Same behavior was seen with Jenkins 1.651.1 when I tested it.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27392) API to decorate console output
Title: Message Title Sam Gleske commented on JENKINS-27392 Re: API to decorate console output I encounter the same bug. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-34350) CSRF breaks generic polling skipper /git/notifyCommit?url=
Title: Message Title jieryn commented on JENKINS-34350 Re: CSRF breaks generic polling skipper /git/notifyCommit?url=""> Any chance for a rollback? Because we don't plan to migrate to 2.0 anytime soon. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-34350) CSRF breaks generic polling skipper /git/notifyCommit?url=
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-34350
CSRF breaks generic polling skipper /git/notifyCommit?url="">
Change By:
Mark Waite
Comment:
It appears that the recommendation from [~jglick] in a [comment|https://issues.jenkins-ci.org/browse/JENKINS-10263?focusedCommentId=210374=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-210374] to JENKINS-10263 was implemented in Jenkins 2.0 and in Jenkins 1.651.1 to cause all 'UnprotectedRootAction' to automatically have a CrumbExclusion.I tried the same steps with Jenkins 1.651.1 and was able to confirm that the request to git/notifyCommit is honored if CSRF protection is enabled. The steps I took to show the problem with Jenkins 1.651.1 were:# Run jenkins 1.651.1 from docker{code}docker run -p 8080:8080 -p 5:5 jenkins:1.651.1{code}# Enable CSRF protection from "Manage Jenkins", "Configure Global Security", "Prevent Cross Site Request Forgery exploits", and enable "Default crumb issuer"# Configure a job which uses a git repo and has "Poll SCM" enabled with no schedule# Use curl to "prod" that server{code}curl -s http://debian8:8080/git/notifyCommit?url="" />{code}# Confirmed that the job ran even though CSRF protection was enabledWhen I do that, the job starts on initial poll (before the job exists) and on changes to the repository (so long as the notifyCommit is called).
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
[JIRA] [git-plugin] (JENKINS-34350) CSRF breaks generic polling skipper /git/notifyCommit?url=
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-34350
CSRF breaks generic polling skipper /git/notifyCommit?url="">
Change By:
Mark Waite
Comment:
It appears that the recommendation from [~jglick] in a [comment|https://issues.jenkins-ci.org/browse/JENKINS-10263?focusedCommentId=210374=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-210374] to JENKINS-10263 was implemented in Jenkins 2.0 to cause all 'UnprotectedRootAction' to automatically have a CrumbExclusion.I tried the same steps with Jenkins 1.651.1 and was able to confirm that the request to git/notifyCommit is ignored if CSRF protection is enabled. The steps I took to show the problem with Jenkins 1.651.1 were:# Run jenkins 1.651.1 from docker{code}docker run -p 8080:8080 -p 5:5 jenkins:1.651.1{code}# Enable CSRF protection from "Manage Jenkins", "Configure Global Security", "Prevent Cross Site Request Forgery exploits", and enable "Default crumb issuer"# Configure a job which uses a git repo and has "Poll SCM" enabled with no schedule# Use curl to "prod" that server{code}curl -s http://debian8:8080/git/notifyCommit?url="" />{code}When I do that, the job does not start.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-34540) Can't use Pipeline Parameter in Branch Specifier on Jenkins 2.0/2.1
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-34540 Can't use Pipeline Parameter in Branch Specifier on Jenkins 2.0/2.1 Change By: Mark Waite Assignee: Mark Waite 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-34657) Ensure that appropriate plugins are able to be used within Pipeline DSL
Title: Message Title Patrick Wolf updated an issue Jenkins / JENKINS-34657 Ensure that appropriate plugins are able to be used within Pipeline DSL Change By: Patrick Wolf Summary: Ensure that all appropriate plugins are able to be used within Pipeline DSL 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-34657) Ensure that all plugins are able to be used within Pipeline DSL
Title: Message Title Patrick Wolf updated an issue Jenkins / JENKINS-34657 Ensure that all plugins are able to be used within Pipeline DSL Change By: Patrick Wolf For architectural reasons, plugins providing various extensions of interest to builds cannot be made automatically compatible with Pipeline. Typically they require use of some newer APIs, large or small (see the bottom of this document for details). This document captures the ongoing status of plugins known to be compatible or incompatible.https://github.com/jenkinsci/pipeline-plugin/blob/master/DEVGUIDE.md https://www.youtube.com/watch?v=4zdy7XGx3PA 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-34657) Ensure that all plugins are able to be used within Pipeline DSL
Title: Message Title Patrick Wolf assigned an issue to Patrick Wolf Jenkins / JENKINS-34657 Ensure that all plugins are able to be used within Pipeline DSL Change By: Patrick Wolf Assignee: Jesse Glick Patrick Wolf 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-organization-folder-plugin] (JENKINS-34612) Jenkins 2.1 not registering GitHub org webhooks: "WARNING: Failed to register GitHub Org hook to ..."
Title: Message Title Simon So commented on JENKINS-34612 Re: Jenkins 2.1 not registering GitHub org webhooks: "WARNING: Failed to register GitHub Org hook to ..." Unbelievable. Thank you karlmdavis! Cost me probably a day as well, could have been worse! 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] [port-allocator-plugin] (JENKINS-31449) Port Allocator Pipeline support
Title: Message Title Patrick Wolf updated an issue Jenkins / JENKINS-31449 Port Allocator Pipeline support Change By: Patrick Wolf Summary: workflow Port Allocator Pipeline support 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-34657) Ensure that all plugins are able to be used within Pipeline DSL
Title: Message Title Patrick Wolf created an issue Jenkins / JENKINS-34657 Ensure that all plugins are able to be used within Pipeline DSL Issue Type: Epic Assignee: Jesse Glick Components: workflow-plugin Created: 2016/May/06 9:12 PM Priority: Minor Reporter: Patrick Wolf For architectural reasons, plugins providing various extensions of interest to builds cannot be made automatically compatible with Pipeline. Typically they require use of some newer APIs, large or small (see the bottom of this document for details). This document captures the ongoing status of plugins known to be compatible or incompatible. https://github.com/jenkinsci/pipeline-plugin/blob/master/DEVGUIDE.md Add Comment
[JIRA] [cmakebuilder-plugin] (JENKINS-34613) Set default value of Generator in Java instead of jelly, for improved usability in pipeline plugin
Title: Message Title Martin Weber closed an issue as Fixed Jenkins / JENKINS-34613 Set default value of Generator in Java instead of jelly, for improved usability in pipeline plugin Change By: Martin Weber Status: In Progress Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudfoundry-plugin] (JENKINS-34656) Plugin installed but not visible
Title: Message Title Brian Hegerty created an issue Jenkins / JENKINS-34656 Plugin installed but not visible Issue Type: Bug Assignee: William Gautier Components: cloudfoundry-plugin Created: 2016/May/06 8:36 PM Environment: RHEL 6.7 Jenkins 1.609 Cloud Foundry Plugin 1.5 Credentials Plugin 1.28 Token Macro Plugin 1.12.1 Priority: Major Reporter: Brian Hegerty I've installed the cloud foundry plugin and it shows as installed, but no option for "Push to Cloud Foundry" exists in the post build actions. The dependency plugins are also installed and functioning. I'm not sure what I'm not doing. I installed the plugin and restarted, then I uninstalled it and installed it manually with the hpi file and restarted. Neither way shows any difference (cloud foundry plugin shows as installed, no option in post build actions).
[JIRA] [cmakebuilder-plugin] (JENKINS-34613) Set default value of Generator in Java instead of jelly, for improved usability in pipeline plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34613 Re: Set default value of Generator in Java instead of jelly, for improved usability in pipeline plugin Code changed in jenkins User: 15knots Path: src/main/java/hudson/plugins/cmake/CmakeBuilder.java src/main/resources/hudson/plugins/cmake/CmakeBuilder/config.jelly src/test/java/hudson/plugins/cmake/CmakeBuilderBuildTest.java src/test/java/hudson/plugins/cmake/CmakeBuilderFormRoundTripTest.java src/test/java/hudson/plugins/cmake/CmakeBuilderTest.java http://jenkins-ci.org/commit/cmakebuilder-plugin/7fc4866e02c0bf6ec847a2bce5363153bddf688b Log: FIXED JENKINS-34613 Set default value of Generator in Java instead of jelly, for improved usability in pipeline plugin Compare: https://github.com/jenkinsci/cmakebuilder-plugin/compare/bfe1506a258e...7fc4866e02c0 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-34655) Build icon not shown in Pull Requests Dashboard
Title: Message Title Nathanial Woolls created an issue Jenkins / JENKINS-34655 Build icon not shown in Pull Requests Dashboard Issue Type: Improvement Assignee: Antonio Mansilla Components: bitbucket-build-status-notifier-plugin Created: 2016/May/06 8:24 PM Environment: Jenkins ver. 1.629 Labels: plugin Priority: Minor Reporter: Nathanial Woolls The plugin works great and posts an icon to both the Branches page and the Pull Requests page for the repo in question. However, the build icon does not show on the Pull Requests Dashboard page: https://bitbucket.org/dashboard/pullrequests
[JIRA] [git-parameter-plugin] (JENKINS-33584) git-parameter-plugin cannot fetch tags from other repositories
Title: Message Title Boguslaw Klimas commented on JENKINS-33584 Re: git-parameter-plugin cannot fetch tags from other repositories Hi @Daniel Bengtsson, Problem "You must first trigger a build if your workspace is empty. The list to choose from will be empty." I have fixed locally and testing it. In the next release I will push this fix in repository. "And we do need to list tags from all of them." All tags on one list? In java code It is selected, only the first repository. 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-parameter-plugin] (JENKINS-31939) The top value is better to be chosed by default of to have such option
Title: Message Title Dan Doyle commented on JENKINS-31939 Re: The top value is better to be chosed by default of to have such option That sounds good to me! Thanks for the quick response. 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] [cmakebuilder-plugin] (JENKINS-34613) Set default value of Generator in Java instead of jelly, for improved usability in pipeline plugin
Title: Message Title Martin Weber started work on JENKINS-34613 Change By: Martin Weber 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] [docker-workflow-plugin] (JENKINS-34654) support copy file from image
Title: Message Title Nicolas De Loof created an issue Jenkins / JENKINS-34654 support copy file from image Issue Type: New Feature Assignee: Jesse Glick Components: docker-workflow-plugin Created: 2016/May/06 7:48 PM Priority: Minor Reporter: Nicolas De Loof Using Docker to control environment is great, but one does not want all build tools, source code and test results to be part of production image. So the need for a multi-step docker build (see https://github.com/docker/docker/issues/7115) I use to have two Dockerfiles, one to build form source, the second to package binary into production environment. In the middle I need to get binaries from the build image to create second docker build context. As `docker cp` does not support copy from image (https://github.com/docker/docker/issues/7710) I have to create a container, copy, delete container. Would be nice for docker-pipeline to make this simple by offering a `cp` method on image. Add Comment
[JIRA] [git-parameter-plugin] (JENKINS-31939) The top value is better to be chosed by default of to have such option
Title: Message Title
Boguslaw Klimas edited a comment on JENKINS-31939
Re: The top value is better to be chosed by default of to have such option
Hi,@[~daldoyle] [~slavik334]This change was not fully thought through, but in next release I will add configuration parameter"Selected value" which will have value: "none, top, default" (default will by 'none') and help description. "Which value is selected, after loaded parameters". I think this good resolving, do you agree with me?@[~slavik334]Selecting values is realized in java script on browser. When you run job by timer plugin returned default value or blank when you not set default value, because Jenkins invoke method{code:java}@Overridepublic ParameterValue getDefaultParameterValue(){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] [git-parameter-plugin] (JENKINS-31939) The top value is better to be chosed by default of to have such option
Title: Message Title Boguslaw Klimas commented on JENKINS-31939 Re: The top value is better to be chosed by default of to have such option Hi, @Dan Doyle Viachaslau Kabak This change was not fully thought through, but in next release I will add configuration parameter "Selected value" which will have value: "none, top, default" (default will by 'none') and help description. "Which value is selected, after loaded parameters". I think this good resolving, do you agree with me? @Viachaslau Kabak Selecting values is realized in _javascript_ on browser. When you run job by timer plugin returned default value or blank when you not set default value, because invoke method @Override public ParameterValue getDefaultParameterValue() Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-credentials-plugin] (JENKINS-34653) nullpointerexception
Title: Message Title
Jeff Blaine updated an issue
Jenkins / JENKINS-34653
nullpointerexception
Change By:
Jeff Blaine
Jenkins 1.658 and SSH Credentials 1.10 and 1.11 The command: {{/usr/lib/jvm/java-1.8.0/bin/java -jar /var/chef/cache/jenkins-cli.jar -s http://jenkins.our.org:8080 -i /var/chef/cache/jenkins-key groovy /tmp/groovy20160506-13473-xnbfhf}}Where {{/tmp/groovy20160506-13473-xnbfhf}} consists of:{code}import com.cloudbees.plugins.credentials.impl.*;import com.cloudbees.jenkins.plugins.sshcredentials.impl.*;import jenkins.model.*import com.cloudbees.plugins.credentials.*import com.cloudbees.plugins.credentials.common.*import com.cloudbees.plugins.credentials.domains.*;username_matcher = CredentialsMatchers.withUsername("jenkins")available_credentials = CredentialsProvider.lookupCredentials(StandardUsernameCredentials.class,Jenkins.getInstance(),hudson.security.ACL.SYSTEM,new SchemeRequirement("ssh") )credentials = CredentialsMatchers.firstOrNull(available_credentials,username_matcher )if (credentials == null) { return null}current_credentials = [ id:credentials.id, description:credentials.description, username:credentials.username]current_credentials['private_key'] = credentials.privateKeycurrent_credentials['passphrase'] = credentials.passphrase.plainTextbuilder = new groovy.json.JsonBuilder(current_credentials)println(builder){code}Results in:{code}java.lang.NullPointerException at com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey.getPrivateKeys(BasicSSHUserPrivateKey.java:127) at com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey.getPrivateKey(BasicSSHUserPrivateKey.java:121) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233) at groovy.lang.MetaClassImpl$GetBeanMethodMetaProperty.getProperty(MetaClassImpl.java:3500) at org.codehaus.groovy.runtime.callsite.GetEffectivePojoPropertySite.getProperty(GetEffectivePojoPropertySite.java:61) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGetProperty(AbstractCallSite.java:227) at RemoteClass.run(RemoteClass:35) at groovy.lang.GroovyShell.runScriptOrMainOrTestOrRunnable(GroovyShell.java:266) at groovy.lang.GroovyShell.run(GroovyShell.java:517) at hudson.cli.GroovyCommand.run(GroovyCommand.java:86) at hudson.cli.CLICommand.main(CLICommand.java:256) at hudson.cli.CliManagerImpl.main(CliManagerImpl.java:92) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at
[JIRA] [ssh-credentials-plugin] (JENKINS-34653) nullpointerexception
Title: Message Title
Jeff Blaine created an issue
Jenkins / JENKINS-34653
nullpointerexception
Issue Type:
Bug
Assignee:
stephenconnolly
Components:
ssh-credentials-plugin
Created:
2016/May/06 7:33 PM
Labels:
credentials
Priority:
Major
Reporter:
Jeff Blaine
The command: /usr/lib/jvm/java-1.8.0/bin/java -jar /var/chef/cache/jenkins-cli.jar -s http://jenkins.our.org:8080 -i /var/chef/cache/jenkins-key groovy /tmp/groovy20160506-13473-xnbfhf
Where /tmp/groovy20160506-13473-xnbfhf consists of:
import com.cloudbees.plugins.credentials.impl.*;
import com.cloudbees.jenkins.plugins.sshcredentials.impl.*;
import jenkins.model.*
import com.cloudbees.plugins.credentials.*
import com.cloudbees.plugins.credentials.common.*
import com.cloudbees.plugins.credentials.domains.*;
username_matcher = CredentialsMatchers.withUsername("jenkins")
available_credentials =
CredentialsProvider.lookupCredentials(
StandardUsernameCredentials.class,
Jenkins.getInstance(),
hudson.security.ACL.SYSTEM,
new SchemeRequirement("ssh")
)
credentials =
[JIRA] [cloud-stats-plugin] (JENKINS-33780) Listener for slave creation/deletion/update.
Title: Message Title Oliver Gondža started work on JENKINS-33780 Change By: Oliver Gondža Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [saltstack-plugin] (JENKINS-34535) net.sf.json.JSONException: JSONObject["result"] is not a Boolean
Title: Message Title Christian McHugh closed an issue as Fixed Handed in 9d93e179 Jenkins / JENKINS-34535 net.sf.json.JSONException: JSONObject["result"] is not a Boolean Change By: Christian McHugh Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [saltstack-plugin] (JENKINS-34535) net.sf.json.JSONException: JSONObject["result"] is not a Boolean
Title: Message Title Christian McHugh commented on JENKINS-34535 Re: net.sf.json.JSONException: JSONObject["result"] is not a Boolean As mentioned, performing a state.highstate test=True causes the results key to equal "null". This situation is now tested for and handled as of 9d93e179 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] [saltstack-plugin] (JENKINS-34535) net.sf.json.JSONException: JSONObject["result"] is not a Boolean
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34535 Re: net.sf.json.JSONException: JSONObject["result"] is not a Boolean Code changed in jenkins User: Christian McHugh Path: src/main/java/com/waytta/Utils.java src/test/java/com/waytta/UtilsTest.java http://jenkins-ci.org/commit/saltstack-plugin/9d93e17995a4a86fec1cfee70b2f117dc9c49c13 Log: Properly detect scenario where highstate would create changes and test=True. This causes the minion result key = "null" instead of a boolean. Closes JENKINS-34535 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-34652) Support for parameter in commit revision
Title: Message Title James Douglass closed an issue as Duplicate accidentally submitted twice! Jenkins / JENKINS-34652 Support for parameter in commit revision Change By: James Douglass Status: Open Closed Assignee: Antonio Mansilla 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] [bitbucket-build-status-notifier-plugin] (JENKINS-34652) Support for parameter in commit revision
Title: Message Title James Douglass commented on JENKINS-34652 Re: Support for parameter in commit revision Whoops ... I accidentally submitted this twice. Sorry! 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-34652) Support for parameter in commit revision
Title: Message Title James Douglass created an issue Jenkins / JENKINS-34652 Support for parameter in commit revision Issue Type: Improvement Assignee: Antonio Mansilla Components: bitbucket-build-status-notifier-plugin Created: 2016/May/06 6:23 PM Environment: Jenkins 1.580.2 Bitbucket build status notifier plugin 1.2.0 Priority: Minor Reporter: James Douglass This plugin works flawlessly, but it appears to only work if the `revision` string is interpreted as a string, and not evaluated (such as if a variable is provided) So if I use a specific revision (e.g. develop or tip), the build status is reported correctly. If I use a variable, however (such as with a build parameter), the build status is not posted correctly. In the job's console log, this message is posted: Sending build status INPROGRESS for commit $VERSION to BitBucket is done!. $VERSION is the variable that I'm using. In the system log, this message is posted: May 06, 2016 4:41:31 PM INFO org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifier perform Bitbucket notify on finish May 06, 2016 4:41:31 PM INFO
[JIRA] [bitbucket-build-status-notifier-plugin] (JENKINS-34651) Support for parameter in commit revision
Title: Message Title James Douglass created an issue Jenkins / JENKINS-34651 Support for parameter in commit revision Issue Type: Improvement Assignee: Antonio Mansilla Components: bitbucket-build-status-notifier-plugin Created: 2016/May/06 6:20 PM Environment: Jenkins 1.580.2 Bitbucket build status notifier plugin 1.2.0 Priority: Minor Reporter: James Douglass This plugin works flawlessly, but it appears to only work if the `revision` string is interpreted as a string, and not evaluated (such as if a variable is provided) So if I use a specific revision (e.g. develop or tip), the build status is reported correctly. If I use a variable, however (such as with a build parameter), the build status is not posted correctly. In the job's console log, this message is posted: Sending build status INPROGRESS for commit $VERSION to BitBucket is done!. $VERSION is the variable that I'm using. In the system log, this message is posted: May 06, 2016 4:41:31 PM INFO org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifier perform Bitbucket notify on finish May 06, 2016 4:41:31 PM INFO
[JIRA] [htmlpublisher-plugin] (JENKINS-34557) HTML report does not show "table & color"
Title: Message Title mcrooney closed an issue as Not A Defect Jenkins / JENKINS-34557 HTML report does not show "table & color" Change By: mcrooney Status: Open Closed 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] [htmlpublisher-plugin] (JENKINS-34557) HTML report does not show "table & color"
Title: Message Title mcrooney commented on JENKINS-34557 Re: HTML report does not show "table & color" Thanks Bo, please read the full page. This is due to your Jenkins version, and you'll need at least HTML Publisher 1.10. You'll have to modify your Jenkins settings to allow your _javascript_ and CSS. It works in IE because IE doesn't support CSP (Content Security Policy). 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] [other] (JENKINS-34608) Unable to save or to apply Configure System after upgrading to 2.1
Title: Message Title Basile Baranetskyy commented on JENKINS-34608 Re: Unable to save or to apply Configure System after upgrading to 2.1 No. How to demo: Open Chromium Navigate to the http://172.29.0.233:8080/configure Change a parameter or not (e.g. test connection on git lab plugin) Ctrl+Shift+J Click on save Only post error on 400 (Bad request) Else I can join the event log normal like as: prototype.js:1585 XHR finished loading: POST "http://172.29.0.233:8080/ajaxBuildQueue". prototype.js:1585 XHR finished loading: POST "http://172.29.0.233:8080/ajaxExecutors". 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
[JIRA] [cmakebuilder-plugin] (JENKINS-34613) Set default value of Generator in Java instead of jelly, for improved usability in pipeline plugin
Title: Message Title Martin Weber updated an issue Jenkins / JENKINS-34613 Set default value of Generator in Java instead of jelly, for improved usability in pipeline plugin Change By: Martin Weber Summary: Set default value of BuildType Generator in Java instead of jelly, for improved usability in pipeline plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-15331) Workaround Windows unpredictable file locking in Util.deleteContentsRecursive
Title: Message Title James Brown updated an issue Jenkins / JENKINS-15331 Workaround Windows unpredictable file locking in Util.deleteContentsRecursive Change By: James Brown Labels: lts-candidate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-34573) Running out of Heap Memory (2048m)
Title: Message Title Raymond Accary updated an issue Jenkins / JENKINS-34573 Running out of Heap Memory (2048m) GC was run during multiple peaks to avoid a crash. Change By: Raymond Accary Attachment: memory.png 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-34573) Running out of Heap Memory (2048m)
Title: Message Title Raymond Accary updated an issue Jenkins / JENKINS-34573 Running out of Heap Memory (2048m) Change By: Raymond Accary Comment: GC was run during multiple peaks to avoid a crash. 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-34650) Allow global libraries to bypass the sandbox
Title: Message Title Jesse Glick commented on JENKINS-34650 Re: Allow global libraries to bypass the sandbox JENKINS-26538 requests the converse, in a sense: libraries that regular users could upload but which could not run unsafe methods. 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-34650) Allow global libraries to bypass the sandbox
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-34650 Allow global libraries to bypass the sandbox Issue Type: New Feature Assignee: Kohsuke Kawaguchi Components: workflow-plugin Created: 2016/May/06 4:39 PM Labels: groovy permissions Priority: Major Reporter: Jesse Glick Although you are required to have RUN_SCRIPTS to push anything to workflowLibs, the code is run under the same sandbox settings as the main Pipeline scripts. In the case of a Pipeline script using whole-script approval, it makes sense to be checking RUN_SCRIPTS for libraries. But in the case of Pipeline scripts configured to use the Groovy sandbox, the workflowLibs code is also run in the sandbox—a pointless restriction, since only a trusted user could have written that code. You would expect that the library code would be trusted and run in a privileged mode, so it could safely encapsulate otherwise unsafe method calls.
[JIRA] [support-core-plugin] (JENKINS-21670) Option to anonymize customer labels
Title: Message Title Arnaud Héritier assigned an issue to Minudika Malshan Jenkins / JENKINS-21670 Option to anonymize customer labels Change By: Arnaud Héritier Assignee: Minudika Malshan 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] [support-core-plugin] (JENKINS-33091) Allow to create an issue and submit a bundle into the OSS tracker
Title: Message Title Arnaud Héritier assigned an issue to Minudika Malshan Jenkins / JENKINS-33091 Allow to create an issue and submit a bundle into the OSS tracker Change By: Arnaud Héritier Assignee: Steven Christou Minudika Malshan 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] [support-core-plugin] (JENKINS-33090) Ease the management bundles by the administrator
Title: Message Title Arnaud Héritier assigned an issue to Minudika Malshan Jenkins / JENKINS-33090 Ease the management bundles by the administrator Change By: Arnaud Héritier Assignee: Steven Christou Minudika Malshan Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-33734) P4 Plugin does not reload UI configuration using the Pipeline Workflow
Title: Message Title Russell Gallop updated an issue Jenkins / JENKINS-33734 P4 Plugin does not reload UI configuration using the Pipeline Workflow I'm not the original reporter but here's a config file from me, with which I see the same symptom. I obfuscated the depot path and the p4_credentials. jenkins 1.642.4 p4 plugin 1.3.8 workflow-aggregator 2.0 Change By: Russell Gallop Attachment: config_ob.xml 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-34649) Get ssh public keys from github as well
Title: Message Title Sam Gleske commented on JENKINS-34649 Re: Get ssh public keys from github as well This is a welcome idea. Contributions are welcome as well. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-oauth-plugin] (JENKINS-34649) Get ssh public keys from github as well
Title: Message Title Christian Höltje created an issue Jenkins / JENKINS-34649 Get ssh public keys from github as well Issue Type: New Feature Assignee: Sam Gleske Components: github-oauth-plugin Created: 2016/May/06 4:26 PM Environment: Jenkins-Version: 1.651.1 github-api: 1.75 github: 1.19.0 github-oauth: 0.23 Priority: Minor Reporter: Christian Höltje Github has SSH public keys already. The Github OAuth plugin should fetch them from github and add them to user accounts automagically. Add Comment
[JIRA] [android-emulator-plugin] (JENKINS-31501) Jenkins fails to connect to running emulator
Title: Message Title Hugo Freire commented on JENKINS-31501 Re: Jenkins fails to connect to running emulator Same problem here with plugin 2.14.1. I can send any information do you need. 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] [itemcategories-plugin] (JENKINS-34648) Cannot create new items after upgrade to 2.1
Title: Message Title
Yannick Marcon updated an issue
Jenkins / JENKINS-34648
Cannot create new items after upgrade to 2.1
Change By:
Yannick Marcon
I just upgraded from version 1.558 to 2.1 and after restart I have some NoSuchMethodError errors. When clicking on "New Item", the resulting page is blank and the same error appear in the logs. The rest of the application seems to be operational. {code} WARNING: Error while serving https://ci.obiba.org/view/All/itemCategories... java.lang.NoSuchMethodError: hudson.model.Messages.ExternalJob_DisplayName()Ljava/lang/String; at hudson.model.ExternalJob$DescriptorImpl.getDisplayName(ExternalJob.java:132) at hudson.ExtensionComponent.compareTo(ExtensionComponent.java:97) at hudson.ExtensionComponent.compareTo(ExtensionComponent.java:42) at java.util.ComparableTimSort.binarySort(ComparableTimSort.java:258) at java.util.ComparableTimSort.sort(ComparableTimSort.java:203) at java.util.Arrays.sort(Arrays.java:1312) at java.util.Arrays.sort(Arrays.java:1506) at java.util.ArrayList.sort(ArrayList.java:1454) at java.util.Collections.sort(Collections.java:141) at hudson.ExtensionList.sort(ExtensionList.java:369) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:289) at hudson.ExtensionList.getComponents(ExtensionList.java:167) at hudson.DescriptorExtensionList.load(DescriptorExtensionList.java:185) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:287) at hudson.ExtensionList.iterator(ExtensionList.java:156) at hudson.ExtensionList.get(ExtensionList.java:147) at com.cloudbees.jenkins.GitHubPushTrigger$DescriptorImpl.get(GitHubPushTrigger.java:329) at org.jenkinsci.plugins.github.migration.Migrator.migrate(Migrator.java:40) at org.jenkinsci.plugins.github.GitHubPlugin.postInitialize(GitHubPlugin.java:39) at hudson.PluginManager$2$1$2.run(PluginManager.java:433) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$8.runTask(Jenkins.java:1011) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745){code} When clicking on "New Item", the resulting page is blank and the same error appear in the logs. The rest of the application seems to be operational.{code}WARNING: Error while serving https://ci.obiba.org/view/All/itemCategories...Caused by: java.lang.NoSuchMethodError: hudson.model.Messages.ExternalJob_DisplayName()Ljava/lang/String; at hudson.model.ExternalJob$DescriptorImpl.getDisplayName(ExternalJob.java:132) at hudson.model.View.doItemCategories(View.java:1058) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:320) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:163) at
[JIRA] [core] (JENKINS-34646) High CPU Usage navigating the UI
Title: Message Title Luigi Tagliamonte updated an issue Jenkins / JENKINS-34646 High CPU Usage navigating the UI Change By: Luigi Tagliamonte I'm using the official docker image, no customisation.After the update to the 2.0, the Jenkins CPU usage has increased from near 2% to 40%.I get CPU spikes navigating the UI for example in http:///configure , the scheduled job seems not to have this behaviours. 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] [itemcategories-plugin] (JENKINS-34648) Cannot create new items after upgrade to 2.1
Title: Message Title
Yannick Marcon updated an issue
Jenkins / JENKINS-34648
Cannot create new items after upgrade to 2.1
Change By:
Yannick Marcon
I just upgraded from version 1.558 to 2.1 and after restart I have some NoSuchMethodError errors.When clicking on "New Item", the resulting page is blank and the same error appear in the logs. The rest of the application seems to be operational.{code} WARNING: Error while serving https://ci.obiba.org/view/All/itemCategories... java.lang.NoSuchMethodError: hudson.model.Messages.ExternalJob_DisplayName()Ljava/lang/String; at hudson.model.ExternalJob$DescriptorImpl.getDisplayName(ExternalJob.java:132) at hudson.ExtensionComponent.compareTo(ExtensionComponent.java:97) at hudson.ExtensionComponent.compareTo(ExtensionComponent.java:42) at java.util.ComparableTimSort.binarySort(ComparableTimSort.java:258) at java.util.ComparableTimSort.sort(ComparableTimSort.java:203) at java.util.Arrays.sort(Arrays.java:1312) at java.util.Arrays.sort(Arrays.java:1506) at java.util.ArrayList.sort(ArrayList.java:1454) at java.util.Collections.sort(Collections.java:141) at hudson.ExtensionList.sort(ExtensionList.java:369) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:289) at hudson.ExtensionList.getComponents(ExtensionList.java:167) at hudson.DescriptorExtensionList.load(DescriptorExtensionList.java:185) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:287) at hudson.ExtensionList.iterator(ExtensionList.java:156) at hudson.ExtensionList.get(ExtensionList.java:147) at com.cloudbees.jenkins.GitHubPushTrigger$DescriptorImpl.get(GitHubPushTrigger.java:329) at org.jenkinsci.plugins.github.migration.Migrator.migrate(Migrator.java:40) at org.jenkinsci.plugins.github.GitHubPlugin.postInitialize(GitHubPlugin.java:39) at hudson.PluginManager$2$1$2.run(PluginManager.java:433) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$8.runTask(Jenkins.java:1011) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745){code}I do not know if it's relevant but I can see other errors in the logs: {code}Caused by: java.lang.NullPointerExceptionat hudson.plugins.analysis.core.HealthReportBuilder.computeHealth(HealthReportBuilder.java:47)at hudson.plugins.analysis.core.AbstractResultAction.getBuildHealth(AbstractResultAction.java:87)at hudson.model.Job.getBuildHealthReports(Job.java:1122){code}
[JIRA] [itemcategories-plugin] (JENKINS-34648) Cannot create new items after upgrade to 2.1
Title: Message Title Yannick Marcon created an issue Jenkins / JENKINS-34648 Cannot create new items after upgrade to 2.1 Issue Type: Bug Assignee: Manuel Jesús Recena Soto Components: itemcategories-plugin Created: 2016/May/06 4:01 PM Environment: Install from debian package Priority: Critical Reporter: Yannick Marcon I just upgraded from version 1.558 to 2.1 and after restart I have some NoSuchMethodError errors. When clicking on "New Item", the resulting page is blank and the same error appear in the logs. The rest of the application seems to be operational. java.lang.NoSuchMethodError: hudson.model.Messages.ExternalJob_DisplayName()Ljava/lang/String; at hudson.model.ExternalJob$DescriptorImpl.getDisplayName(ExternalJob.java:132) at hudson.ExtensionComponent.compareTo(ExtensionComponent.java:97) at hudson.ExtensionComponent.compareTo(ExtensionComponent.java:42) at java.util.ComparableTimSort.binarySort(ComparableTimSort.java:258) at java.util.ComparableTimSort.sort(ComparableTimSort.java:203) at java.util.Arrays.sort(Arrays.java:1312) at java.util.Arrays.sort(Arrays.java:1506) at java.util.ArrayList.sort(ArrayList.java:1454) at java.util.Collections.sort(Collections.java:141) at
[JIRA] [durable-task-plugin] (JENKINS-34647) Migrate to 2.x parent pom
Title: Message Title Armando Fernandez started work on JENKINS-34647 Change By: Armando Fernandez 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] [durable-task-plugin] (JENKINS-34647) Migrate to 2.x parent pom
Title: Message Title Armando Fernandez created an issue Jenkins / JENKINS-34647 Migrate to 2.x parent pom Issue Type: Improvement Assignee: Armando Fernandez Components: durable-task-plugin Created: 2016/May/06 3:51 PM Priority: Minor Reporter: Armando Fernandez Migrate to 2.x parent pom Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [other] (JENKINS-34608) Unable to save or to apply Configure System after upgrading to 2.1
Title: Message Title Daniel Beck commented on JENKINS-34608 Re: Unable to save or to apply Configure System after upgrading to 2.1 Is there something missing from the JS? 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-34646) High CPU Usage navigating the UI
Title: Message Title Luigi Tagliamonte created an issue Jenkins / JENKINS-34646 High CPU Usage navigating the UI Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/May/06 3:50 PM Environment: Jenkins 2.0 Priority: Critical Reporter: Luigi Tagliamonte I'm using the official docker image, no customisation. After the update to the 2.0, the Jenkins CPU usage has increased from near 2% to 40%. I get CPU spikes navigating the UI, the scheduled job seems not to have this behaviours. Add Comment
[JIRA] [durable-task-plugin] (JENKINS-34150) Pipeline Batch hangs
Title: Message Title Nick Sonneveld commented on JENKINS-34150 Re: Pipeline Batch hangs There is a pull request being worked on by Martin Karing you might want to look at and comment on. Link is attached to this issue https://github.com/jenkinsci/durable-task-plugin/pull/21 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-33901) Bitbucket notifier plugin does not support SSH on port 443
Title: Message Title Antonio Mansilla commented on JENKINS-33901 Re: Bitbucket notifier plugin does not support SSH on port 443 Hi again Jean-Paul Delimat, I've fixed the bug and now your use case is supported. This changes will be available in the next plugin release. 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-33901) Bitbucket notifier plugin does not support SSH on port 443
Title: Message Title Antonio Mansilla resolved as Fixed Jenkins / JENKINS-33901 Bitbucket notifier plugin does not support SSH on port 443 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] [bitbucket-build-status-notifier-plugin] (JENKINS-33901) Bitbucket notifier plugin does not support SSH on port 443
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33901 Re: Bitbucket notifier plugin does not support SSH on port 443 Code changed in jenkins User: Antonio Mansilla Path: src/main/java/org/jenkinsci/plugins/bitbucket/BitbucketBuildStatusNotifier.java http://jenkins-ci.org/commit/bitbucket-build-status-notifier-plugin/feba62bf0558c7bb46118b66e9863cd479ffaa77 Log: JENKINS-33901 Add support for bitbucket ssh on port 443 Usable on servers where the outgoing traffic on port 22 is blocked and bitbucket supports that by providing an alternative URL scheme. More info: https://confluence.atlassian.com/bitbucket/use-the-ssh-protocol-with-bitbucket-cloud-221449711.html#UsetheSSHprotocolwithBitbucketCloud-SSHonPort443 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-33901) Bitbucket notifier plugin does not support SSH on port 443
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33901 Re: Bitbucket notifier plugin does not support SSH on port 443 Code changed in jenkins User: Antonio Mansilla Path: src/main/java/org/jenkinsci/plugins/bitbucket/validator/BitbucketHostValidator.java http://jenkins-ci.org/commit/bitbucket-build-status-notifier-plugin/ed13d4f626438c7258386ad824c720db160dafed Log: JENKINS-33901 Add bitbucket host validator 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-33901) Bitbucket notifier plugin does not support SSH on port 443
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33901 Re: Bitbucket notifier plugin does not support SSH on port 443 Code changed in jenkins User: Antonio Mansilla Path: src/main/java/org/jenkinsci/plugins/bitbucket/BitbucketBuildStatusNotifier.java src/main/java/org/jenkinsci/plugins/bitbucket/validator/BitbucketHostValidator.java http://jenkins-ci.org/commit/bitbucket-build-status-notifier-plugin/66a0a89267653818d55c0276a6a98b365b04206e Log: Merge pull request #20 from Flagbit/flagbit-33901 Fix JENKINS-33901 add support for ssh on 443 port Compare: https://github.com/jenkinsci/bitbucket-build-status-notifier-plugin/compare/ed69c7dcdd31...66a0a8926765 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-34645) for in loop over result of String.split() gives NotSerializableException
Title: Message Title
Csongor Somogyi created an issue
Jenkins / JENKINS-34645
for in loop over result of String.split() gives NotSerializableException
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
2016/May/06 2:49 PM
Priority:
Minor
Reporter:
Csongor Somogyi
Similar to
JENKINS-27421
(maybe the same, I cannot decide, please analyze).
Following snippet produces the exception:
node {
def ARTIFACTS = "a01;a02".split(';')
for (ARTIFACT in ARTIFACTS) {
echo ARTIFACT
build job: 'a', parameters: [[$class: 'StringParameterValue', name: 'ARTIFACT', value: ARTIFACT]]
}
}
Exception thrown:
java.io.NotSerializableException: java.util.AbstractList$Itr
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:860)
at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032)
at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988)
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854)
at
[JIRA] [core] (JENKINS-34601) "Failed to load help file: Not Found" for "Name" in a New Agent configuration screen
Title: Message Title Vincent Latombe resolved as Fixed Jenkins / JENKINS-34601 "Failed to load help file: Not Found" for "Name" in a New Agent configuration screen Change By: Vincent Latombe Status: Open Resolved Assignee: Vincent Latombe 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.
