[JIRA] [scm-sync-configuration-plugin] (JENKINS-28366) build with java 7
Title: Message Title Craig Rodrigues resolved as Fixed Fixed in 0.0.9 Jenkins / JENKINS-28366 build with java 7 Change By: Craig Rodrigues Status: Open Resolved Assignee: Frédéric Camblor Craig Rodrigues 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] [build-environment-plugin] (JENKINS-22916) build on SCM change doesn't work
Title: Message Title Craig Rodrigues updated an issue Jenkins / JENKINS-22916 build on SCM change doesn't work Change By: Craig Rodrigues Component/s: scm-sync-configuration-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] [sqlplus-script-runner-plugin] (JENKINS-32105) SQLPlus Script Runner Plugin: Global ORACLE_HOME cannot save after Jenkins 1.640.
Title: Message Title alex chan created an issue Jenkins / JENKINS-32105 SQLPlus Script Runner Plugin: Global ORACLE_HOME cannot save after Jenkins 1.640. Issue Type: Bug Assignee: Fernando Boaglio Components: sqlplus-script-runner-plugin Created: 16/Dec/15 9:10 PM Environment: Jenkins 1.642, SQLPlus Script Runner 1.0.0 Labels: plugin configuration SQL-Plus Priority: Minor Reporter: alex chan Navigate to Manage Jenkins | Configure System | SQLPlus Script Runner Global ORACLE_HOME will not save.
[JIRA] [scm-sync-configuration-plugin] (JENKINS-22365) Cannot install latest version of scm-sync-configuration plugin
Title: Message Title Craig Rodrigues closed an issue as Cannot Reproduce Jenkins / JENKINS-22365 Cannot install latest version of scm-sync-configuration plugin Change By: Craig Rodrigues 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] [scm-sync-configuration-plugin] (JENKINS-22666) No popup window when committing changes to job config for putting in commit message
Title: Message Title Craig Rodrigues resolved as Fixed Fixed in 0.0.9 Jenkins / JENKINS-22666 No popup window when committing changes to job config for putting in commit message Change By: Craig Rodrigues Status: Open Resolved Assignee: Frédéric Camblor Craig Rodrigues 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] [scm-sync-configuration-plugin] (JENKINS-26652) SCM Sync fails after deleting a project
Title: Message Title Craig Rodrigues closed an issue as Fixed Fixed in 0.0.9 Jenkins / JENKINS-26652 SCM Sync fails after deleting a project Change By: Craig Rodrigues 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] [core] (JENKINS-32090) NullPointerException when processing email template when JDKs are installed automatically
Title: Message Title Alex Earl commented on JENKINS-32090 Re: NullPointerException when processing email template when JDKs are installed automatically My mistake, the context provides a logger, not listener. So, the user does need to update the template to retrieve the listener from the build instead of using "listener" as the parameter. Jelly sets to null anything it can't find in the context as far as I can tell. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds-plugin] (JENKINS-32100) Promotion job appears to perform SCM tasks the parent job does
Title: Message Title Victor Chan created an issue Jenkins / JENKINS-32100 Promotion job appears to perform SCM tasks the parent job does Issue Type: Bug Assignee: Oleg Nenashev Components: promoted-builds-plugin Created: 16/Dec/15 5:27 PM Environment: Promotion Builds version 2.24 Jenkins version: 1.605 Labels: jenkins plugins Priority: Major Reporter: Victor Chan We updated the Promotion builds to 2.24 to fix a specific issue, https://issues.jenkins-ci.org/browse/JENKINS-27716 However, we are seeing a different issue now... Our parent job pulls code from a git repo as a part of the build process. Our promotion job does very little; it has an approval process, and, when approved, it calls a parameterized secondary job. It appears that, for whatever reason, the promotion job (not the secondary job) now also tries appears to now perform
[JIRA] [bitbucket-pullrequest-builder-plugin] (JENKINS-31680) Use new bitbucket api to set if build success instead of add a comment
Title: Message Title Nenad Miksa commented on JENKINS-31680 Re: Use new bitbucket api to set if build success instead of add a comment It appears that global settings I found were for Bitbucket Approve plugin, not for Bitbucket pull request builder plugin. I still do not get Bitbucket statuses on build start. From log I can see that POST was sent, but in log I cannot see Bitbucket's response. If I try to reproduce the call with Postman, I get 403 "CSRF verification failed.". BitBucket API suggests using OAuth, and settings for plugin allow entering only BasicAuth username and password (if user has two-step authentication enabled, then plugin does not work at all). Is there a way to see what was returned from server? There are no exceptions in the log. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration-plugin] (JENKINS-24997) Updated configuration won't be committed.
Title: Message Title Craig Rodrigues closed an issue as Fixed Fixed in 0.0.9 Jenkins / JENKINS-24997 Updated configuration won't be committed. Change By: Craig Rodrigues 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] [scm-sync-configuration-plugin] (JENKINS-24881) Rename job starts to sync workspace
Title: Message Title Craig Rodrigues closed an issue as Duplicate Duplicate of JENKINS-15128 Jenkins / JENKINS-24881 Rename job starts to sync workspace Change By: Craig Rodrigues 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] [ssh-agent-plugin] (JENKINS-32101) Credentials must be referred to by ID which is Jenkins master specific
Title: Message Title R. Tyler Croy commented on JENKINS-32101 Re: Credentials must be referred to by ID which is Jenkins master specific Patrick Wolf I suppose you could interpret that as two bugs, The snippet generator is not performing the false behavior, since that's the only way to make the sshagent() step work, so I'm not sure I would consider that a 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] [workflow-plugin] (JENKINS-32067) Use ACE editor annotations to show Groovy syntax errors
Title: Message Title Antonio Muñiz started work on JENKINS-32067 Change By: Antonio Muñiz 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] [workflow-plugin] (JENKINS-26126) DSLD and/or GDSL
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26126 Re: DSLD and/or GDSL Code changed in jenkins User: Jesse Glick Path: CHANGES.md cps/src/main/java/org/jenkinsci/plugins/workflow/cps/EnvActionImpl.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/Snippetizer.java cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/EnvActionImpl/Binder/help.jelly cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/block.jelly cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/steps/EvaluateStep/config.jelly cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/steps/EvaluateStep/help-path.html cps/src/test/java/org/jenkinsci/plugins/workflow/cps/SnippetizerTest.java step-api/src/main/java/org/jenkinsci/plugins/workflow/structs/DescribableHelper.java step-api/src/test/java/org/jenkinsci/plugins/workflow/structs/DescribableHelperTest.java step-api/src/test/resources/org/jenkinsci/plugins/workflow/structs/DescribableHelperTest/Impl1/help-text.html step-api/src/test/resources/org/jenkinsci/plugins/workflow/structs/DescribableHelperTest/Impl1/help.html http://jenkins-ci.org/commit/workflow-plugin/4934c1c45b1bf308c3c99a4c79d1275c44850249 Log: JENKINS-26126 Noting merge of #275. Compare: https://github.com/jenkinsci/workflow-plugin/compare/521099bd8a31...4934c1c45b1b Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-agent-plugin] (JENKINS-32101) Credentials must be referred to by ID which is Jenkins master specific
Title: Message Title Patrick Wolf commented on JENKINS-32101 Re: Credentials must be referred to by ID which is Jenkins master specific Is this two separate bugs R. Tyler Croy? the snippet generator inputs the id instead of the name Using the credentials name fails . Do you know if this limited to the SSH-Agent 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] [reverse-proxy-auth-plugin] (JENKINS-32089) Encoding issue causes login failure
Title: Message Title Clément commented on JENKINS-32089 Re: Encoding issue causes login failure 1.4.1-SNAPSHOT (private-05/29/2014 18:04-ubuntu), apparently Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-environment-plugin] (JENKINS-22916) build on SCM change doesn't work
Title: Message Title Craig Rodrigues closed an issue as Won't Fix This has nothing to do with the SCM Sync Configuration plugin Jenkins / JENKINS-22916 build on SCM change doesn't work Change By: Craig Rodrigues Status: Open Closed 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] [scm-sync-configuration-plugin] (JENKINS-15128) Renaming job doesn't work with Git
Title: Message Title Craig Rodrigues closed an issue as Fixed Fixed in 0.0.9 Jenkins / JENKINS-15128 Renaming job doesn't work with Git Change By: Craig Rodrigues Status: Reopened Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration-plugin] (JENKINS-27649) Custom commit message not possible when configuring jobs
Title: Message Title Craig Rodrigues closed an issue as Duplicate Duplicate of JENKINS-22666 Jenkins / JENKINS-27649 Custom commit message not possible when configuring jobs Change By: Craig Rodrigues 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] [scm-sync-configuration-plugin] (JENKINS-16348) If SVN repository path has leading whitespace scm-sync-configration doesn't work and doesn't give errors
Title: Message Title Craig Rodrigues closed an issue as Fixed Fixed in 0.0.9 Jenkins / JENKINS-16348 If SVN repository path has leading whitespace scm-sync-configration doesn't work and doesn't give errors Change By: Craig Rodrigues 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] [job-dsl-plugin] (JENKINS-31830) Add support for some RubyMetrics report plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31830 Re: Add support for some RubyMetrics report plugin Code changed in jenkins User: Victor Martinez Path: job-dsl-core/src/main/docs/examples/javaposse/jobdsl/dsl/helpers/publisher/PublisherContext/flog.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/FlogContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/PublisherContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/publisher/PublisherContextSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/922a7e49edd5e6ee5956ab966bac650a2c27266e Log: JENKINS-31830 Added support for flog publisher as part of the RubyMetrics Reports 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] [scm-sync-configuration-plugin] (JENKINS-22308) SCM Sync Error in Jenkins
Title: Message Title Craig Rodrigues resolved as Fixed Fixed in 0.0.9 Jenkins / JENKINS-22308 SCM Sync Error in Jenkins Change By: Craig Rodrigues 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] [scm-sync-configuration-plugin] (JENKINS-25786) Renaming Job Causes a poisoned commitQueue
Title: Message Title Craig Rodrigues resolved as Fixed Fixed in 0.0.9 Jenkins / JENKINS-25786 Renaming Job Causes a poisoned commitQueue Change By: Craig Rodrigues Status: Open Resolved Assignee: Frédéric Camblor Craig Rodrigues 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] [scm-sync-configuration-plugin] (JENKINS-13593) Seems to not handle having builds in seperate folder
Title: Message Title Craig Rodrigues closed an issue as Fixed Fixed in 0.0.9 Jenkins / JENKINS-13593 Seems to not handle having builds in seperate folder Change By: Craig Rodrigues 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] [git-plugin] (JENKINS-29603) notifyCommit branch parameter can't contain slashes
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29603 Re: notifyCommit branch parameter can't contain slashes Code changed in jenkins User: Jesse Glick Path: multibranch/src/test/java/org/jenkinsci/plugins/workflow/multibranch/WorkflowBranchProjectFactoryTest.java http://jenkins-ci.org/commit/workflow-plugin/521099bd8a31963ea6149de0a4f4ab9fe5617e97 Log: Merge pull request #276 from jglick/test-JENKINS-29603 Extend JENKINS-30744 test to confirm that it is unaffected by JENKINS-29603 Compare: https://github.com/jenkinsci/workflow-plugin/compare/3840d8ca847e...521099bd8a31 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-30744) multibranch issues if branch contains /
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30744 Re: multibranch issues if branch contains / Code changed in jenkins User: Jesse Glick Path: multibranch/src/test/java/org/jenkinsci/plugins/workflow/multibranch/WorkflowBranchProjectFactoryTest.java http://jenkins-ci.org/commit/workflow-plugin/521099bd8a31963ea6149de0a4f4ab9fe5617e97 Log: Merge pull request #276 from jglick/test-JENKINS-29603 Extend JENKINS-30744 test to confirm that it is unaffected by JENKINS-29603 Compare: https://github.com/jenkinsci/workflow-plugin/compare/3840d8ca847e...521099bd8a31 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-29603) notifyCommit branch parameter can't contain slashes
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29603 Re: notifyCommit branch parameter can't contain slashes Code changed in jenkins User: Jesse Glick Path: multibranch/src/test/java/org/jenkinsci/plugins/workflow/multibranch/WorkflowBranchProjectFactoryTest.java http://jenkins-ci.org/commit/workflow-plugin/fca115faca36a62968c1500ffd89e06b982a56f4 Log: Extend JENKINS-30744 test to confirm that it is unaffected by JENKINS-29603. (Multibranch Git webhooks rely only on the url parameter to detect changes.) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-30744) multibranch issues if branch contains /
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30744 Re: multibranch issues if branch contains / Code changed in jenkins User: Jesse Glick Path: multibranch/src/test/java/org/jenkinsci/plugins/workflow/multibranch/WorkflowBranchProjectFactoryTest.java http://jenkins-ci.org/commit/workflow-plugin/fca115faca36a62968c1500ffd89e06b982a56f4 Log: Extend JENKINS-30744 test to confirm that it is unaffected by JENKINS-29603. (Multibranch Git webhooks rely only on the url parameter to detect changes.) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multijob-plugin] (JENKINS-31888) BuildHistoryWidget causing job page slowdowns
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-31888 BuildHistoryWidget causing job page slowdowns Change By: Daniel Beck Component/s: multijob-plugin Component/s: core Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-32090) NullPointerException when processing email template when JDKs are installed automatically
Title: Message Title Daniel Beck commented on JENKINS-32090 Re: NullPointerException when processing email template when JDKs are installed automatically Further debugging should probably be done in the template. Is it possible user customization unset the var or something? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-32090) NullPointerException when processing email template when JDKs are installed automatically
Title: Message Title Alex Earl commented on JENKINS-32090 Re: NullPointerException when processing email template when JDKs are installed automatically Listener is provided in the context by email-ext, but it shouldn't be null since it comes from the build. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27694) Download update data immediately when installing a new tool installer plugin
Title: Message Title Daniel Beck resolved as Fixed Sorry for late answer, steps to reproduce on docker: As you did never really installed the plugin, but just put the file there, Jenkins never got the trigger that it needs to update its metadata. Install using the UI or the CLI and the issue will disappear. Support for scanning manually installed plugins, like you're doing, for missing metadata is a different issue. Your attempt with an older release is likely only the result of there not being (recent enough) update center metadata to begin with. If Jenkins downloads everything anew, like in your log snippet, it's a case of exactly that. Jenkins / JENKINS-27694 Download update data immediately when installing a new tool installer plugin Change By: Daniel Beck Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-32086) Uploading custom plugin fails
Title: Message Title Thirumal Jayaraman commented on JENKINS-32086 Re: Uploading custom plugin fails Firefox 42.0 and OS Windows Server 2008 R2. This issue there with IE 11 and Windows 7 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] [core] (JENKINS-32090) NullPointerException when processing email template when JDKs are installed automatically
Title: Message Title Alex Earl reopened an issue Jenkins / JENKINS-32090 NullPointerException when processing email template when JDKs are installed automatically Change By: Alex Earl Resolution: Not A Defect Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32090) NullPointerException when processing email template when JDKs are installed automatically
Title: Message Title Alex Earl resolved as Not A Defect Jenkins / JENKINS-32090 NullPointerException when processing email template when JDKs are installed automatically Change By: Alex Earl Status: Reopened Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multijob-plugin] (JENKINS-31694) Allow setting a name for a job in a phase
Title: Message Title dheeraj kichloo commented on JENKINS-31694 Re: Allow setting a name for a job in a phase please fix this issue,as it is needed for my jenkin setup also Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [robot-plugin] (JENKINS-32077) Javascript errors
Title: Message Title Nico Bollen commented on JENKINS-32077 Re: _javascript_ errors Running the job again did the trick for me at 1.640... But because of GIT problems in this version I had to go back to 1.639... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multijob-plugin] (JENKINS-31694) Allow setting a name for a job in a phase
Title: Message Title dheeraj kichloo assigned an issue to Quint Stoffers Jenkins / JENKINS-31694 Allow setting a name for a job in a phase Change By: dheeraj kichloo Assignee: Quint Stoffers Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-32090) NullPointerException when processing email template when JDKs are installed automatically
Title: Message Title Alex Earl assigned an issue to Alex Earl Jenkins / JENKINS-32090 NullPointerException when processing email template when JDKs are installed automatically Change By: Alex Earl Assignee: Alex Earl Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-32103) Expose workspace path in environment for "prepare environment" scripts
Title: Message Title Sam Clippinger created an issue Jenkins / JENKINS-32103 Expose workspace path in environment for "prepare environment" scripts Issue Type: Improvement Assignee: Unassigned Components: core Created: 16/Dec/15 6:23 PM Environment: LTS 1.625.3 Priority: Minor Reporter: Sam Clippinger We use the "Prepare an environment for the run" option to run scripts prior to SCM checkout. However, the WORKSPACE environment variable is not set when those scripts run and I cannot find any way to discover what the workspace will eventually be. For example, if the project is set to allow concurrent builds and the workspace will have "@3" appended to the path, that information is inaccessible. This means our scripts that sanitize the git folders on the slave have to make some dangerous assumptions about where to run. I'm not very familiar with the Jenkins code, but from what I can tell the workspace is "leased" in AbstractBuild$AbstractBuildExecution.run() just before the call to prepareWorkspace(). If the WORKSPACE variable were added to the environment at that point, I think it would be visible from any scripts running before SCM checkout. Would it be possible to add this?
[JIRA] [ssh-agent-plugin] (JENKINS-32104) Failing to find credentials doesn't actually fail a Workflow
Title: Message Title
R. Tyler Croy created an issue
Jenkins / JENKINS-32104
Failing to find credentials doesn't actually fail a Workflow
Issue Type:
Bug
Assignee:
Unassigned
Components:
ssh-agent-plugin
Created:
16/Dec/15 6:46 PM
Labels:
workflow
Priority:
Minor
Reporter:
R. Tyler Croy
Because of the presence of the ignoreMissing option for the sshagent() Workflow step, one might assume that the absence of a credential will result in a failed build. Or at the very least that the contents of the sshagent() {} block would not execute.
Neither is the case unfortunately.
With the following workflow:
node {
sshagent(["non-existent-garbage"]) {
unstash "foo"
sh "ls"
}
}
The following will occur:
[Workflow] Allocate node : Start
Running on Docker-bb75aee9cf85 in /home/jenkins/workspace/multipass/master
[Workflow]
[JIRA] [core] (JENKINS-32086) Uploading custom plugin fails
Title: Message Title Daniel Beck commented on JENKINS-32086 Re: Uploading custom plugin fails You're using Firefox? What version and OS? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-32086) Uploading custom plugin fails
Title: Message Title Thirumal Jayaraman commented on JENKINS-32086 Re: Uploading custom plugin fails yes, in Advance tab using Upload 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] [ssh-agent-plugin] (JENKINS-32102) Only credentials added via the snippet generator are usable
Title: Message Title
R. Tyler Croy created an issue
Jenkins / JENKINS-32102
Only credentials added via the snippet generator are usable
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
workflow-ssh-agent-snippet-credentials.png
Components:
ssh-agent-plugin
Created:
16/Dec/15 6:18 PM
Labels:
workflow
Priority:
Minor
Reporter:
R. Tyler Croy
I had an SSH credential added before starting to use the sshagent workflow step and I was unable to refer to the credential by name (JENKINS-32101) or even by ID. Not in the screenshot that it doesn't show up in the snippet generator UI either.
When referring to a credential which was previously added (2d954d6d-9eda-444a-90ff-693df2ef3f26) with:
node {
sshagent(['2d954d6d-9eda-444a-90ff-693df2ef3f26']) {
// do work here
}
}
[JIRA] [bitbucket-pullrequest-builder-plugin] (JENKINS-31680) Use new bitbucket api to set if build success instead of add a comment
Title: Message Title Rubens M commented on JENKINS-31680 Re: Use new bitbucket api to set if build success instead of add a comment I create this request before the release of version 1.4.8, but yes, it is (sort of) implemented by the latest release, Another problem in this released version is the option 'Rebuild if destination branch changes' doesnt work anymore. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-agent-plugin] (JENKINS-32101) Credentials must be referred to by ID which is Jenkins master specific
Title: Message Title
R. Tyler Croy created an issue
Jenkins / JENKINS-32101
Credentials must be referred to by ID which is Jenkins master specific
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
workflow-ssh-agent-id.png
Components:
ssh-agent-plugin
Created:
16/Dec/15 6:10 PM
Labels:
workflow
Priority:
Minor
Reporter:
R. Tyler Croy
The helptext is at odds with what gets generated by the Snippet Generator (see screenshot).
node {
sshagent (credentials: ['deploy-dev']) {
sh 'ssh -o StrictHostKeyChecking=no -l cloudbees 192.168.1.106 uname -a'
}
}
Multiple credentials could be passed in the array but it is not supported using Snippet Generator.
[JIRA] [ssh-agent-plugin] (JENKINS-32104) Failing to find credentials doesn't actually fail a Workflow
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32104 Re: Failing to find credentials doesn't actually fail a Workflow Code changed in jenkins User: R. Tyler Croy Path: Jenkinsfile http://jenkins-ci.org/commit/jenkins.io/ff3bc09b643da104c514798098a735f8fff591b3 Log: Add support for deploying the built zip out to the beta site The following tickets were created as a result of this experimentation: JENKINS-32101 JENKINS-32102 JENKINS-32104 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-agent-plugin] (JENKINS-32101) Credentials must be referred to by ID which is Jenkins master specific
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32101 Re: Credentials must be referred to by ID which is Jenkins master specific Code changed in jenkins User: R. Tyler Croy Path: Jenkinsfile http://jenkins-ci.org/commit/jenkins.io/ff3bc09b643da104c514798098a735f8fff591b3 Log: Add support for deploying the built zip out to the beta site The following tickets were created as a result of this experimentation: JENKINS-32101 JENKINS-32102 JENKINS-32104 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-agent-plugin] (JENKINS-32102) Only credentials added via the snippet generator are usable
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32102 Re: Only credentials added via the snippet generator are usable Code changed in jenkins User: R. Tyler Croy Path: Jenkinsfile http://jenkins-ci.org/commit/jenkins.io/ff3bc09b643da104c514798098a735f8fff591b3 Log: Add support for deploying the built zip out to the beta site The following tickets were created as a result of this experimentation: JENKINS-32101 JENKINS-32102 JENKINS-32104 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration-plugin] (JENKINS-30306) SCM plugin stops working after adding a slave
Title: Message Title Craig Rodrigues resolved as Fixed Fixed in 0.0.9 Jenkins / JENKINS-30306 SCM plugin stops working after adding a slave Change By: Craig Rodrigues 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] [scm-sync-configuration-plugin] (JENKINS-19984) Groovy Postbuild Plugin does not like Jenkins Option: "Build Record Root Directory"
Title: Message Title Craig Rodrigues closed an issue as Fixed Fixed in 0.0.9 Jenkins / JENKINS-19984 Groovy Postbuild Plugin does not like Jenkins Option: "Build Record Root Directory" Change By: Craig Rodrigues 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] [workflow-plugin] (JENKINS-31897) Default parameter value is not used
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31897 Re: Default parameter value is not used Code changed in jenkins User: Antonio Muñiz Path: support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStepExecution.java http://jenkins-ci.org/commit/workflow-plugin/c24fd075742ef5034015dec9bed1a28c6cccb5f9 Log: JENKINS-31897 Set default parameters if needed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31897) Default parameter value is not used
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31897 Re: Default parameter value is not used Code changed in jenkins User: Jesse Glick Path: CHANGES.md aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/build/BuildTriggerStepTest.java support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStepExecution.java http://jenkins-ci.org/commit/workflow-plugin/f5fe6534087dd35dcf46de192ad6cfc2390e2ba5 Log: [FIXED JENKINS-31897] Merging #269. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-31897) Default parameter value is not used
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-31897 Default parameter value is not used 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] [scm-sync-configuration-plugin] (JENKINS-16939) Missing .png
Title: Message Title Craig Rodrigues closed an issue as Fixed Fixed in 0.0.9 Jenkins / JENKINS-16939 Missing .png Change By: Craig Rodrigues 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] [scm-sync-configuration-plugin] (JENKINS-9166) SCM Sync saves previous version, not the most recent change
Title: Message Title Craig Rodrigues closed an issue as Cannot Reproduce Jenkins / JENKINS-9166 SCM Sync saves previous version, not the most recent change Change By: Craig Rodrigues 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] [workflow-plugin] (JENKINS-32099) Using StringBuilder in Workflow makes failing build without warning
Title: Message Title
Jesse Glick resolved as Not A Defect
Please provide a complete, self-contained test case to reproduce. After I ran a fresh 1.642, installed Workflow: Aggregator with the required restart, made a new flow with the text supplied, commented out your phony git step, and also commented out the JUnitResultArchiver step, I got
org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use new java.lang.StringBuilder
which looks right to me.
Perhaps you meant to fix the test step to delete testDataPublishers: [] which does not work (filed elsewhere), in which case you get
Started by user anonymous
[Workflow] Allocate node : Start
Running on master in /…/workspace
[Workflow] node {
[Workflow] archive
[Workflow] step
Recording test results
[Workflow] } //node
[Workflow] Allocate node : End
[Workflow] End of Workflow
ERROR: No test report files were found. Configuration error?
Finished: FAILURE
which is correct behavior—it is your script which is foolishly doing something in a finally block, which if it fails will mask any earlier error. (And it will fail, because there are no test results yet, pending an RFE in junit.)
If you want to archive failing test results, ask Gradle to return a zero exit code in case tests ran but failed. You could also use the catchError step.
If you really want it is also possible to call Throwable.addSuppressed, though in this case it is tricky since AbortException stack traces are not printed, so you would need a wrapper exception:
def err
try {
executeGradle('clean test')
} catch (_err) {
err = _err
} finally {
try {
archive '**/*'
step([$class: 'JUnitResultArchiver', keepLongStdio: false, testResults: '**/build/test-results/*.xml'])
} catch (_err) {
if (err != null) {
def x = new Exception(_err)
x.addSuppressed(err)
throw x
} else {
throw _err
}
}
}
(Of course in this case you need to approve a couple more signatures for the exotic error handling.)
Jenkins / JENKINS-32099
Using StringBuilder in Workflow makes failing build without warning
Change By:
Jesse Glick
[JIRA] [scm-sync-configuration-plugin] (JENKINS-15607) SCM Sync configuration plugin installation failed due to inability to delete antlr-2.7.6.jar
Title: Message Title Craig Rodrigues closed an issue as Cannot Reproduce Jenkins / JENKINS-15607 SCM Sync configuration plugin installation failed due to inability to delete antlr-2.7.6.jar Change By: Craig Rodrigues 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] [scm-sync-configuration-plugin] (JENKINS-18036) scm-sync plugin ends up in commit-conflicts and eventually eats most of available CPU time
Title: Message Title Craig Rodrigues closed an issue as Fixed Fixed in 0.0.9 Jenkins / JENKINS-18036 scm-sync plugin ends up in commit-conflicts and eventually eats most of available CPU time Change By: Craig Rodrigues 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] [scm-sync-configuration-plugin] (JENKINS-10095) No initial checkin to svn
Title: Message Title Craig Rodrigues closed an issue as Cannot Reproduce Jenkins / JENKINS-10095 No initial checkin to svn Change By: Craig Rodrigues 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] [scm-sync-configuration-plugin] (JENKINS-24344) Discard Old Builds does not remove any old builds on a system with data storage on seperate logical partition
Title: Message Title Craig Rodrigues closed an issue as Fixed Fixed in 0.0.9 Jenkins / JENKINS-24344 Discard Old Builds does not remove any old builds on a system with data storage on seperate logical partition Change By: Craig Rodrigues 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] [scm-sync-configuration-plugin] (JENKINS-18327) FATAL: javax.xml.parsers.SAXParserFactory.setXIncludeAware(Z)V during hudson.scm.SubversionChangeLogParser.parse(SubversionChangeLogParser.java:
Title: Message Title Craig Rodrigues closed an issue as Cannot Reproduce Jenkins / JENKINS-18327 FATAL: javax.xml.parsers.SAXParserFactory.setXIncludeAware(Z)V during hudson.scm.SubversionChangeLogParser.parse(SubversionChangeLogParser.java:76) Change By: Craig Rodrigues 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] [script-security-plugin] (JENKINS-31701) sleep step inside node throws RejectedAccessException
Title: Message Title Jesse Glick resolved as Fixed Jenkins / JENKINS-31701 sleep step inside node throws RejectedAccessException Change By: Jesse Glick 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] [google-play-android-publisher-plugin] (JENKINS-32109) Split out setting of "recent changes" into its own build step
Title: Message Title Christopher Orr created an issue Jenkins / JENKINS-32109 Split out setting of "recent changes" into its own build step Issue Type: Improvement Assignee: Christopher Orr Components: google-play-android-publisher-plugin Created: 16/Dec/15 11:23 PM Priority: Minor Reporter: Christopher Orr With JENKINS-32107, other build steps will be able to see which APK(s) have been uploaded during a build. So the current "Recent changes" part of the APK upload build step could be (potentially) split out into its own build step, where it would automatically pick up the APKs used (and credentials). This would be good, as this new "Upload recent changes text" would be helpful as a standalone build step. e.g. There is an APK in beta, with beta-tester release notes. When using Jenkins to promote that APK to production, you may also want to apply updated release notes. Add Comment
[JIRA] [support-core-plugin] (JENKINS-32110) networkInterface.md not correctly generated with Java 6
Title: Message Title Arnaud Héritier created an issue Jenkins / JENKINS-32110 networkInterface.md not correctly generated with Java 6 Issue Type: Bug Assignee: Steven Christou Components: support-core-plugin Created: 16/Dec/15 11:30 PM Priority: Minor Reporter: Arnaud Héritier In the file networkInterface.md we have N/A: No connection to node, or no cache. Source of the issue: /Users/arnaud/Code/jenkinsci/support-core-plugin/src/main/java/com/cloudbees/jenkins/support/impl/NetworkInterfaces.java:[122,56] getIndex() is not public in java.net.NetworkInterface; cannot be accessed from outside package java.net.NetworkInterface#getIndex() is Java 7+ Several issues : https://jenkins.ci.cloudbees.com/job/plugins/job/support-core-plugin is building with J7 animal sniffer is configured to check with java 5 ... but it isn't called by default
[JIRA] [scm-sync-configuration-plugin] (JENKINS-22540) Jenkins config files are not tracked
Title: Message Title Craig Rodrigues closed an issue as Fixed Fixed in 0.0.9 Jenkins / JENKINS-22540 Jenkins config files are not tracked Change By: Craig Rodrigues 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] [scm-sync-configuration-plugin] (JENKINS-24992) Restore from scm-sync-configuration does not restore symlinks
Title: Message Title Craig Rodrigues closed an issue as Cannot Reproduce Cannot reproduce in 0.0.9 Jenkins / JENKINS-24992 Restore from scm-sync-configuration does not restore symlinks Change By: Craig Rodrigues 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] [scm-sync-configuration-plugin] (JENKINS-16378) All build logs added and committed when renaming job
Title: Message Title Craig Rodrigues closed an issue as Fixed Fixed in 0.0.9 Jenkins / JENKINS-16378 All build logs added and committed when renaming job Change By: Craig Rodrigues 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] [config-file-provider-plugin] (JENKINS-15687) Config File Provider and SCM Sync causes lots of changes to config files
Title: Message Title Craig Rodrigues closed an issue as Won't Fix Jenkins / JENKINS-15687 Config File Provider and SCM Sync causes lots of changes to config files Change By: Craig Rodrigues Status: Open Closed 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] [support-core-plugin] (JENKINS-28876) Include user agent in slow requests
Title: Message Title Arnaud Héritier commented on JENKINS-28876 Re: Include user agent in slow requests fixed in 2.27 Steven Christou ?? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration-plugin] (JENKINS-12774) SCM sync configuration plugin crashes jenkins
Title: Message Title Craig Rodrigues closed an issue as Cannot Reproduce Jenkins / JENKINS-12774 SCM sync configuration plugin crashes jenkins Change By: Craig Rodrigues 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] [scm-sync-configuration-plugin] (JENKINS-8527) Two way synchronization
Title: Message Title Craig Rodrigues closed an issue as Won't Fix Jenkins / JENKINS-8527 Two way synchronization Change By: Craig Rodrigues Status: Open Closed 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] [assembla-auth] (JENKINS-19189) Providing Assembla Auth plugin support
Title: Message Title Craig Rodrigues closed an issue as Fixed Fixed in 0.0.9 Jenkins / JENKINS-19189 Providing Assembla Auth plugin support Change By: Craig Rodrigues 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] [scm-sync-configuration-plugin] (JENKINS-24775) SCM Sync configuration plugin can not work~
Title: Message Title Craig Rodrigues closed an issue as Cannot Reproduce Jenkins / JENKINS-24775 SCM Sync configuration plugin can not work~ Change By: Craig Rodrigues Status: Reopened 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] [google-play-android-publisher-plugin] (JENKINS-32107) Store uploaded APK metadata with the build
Title: Message Title Christopher Orr created an issue Jenkins / JENKINS-32107 Store uploaded APK metadata with the build Issue Type: Improvement Assignee: Christopher Orr Components: google-play-android-publisher-plugin Created: 16/Dec/15 10:58 PM Priority: Minor Reporter: Christopher Orr Currently we just print a bunch of stuff to the console about which APKs, their application ID, checksum and version codes are being uploaded. For use in subsequent build steps, or other builds, we should associate this data with the build in which the upload (successfully) occurred. Add Comment
[JIRA] [support-core-plugin] (JENKINS-31952) Dockerfile: cloudbees/jenkins needs to be cloudbees/jenkins-enterprise
Title: Message Title Arnaud Héritier commented on JENKINS-31952 Re: Dockerfile: cloudbees/jenkins needs to be cloudbees/jenkins-enterprise yes and no Owen Wood It depends of the distribution. By default this plugin must work with Jenkins OSS In that case docker files are here : https://hub.docker.com/_/jenkins/ In the case of our cloudbees product we have an extension/customisation of this support plugin and we should find a way in it to change this value to use our images https://hub.docker.com/r/cloudbees/jenkins-enterprise/ https://hub.docker.com/r/cloudbees/jenkins-operations-center/ Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration-plugin] (JENKINS-8204) scm-sync URL should be per job
Title: Message Title Craig Rodrigues closed an issue as Won't Fix Jenkins / JENKINS-8204 scm-sync URL should be per job Change By: Craig Rodrigues Status: Open Closed 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] [accurev-plugin] (JENKINS-13258) Set the default params in parametrized build as env variables in the SCM poll
Title: Message Title Craig Rodrigues updated an issue Jenkins / JENKINS-13258 Set the default params in parametrized build as env variables in the SCM poll Not related to scm-sync-configuration plugin Change By: Craig Rodrigues Component/s: scm-sync-configuration-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] [scm-sync-configuration-plugin] (JENKINS-18516) Bad urls while restoring configuration
Title: Message Title Craig Rodrigues closed an issue as Fixed Fixed in 0.0.9 Jenkins / JENKINS-18516 Bad urls while restoring configuration Change By: Craig Rodrigues 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] [scm-sync-configuration-plugin] (JENKINS-16441) Scm sync fails completely if folder name starts with a hyphen
Title: Message Title Craig Rodrigues closed an issue as Fixed Fixed in 0.0.9 Jenkins / JENKINS-16441 Scm sync fails completely if folder name starts with a hyphen Change By: Craig Rodrigues 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] [scm-sync-configuration-plugin] (JENKINS-15898) Subversion back-end cannot handle renaming of jobs
Title: Message Title Craig Rodrigues closed an issue as Fixed Fixed in 0.0.9 Jenkins / JENKINS-15898 Subversion back-end cannot handle renaming of jobs Change By: Craig Rodrigues 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] [scm-sync-configuration-plugin] (JENKINS-9154) multiple warnings after a couple days working
Title: Message Title Craig Rodrigues closed an issue as Cannot Reproduce Jenkins / JENKINS-9154 multiple warnings after a couple days working Change By: Craig Rodrigues 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] [scm-sync-configuration-plugin] (JENKINS-8705) Create SCM directory on first sync if it doesn't exist
Title: Message Title Craig Rodrigues closed an issue as Fixed Fixed in 0.0.9 Jenkins / JENKINS-8705 Create SCM directory on first sync if it doesn't exist Change By: Craig Rodrigues 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] [jira-plugin] (JENKINS-32106) Issue type "UNKNOWN" in Release Notes
Title: Message Title Jonathan Langevin created an issue Jenkins / JENKINS-32106 Issue type "UNKNOWN" in Release Notes Issue Type: Bug Assignee: Radek Antoniuk Components: jira-plugin Created: 16/Dec/15 10:57 PM Labels: jenkins jira jira-plugin-2.1 Priority: Minor Reporter: Jonathan Langevin Jenkins 1.625.3 Jira 6.3.7 Jira-Plugin 2.1 I'm seeing an issue in release notes, where the issue type (in this case, for Bug) is being listed as "UNKNOWN". This is definitely unhelpful for anyone that uses the release notes for tracking purposes. Add Comment
[JIRA] [google-play-android-publisher-plugin] (JENKINS-32107) Store uploaded APK metadata with the build
Title: Message Title Christopher Orr commented on JENKINS-32107 Re: Store uploaded APK metadata with the build We should also store the Google Play credentials ID used. Which would be much nicer if JENKINS-29018 got implemented. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-32110) networkInterface.md not correctly generated with Java 6
Title: Message Title
Arnaud Héritier updated an issue
Jenkins / JENKINS-32110
networkInterface.md not correctly generated with Java 6
Change By:
Arnaud Héritier
In the file networkInterface.md we have{code}N/A: No connection to node, or no cache.{code}Source of the issue: /Users/arnaud/Code/jenkinsci/ support-core-plugin/src/main/java/com/cloudbees/jenkins/support/impl/NetworkInterfaces.java:[122,56] getIndex() is not public in java.net.NetworkInterface; cannot be accessed from outside packagejava.net.NetworkInterface#getIndex() is Java 7+Several issues :* https://jenkins.ci.cloudbees.com/job/plugins/job/support-core-plugin is building with J7 :(* animal sniffer is configured to check with java 5 ... but it isn't called by defaultIf we remove this line the file is correctly generated
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration-plugin] (JENKINS-24993) scm-sync-configration plugin keeps on adding directory structure scm-sync-configuration/checkoutConfiguration
Title: Message Title Craig Rodrigues closed an issue as Duplicate Duplicates JENKINS-22040 Jenkins / JENKINS-24993 scm-sync-configration plugin keeps on adding directory structure scm-sync-configuration/checkoutConfiguration Change By: Craig Rodrigues 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] [workflow-plugin] (JENKINS-31909) Groovy script syntax validation not working as expected
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-31909 Groovy script syntax validation not working as expected 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] [scm-sync-configuration-plugin] (JENKINS-8517) Set revision number in JobRevision Plugin
Title: Message Title Craig Rodrigues closed an issue as Won't Fix Jenkins / JENKINS-8517 Set revision number in JobRevision Plugin Change By: Craig Rodrigues Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31909) Groovy script syntax validation not working as expected
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31909 Re: Groovy script syntax validation not working as expected Code changed in jenkins User: Jesse Glick Path: CHANGES.md cps/src/main/js/workflow-editor.js http://jenkins-ci.org/commit/workflow-plugin/1d8a2a49a55b63e62361e3d08d2fc98f97e0bd7f Log: [FIXED JENKINS-31909] Merging #273. Compare: https://github.com/jenkinsci/workflow-plugin/compare/5206f6650bba...1d8a2a49a55b Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-31909) Groovy script syntax validation not working as expected
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31909 Re: Groovy script syntax validation not working as expected Code changed in jenkins User: Antonio Muñiz Path: cps/src/main/js/workflow-editor.js http://jenkins-ci.org/commit/workflow-plugin/4e635fefa742ec0db86f5231be91e06a2863a5a2 Log: JENKINS-31909 Show groovy syntax validation message Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-31830) Add support for some RubyMetrics report plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31830 Re: Add support for some RubyMetrics report plugin Code changed in jenkins User: Victor Martinez Path: job-dsl-core/src/main/docs/examples/javaposse/jobdsl/dsl/helpers/publisher/PublisherContext/railsNotes.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/PublisherContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/RailsNotesContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/publisher/PublisherContextSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/f9dff4b3dd5dfe07b5fce5a2b58daee37cb017b9 Log: JENKINS-31830 Added support for railsNotes which it's part of the RubyMetrics Reports Plugin Added no options test case for railsNotes Fixed empty attribute since it might be empty in some cases Fixed empty attribute since it might be empty in some cases Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration-plugin] (JENKINS-24686) scm-sync-configuration fails if job name contains whitespace
Title: Message Title Craig Rodrigues closed an issue as Fixed Fixed in 0.0.9 Jenkins / JENKINS-24686 scm-sync-configuration fails if job name contains whitespace Change By: Craig Rodrigues 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] [support-core-plugin] (JENKINS-22764) Record update center information
Title: Message Title Arnaud Héritier commented on JENKINS-22764 Re: Record update center information Steven Christou you started to do this in 2.29 ? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration-plugin] (JENKINS-25129) SCM Sync Shows Errors in the logs but GIT show no issues.
Title: Message Title Craig Rodrigues closed an issue as Fixed Fixed in 0.0.9 Jenkins / JENKINS-25129 SCM Sync Shows Errors in the logs but GIT show no issues. Change By: Craig Rodrigues 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] [scm-sync-configuration-plugin] (JENKINS-16112) Provide option to either suppress commit or collapse changes into a single commit
Title: Message Title Craig Rodrigues closed an issue as Won't Fix Jenkins / JENKINS-16112 Provide option to either suppress commit or collapse changes into a single commit Change By: Craig Rodrigues Status: Open Closed 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] [script-security-plugin] (JENKINS-31701) sleep step inside node throws RejectedAccessException
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31701 Re: sleep step inside node throws RejectedAccessException Code changed in jenkins User: Jesse Glick Path: src/main/java/org/jenkinsci/plugins/scriptsecurity/sandbox/groovy/GroovyCallSiteSelector.java src/test/java/org/jenkinsci/plugins/scriptsecurity/sandbox/groovy/GroovyCallSiteSelectorTest.java src/test/java/org/jenkinsci/plugins/scriptsecurity/sandbox/groovy/SandboxInterceptorTest.java http://jenkins-ci.org/commit/script-security-plugin/af0b1ae64f365f015836f47d2b642d085cd6e069 Log: Merge pull request #33 from jglick/RejectedAccessException-JENKINS-31701 JENKINS-31701 Misclassification of a method taking long and being passed an int Compare: https://github.com/jenkinsci/script-security-plugin/compare/bad55dc4c719...af0b1ae64f36 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-31701) sleep step inside node throws RejectedAccessException
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31701 Re: sleep step inside node throws RejectedAccessException Code changed in jenkins User: Jesse Glick Path: src/main/java/org/jenkinsci/plugins/scriptsecurity/sandbox/groovy/GroovyCallSiteSelector.java src/test/java/org/jenkinsci/plugins/scriptsecurity/sandbox/groovy/GroovyCallSiteSelectorTest.java src/test/java/org/jenkinsci/plugins/scriptsecurity/sandbox/groovy/SandboxInterceptorTest.java http://jenkins-ci.org/commit/script-security-plugin/e6ccfc979b959490f8db21166a5bf2c69e566e43 Log: JENKINS-31701 Misclassification of a method taking long and being passed an int. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-31814) dpkg error installing jenkins 1.639 on debian platforms
Title: Message Title Brandon Raabe commented on JENKINS-31814 Re: dpkg error installing jenkins 1.639 on debian platforms I can confirm Georg Koester answer. It only happens upon installation. A stop and start does not cause the same error. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [google-play-android-publisher-plugin] (JENKINS-32108) Add ability to select APKs to be moved based on a previous build
Title: Message Title Christopher Orr created an issue Jenkins / JENKINS-32108 Add ability to select APKs to be moved based on a previous build Issue Type: Improvement Assignee: Christopher Orr Components: google-play-android-publisher-plugin Created: 16/Dec/15 11:16 PM Priority: Minor Reporter: Christopher Orr Currently, the "Move Android APKs to a different release track" build step expects that the user inputs the version codes, or provides the previous APKs. Inputting the version codes, whether by parameter or whatever, is a bit awkward. Similarly, providing the previous APKs requires that they were previously archived somewhere (which hopefully people do anyway), and then using Copy Artifact to get them into the current workspace. So there should be an additional "Use APKs uploaded in another build" option. This would provide a field for the job name, plus a dropdown with stuff like "last successful build", or "upstream build" etc. Hopefully these dropdown values and UI are somewhat standardised, or provided via extension point? See the Copy Artifact plugin, as it probably has the most useful set of options in this dropdown.
