[JIRA] [integrity-plugin] (JENKINS-25228) Using the integrity-plugin together with concurrent builds causes SQL Exceptions
Title: Message Title
Leon Leon edited a comment on JENKINS-25228
Re: Using the integrity-plugin together with concurrent builds causes SQL Exceptions
Can you please tell me in which PTC plugin version is the problem solved ? We are using PTC version 1.34 and this problem still persisting with workflow jobs.{color:red}A SQL Exception was caught!Table/View 'SCM_E9A7D857_553C_48D3_AF6D_FF45A06EFD90' does not exist.{color}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-27977) NullPointer & authentication cancelled occure immediately on SVN checkout
Title: Message Title An Tran commented on JENKINS-27977 Re: NullPointer & authentication cancelled occure immediately on SVN checkout We could observe this bug too. We have svn externals in our 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] [cobertura-plugin] (JENKINS-13889) Cobertura plugin is not able to find code from python coverage
Title: Message Title SCM/JIRA link daemon commented on JENKINS-13889 Re: Cobertura plugin is not able to find code from python coverage Code changed in jenkins User: Arcadiy Ivanov Path: src/main/java/hudson/plugins/cobertura/CoberturaPublisher.java http://jenkins-ci.org/commit/cobertura-plugin/a94a23f2570e27c7405290e57857ca9179156876 Log: Merge pull request #43 from dzudek/master [FIXED JENKINS-13889] Not able to find source code from subdirectories Compare: https://github.com/jenkinsci/cobertura-plugin/compare/c27a7e591747...a94a23f2570e Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cobertura-plugin] (JENKINS-13889) Cobertura plugin is not able to find code from python coverage
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-13889 Cobertura plugin is not able to find code from python coverage Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [extensible-choice-parameter-plugin] (JENKINS-31131) Improving visual style.
Title: Message Title Alexey Larsky commented on JENKINS-31131 Re: Improving visual style. Nothing bad if it by design. It just looks some wider and old-fashioned than other parameters plugins. Maybe style changing helps it be more popular PS. I really like plugin functionality. Thanks for 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-31161) Update HTMLUnit in Jenkins Core
Title: Message Title Patrick Wolf created an issue Jenkins / JENKINS-31161 Update HTMLUnit in Jenkins Core Issue Type: Story Assignee: Unassigned Components: core Created: 26/Oct/15 7:05 AM Labels: 2.0 Priority: Minor Reporter: Patrick Wolf It is hoped to use modern JS libs for all of our new UI work (create item, 1st run plugin bundling experience etc). Jenkins Core currently uses old JS libs, mainly prototypejs. This library has been dead for years + we are using a forked version of it. We were hoping to get away from it in the newer work. We are also currently using a forked version of HtmlUnit in Jenkins Core. It's an old version (2.6 - latest is 2.18). This version of HtmlUnit doesn't support use of jQuery (and probably lots of other JS libs we would want to use) e.g. it complains about how the "isArray" method is defined in the lib. They claim that the latest version of HtmlUnit "fully supports" jQuery (I'm not convinced). The problem for us is that the Jenkins Core test harness relies heavily on HtmlUnit. There are many many tests written to run against the forked version, which means they fail when we try to do anything that that version of HtmlUnit doesn't like e.g. introduce jQuery.
[JIRA] [plugin-proposals] (JENKINS-9802) Manage Plugins section should be more informative and User freindly
Title: Message Title Patrick Wolf updated an issue Jenkins / JENKINS-9802 Manage Plugins section should be more informative and User freindly Change By: Patrick Wolf Issue Type: New Feature Story Priority: Trivial Minor Labels: 2.0 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [extensible-choice-parameter-plugin] (JENKINS-31131) Improving visual style.
Title: Message Title Alexey Larsky edited a comment on JENKINS-31131 Re: Improving visual style. Nothing bad if it by design.It just looks some wider and old-fashioned than other parameters plugins.Maybe style changing helps it to be more popular :)PS. I really like plugin functionality. Thanks for 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] [log-parser-plugin] (JENKINS-26572) Log Parser incompatible with Jenkins 1.597 (build record change)
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-26572 Re: Log Parser incompatible with Jenkins 1.597 (build record change) Mark Sinclair, Any feedback? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-14155) Automatically select/build the latest svn tag (via "List Subversion tags" build params?)
Title: Message Title Manuel Jesús Recena Soto updated an issue Jenkins / JENKINS-14155 Automatically select/build the latest svn tag (via "List Subversion tags" build params?) Change By: Manuel Jesús Recena Soto Issue Type: New Feature Improvement Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [accurev-plugin] (JENKINS-30336) Accurev plugin 0.6.33 does not work with Accurev installation on Mac ios Yosemite 10.10.5
Title: Message Title Jesper Mønsted assigned an issue to Unassigned Jenkins / JENKINS-30336 Accurev plugin 0.6.33 does not work with Accurev installation on Mac ios Yosemite 10.10.5 Change By: Jesper Mønsted Assignee: Joshua Sherwood Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-custom-build-environment-plugin] (JENKINS-31166) 'ls' and 'mkdir' "not found" since v1.6.2
Title: Message Title Cyrille Le Clerc created an issue Jenkins / JENKINS-31166 'ls' and 'mkdir' "not found" since v1.6.2 Issue Type: Bug Assignee: Nicolas De Loof Attachments: config.xml Components: docker-custom-build-environment-plugin Created: 26/Oct/15 9:51 AM Environment: docker-custom-build-environment-plugin 1.6.2 jenkins-core 1.609.3.1 Labels: plugin regression Priority: Major Reporter: Cyrille Le Clerc Shell step env pwd ls -al mkdir -p ./.m2 echo "$(pwd)/.m2/repository" >> ./.m2/settings.xml mvn -B -V -s ./.m2/settings.xml verify -Dselenium.host=127.0.0.1
[JIRA] [core] (JENKINS-31015) Failure when downloading zipped artifacts
Title: Message Title Zoltan D commented on JENKINS-31015 Re: Failure when downloading zipped artifacts I observed the same issue after upgrading to 1.634 (on Win2012 x64). I had to rollback to 1.633 as the test framework depends on downloading the whole artifact pack as ZIP. 1.633 works fine. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-31111) DownstreamTriggerParameterContext should be an ExtensibleContext
Title: Message Title Daniel Spilker commented on JENKINS-3 Re: DownstreamTriggerParameterContext should be an ExtensibleContext https://github.com/jenkinsci/job-dsl-plugin/pull/647 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-14155) Automatically select/build the latest svn tag (via "List Subversion tags" build params?)
Title: Message Title Manuel Jesús Recena Soto assigned an issue to Manuel Jesús Recena Soto Jenkins / JENKINS-14155 Automatically select/build the latest svn tag (via "List Subversion tags" build params?) Change By: Manuel Jesús Recena Soto Assignee: Pedro Goncalves Manuel Jesús Recena Soto Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cobertura-plugin] (JENKINS-13889) Cobertura plugin is not able to find code from python coverage
Title: Message Title SCM/JIRA link daemon commented on JENKINS-13889 Re: Cobertura plugin is not able to find code from python coverage Code changed in jenkins User: Karol Judek Path: src/main/java/hudson/plugins/cobertura/CoberturaPublisher.java http://jenkins-ci.org/commit/cobertura-plugin/2ea94adb834c8dbd0c614b8eb93748c43e595150 Log: [FIXED JENKINS-13889] Not able to find source code from subdirectories Code style fixes Fix line endings Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clearcase-plugin] (JENKINS-31165) ClearCase plugin does not Filter destroy sub-branch events
Title: Message Title Saar Netzer created an issue Jenkins / JENKINS-31165 ClearCase plugin does not Filter destroy sub-branch events Issue Type: Bug Assignee: Praqma Support Components: clearcase-plugin Created: 26/Oct/15 9:32 AM Environment: Jenkins 1.624 ClearCase Plugin 1.6 Labels: clearcase clearcaseplugin Filter_destroy_sub-branch_events Priority: Major Reporter: Saar Netzer In our job, ClearCase plugin is set to Filter destroy sub-branch events. However, it is not actually filtering the event and starting a build due to it. This is taken from the job changes list (I removed some naming information, nothing which related to the bug: #002395 (Oct 25, 2015 3:22:58 PM) 1. ClearCase Administrator detail Destroyed branch "/main/xxx/yyy/zzz".
[JIRA] [integrity-plugin] (JENKINS-25228) Using the integrity-plugin together with concurrent builds causes SQL Exceptions
Title: Message Title Leon Leon commented on JENKINS-25228 Re: Using the integrity-plugin together with concurrent builds causes SQL Exceptions Can you please tell me in which PTC plugin version is the problem solved ? We are using version 1.34 and this problem still persisting with workflow jobs. A SQL Exception was caught! Table/View 'SCM_E9A7D857_553C_48D3_AF6D_FF45A06EFD90' does not exist. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-27977) NullPointer & authentication cancelled occure immediately on SVN checkout
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-27977 Re: NullPointer & authentication cancelled occure immediately on SVN checkout An Tran, I would need a step by step process to produce the bug. As I said few comments before, I could not to reproduce the 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] [core] (JENKINS-9598) Overhaul bundled plugins or setup experience
Title: Message Title Patrick Wolf updated an issue Jenkins / JENKINS-9598 Overhaul bundled plugins or setup experience Change By: Patrick Wolf It would be useful to include support for Git in the standard jenkins distribution. As a new Jenkins user, I will like to choose a feature area that I am interested in and Jenkins installs the related plugins for me.As an existing Jenkins user who is upgrading, I will like to choose the feature areas that I am interested in and Jenkins installs the related plugins for me. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-plugin] (JENKINS-31122) Unable to disable Accept merge request on success -functionality
Title: Message Title jsyrjala commented on JENKINS-31122 Re: Unable to disable Accept merge request on success -functionality The fix is available in https://github.com/DABSquared/gitlab-plugin/pull/124 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-31095) 2.0: Jenkins terminology sweep
Title: Message Title Patrick Wolf commented on JENKINS-31095 Re: 2.0: Jenkins terminology sweep Kohsuke Kawaguchi Should we make this an epic and make the related tickets stories under this epic? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [release-plugin] (JENKINS-31159) Release post build steps for Matrix project cannot be set from UI
Title: Message Title
Frédéric Chuong created an issue
Jenkins / JENKINS-31159
Release post build steps for Matrix project cannot be set from UI
Issue Type:
Bug
Assignee:
Peter Hayes
Components:
release-plugin
Created:
26/Oct/15 6:37 AM
Environment:
Jenkins 1.619 release-plugin 2.5.3
Labels:
release-plugin jelly matrix
Priority:
Major
Reporter:
Frédéric Chuong
Assigning release build steps to After failed or successful release build and all matrix configurations is impossible from Jelly UI because of code duplication in src/main/resources/hudson/plugins/release/ReleaseWrapper/config.jelly 2.5.3:
Line 105
"attach-previous">${%After failed or successful release build}
"postBuildSteps" hasHeader="true"
descriptors="${h2.getBuildSteps(it)}"
items="${instance.postBuildSteps}"
addCaption="${%Add release
[JIRA] [core] (JENKINS-12462) Jenkins configuration page could be improved
Title: Message Title Patrick Wolf updated an issue Jenkins / JENKINS-12462 Jenkins configuration page could be improved Change By: Patrick Wolf Labels: 2.0 user-experience Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-31162) New item categorization and dynamic choice offering
Title: Message Title Patrick Wolf created an issue Jenkins / JENKINS-31162 New item categorization and dynamic choice offering Issue Type: Story Assignee: Unassigned Components: core Created: 26/Oct/15 7:49 AM Labels: 2.0 Priority: Minor Reporter: Patrick Wolf This is the first segment of the item creation step. As plugins add new item types for creation, it would be nice if they could be categorized. Then the GUI could decide based on the total number and distribution of item types, exactly how or if they should be categorize Add Comment
[JIRA] [ec2-plugin] (JENKINS-26493) Use new EC2 API endpoint hostnames
Title: Message Title Manuel Stadelmann reopened an issue See my latest comment on this issue. It could be that I did something strange but I think the error I got is worth looking into. Jenkins / JENKINS-26493 Use new EC2 API endpoint hostnames Change By: Manuel Stadelmann Resolution: Fixed 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] [jira-plugin] (JENKINS-31164) Hardcoded Bug value will not work with JIRA 7.0
Title: Message Title
Radek Antoniuk updated an issue
Jenkins / JENKINS-31164
Hardcoded Bug value will not work with JIRA 7.0
Change By:
Radek Antoniuk
JIRA 7.0 comes in different flavors and because of that it does not have the "Bug" with ID=1 that is hardcoded in JiraRestService class.Need to provide a configuration dropdown field to select issue type. This results in an NPE during Create Issue task:{code}java.lang.NullPointerExceptionat hudson.plugins.jira.JiraSession.createIssue(JiraSession.java:305){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] [jira-plugin] (JENKINS-31164) Hardcoded Bug value will not work with JIRA 7.0
Title: Message Title Radek Antoniuk created an issue Jenkins / JENKINS-31164 Hardcoded Bug value will not work with JIRA 7.0 Issue Type: Bug Assignee: Unassigned Components: jira-plugin Created: 26/Oct/15 9:19 AM Priority: Minor Reporter: Radek Antoniuk JIRA 7.0 comes in different flavors and because of that it does not have the "Bug" with ID=1 that is hardcoded in JiraRestService class. Need to provide a configuration dropdown field to select issue type. Add Comment
[JIRA] [core] (JENKINS-31160) Update Jenkins UI not to call everything a "Build"
Title: Message Title Patrick Wolf created an issue Jenkins / JENKINS-31160 Update Jenkins UI not to call everything a "Build" Issue Type: Improvement Assignee: Unassigned Components: core Created: 26/Oct/15 6:54 AM Labels: 2.0 Priority: Minor Reporter: Patrick Wolf Jenkins (core, plugins, etc.) has a tendency to call everything a "build". These days, "build" tends to conjure thoughts of Continuous Integration use cases only. In fact, our very own [~uaarkoti] wrote a plugin so users could change the "build now" button to "deploy now" (or whatever his customer's heart desired). There are many other areas in Jenkins where the notion of "build" is the default. This RFE requests updating them to a more fashionable term. It seems there are two options: Jenkins either needs to be "smarter" to know there are different types of things (eg: Build Job, Test Job, Deploy Job, Pipeline) Or we need a more acceptable generic word than "build" (since it seems less
[JIRA] [release-plugin] (JENKINS-31159) Release post build steps for Matrix project cannot be set from UI
Title: Message Title
Frédéric Chuong updated an issue
Jenkins / JENKINS-31159
Release post build steps for Matrix project cannot be set from UI
Change By:
Frédéric Chuong
Assigning release build steps to _After failed or successful release build and all matrix configurations_ is impossible from Jelly UI because of code duplication in {{src/main/resources/hudson/plugins/release/ReleaseWrapper/config.jelly}} 2.5.3:Line 105{code:xml} ${%After failed or successful release build} ${%After failed or successful release build and all matrix configurations}
[JIRA] [core] (JENKINS-31163) OSS Multi-select column
Title: Message Title Patrick Wolf created an issue Jenkins / JENKINS-31163 OSS Multi-select column Issue Type: Story Assignee: Unassigned Components: core Created: 26/Oct/15 7:58 AM Labels: 2.0 Priority: Minor Reporter: Patrick Wolf As a Jenkins user, I would like to be able to select multiple items from a view and run operations against that subset of items. Acceptance Criteria. The user is able to select multiple items from a single item group. There will be a way to select items from a normal view. The user shouldn't have to navigate to a special screen to select items. Once the user selects an item, they are shown a list of operations which can be applied to multiple items
[JIRA] [core] (JENKINS-25488) New UI wastes horizontal space
Title: Message Title Patrick Wolf updated an issue Jenkins / JENKINS-25488 New UI wastes horizontal space Change By: Patrick Wolf Labels: 2.0 user-experience Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-30682) JIRA ticket creation failing with java.lang.NullPointerException
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-30682 JIRA ticket creation failing with java.lang.NullPointerException Change By: Radek Antoniuk Labels: confirmed jira-plugin-2.0.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-30682) JIRA ticket creation failing with java.lang.NullPointerException
Title: Message Title Radek Antoniuk assigned an issue to Radek Antoniuk Jenkins / JENKINS-30682 JIRA ticket creation failing with java.lang.NullPointerException 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] [ec2-plugin] (JENKINS-26493) Use new EC2 API endpoint hostnames
Title: Message Title Manuel Stadelmann commented on JENKINS-26493 Re: Use new EC2 API endpoint hostnames I tested a snapshot but ran into problems. First, the aws-java-sdk plugin is only available in version 1.10.26 from within Jenkins but the EC2 plugin depends on 1.10.16. You should probably update to 1.10.26 prior to release. I got the 1.10.16 version of aws-java-sdk from the archive and could manually install the 1.30-SNAPSHOT of the ec2 plugin. When I tried to test the connection from withing "Manage Jenkins" -> "Cloud" -> "Amazon EC2" for the AZ eu-central-1 i got an error: AWS was not able to validate the provided access credentials (Service: AmazonEC2; Status Code: 401; Error Code: AuthFailure; Request ID: ea2e20e5-1e5f-4339-be55-721b6b1a66bc) When I try to test the connection to any other availability zone where the the key is missing I get The EC2 key pair private key isn't registered to this EC2 region (fingerprint is fd:1c::7e) It seems like there is still a problem with the APIs and eu-central-1 Full stack trace: Oct 26, 2015 8:14:12 AM hudson.plugins.ec2.EC2Cloud$DescriptorImpl doTestConnection WARNING: Failed to check EC2 credential com.amazonaws.AmazonServiceException: AWS was not able to validate the provided access credentials (Service: AmazonEC2; Status Code: 401; Error Code: AuthFailure; Request ID: ea2e20e5-1e5f-4339-be55-721b6b1a66bc) at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:1181) at com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:766) at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:485) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:306) at com.amazonaws.services.ec2.AmazonEC2Client.invoke(AmazonEC2Client.java:11901) at com.amazonaws.services.ec2.AmazonEC2Client.describeInstances(AmazonEC2Client.java:5940) at com.amazonaws.services.ec2.AmazonEC2Client.describeInstances(AmazonEC2Client.java:11256) at hudson.plugins.ec2.EC2Cloud$DescriptorImpl.doTestConnection(EC2Cloud.java:616) at hudson.plugins.ec2.AmazonEC2Cloud$DescriptorImpl.doTestConnection(AmazonEC2Cloud.java:175) 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:497) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at
[JIRA] [jira-plugin] (JENKINS-30682) JIRA ticket creation fails when no components in JIRA project exist
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-30682 JIRA ticket creation fails when no components in JIRA project exist Change By: Radek Antoniuk Summary: JIRA ticket creation failing with java.lang.NullPointerException fails when no components in JIRA project exist Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-30682) Ticket creation fails when no components in JIRA project exist / JIRA rejects empty component list
Title: Message Title Thom Wilhelm commented on JENKINS-30682 Re: Ticket creation fails when no components in JIRA project exist / JIRA rejects empty component list Hey Radek Antoniuk thanks so much that's fixed the issue for us. Legend. Big up yourself. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug. Details: ------- org.apache.velocity.exception.MethodInvocationException: Inv
Title: Message Title Daniel Beck deleted an issue test / TEST-56 On average a physically active man needs around 2,500 calories per day, while a woman needs 2,000. If we eat any more, the extra energy is stored for later use, mostly as fat. This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-31174) Exceptions during script evaluation not logged
Title: Message Title Dan Alvizu commented on JENKINS-31174 Re: Exceptions during script evaluation not logged PR: https://github.com/jenkinsci/job-dsl-plugin/pull/649 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-30519) Declarative job properties in multibranch
Title: Message Title Jesse Glick commented on JENKINS-30519 Re: Declarative job properties in multibranch Pending JENKINS-27295, using ParametersDefinitionProperty is not ideal since the first build (or the first build to request this job property) will not be started with any parameters, so even default parameter values will not be honored: you need to manually fall back to some default. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-31174) Exceptions during script evaluation not logged
Title: Message Title
Dan Alvizu created an issue
Jenkins / JENKINS-31174
Exceptions during script evaluation not logged
Issue Type:
Bug
Assignee:
Dan Alvizu
Components:
job-dsl-plugin
Created:
26/Oct/15 7:18 PM
Priority:
Minor
Reporter:
Dan Alvizu
To reproduce:
Create a freestyle project with the following as DSL script
project {
job {
foo()
}
}
Run
Expect:
Error saying foo() is not a valid method
Observe: generate 'Error calling extension' message, no detail
[JIRA] [core] (JENKINS-31089) Signature verification failed in update site 'default'
Title: Message Title Keith Albright commented on JENKINS-31089 Re: Signature verification failed in update site 'default' For now, use the workaround by changing the Java security jdk.certpath.disabledAlgorithms=MD2, RSA keySize < 1024 to jdk.certpath.disabledAlgorithms=MD2, RSA keySize < 512 jre/lib/security/java.security (should be /Library/Java/JavaVirtualMachines/jdk1.8.0_XX.jdk/Contents/Home/jre/lib/security/java.security on OS X), Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-26493) Use new EC2 API endpoint hostnames
Title: Message Title Johannes Weißl commented on JENKINS-26493 Re: Use new EC2 API endpoint hostnames @Manuel Stadelmann: I had the same problem with aws-java-sdk and with the 401 error. But I discovered that in my case it was not the fault of the ec2-plugin: While the IAM credentials worked with aws-cli from my laptop, I got the same 401 error when using the aws-cli from the EC2 instance where Jenkins was running. Can you confirm if you experience the same behavior? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-31089) Signature verification failed in update site 'default'
Title: Message Title Florian Koch commented on JENKINS-31089 Re: Signature verification failed in update site 'default' the issue "Signature verification failed in downloadable 'hudson.tasks.Maven.MavenInstaller' (show details)" is not gone any News on this? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [rundeck-plugin] (JENKINS-31150) Support Multiple SCM tags for rundeck notifier
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31150 Re: Support Multiple SCM tags for rundeck notifier Code changed in jenkins User: Yuri Goikhman Path: src/main/java/org/jenkinsci/plugins/rundeck/RundeckNotifier.java src/test/java/org/jenkinsci/plugins/rundeck/RundeckNotifierTest.java http://jenkins-ci.org/commit/rundeck-plugin/b20a96e5046ed751af9c0fdd5ec7e71d66ef6e7d Log: JENKINS-31150 - supporting multiple coma separated scm tags, aded tests Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [rundeck-plugin] (JENKINS-31150) Support Multiple SCM tags for rundeck notifier
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31150 Re: Support Multiple SCM tags for rundeck notifier Code changed in jenkins User: Yuri Goikhman Path: src/main/java/org/jenkinsci/plugins/rundeck/RundeckNotifier.java src/test/java/org/jenkinsci/plugins/rundeck/RundeckNotifierTest.java http://jenkins-ci.org/commit/rundeck-plugin/3ddad7c59b29c6fd99b29aa1430f6aba6c8274ce Log: JENKINS-31150 - supporting multiple coma separated scm tags Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [rundeck-plugin] (JENKINS-31150) Support Multiple SCM tags for rundeck notifier
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31150 Re: Support Multiple SCM tags for rundeck notifier Code changed in jenkins User: Yuri Goikhman Path: src/test/java/org/jenkinsci/plugins/rundeck/RundeckNotifierTest.java http://jenkins-ci.org/commit/rundeck-plugin/2829e69510442dd25dfc232483a64a0b85883a50 Log: JENKINS-31150 - supporting multiple coma separated scm tags, remove unnecessary imports from previous commit Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-27140) Workflow support for Integrity SCM Plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27140 Re: Workflow support for Integrity SCM Plugin Code changed in jenkins User: Cletus D'Souza Path: src/main/java/hudson/scm/IntegritySCM.java src/main/java/hudson/scm/IntegritySCMLabelNotifierStep.java src/main/java/hudson/scm/IntegritySCMLabelStep.java src/main/java/hudson/scm/IntegritySCMStep.java src/main/resources/hudson/scm/IntegritySCMLabelStep/config.jelly src/main/resources/hudson/scm/IntegritySCMStep/config.jelly http://jenkins-ci.org/commit/integrity-plugin/cb0561f4265def5bcac0a8a02585d2103e636d74 Log: Added support for SCM Tagging in continuation of JENKINS-27140 workflow steps Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-24331) Progress JIRA issue by workflow action does not work if field is required
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-24331 Progress JIRA issue by workflow action does not work if field is required Change By: Radek Antoniuk Summary: [JIRA Plugin] Progress JIRA issue by workflow action does not work if field is required Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25829) Proxy configuration does not work
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-25829 Proxy configuration does not work Change By: Radek Antoniuk Summary: [JIRA Plugin] Proxy configuration does not work Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-plugin] (JENKINS-24331) [JIRA Plugin] Progress JIRA issue by workflow action does not work if field is required
Title: Message Title Radek Antoniuk commented on JENKINS-24331 Re: [JIRA Plugin] Progress JIRA issue by workflow action does not work if field is required Rodolfo, can you explain your usecase? Jonathan's workaround should be the way to go. If you have a transition that requires some input of data, how do you want Jenkins to determine the value of the required JIRA field? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [naginator-plugin] (JENKINS-26637) naginator doesn't apply regexp to multi-configuration child builds
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26637 Re: naginator doesn't apply regexp to multi-configuration child builds Code changed in jenkins User: ikedam Path: pom.xml src/main/java/com/chikli/hudson/plugin/naginator/NaginatorPublisher.java src/main/java/com/chikli/hudson/plugin/naginator/NaginatorPublisherScheduleAction.java src/main/resources/com/chikli/hudson/plugin/naginator/NaginatorPublisher/config.jelly src/test/java/com/chikli/hudson/plugin/naginator/NaginatorListenerTest.java src/test/java/com/chikli/hudson/plugin/naginator/NaginatorPublisherTest.java src/test/java/com/chikli/hudson/plugin/naginator/testutils/MyBuilder.java http://jenkins-ci.org/commit/naginator-plugin/82ff6a07f300b0795b83e310b7b51e8f7edeb5ef Log: Merge pull request #21 from ikedam/feature/regexpForMatrixChildren [FIXED JENKINS-26637] Allow regexp applied for matrix children logs Compare: https://github.com/jenkinsci/naginator-plugin/compare/6b07b088edcd...82ff6a07f300 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [naginator-plugin] (JENKINS-26637) naginator doesn't apply regexp to multi-configuration child builds
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-26637 naginator doesn't apply regexp to multi-configuration child builds Change By: SCM/JIRA link daemon Resolution: Fixed Status: In Progress Resolved Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [versionnumber-plugin] (JENKINS-30224) NPE thrown when a job uses an automatically installed JDK
Title: Message Title Deniz Bahadir commented on JENKINS-30224 Re: NPE thrown when a job uses an automatically installed JDK I released a new version 1.6 of the plugin. It should be available in the plugin-list within the next 8 hours. Sorry for the delay. I did expect that releasing the plugin was someone else's responsibility. But as it seems, nobody else felt responsible for it and my access-rights where obviously enough to release it myself, so I just did that. I hope, everything worked as expected. If not, please notify me again. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-plugin] (JENKINS-15275) Update Relevant Issues doesn't work with Promote plugin
Title: Message Title Radek Antoniuk resolved as Not A Defect Jenkins / JENKINS-15275 Update Relevant Issues doesn't work with Promote plugin Change By: Radek Antoniuk Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-plugin] (JENKINS-12578) Jira issue parameter value is not exposed via remote API
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-12578 Jira issue parameter value is not exposed via remote API Change By: Radek Antoniuk Labels: confirmed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-31176) Ability to limit job types based on permissions
Title: Message Title Patrick Wolf created an issue Jenkins / JENKINS-31176 Ability to limit job types based on permissions Issue Type: Story Assignee: Unassigned Components: core Created: 27/Oct/15 2:09 AM Labels: 2.0 Priority: Minor Reporter: Patrick Wolf As a Jenkins administrator I want to control what job types users can create. This includes turning off Freestyle and Maven Job types. Ideally, I would be able to set this up based on roles but a binary (on/off) setting at the system level would work initially. Add Comment
[JIRA] [email-ext-plugin] (JENKINS-31177) email notification corrupted due to build failure "FATAL: java.io.IOException: Unexpected termination of the channel"
Title: Message Title hiteswar kumar created an issue Jenkins / JENKINS-31177 email notification corrupted due to build failure "FATAL: java.io.IOException: Unexpected termination of the channel" Issue Type: Bug Assignee: Alex Earl Components: email-ext-plugin Created: 27/Oct/15 4:55 AM Environment: email-ext plugin version- 2.40.5 Priority: Minor Reporter: hiteswar kumar [what] email notification reached to recipient but wrong content in subject and body due to environment variables(like $JOB_NAME, $BUILD_NUMBER) used in subject or in body but not expanded to actual value. this issue when build failed due to below thrown Jenkins master-slave connection : stacktrace below: FATAL: java.io.IOException: Unexpected termination of the channel hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.Request.abort(Request.java:295) at hudson.remoting.Channel.terminate(Channel.java:814) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) at ..remote call to jptolx22585(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356) at hudson.remoting.Request.call(Request.java:171) at hudson.remoting.Channel.call(Channel.java:751) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:173)
[JIRA] [email-ext-plugin] (JENKINS-31046) How to stop the “no changes” mail in e-mail notification.
Title: Message Title srinivas varanasi commented on JENKINS-31046 Re: How to stop the “no changes” mail in e-mail notification. Thanks Tyler. i consulted my issue in wiki page. will i take your help if i 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.
Re:
- Original Message - I NEED YOUR HELP -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-30854) Support AWS SES Message IDs for In-Reply-To header
Title: Message Title
SCM/JIRA link daemon commented on JENKINS-30854
Re: Support AWS SES Message IDs for In-Reply-To header
Code changed in jenkins User: Johannes Weißl Path: src/main/java/hudson/plugins/emailext/ExtendedEmailPublisher.java src/main/java/hudson/plugins/emailext/ExtendedEmailPublisherDescriptor.java src/main/java/hudson/plugins/emailext/plugins/ContentBuilder.java src/main/resources/hudson/plugins/emailext/ExtendedEmailPublisher/config.groovy src/main/resources/hudson/plugins/emailext/ExtendedEmailPublisher/global.groovy src/main/resources/hudson/plugins/emailext/ExtendedEmailPublisher/help-tokens.groovy src/main/resources/hudson/plugins/emailext/ExtendedEmailPublisher/help-tokens.properties src/main/resources/hudson/plugins/emailext/templates/Jive-Formatter-README.md src/main/resources/hudson/plugins/emailext/templates/jive-formatter.groovy src/main/webapp/help/globalConfig/defaultClasspath.html src/main/webapp/help/globalConfig/defaultPostsendScript.html src/main/webapp/help/globalConfig/security.html src/main/webapp/help/projectConfig/defaultClasspath.html src/main/webapp/help/projectConfig/postsendScript.html src/test/java/hudson/plugins/emailext/ExtendedEmailPublisherTest.java src/test/java/hudson/plugins/emailext/plugins/ContentBuilderTest.java src/test/java/hudson/plugins/emailext/plugins/content/TriggerNameContentTest.java src/test/postsend/hudson/plugins/emailext/ExtendedEmailPublisherTestHelper.groovy src/test/resources/recipient-provider-upgrade.xml src/test/resources/recipient-provider-upgrade2.xml http://jenkins-ci.org/commit/email-ext-plugin/8c0c532a524f14730ad221a9d15f98c6341bbd37 Log: Add post-send script feature
For some tasks pre-send scripts are not sufficient, like rewriting the Message-ID based on the SMTP response for later In-Reply-To headers. This is needed when using Amazon Simple Email Service (AWS SES) for sending emails.
Other possible use cases are scripts that act upon failed sending attempts.
Here is a example post-send script that does the message id rewriting for AWS SES:
```groovy import com.sun.mail.smtp.SMTPTransport; import java.util.regex.Matcher; import java.util.regex.Pattern; import hudson.plugins.emailext.ExtendedEmailPublisherDescriptor;
String smtpHost = props.getProperty("mail.smtp.host", ""); String awsRegex = "^email-smtp\\.([a-z0-9-]+)\\.amazonaws\\.com\$"; Pattern p = Pattern.compile(awsRegex); Matcher m = p.matcher(smtpHost); if (m.matches()) { String region = m.group(1); if (transport instanceof SMTPTransport) { String response = ((SMTPTransport)transport).getLastServerResponse(); String[] parts = response.trim().split(" +"); if (parts.length == 3 && parts[0].equals("250") && parts[1].equals("Ok")) { String MessageID = "<" + parts[2] + "@" + region + ".amazonses.com>"; msg.setHeader("Message-ID", MessageID); }
} } ```
References:
https://issues.jenkins-ci.org/browse/JENKINS-30854
https://github.com/jenkinsci/email-ext-plugin/pull/108
http://docs.aws.amazon.com/ses/latest/DeveloperGuide/smtp-response-codes.html
[JIRA] [email-ext-plugin] (JENKINS-30854) Support AWS SES Message IDs for In-Reply-To header
Title: Message Title Alex Earl resolved as Fixed Will be in next release 2.41 Jenkins / JENKINS-30854 Support AWS SES Message IDs for In-Reply-To header Change By: Alex Earl 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] [integrity-plugin] (JENKINS-25228) Using the integrity-plugin together with concurrent builds causes SQL Exceptions
Title: Message Title Cletus D'Souza commented on JENKINS-25228 Re: Using the integrity-plugin together with concurrent builds causes SQL Exceptions Did you say workflow jobs? The plugin doesn't currently support workflow. It will be supported in the next release (1.36) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-30367) Unable to send core-review +2 from one job if 2 jobs triggered for same event
Title: Message Title Scott Hebert commented on JENKINS-30367 Re: Unable to send core-review +2 from one job if 2 jobs triggered for same event Will be present in 2.16.1 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [timestamper-plugin] (JENKINS-31168) display current elapsed time (and time since)
Title: Message Title Adrian Bridgett created an issue Jenkins / JENKINS-31168 display current elapsed time (and time since) Issue Type: Improvement Assignee: stevengbrown Components: timestamper-plugin Created: 26/Oct/15 12:25 PM Priority: Minor Reporter: Adrian Bridgett I find this plugin invaluable for checking for stuck builds or estimating time to finish. One improvement that would make a big difference would be to display the current time (or elapsed time as appropriate) on the last line. Currently if you are using "elapsed time" it's difficult to tell how long the build has been running for. It maybe that you can only filter the log and that this would be very tricky to implement and/or best implemented as a separate plugin in which case please close. Add Comment
[JIRA] [p4-plugin] (JENKINS-31169) NullPointerException if user doesn't exist when collecting changes
Title: Message Title Phil McArdle created an issue Jenkins / JENKINS-31169 NullPointerException if user doesn't exist when collecting changes Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 26/Oct/15 12:26 PM Environment: Jenkins: 1.634 P4 Plugin: 1.3.2 Priority: Minor Reporter: Phil McArdle (p4):stop:6 (p4):cmd:... p4 user -o username p4 user -o username (p4):stop:7 Unable to get current change: java.lang.NullPointerException FATAL: null java.lang.NullPointerException at org.jenkinsci.plugins.p4.changes.P4ChangeSet.store(P4ChangeSet.java:74) at org.jenkinsci.plugins.p4.PerforceScm.checkout(PerforceScm.java:346) at hudson.scm.SCM.checkout(SCM.java:485) at hudson.model.AbstractProject.checkout(AbstractProject.java:1277) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:610) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Finished: FAILURE
[JIRA] [gerrit-trigger-plugin] (JENKINS-31167) Gerrit Trigger: every build has all commits listed in the Changelog
Title: Message Title Andy Wang updated an issue Jenkins / JENKINS-31167 Gerrit Trigger: every build has all commits listed in the Changelog Change By: Andy Wang Attachment: 2015-10-26meitu_1.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] [gerrit-trigger-plugin] (JENKINS-31167) Gerrit Trigger: every build has all commits listed in the Changelog
Title: Message Title Andy Wang updated an issue Jenkins / JENKINS-31167 Gerrit Trigger: every build has all commits listed in the Changelog Change By: Andy Wang Attachment: 2015-10-26_meitu_2.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] [subversion-plugin] (JENKINS-27977) NullPointer & authentication cancelled occure immediately on SVN checkout
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-27977 Re: NullPointer & authentication cancelled occure immediately on SVN checkout An Tran, I'll try it again but the most important thing is to produce the bug. I'm not sure if AD is involved here. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-31167) Gerrit Trigger: every build has all commits listed in the Changes page
Title: Message Title Andy Wang updated an issue Jenkins / JENKINS-31167 Gerrit Trigger: every build has all commits listed in the Changes page Change By: Andy Wang I configed the Gerrit Trigger plugin on jenkins based on the article https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger.On git plugin, I set Refspec to *refs/changes/\*:refs/changes/\** and 'Branches to build' to *$GERRIT_REFSPEC*.The job can be triggered whenever new patch set is created. However, the changelog changes to this build contains all the changes (can show max to 1024 changes in total).This issue bothers me a lot because I'm supposed to send email only to the committer instead of sending emails to all the people contributing to that changelog.Same issue happened in this url: https://groups.google.com/forum/#!topic/jenkinsci-users/KKITzpqG5_s Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-31167) Gerrit Trigger: every build has all commits listed in the Changes page
Title: Message Title Andy Wang updated an issue Jenkins / JENKINS-31167 Gerrit Trigger: every build has all commits listed in the Changes page Change By: Andy Wang Attachment: 2015-10-26meitu_4.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] [jira-plugin] (JENKINS-30682) JIRA ticket creation fails when no components in JIRA project exist
Title: Message Title Radek Antoniuk commented on JENKINS-30682 Re: JIRA ticket creation fails when no components in JIRA project exist Thom, I just released v.2.0.3, give it a try and let me know how it goes. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xunit-plugin] (JENKINS-31101) XUnit is not rendering the test result summary correctly for a Custom tool
Title: Message Title Daniel MS updated an issue Jenkins / JENKINS-31101 XUnit is not rendering the test result summary correctly for a Custom tool Change By: Daniel MS Environment: Jenkins ver. 1.626 xUnit 1.96 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-30393) Don't vote 0 if voting is skipped
Title: Message Title Scott Hebert resolved as Fixed Jenkins / JENKINS-30393 Don't vote 0 if voting is skipped Change By: Scott Hebert 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] [gerrit-trigger-plugin] (JENKINS-30367) Unable to send core-review +2 from one job if 2 jobs triggered for same event
Title: Message Title Scott Hebert resolved as Fixed Jenkins / JENKINS-30367 Unable to send core-review +2 from one job if 2 jobs triggered for same event Change By: Scott Hebert 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] [gerrit-trigger-plugin] (JENKINS-30393) Don't vote 0 if voting is skipped
Title: Message Title Scott Hebert assigned an issue to Scott Hebert Jenkins / JENKINS-30393 Don't vote 0 if voting is skipped Change By: Scott Hebert Assignee: rsandell Scott Hebert Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-30393) Don't vote 0 if voting is skipped
Title: Message Title Scott Hebert commented on JENKINS-30393 Re: Don't vote 0 if voting is skipped Will be present in 2.16.1 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25550) Hard kill
Title: Message Title SCM/JIRA link daemon commented on JENKINS-25550 Re: Hard kill Code changed in jenkins User: Jesse Glick Path: CHANGES.md aggregator/src/test/java/org/jenkinsci/plugins/workflow/WorkflowRunRestartTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/SynchronousNonBlockingStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/durable_task/ShellStepTest.java api/src/main/java/org/jenkinsci/plugins/workflow/actions/ErrorAction.java durable-task-step/src/main/java/org/jenkinsci/plugins/workflow/steps/durable_task/DurableTaskStep.java job/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java step-api/src/main/java/org/jenkinsci/plugins/workflow/steps/AbstractSynchronousNonBlockingStepExecution.java support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/ExecutorStepExecution.java support/src/main/resources/org/jenkinsci/plugins/workflow/support/steps/ExecutorStepExecution/PlaceholderTask/PlaceholderExecutable/executorCell.jelly http://jenkins-ci.org/commit/workflow-plugin/5aca627c9f3c1d58c38c2ac765d4b430044e4433 Log: Merge pull request #141 from jglick/kill- JENKINS-25550 JENKINS-25550 Hard kill Compare: https://github.com/jenkinsci/workflow-plugin/compare/7eb7a8a5e6c4...5aca627c9f3c Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25550) Hard kill
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-25550 Hard kill 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] [jira-plugin] (JENKINS-30829) JIRA Generate Release Notes needs default Environment Variable
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30829 Re: JIRA Generate Release Notes needs default Environment Variable Code changed in jenkins User: Radosław Antoniuk Path: src/main/java/hudson/plugins/jira/JiraCreateReleaseNotes.java src/main/resources/hudson/plugins/jira/JiraCreateReleaseNotes/help-jiraEnvironmentVariable.html src/test/java/hudson/plugins/jira/JiraCreateReleaseNotesTest.java http://jenkins-ci.org/commit/jira-plugin/dc146476026d24b1ee51f183b69ce7416b009534 Log: Add default variable name for ReleaseNotes generation. JENKINS-30829 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25550) Hard kill
Title: Message Title SCM/JIRA link daemon commented on JENKINS-25550 Re: Hard kill Code changed in jenkins User: Jesse Glick Path: CHANGES.md aggregator/src/test/java/org/jenkinsci/plugins/workflow/WorkflowRunTest.java job/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java http://jenkins-ci.org/commit/workflow-plugin/60a0db70e7747d212632854deca1efb5e081cd8b Log: [FIXED JENKINS-25550] Hard kill. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-27718) Build parameter for "List Subversion Tags (and more)" is not exposed to workflow script.
Title: Message Title Josh Shapiro commented on JENKINS-27718 Re: Build parameter for "List Subversion Tags (and more)" is not exposed to workflow script. Thanks for your guys' responses. If anyone else stumbles into this, a simple and inelegant workaround until this is resolved is use an upstream job which uses the subversion plugin for it's ability to poll the repository, converts desired values into string parameters, and then calls the workflow using the converted values. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-30367) Unable to send core-review +2 from one job if 2 jobs triggered for same event
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30367 Re: Unable to send core-review +2 from one job if 2 jobs triggered for same event Code changed in jenkins User: Scott Hebert Path: src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/config/Config.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/config/IGerritHudsonTriggerConfig.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/ParameterExpander.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/job/rest/BuildCompletedRestCommandJob.java src/main/resources/com/sonyericsson/hudson/plugins/gerrit/trigger/GerritServer/index.jelly src/main/webapp/help-GerritBuildFailedCodeReview.html src/main/webapp/help-GerritBuildFailedVerified.html src/main/webapp/help-GerritBuildNotBuiltCodeReview.html src/main/webapp/help-GerritBuildNotBuiltVerified.html src/main/webapp/help-GerritBuildStartedCodeReview.html src/main/webapp/help-GerritBuildStartedVerified.html src/main/webapp/help-GerritBuildSuccessfulCodeReview.html src/main/webapp/help-GerritBuildSuccessfulVerified.html src/main/webapp/help-GerritBuildUnstableCodeReview.html src/main/webapp/help-GerritBuildUnstableVerified.html src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/config/ConfigTest.java src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/ParameterExpanderParameterizedTest.java src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/ParameterExpanderSkipVoteParameterTest.java src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/ParameterExpanderTest.java src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/mock/MockGerritHudsonTriggerConfig.java src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/mock/Setup.java src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/utils/MockPluginCheckerConfig.java http://jenkins-ci.org/commit/gerrit-trigger-plugin/3a5273ee681ad93be9f77b038b77d6523a3be9fb Log: Allow override of code-review/verified value from job Currently, it is NOT possible to have one Jenkins job setting only the Verified label to +1 or -1 and another Jenkins job setting only code-review label to +1 or -1 for the same patch-set in Gerrit. This change will now allow: Setting a code-review or verified value to empty for the Server default value Setting a job specific value for a code-review or verified value Only the jobs that have overridden the value in their configuration will contribute to the code-review or verified value. JENKINS-30367 JENKINS-30393 Change-Id: I08d5b77fc55b49ae2d07a4eb97bbff80aa87b46b
[JIRA] [gerrit-trigger-plugin] (JENKINS-30393) Don't vote 0 if voting is skipped
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30393 Re: Don't vote 0 if voting is skipped Code changed in jenkins User: Scott Hebert Path: src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/config/Config.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/config/IGerritHudsonTriggerConfig.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/ParameterExpander.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/job/rest/BuildCompletedRestCommandJob.java src/main/resources/com/sonyericsson/hudson/plugins/gerrit/trigger/GerritServer/index.jelly src/main/webapp/help-GerritBuildFailedCodeReview.html src/main/webapp/help-GerritBuildFailedVerified.html src/main/webapp/help-GerritBuildNotBuiltCodeReview.html src/main/webapp/help-GerritBuildNotBuiltVerified.html src/main/webapp/help-GerritBuildStartedCodeReview.html src/main/webapp/help-GerritBuildStartedVerified.html src/main/webapp/help-GerritBuildSuccessfulCodeReview.html src/main/webapp/help-GerritBuildSuccessfulVerified.html src/main/webapp/help-GerritBuildUnstableCodeReview.html src/main/webapp/help-GerritBuildUnstableVerified.html src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/config/ConfigTest.java src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/ParameterExpanderParameterizedTest.java src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/ParameterExpanderSkipVoteParameterTest.java src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/ParameterExpanderTest.java src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/mock/MockGerritHudsonTriggerConfig.java src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/mock/Setup.java src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/utils/MockPluginCheckerConfig.java http://jenkins-ci.org/commit/gerrit-trigger-plugin/3a5273ee681ad93be9f77b038b77d6523a3be9fb Log: Allow override of code-review/verified value from job Currently, it is NOT possible to have one Jenkins job setting only the Verified label to +1 or -1 and another Jenkins job setting only code-review label to +1 or -1 for the same patch-set in Gerrit. This change will now allow: Setting a code-review or verified value to empty for the Server default value Setting a job specific value for a code-review or verified value Only the jobs that have overridden the value in their configuration will contribute to the code-review or verified value. JENKINS-30367 JENKINS-30393 Change-Id: I08d5b77fc55b49ae2d07a4eb97bbff80aa87b46b
[JIRA] [hockeyapp-plugin] (JENKINS-31171) Hockeyapp Plugin: Support restricting downloads per team
Title: Message Title Simo Punnonen created an issue Jenkins / JENKINS-31171 Hockeyapp Plugin: Support restricting downloads per team Issue Type: Improvement Assignee: Unassigned Components: hockeyapp-plugin Created: 26/Oct/15 2:46 PM Priority: Minor Reporter: Simo Punnonen Currently the hockeyapp plugin only supports restricting build downloads using tags, however the API also supports restricting based on teams and users. Please implement restricting downloads with teams to the jenkins plugin. Tags in hockeyapp are associated with apps and users. When you have multiple teams, with many users (and people get added / removed), it's more convenient to use teams for restricting app distribution rather than tags. Add Comment
[JIRA] [doxygen-plugin] (JENKINS-31172) doxgen warnings: categorization and/or priority banding
Title: Message Title Greg Moncreaff created an issue Jenkins / JENKINS-31172 doxgen warnings: categorization and/or priority banding Issue Type: Improvement Assignee: Gregory Boissinot Components: doxygen-plugin Created: 26/Oct/15 3:10 PM Priority: Minor Reporter: Greg Moncreaff Current plugin implementation doesn't use any categories or priorities. Suggest it could be improved to use either/both. Current report (warnings detail) text is like: Compound <> is not documented. Member <> of class <> is not documented. parameters of member <> are not (all) documented suggest it have categories like (Compounds, Members, Parameters) priorities may want to let user to decide if if they want all NORMAL (current), or something else. e.g. Compounds=>HIGH; Members=>Normal, Parameters/etc=>LOW Add Comment
[JIRA] [gerrit-trigger-plugin] (JENKINS-31167) Gerrit Trigger: every build has all commits listed in the Changelog
Title: Message Title Andy Wang updated an issue Jenkins / JENKINS-31167 Gerrit Trigger: every build has all commits listed in the Changelog Change By: Andy Wang Component/s: git-client-plugin Component/s: git-plugin Environment: Ubuntu 14.04.3 LTS Jenkins ver. 1.634 Gerrit Trigger 2.16.0 GIT client plugin 1.19.0GIT plugin 2.4.0 java version "1.7.0_79" Gerrit Code Review version: 2.10 Attachment: 2015-10-26meitu_1.png Attachment: 2015-10-26_meitu_2.png I configed the Gerrit Trigger plugin on jenkins based on the article https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger.On git plugin, I set Refspec to * refs/changes/ \ *:refs/changes/ \ * * and 'Branches to build' to *$GERRIT_REFSPEC*.The job can be triggered whenever new patch set is created. However, the changelog to this build contains all the changes (can show max to 1024 changes in total).This issue bothers me a lot because I'm supposed to send email only to the committer instead of sending emails to all the people contributing to that changelog.Same issue happened in this url: https://groups.google.com/forum/#!topic/jenkinsci-users/KKITzpqG5_s Add Comment
[JIRA] [parameterized-remote-trigger-plugin] (JENKINS-31170) Credentials aren't filtered based on entered remote server address (and port)
Title: Message Title Anders Hammar updated an issue Jenkins / JENKINS-31170 Credentials aren't filtered based on entered remote server address (and port) Change By: Anders Hammar Both in the server's config and the job's config, all credentials configured in the server show up in the drop-down list regardless of the credentials' configured domain. Using domains for the credentials they are supposed to be filtered which doesn't seem to work.What I have:* A credential domain for the hostname "remotejenkins.acme.org"* In the server's config I've configured the "Remote address and port" in "Parameterized Remote Trigger Configuration" as "http://remotejenkins.acme.org"What I then see:* In the credentials drop-down list (both in server's config and job's config) lists all credentails configured are listed regardless of credentail credential domain. Even credential credentials configured for hostname such as "svn.acme.org". Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-remote-trigger-plugin] (JENKINS-31170) Credentials aren't filtered based on entered remote server address (and port)
Title: Message Title Anders Hammar created an issue Jenkins / JENKINS-31170 Credentials aren't filtered based on entered remote server address (and port) Issue Type: Bug Assignee: Maurice W. Components: parameterized-remote-trigger-plugin Created: 26/Oct/15 12:51 PM Environment: Jenkins LTS v1.609.3 parameterized-remote-trigger-plugin v2.2.2 credentials plugin v1.24 Oracle JDK 1.7.0_75 Priority: Minor Reporter: Anders Hammar Both in the server's config and the job's config, all credentials configured in the server show up in the drop-down list regardless of the credentials' configured domain. Using domains for the credentials they are supposed to be filtered which doesn't seem to work. What I have: A credential domain for the hostname "remotejenkins.acme.org" In the server's config I've configured the "Remote address and port" in "Parameterized Remote Trigger Configuration" as "http://remotejenkins.acme.org"
[JIRA] [log-parser-plugin] (JENKINS-26572) Log Parser incompatible with Jenkins 1.597 (build record change)
Title: Message Title Mark Sinclair commented on JENKINS-26572 Re: Log Parser incompatible with Jenkins 1.597 (build record change) I can provide feedback in mid Nov - next scheduled downtime when I can reboot and update Jenkins plugins. If time allows, I'll get a test server up and running... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-plugin] (JENKINS-31103) How to troubleshoot maximum number of statuses errors?
Title: Message Title Kanstantsin Shautsou commented on JENKINS-31103 Re: How to troubleshoot maximum number of statuses errors? I wish some performance tests. Traffic can be dumped and measured somehow. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-30682) JIRA ticket creation fails when no components in JIRA project exist
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30682 Re: JIRA ticket creation fails when no components in JIRA project exist Code changed in jenkins User: Radosław Antoniuk Path: src/main/java/hudson/plugins/jira/JiraCreateIssueNotifier.java src/main/java/hudson/plugins/jira/JiraRestService.java src/main/java/hudson/plugins/jira/JiraSession.java http://jenkins-ci.org/commit/jira-plugin/43f5439fa5e5ea2dbc4b74773945b242db551913 Log: JENKINS-30682 - Fix NPE on empty Component list in JIRA project. #nomerge - this was already changed in master. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-27977) NullPointer & authentication cancelled occure immediately on SVN checkout
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-27977 Re: NullPointer & authentication cancelled occure immediately on SVN checkout An Tran, By the way, this ticket JENKINS-29340 is completely different and is solved. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-remote-trigger-plugin] (JENKINS-31170) Credentials aren't filtered based on entered remote server address (and port)
Title: Message Title Anders Hammar commented on JENKINS-31170 Re: Credentials aren't filtered based on entered remote server address (and port) Possibly this could be due to something in the credentials plugin. I see a similar behavior for a different plugin using credentials. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [log-parser-plugin] (JENKINS-26572) Log Parser incompatible with Jenkins 1.597 (build record change)
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-26572 Re: Log Parser incompatible with Jenkins 1.597 (build record change) Mark Sinclair, Ok. Do not you try it locally? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-30682) Ticket creation fails when no components in JIRA project exist / JIRA rejects empty component list
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-30682 Ticket creation fails when no components in JIRA project exist / JIRA rejects empty component list Change By: Radek Antoniuk Summary: JIRA ticket Ticket creation fails when no components in JIRA project exist / JIRA rejects empty component list Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [test1] (TEST-56) On average a physically active man needs around 2,500 calories per day, while a woman needs 2,000. If we eat any more, the extra energy is stored for later use, mostly as fat.
Title: Message Title Gembrot Bokong closed an issue as Fixed http://www.vimaxpalsu.com test / TEST-56 On average a physically active man needs around 2,500 calories per day, while a woman needs 2,000. If we eat any more, the extra energy is stored for later use, mostly as fat. Change By: Gembrot Bokong 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] [gerrit-trigger-plugin] (JENKINS-31167) Gerrit Trigger: every build has all commits listed in the Changelog
Title: Message Title Andy Wang updated an issue Jenkins / JENKINS-31167 Gerrit Trigger: every build has all commits listed in the Changelog Change By: Andy Wang I configed the Gerrit Trigger plugin on jenkins based on the article https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger.On git plugin, I set Refspec to * refs/changes/*:refs/changes/* * and 'Branches to build' to * $GERRIT_REFSPEC * .The job can be triggered whenever new patch set is created. However, the changelog to this build contains all the changes (can show max to 1024 changes in total).This issue bothers me a lot because I'm supposed to send email only to the committer instead of sending emails to all the people contributing to that changelog.Same issue happened in this url: https://groups.google.com/forum/#!topic/jenkinsci-users/KKITzpqG5_s Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-31167) Gerrit Trigger: every build has all commits listed in the Changelog
Title: Message Title Andy Wang updated an issue Jenkins / JENKINS-31167 Gerrit Trigger: every build has all commits listed in the Changelog Change By: Andy Wang I configed the Gerrit Trigger plugin on jenkins based on the article https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger.On git plugin, I set Refspec to * refs/changes/*:refs/changes/* * and 'Branches to build' to *$GERRIT_REFSPEC*.The job can be triggered whenever new patch set is created. However, the changelog to this build contains all the changes (can show max to 1024 changes in total).This issue bothers me a lot because I'm supposed to send email only to the committer instead of sending emails to all the people contributing to that changelog.Same issue happened in this url: https://groups.google.com/forum/#!topic/jenkinsci-users/KKITzpqG5_s Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-27977) NullPointer & authentication cancelled occure immediately on SVN checkout
Title: Message Title An Tran commented on JENKINS-27977 Re: NullPointer & authentication cancelled occure immediately on SVN checkout Manuel Jesús Recena Soto I wish I can post our settings here. But it's a complex master slave setup inside an enterprise network. One thing I can say that we didn't have this issue before we use the "SVN External" feature. After add that we start facing this error sporadically. I found some other tickets about this issue here: Subversion fails to update externals once after external is changed. : https://issues.jenkins-ci.org/browse/JENKINS-25070 E200015: ISVNAuthentication provider did not provide credentials : https://issues.jenkins-ci.org/browse/JENKINS-29340 / Check for changes in folders linked via svn:externals fails due to missing credentials: https://issues.jenkins-ci.org/browse/JENKINS-21785 NullPointer & authentication cancelled occure immediately on SVN checkout: https://issues.jenkins-ci.org/browse/JENKINS-27977 I tried everything from those tickets but couldn't make the error disappeared. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
