[JIRA] [perforce-plugin] (JENKINS-35369) Changeset should not be calculated in each run in the job when P4DISABLESYNC has been set in environment
Title: Message Title Rob Petti commented on JENKINS-35369 Re: Changeset should not be calculated in each run in the job when P4DISABLESYNC has been set in environment This is not an issue. You have set P4DISABLESYNC and P4DISABLECHANGELOG. It is not syncing any changes, and it is not getting any changelog information. This is by design. The results of the line "p4 changes -s submitted -m 1 //job_name/..." is not being used for anything, because you have explicitly disabled everything. Once again, this plugin is deprecated. Use p4-plugin instead. If you have problems with it, contact perforce support or file another ticket against it. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-35369) Changeset should not be calculated in each run in the job when P4DISABLESYNC has been set in environment
Title: Message Title Rob Petti updated an issue Jenkins / JENKINS-35369 Changeset should not be calculated in each run in the job when P4DISABLESYNC has been set in environment Change By: Rob Petti Priority: Major Trivial Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-35369) Changeset should not be calculated in each run in the job when P4DISABLESYNC has been set in environment
Title: Message Title Rob Petti assigned an issue to Unassigned Jenkins / JENKINS-35369 Changeset should not be calculated in each run in the job when P4DISABLESYNC has been set in environment Change By: Rob Petti Assignee: Rob Petti Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-35369) Changeset should not be calculated in each run in the job when P4DISABLESYNC has been set in environment
Title: Message Title kalai arasan edited a comment on JENKINS-35369 Re: Changeset should not be calculated in each run in the job when P4DISABLESYNC has been set in environment Thanks for your valuable suggestion. we are using p4 plugin now.is there any way to trigger a job without sync, even though job configuration has sync workspace in it?our requirement is that, we want to run the same job whether the sync has to be done or not decided by the environment variable.Also, p4 plugin should not take latest changeset when we disable sync happens.Could you please let us know how to resolve this issue.PS: our issue in perforce plugin is, eventhough we use P4DISABLESYNC, it is taking latest changeset ( from p4 changes -s submitted -m 1 ///... ) at the end which might not built . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-35369) Changeset should not be calculated in each run in the job when P4DISABLESYNC has been set in environment
Title: Message Title kalai arasan edited a comment on JENKINS-35369 Re: Changeset should not be calculated in each run in the job when P4DISABLESYNC has been set in environment Thanks for your valuable suggestion. we are using p4 plugin now.is there any way to trigger a job without sync, even though job configuration has sync workspace in it . ? our requirement is that, we want to run the same job whether the sync has to be done or not decided by the environment variable.Also, p4 plugin should not take latest changeset when we use disable sync option happens . Please Could you please let us know how to resolve this issue .PS: our issue in perforce plugin is, eventhough we use P4DISABLESYNC, it is taking latest changeset ( from p4 changes -s submitted -m 1 ///... ) at the end which might not built . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-35369) Changeset should not be calculated in each run in the job when P4DISABLESYNC has been set in environment
Title: Message Title kalai arasan edited a comment on JENKINS-35369 Re: Changeset should not be calculated in each run in the job when P4DISABLESYNC has been set in environment Thanks for your valuable suggestion. we are using p4 plugin now.is there any way to trigger a job without sync, even though job configuration has sync workspace in it.our requirement is that, we want to run the same job whether the sync has to be done or not decided by the environment variable. Also, p4 plugin should not take latest changeset when we use disable sync option. Please let us know.PS: our issue in perforce plugin is, eventhough we use P4DISABLESYNC, it is taking latest changeset ( from p4 changes -s submitted -m 1 ///... ) at the end which might not built . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-35369) Changeset should not be calculated in each run in the job when P4DISABLESYNC has been set in environment
Title: Message Title kalai arasan edited a comment on JENKINS-35369 Re: Changeset should not be calculated in each run in the job when P4DISABLESYNC has been set in environment Thanks for your valuable suggestion. we are using p4 plugin now.is there any way to trigger a job without sync, even though job configuration has sync workspace in it.our requirement is that, we want to run the same job whether the sync has to be done or not decided by the environment variable.Please let us know.PS: our issue in perforce plugin is, eventhough we use P4DISABLESYNC, it is taking latest changeset ( from p4 changes -s submitted -m 1 ///... ) at the end which is might not built . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-35369) Changeset should not be calculated in each run in the job when P4DISABLESYNC has been set in environment
Title: Message Title kalai arasan edited a comment on JENKINS-35369 Re: Changeset should not be calculated in each run in the job when P4DISABLESYNC has been set in environment Thanks for your valuable suggestion. we are using p4 plugin now.is there any way to trigger a job without sync, even though job configuration has sync workspace in it.our requirement is that, we want to run the same job whether the sync has to be done or not decided by the environment variable.Please let us know.PS: our issue in perforce plugin is, eventhough we use P4DISABLESYNC, it is taking latest changeset ( from p4 changes -s submitted -m 1 ///... ) at the end which is not built . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-35369) Changeset should not be calculated in each run in the job when P4DISABLESYNC has been set in environment
Title: Message Title kalai arasan edited a comment on JENKINS-35369 Re: Changeset should not be calculated in each run in the job when P4DISABLESYNC has been set in environment Thanks for your valuable suggestion. we are using p4 plugin now.is there any way to trigger job without sync, even though job configuration has sync workspace in it.our requirement is that, we want to run the same job whether the sync has to be done or not decided by the environment variable.Please let us know.PS: our issue in perforce plugin is, eventhough we use P4DISABLESYNC, it is taking latest changeset ( from p4 changes -s submitted -m 1 ///... ) at the end which is not built. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-35369) Changeset should not be calculated in each run in the job when P4DISABLESYNC has been set in environment
Title: Message Title kalai arasan commented on JENKINS-35369 Re: Changeset should not be calculated in each run in the job when P4DISABLESYNC has been set in environment Thanks for your valuable suggestion. we are using p4 plugin now. is there any way to trigger job without sync, even though job configuration has sync workspace in it. our requirement is that, we want to run the same job whether the sync has to be done or not decided by the environment variable. Please let us know. PS: our issue in perforce plugin is, eventhough we use P4DISABLESYNC, it is taking latest changeset at the end which is not built. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-35369) Changeset should not be calculated in each run in the job when P4DISABLESYNC has been set in environment
Title: Message Title kalai arasan assigned an issue to Rob Petti Jenkins / JENKINS-35369 Changeset should not be calculated in each run in the job when P4DISABLESYNC has been set in environment Change By: kalai arasan Assignee: Rob Petti Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-35369) Changeset should not be calculated in each run in the job when P4DISABLESYNC has been set in environment
Title: Message Title kalai arasan updated an issue Jenkins / JENKINS-35369 Changeset should not be calculated in each run in the job when P4DISABLESYNC has been set in environment Change By: kalai arasan Priority: Trivial 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] [perforce-plugin] (JENKINS-35369) Changeset should not be calculated in each run in the job when P4DISABLESYNC has been set in environment
Title: Message Title Rob Petti updated an issue Jenkins / JENKINS-35369 Changeset should not be calculated in each run in the job when P4DISABLESYNC has been set in environment Change By: Rob Petti Priority: Critical Trivial Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-35369) Changeset should not be calculated in each run in the job when P4DISABLESYNC has been set in environment
Title: Message Title Rob Petti assigned an issue to Unassigned Jenkins / JENKINS-35369 Changeset should not be calculated in each run in the job when P4DISABLESYNC has been set in environment Change By: Rob Petti Assignee: Rob Petti Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-35369) Changeset should not be calculated in each run in the job when P4DISABLESYNC has been set in environment
Title: Message Title Rob Petti commented on JENKINS-35369 Re: Changeset should not be calculated in each run in the job when P4DISABLESYNC has been set in environment This plugin is deprecated. Please use the official one from Perforce. On the other had, since you don't want changelogs or syncing, you should probably not use an SCM plugin to begin with. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-35369) Changeset should not be calculated in each run in the job when P4DISABLESYNC has been set in environment
Title: Message Title
kalai arasan updated an issue
Jenkins / JENKINS-35369
Changeset should not be calculated in each run in the job when P4DISABLESYNC has been set in environment
Change By:
kalai arasan
when P4DISABLESYNC is set it to environment, sync is not happening but changeset taking the latest changes in the respective branch.I am using P4DISABLECHANGELOG and P4DISABLESYNC env variable, in a job, p4 is not syncing the actual code from depot, but taking latest CL which is not sycned to workspace from the below command.p4 changes -s submitted -m 1 ///...i believe, we should not take the latest changeset when we have P4DISABLESYNC variable set. or let me know how to solve this issue if you have any idea to resolve the same.can some one please take a look. PerforceSCM.java : line 1009//use the latest submitted change from workspace, or depottry {List workspaceChanges = depot.getChanges().getChangeNumbers(p4WorkspacePath, 0, 1);if (workspaceChanges != null && !workspaceChanges.isEmpty()) {newestChange = workspaceChanges.get(0);} else {List depotChanges = depot.getChanges().getChangeNumbers("//...", 0, 1);if (depotChanges != null && !depotChanges.isEmpty()) {newestChange = depotChanges.get(0);}}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because y
[JIRA] [perforce-plugin] (JENKINS-35369) Changeset should not be calculated in each run in the job when P4DISABLESYNC has been set in environment
Title: Message Title kalai arasan created an issue Jenkins / JENKINS-35369 Changeset should not be calculated in each run in the job when P4DISABLESYNC has been set in environment Issue Type: Bug Assignee: Rob Petti Components: perforce-plugin Created: 2016/Jun/06 10:15 AM Environment: jenkins - 1.599 perforce plugin - 1.3.24 Labels: perforce Priority: Critical Reporter: kalai arasan when P4DISABLESYNC is set it to environment, sync is not happening but changeset taking the latest changes in the respective branch. I am using P4DISABLECHANGELOG and P4DISABLESYNC env variable, in a job, p4 is not syncing the actual code from depot, but taking latest CL which is not sycned to workspace from the below command. p4 changes -s submitted -m 1 ///... i believe, we should not take the latest changeset when we have P4DISABLESYNC variable set. or let me know how to solve this issue if you have any idea to resolve the same. can some one please take a look.
