[JIRA] (JENKINS-41102) Job "Changes" do not match "Filter for Poll SCM"
Title: Message Title Timothy Williams closed an issue as Incomplete While a specific fix from AccuRev was never provided to address this issue, several fixes to the plug-in were provided - those fixes in addition to recreating the jobs with some AccuRev filtering changes has provided more consistent results in the job changes report. Closing this issue as clean-up, as it will never be specifically worked on. Jenkins / JENKINS-41102 Job "Changes" do not match "Filter for Poll SCM" Change By: Timothy Williams Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-41102) Job "Changes" do not match "Filter for Poll SCM"
Title: Message Title Timothy Williams edited a comment on JENKINS-41102 Re: Job "Changes" do not match "Filter for Poll SCM" * 15/Oct/ 2018 -10-15 update:*Micro Focus internal defect RPI #1115588 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-41102) Job "Changes" do not match "Filter for Poll SCM"
Title: Message Title Timothy Williams commented on JENKINS-41102 Re: Job "Changes" do not match "Filter for Poll SCM" 15/Oct/2018 update: Micro Focus internal defect RPI #1115588 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-41102) Job "Changes" do not match "Filter for Poll SCM"
Title: Message Title Timothy Williams commented on JENKINS-41102 Re: Job "Changes" do not match "Filter for Poll SCM" Is there anyway someone from Micro Focus could look into and correct this issue? It really makes it impossible to accurately and programmatically update JIRAs during the build process when the changes for a sub-folder filtered build job show all changes in the stream (regardless of sub-folder) since the last run of the job. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-41102) Job "Changes" do not match "Filter for Poll SCM"
Title: Message Title Timothy Williams commented on JENKINS-41102 Re: Job "Changes" do not match "Filter for Poll SCM" AccuRev plugin 0.7.16 did not fix this issue. 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-41102) Job "Changes" do not match "Filter for Poll SCM"
Title: Message Title
Timothy Williams edited a comment on JENKINS-41102
Re: Job "Changes" do not match "Filter for Poll SCM"
I have not tested this yet, but is this issue resolved by the following bolded bold [release note text|https://wiki.jenkins.io/display/JENKINS/AccuRev+Plugin]? Thanks.{quote}{color:red}Version 0.7.16 (05/15/2018) - Micro Focus Contributed{color}* It is now possible to enable / disable the AccuRev plugin from interacting with the AccuRev server. This is useful when the AccuRev stream hierarchy is being reworked and you don’t want Jenkins building while this activity is underway.* Fixed problem with Jenkins reporting "No port number specified for connecting to server" error, when using AccuRev 7.1 or higher.* *Jenkins now correctly works with the "Filter for Poll SCM" option.** Jenkins user can now validate the connection of configured AccuRev server , using "Test Connection" option.{quote}
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-41102) Job "Changes" do not match "Filter for Poll SCM"
Title: Message Title Timothy Williams commented on JENKINS-41102 Re: Job "Changes" do not match "Filter for Poll SCM" I have not tested this yet, but is this issue resolved by the following bolded release note text? Thanks. Version 0.7.16 (05/15/2018) - Micro Focus Contributed It is now possible to enable / disable the AccuRev plugin from interacting with the AccuRev server. This is useful when the AccuRev stream hierarchy is being reworked and you don’t want Jenkins building while this activity is underway. Fixed problem with Jenkins reporting "No port number specified for connecting to server" error, when using AccuRev 7.1 or higher. Jenkins now correctly works with the "Filter for Poll SCM" option. Jenkins user can now validate the connection of configured AccuRev server , using "Test Connection" option. 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..
[JIRA] (JENKINS-41102) Job "Changes" do not match "Filter for Poll SCM"
Title: Message Title Timothy Williams commented on JENKINS-41102 Re: Job "Changes" do not match "Filter for Poll SCM" Ok, thank you for the update Joseph Petersen 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-41102) Job "Changes" do not match "Filter for Poll SCM"
Title: Message Title Timothy Williams commented on JENKINS-41102 Re: Job "Changes" do not match "Filter for Poll SCM" Joseph Petersen Is this something that may be addressed in a future update, or is this something you are not looking to implement? If you are not looking to implement this, do you have any suggestions for how I may be able to do something similar within the Jenkins job (to prevent changes promoted to folders outside of the build purview from showing in the changeset)? Thanks. 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-41526) "Filter for Poll SCM" detects changes on similarly named folders
Title: Message Title Timothy Williams closed an issue as Fixed Verified appending * to polling folder path resolved this issue. Verified with version 0.7.11. Jenkins / JENKINS-41526 "Filter for Poll SCM" detects changes on similarly named folders Change By: Timothy Williams Status: Open Closed Resolution: Fixed 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...@googl
[JIRA] (JENKINS-42939) AccuRev plugin does not start job on detected changes
Title: Message Title Timothy Williams closed an issue as Fixed Verified appending * to polling folder path resolved this issue. Jenkins / JENKINS-42939 AccuRev plugin does not start job on detected changes Change By: Timothy Williams Status: Open Closed Resolution: Fixed 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 http
[JIRA] (JENKINS-42939) AccuRev plugin does not start job on detected changes
Title: Message Title Timothy Williams commented on JENKINS-42939 Re: AccuRev plugin does not start job on detected changes Thanks Joseph, that's what I thought - just wanted to be sure 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-42939) AccuRev plugin does not start job on detected changes
Title: Message Title
Timothy Williams edited a comment on JENKINS-42939
Re: AccuRev plugin does not start job on detected changes
I updated my jobs and I'll test with the next promotes.*Question:* With the wildcard changes you added made , do you think I''d be able to just remove {{/*}} and specify the folder name now, or do you think I'd still hit the same issue with folder names that begin with the same string (e.g. {{hi-analytics-library}} and {{hi-analytics-library-web}}) kicking off multiple jobs?Thanks!
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-42939) AccuRev plugin does not start job on detected changes
Title: Message Title Timothy Williams commented on JENKINS-42939 Re: AccuRev plugin does not start job on detected changes I updated my jobs and I'll test with the next promotes. Question: With the wildcard changes you added, do you think I''d be able to just remove /* and specify the folder name now, or do you think I'd still hit the same issue with folder names that begin with the same string (e.g. hi-analytics-library and hi-analytics-library-web) kicking off multiple jobs? Thanks! 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-42939) AccuRev plugin does not start job on detected changes
Title: Message Title
Timothy Williams commented on JENKINS-42939
Re: AccuRev plugin does not start job on detected changes
Oh, is that what this comment meant?
So all I could do was simple wildcard without implementing too much.
I thought you were having a conversation with Arno, I didn't realize you were telling me what to change with the next release (0.7.10). I did see a reference to java/* in the 0.7.10 release notes with a reference to JENKINS-41526, but didn't realize what it meant. My bad. So I don't need to update the Sub-path, I just need to add {} to my current *Filter for Poll SCM value to make it hi-analytics-library/*?
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-42939) AccuRev plugin does not start job on detected changes
Title: Message Title Timothy Williams commented on JENKINS-42939 Re: AccuRev plugin does not start job on detected changes Sub-path = gradle.cmd,gradlew,gradlew.bat,gradle,build-config,hi-analytics-library Filter for Poll SCM = hi-analytics-library/ 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-42306) Error "Unable to cast run to abstract build" with AccuRev
Title: Message Title Timothy Williams closed an issue as Fixed I have not see any of the messages detailed in this JIRA with my last few job failures, so I believe this is complete. If I see any resurrection of these messages I'll open a new JIRA. Thanks for your help. Jenkins / JENKINS-42306 Error "Unable to cast run to abstract build" with AccuRev Change By: Timothy Williams Status: Resolved Closed 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-42306) Error "Unable to cast run to abstract build" with AccuRev
Title: Message Title Timothy Williams commented on JENKINS-42306 Re: Error "Unable to cast run to abstract build" with AccuRev I think this may have been written-out by something else in the job. I think your last fix cleaned everything up. Thank you. If I see something in the future I'll open a new JIRA and link it to this one. Thanks for your help. Srivardhan Hebbar I apologize for not getting back to you sooner. I no longer receive an error, but the build console still writes-out this message getAffectedFiles() is not implemented by accurev - some jobs will write this message multiple times. 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-42939) AccuRev plugin does not start job on detected changes
Title: Message Title Timothy Williams created an issue Jenkins / JENKINS-42939 AccuRev plugin does not start job on detected changes Issue Type: Bug Assignee: Joseph Petersen Components: accurev-plugin Created: 2017/Mar/20 1:57 PM Environment: Jenkins 2.32.3 AccuRev plugin 0.7.11 Windows Server 2012 R2 running Jenkins and AccuRev client AccuRev client 6.2.3d Linux server running AccuRev server (same version as client) Labels: windows linux scm accurev Priority: Major Reporter: Timothy Williams AccuRev plugin 0.7.11 detects changes on stream sub-folder polling but states there are "no changes" and does not start Jenkins job. Stream layout: BI-HI-UI-SCS-DEV hi-analytics-library hi-analytics-library-web ... Job polling found changes and stated there were "no changes": AccuRev Polling Log Started on Mar 20, 2017 9:34:04 AM No workspace required. Running commands from folde
[JIRA] (JENKINS-42306) Error "Unable to cast run to abstract build" with AccuRev
Title: Message Title Timothy Williams commented on JENKINS-42306 Re: Error "Unable to cast run to abstract build" with AccuRev Also: Are both Jenkins and AccuRev running in the same server? Yes Is there any special configuration for AccuRev that I need to know to reproduce the same setup here? No Are you using any specific plugin to detect the SCM changes from AccuRev? Accurev plugin 0.7.6 - I haven't upgraded to v0.7.11 yet because of issues I found with v0.7.9 and 0.7.10. 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-42306) Error "Unable to cast run to abstract build" with AccuRev
Title: Message Title Timothy Williams commented on JENKINS-42306 Re: Error "Unable to cast run to abstract build" with AccuRev Srivardhan Hebbar I apologize for not getting back to you sooner. I no longer receive an error, but the build console still writes-out this message getAffectedFiles() is not implemented by accurev - some jobs will write this message multiple times. 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-42306) Error "Unable to cast run to abstract build" with AccuRev
Title: Message Title Timothy Williams commented on JENKINS-42306 Re: Error "Unable to cast run to abstract build" with AccuRev Hi Sri. Sorry for not responding yesterday. What other information do you need about our system setup that I didn't specify in Environment? I updated to version 2.4.1 today and my first build afterward failed - and it seems to have failed because of this plugin update. Failed build output snip-it with plugin 2.4.1: Changelog calculated successfully. FATAL: getAffectedFiles() is not implemented by accurev java.lang.UnsupportedOperationException: getAffectedFiles() is not implemented by accurev at hudson.scm.ChangeLogSet$Entry.getAffectedFiles(ChangeLogSet.java:242) at jenkins.plugins.office365connector.Office365ConnectorWebhookNotifier.addScmDetails(Office365ConnectorWebhookNotifier.java:367) at jenkins.plugins.office365connector.Office365ConnectorWebhookNotifier.addCauses(Office365ConnectorWebhookNotifier.java:446) at jenkins.plugins.office365connector.Office365ConnectorWebhookNotifier.createJobStartedCard(Office365ConnectorWebhookNotifier.java:186) at jenkins.plugins.office365connector.Office365ConnectorWebhookNotifier.getCard(Office365ConnectorWebhookNotifier.java:108) at jenkins.plugins.office365connector.Office365ConnectorWebhookNotifier.getCard(Office365ConnectorWebhookNotifier.java:96) at jenkins.plugins.office365connector.Office365ConnectorWebhookNotifier.sendBuildStaredNotification(Office365ConnectorWebhookNotifier.java:64) at jenkins.plugins.office365connector.WebhookJobProperty.prebuild(WebhookJobProperty.java:52) at hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:834) at hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:829) at hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:825) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:531) at hudson.model.Run.execute(Run.java:1728) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404) Email was triggered for: Always Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Successful build output snip-it with after reverting to plugin 2.4: Changelog calculated successfully. No need to notify webhook 'https://outlook.office.com/webhook/955fbb0e-a7c1-46a2-ba35-9129f21a1128@fbc493a8-0d24-4454-a815-f4ca58e8c09d/JenkinsCI/105bc602d6cb48b187b3ea2d9ec810dc/e6738418-46d9-43a3-a29a-ecacef366d4b' No emails were triggered.
[JIRA] (JENKINS-42306) Error "Unable to cast run to abstract build" with AccuRev
Title: Message Title Timothy Williams updated an issue Jenkins / JENKINS-42306 Error "Unable to cast run to abstract build" with AccuRev Change By: Timothy Williams Environment: Jenkins 2.32.2Office 365 Connector Plugin 2.4AccuRev 6.2.3d (Windows client, Linux server) 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-42306) Error "Unable to cast run to abstract build" with AccuRev
Title: Message Title Timothy Williams created an issue Jenkins / JENKINS-42306 Error "Unable to cast run to abstract build" with AccuRev Issue Type: Bug Assignee: Srivardhan Hebbar Components: office-365-connector-plugin Created: 2017/Feb/24 2:04 PM Environment: Jenkins 2.32.2 Office 365 Connector Plugin 2.4 AccuRev 6.2.3d Labels: api scm Priority: Minor Reporter: Timothy Williams Our build jobs log the error below with each run of the Office 365 webhooks. The error states that AccuRev doesn't support getAffectedFiles(). Is there a similar call that AccuRev does support that can be used instead for AccuRev systems, or is it possible to catch this error for and just log an informational message instead? Thanks, Tim ERROR: Unable to cast run to abstract build. java.lang.UnsupportedOperationException: getAffectedFiles() is not implemented by accurev java.lang.UnsupportedOperationException: getAffectedFiles() is not implemented by accurev Build step 'Invoke Gradle script' changed build result to SUCCESS createJobCompletedCard: 203 ERROR: Unable to cast run to abstract build. java.lang.UnsupportedOperationException: getAffectedFiles() is not implemented by accurev java.lang.UnsupportedOperationException: getAffect
[JIRA] (JENKINS-41526) "Filter for Poll SCM" detects changes on similarly named folders
Title: Message Title Timothy Williams created an issue Jenkins / JENKINS-41526 "Filter for Poll SCM" detects changes on similarly named folders Issue Type: Bug Assignee: Joseph Petersen Components: accurev-plugin Created: 2017/Jan/27 6:47 PM Environment: Jenkins Version 2.32.1 AccuRev Plugin Version 0.7.9 Labels: regression Priority: Major Reporter: Timothy Williams "Filter for Poll SCM" detects changes on similarly named folders. We have three folders in the root of the stream named "hi-lib", "hi-lib-dal", and "hi-lib-dal-mongo". The "Filter for Poll SCM" for each folder job is set as "hi-lib/", "hi-lib-dal/", and "hi-lib-dal-mongo/". This is because without the trailing forward-slash AccuRev Plugin Version 0.7.6 would detect changes in each job even if changes were only promoted to one folder - adding the forward-slash resolved that issue. With AccuRev Plugin Version 0.7.9, after promoting a change to "hi-lib-dal-mongo", all three builds started for detected changes in all three folders even though only "hi-lib-dal-mongo" contained a promoted change. It appears something changed in AccuRev Plugin Version 0.7.9 that broke the polling and filtering by folders by ignoring the forward-slash that denoted the end of the folder name. Is there another way I should qualify the "Filter for Poll SCM" value? Thanks.
[JIRA] (JENKINS-41165) Ignore parent changes not working since v0.7.7
Title: Message Title Timothy Williams commented on JENKINS-41165 Re: Ignore parent changes not working since v0.7.7 +1 - I'm seeing the same issue. Downgraded to AccuRev plugin 0.7.6 and jobs are now seeing changes during polling. 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-41102) Job "Changes" do not match "Filter for Poll SCM"
Title: Message Title Timothy Williams commented on JENKINS-41102 Re: Job "Changes" do not match "Filter for Poll SCM" Joseph Petersen Hi. I'm not sure I fully understand your question. I do want to notify everyone that promoted a change to the package (Package A) of a failed build, but I don't want to notify those who promoted a change to another package (Package B) of a "Package A" failed build - they should only be notified of a "Package B" failed build. We currently notify a distribution list, with a handful of developers on it, of all build success/failures for all package jobs (using the Jenkins email-ext plugin). What I would like to do is have the changes for a job match the change detection. Currently the changes for a job are all the changes for the stream since the job last ran, not just the changes for the sub-folder since the job last ran. I know not everyone may want this behavior, so to optionally be able to enable this would be fine by me. Does this make sense? I can add a scenario example if that would help. 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-41102) Job "Changes" do not match "Filter for Poll SCM"
Title: Message Title Timothy Williams created an issue Jenkins / JENKINS-41102 Job "Changes" do not match "Filter for Poll SCM" Issue Type: Bug Assignee: Joseph Petersen Components: accurev-plugin Created: 2017/Jan/16 2:23 PM Environment: Windows Server 2012 R2 AccuRev 6.2.3 Jenkins 2.32.1 AccuRev Plugin 0.7.6 Labels: scm user-experience Priority: Minor Reporter: Timothy Williams The "Changes" list on my Jenkins jobs (and corresponding emails) using the AccuRev plugin do not match the change detection of the job's "Filter for Poll SCM". Promotes to only the specified sub-folder defined in "Filter for Poll SCM" are correctly identified and kick-off the job, but the "Changes" list for the job that gets kicked-off are all changes for the entire stream since the job last ran, not just the changes for the sub-folder specified in "Filter for Poll SCM". My stream contains many sub-folders for each "package", and a Jenkins job exists for each "package" sub-folder. With the current behavior, irrelevant change-sets are being sent in job notification emails and developers not involved with the changes of a specific "package" job are being notified about success and failures even though they didn't promote changes to said "package". Is there anyway to make the job "Changes" list match on the changes based on "Filter for Poll SCM"? Thanks!
[JIRA] (JENKINS-35388) accurev-plugin parameters
Title: Message Title
Timothy Williams commented on JENKINS-35388
Re: accurev-plugin parameters
Thanks for the info! I was afraid you'd say that ("update"). I inherited this system from someone else, and let's just say that this system is very particular with what you do to it Thanks again.
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-35388) accurev-plugin parameters
Title: Message Title
Timothy Williams edited a comment on JENKINS-35388
Re: accurev-plugin parameters
[~casz] : What version of the AccuRev plug-in is this issue resolved? I'm having the same issue ("FATAL: Must specify a depot") with Jenkins 1.593, AccuRev plug-in 0.6.35, and AccuRev client 6.2.3. Thanks!
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-35388) accurev-plugin parameters
Title: Message Title Timothy Williams commented on JENKINS-35388 Re: accurev-plugin parameters Joseph Petersen What version of the AccuRev plug-in is this issue resolved? I'm having the same issue with Jenkins 1.593, AccuRev plug-in 0.6.35, and AccuRev client 6.2.3. Thanks! 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.
