[JIRA] (JENKINS-37717) CHANGES_SINCE_LAST_SUCCESS is not expanded for jenkins pipeline
Title: Message Title
Andy Wang commented on JENKINS-37717
Re: CHANGES_SINCE_LAST_SUCCESS is not expanded for jenkins pipeline
Thanks David van Laatum I've encountered a situation here: Before pipeline was put into use, I used normal Freestyle job. In build actions, I used Inject environment vairables from a properties file in my workspace. The properties in the file contained the necessary variables which I would use in my email. So my email ext plugin's body part was like below:
"status">
"info">"6">$rom_type $BuildType Build $status
"main round_border">
$rom_type $BuildType Build $status
Build Artifact:
"$ROM_URL">$ROM_URL
The variables like rom_type and ROM_URL was set in the properties file. After migrated the job to pipeline, the variables in the properties file are failed to work. I've tried use withEnv and """ """ to wrap my email content. It is a temporary workaround but the {CHANGES_SINCE_LAST_SUCCESS, reverse="true", showPaths="true"} would fail to work. So I tried use ''' ''' to wrap my content. The {CHANGES_SINCE_LAST_SUCCESS, reverse="true", showPaths="true"} worked, but variables failed. What should I do to keep both work? Thank you.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message
[JIRA] (JENKINS-37717) CHANGES_SINCE_LAST_SUCCESS is not expanded for jenkins pipeline
Title: Message Title
Andy Wang commented on JENKINS-37717
Re: CHANGES_SINCE_LAST_SUCCESS is not expanded for jenkins pipeline
I've read JENKINS-35367, but still don't get how to use {CHANGES_SINCE_LAST_SUCCESS, reverse="true", showPaths="true"} in pipeline. Is it right to put it in a template and use it? An example would be nice. Thank you!
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32796) Can't update plugins: incorrect checksum
Title: Message Title Andy Wang commented on JENKINS-32796 Re: Can't update plugins: incorrect checksum Just out of curiosity, is there anyone who's not from China also encountered this problem? Maybe it's the Chinese network issue. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32796) Can't update plugins: incorrect checksum
Title: Message Title Andy Wang commented on JENKINS-32796 Re: Can't update plugins: incorrect checksum Same problem here. java.io.IOException: Downloaded file /var/lib/jenkins/plugins/jquery-detached.jpi.tmp does not match expected SHA-1, expected 'vuqbKZ3z2kJ78+Nc90ySO72bN9g=', actual '3GcisaizOxcwYMb7SuFf/INCny4=' at hudson.model.UpdateCenter.verifyChecksums(UpdateCenter.java:1799) at hudson.model.UpdateCenter.access$1100(UpdateCenter.java:147) at hudson.model.UpdateCenter$InstallationJob.replace(UpdateCenter.java:1950) at hudson.model.UpdateCenter$UpdateCenterConfiguration.install(UpdateCenter.java:1194) at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1669) at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1864) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1640) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110) at java.lang.Thread.run(Thread.java:745) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email
[JIRA] (JENKINS-32796) Can't update plugins: incorrect checksum
Title: Message Title Andy Wang assigned an issue to Oleg Nenashev Jenkins / JENKINS-32796 Can't update plugins: incorrect checksum Change By: Andy Wang Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32796) Can't update plugins: incorrect checksum
Title: Message Title Andy Wang updated an issue Jenkins / JENKINS-32796 Can't update plugins: incorrect checksum Change By: Andy Wang Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36568) workflow script node step cannot trigger build on specific node
Title: Message Title
Andy Wang edited a comment on JENKINS-36568
Re: workflow script node step cannot trigger build on specific node
Thank you [Cuong Tran|https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=ctran]. The solulition is as follows.# Install [Node and Label parameter plugin|https://wiki.jenkins-ci.org/display/JENKINS/NodeLabel+Parameter+Plugin]# In test_job's configuration, select 'This build is parameterized' and add a Label parameter and set the parameter name to 'node'# In pipeline script, use [Cuong Tran|https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=ctran]'s code:{code:java}build job: 'test_job', parameters: [[$class: 'LabelParameterValue', name: 'node', label: 'tester1']]build job: 'test_job', parameters: [[$class: 'LabelParameterValue', name: 'node', label: 'tester2']]{code}And the job will be built as I wanted.*However*, I think it is only a workaround. I still believe this is a bug. Because the node step should do its jobs job instead of letting other plugins to fulfill them do for it .
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36568) workflow script node step cannot trigger build on specific node
Title: Message Title Andy Wang commented on JENKINS-36568 Re: workflow script node step cannot trigger build on specific node Thank you Cuong Tran. The solulition is as follows. Install Node and Label parameter plugin In test_job's configuration, select 'This build is parameterized' and add a Label parameter and set the parameter name to 'node' In pipeline script, use Cuong Tran's code: build job: 'test_job', parameters: [[$class: 'LabelParameterValue', name: 'node', label: 'tester1']] build job: 'test_job', parameters: [[$class: 'LabelParameterValue', name: 'node', label: 'tester2']] And the job will be built as I wanted. However, I think it is only a workaround. I still believe this is a bug. Because the node step should do its jobs instead of letting other plugins to fulfill them. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving
[JIRA] (JENKINS-36568) workflow script node step cannot trigger build on specific node
Title: Message Title
Andy Wang updated an issue
Jenkins / JENKINS-36568
workflow script node step cannot trigger build on specific node
Change By:
Andy Wang
I have a Jenkins pipeline job called "TestPipeline". I want to trigger a build on 2 different slaves which labeled "tester1' and "tester2". And the pipeline script is quite simple here:{code:java}node('tester1') {build 'test_job'}node('tester2') {build 'test_job'}{code}However when I run the TestPipeline job, the "test_job" won't run on the nodes which I assigned. But run on random nodes instead.I'm wondering if I should set "Restrict where this project can be run" on my "test_job". So I set it to "tester" (The "tester" label contains both node "tester1" and "tester2"). But when I run the pipeline job again, the "test_job" runs on "tester2" twice. I should expect the job to run on "tester1" first and then run on "tester2". So the build job step runs regardless of node option step ?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36568) workflow script node step cannot trigger build on specific node
Title: Message Title
Andy Wang created an issue
Jenkins / JENKINS-36568
workflow script node step cannot trigger build on specific node
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
2016/Jul/11 10:23 AM
Environment:
Jenkins 2.11 Pipeline plugin 2.2
Labels:
pipeline pipeline-build-step-plugin workflow
Priority:
Major
Reporter:
Andy Wang
I have a Jenkins pipeline job called "TestPipeline". I want to trigger a build on 2 different slaves which labeled "tester1' and "tester2". And the pipeline script is quite simple here:
node('tester1') {
build 'test_job'
}
node('tester2') {
build 'test_job'
}
However when I run the TestPipeline job, the "test_job" won't run on the nodes which I assigned. But run on random nodes instead. I'm wondering if I should set "Restrict where this project can be run" on my "test_job". So I set it to "tester" (The "tester" label contains both node "tester1" and "tester2"). But when I run the pipeline job again, the "test_job" runs on "tester2" twice. I should expect the job to run on "tester1" first and then run on "tester2". So the build job step runs regardless of node option?
[JIRA] [gerrit-trigger-plugin] (JENKINS-32898) Disable Strict Forbidden File Verification option always causes trigger
Title: Message Title Andy Wang updated an issue Jenkins / JENKINS-32898 Disable Strict Forbidden File Verification option always causes trigger Change By: Andy Wang Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-21383) Restart feature in update center is brittle
Title: Message Title Andy Wang updated an issue Jenkins / JENKINS-21383 Restart feature in update center is brittle Change By: Andy Wang Labels: 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] [gerrit-trigger-plugin] (JENKINS-31167) Gerrit Trigger: every build has all commits listed in the Changes page
Title: Message Title Andy Wang commented on JENKINS-31167 Re: Gerrit Trigger: every build has all commits listed in the Changes page I did as the mailing list said: set Refspec to $GERRIT_REFSPEC, branches to $GERRIT_BRANCH and it didn't work for me. Then I changed the branch to origin/$GERRIT_BRANCH, it all worked. I guess that the $GERRIT_BRANCH only pass "master" to git plugin, and it need full branch name like origin/master. So problem solved but I think the plugin doc do need some correction. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-31430) Gerrit Trigger Plugin: shouldn't mark aborted jobs as failure
Title: Message Title Andy Wang created an issue Jenkins / JENKINS-31430 Gerrit Trigger Plugin: shouldn't mark aborted jobs as failure Issue Type: Bug Assignee: rsandell Attachments: 2015-11-06-112620_meitu_1.png Components: gerrit-trigger-plugin Created: 06/Nov/15 3:54 AM Environment: Ubuntu 14.04.3 LTS Jenkins ver. 1.636 Gerrit Trigger 2.17.2 GIT client plugin 1.19.0 GIT plugin 2.4.0 java version "1.7.0_79" Gerrit Code Review version: 2.10 Labels: gerrit-trigger Priority: Critical Reporter: Andy Wang I have 4 jobs triggered by 1 gerrit event. If I manually abort 1 of the 4 running jobs, the result of this job will be sent to gerrit server as failure, which makes code-review -1 as a result. This is not what it is supposed to
[JIRA] [gerrit-trigger-plugin] (JENKINS-20607) Gerrit trigger caused git plugin polling to not ignore commit from certain users
Title: Message Title Andy Wang assigned an issue to rsandell Jenkins / JENKINS-20607 Gerrit trigger caused git plugin polling to not ignore commit from certain users Change By: Andy Wang Assignee: rsandell Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-20607) GIT Plugin 2.0: Polling ignores commit from certain users not working
Title: Message Title Andy Wang commented on JENKINS-20607 Re: GIT Plugin 2.0: Polling ignores commit from certain users not working Mark Waite I tested on a small job without Gerrit-trigger plugin. And the result showed that the polling ignores are well functioning. I tested on all three ignore commit options( by user name, by commit message and by file path), they all worked no matter if the "Force polling using workspace" checked or not. But once added Gerrit-trigger plugin, it didn't work. The job triggers on all commits despite the polling ignore settings. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-20607) GIT Plugin 2.0: Polling ignores commit from certain users not working
Title: Message Title Andy Wang commented on JENKINS-20607 Re: GIT Plugin 2.0: Polling ignores commit from certain users not working Hitting the issue and the workaround doesn't work for me. Using Jenkins ver. 1.635; Git plugin 2.4.0; Gerrit-trigger plugin 2.17.0 I set both ignore commit from certain users and in certain paths. But neither worked. How do people deal with it when it relates to change version number in certain file and don't want that to trigger a build? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-14767) Add Reporting Values for Aborted jobs. Currently an aborted job uses the fail value not something everyone will want.
Title: Message Title Andy Wang commented on JENKINS-14767 Re: Add Reporting Values for Aborted jobs. Currently an aborted job uses the fail value not something everyone will want. Yeah. The problem bothers me a lot. My gerrit triggered jobs are to set code-review -1 when build failed. Whenever I manually cancel a job it set the corresponding patch set to code-review -1, which is not what I should expected. I think it would be nice to add a skip value for aborted builds or just don't count canceled build as build failure. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-14767) Add Reporting Values for Aborted jobs. Currently an aborted job uses the fail value not something everyone will want.
Title: Message Title Andy Wang updated an issue Jenkins / JENKINS-14767 Add Reporting Values for Aborted jobs. Currently an aborted job uses the fail value not something everyone will want. Change By: Andy Wang Attachment: 2015-10-28.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-14767) Add Reporting Values for Aborted jobs. Currently an aborted job uses the fail value not something everyone will want.
Title: Message Title Andy Wang updated an issue Jenkins / JENKINS-14767 Add Reporting Values for Aborted jobs. Currently an aborted job uses the fail value not something everyone will want. Change By: Andy Wang Attachment: 2015-10-28.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-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] [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] [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] [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] [gerrit-trigger-plugin] (JENKINS-31167) Gerrit Trigger: every build has all commits listed in the Changelog
Title: Message Title Andy Wang created an issue Jenkins / JENKINS-31167 Gerrit Trigger: every build has all commits listed in the Changelog Issue Type: Bug Assignee: rsandell Attachments: 2015-10-26meitu_1.png, 2015-10-26_meitu_2.png Components: gerrit-trigger-plugin Created: 26/Oct/15 12:18 PM Environment: Ubuntu 14.04.3 LTS Jenkins ver. 1.634 Gerrit Trigger 2.16.0 GIT client plugin 1.19.0 GIT plugin 2.4.0 java version "1.7.0_79" Labels: gerrit-trigger git-plugin changelog Priority: Critical Reporter: 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
[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 Summary: Gerrit Trigger: every build has all commits listed in the Changelog Changes page Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-30982) Gerrit Trigger connection could not be established while test connection is OK
Title: Message Title Andy Wang closed an issue as Won't Do Problem seems fixed when upgrade to 1.634 Jenkins / JENKINS-30982 Gerrit Trigger connection could not be established while test connection is OK Change By: Andy Wang Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-30982) Gerrit Trigger connection could not be established while test connection is OK
Title: Message Title Andy Wang commented on JENKINS-30982 Re: Gerrit Trigger connection could not be established while test connection is OK Problem seems resolved when upgrade to 1.634 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-30982) Gerrit Trigger connection could not be established while test connection is OK
Title: Message Title Andy Wang created an issue Jenkins / JENKINS-30982 Gerrit Trigger connection could not be established while test connection is OK Issue Type: Bug Assignee: rsandell Attachments: screenshot_meitu_1.jpg Components: gerrit-trigger-plugin Created: 16/Oct/15 6:40 AM Environment: Ubuntu 14.04.3 LTS Jenkins ver. 1.632 Gerrit Trigger 2.16.0 GIT client plugin 1.19.0 GIT plugin 2.4.0 java version "1.7.0_579" Labels: gerrit-trigger Priority: Major Reporter: Andy Wang Config the Gerrit Trigger plugin on jenkins based on the article https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger for the first time. After input the connection setting information, press Test Connection, and the result shows Success. But The
[JIRA] [gerrit-trigger-plugin] (JENKINS-30982) Gerrit Trigger connection could not be established while test connection is OK
Title: Message Title Andy Wang updated an issue Jenkins / JENKINS-30982 Gerrit Trigger connection could not be established while test connection is OK Change By: Andy Wang Environment: Ubuntu 14.04.3 LTS Jenkins ver. 1.632 Gerrit Trigger 2.16.0GIT client plugin 1.19.0 GIT plugin 2.4.0 java version "1.7. 0_579 0_79 " Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
