delta-push adds all workflows to the package #261
Assignees
Labels
Comments
|
Note to self - when testing don't use the XSLT. |
|
@pcon - this is odd...something is wonky with the Keep in mind, this is my using cached-delta-push. Anyway, I'm on it... |
|
@pcon - which xslt(s) for workflows should be ignored? |
|
It was the case.workflow. The xslt strips out outbound message
…On Sat, May 12, 2018, 10:02 Scot P. Floess ***@***.***> wrote:
@pcon <https://github.com/pcon> - which xslt for workflows should be
ignored? Outgoing_Message__c_pull.xsl ???? Or all?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#261 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AKH3PzO4c9ys4Ejsj59HFSk1GN7V2IeWks5txuttgaJpZM4TQhuK>
.
|
|
@pcon - ack...lemme try to figure this out 👍 |
|
@pcon - I'm confused as I did a pull from dev and the pulled Case.workflow is missing the Outbound element...whereas in git it's there...am I misunderstanding? |
|
We remove it from the workflow file via the xslt because of this issue.
…On Sat, May 12, 2018, 11:06 Scot P. Floess ***@***.***> wrote:
@pcon <https://github.com/pcon> - I'm confused as I did a pull from dev
and the pulled Case.workflow is missing the Outbound element...whereas in
git it's there...am I misunderstanding?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#261 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AKH3P1-9RLCAoe0kFKyQE2cXIkMgovwJks5txvp5gaJpZM4TQhuK>
.
|
|
@pcon - so is the core issue related to package.xml and workflows being defined in it? I don't think I grok what is happening here. For example, if the Outbound element is removed on pull, but is exists in git, I'd expect the two files are different and will be included in the push |
|
I'll try to explain better later today. Worst case we can talk on Monday
…On Sat, May 12, 2018, 11:12 Scot P. Floess ***@***.***> wrote:
@pcon <https://github.com/pcon> - so is the core issue related to
package.xml and workflows being defined in it? I don't think I grok what is
happening here. For example, if the Outbound element is removed on pull,
but is exiss in gut, I'd expect the two files are different and will be
included in the push
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#261 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AKH3P2DHO7sY5PMb6TVVPFUYpD9Irh5yks5txvvtgaJpZM4TQhuK>
.
|
|
@pcon - being that it's Mother's Day weekend, spend your time with the wife :) Monday is fine... I just feel bad I've neglected this project for so long lately :( |
|
Here's the problem. If we run a |
|
@pcon - ack... I will look at it this weekend again :) |
|
@pcon - we may need to chat about this. I cannot get all workflows as candidates for deploy. Here is what I did:
Only a handfull of workflows were present in I then moved the ccm XSLT workflow dir over to bak.workflow and reran the above. Here is what I get: When running Am I missing something? |
|
If I run this against my personal environment If I run a diff on this directory I get I originally thought that the ones showing as only in the source were in the sfdc ignore file but the ones in that file do not exist in either location. The Oddly, what's in the folder-pull directory are the ones that show as only in the source directory So, what I think may be happening is that the folder-pull is not getting all of the workflows pulled down (or written to disk) for some reason. This is the same for me when I do it against dev as well. |
|
@pcon - thanks for the detailed information! This will greatly assist me :) Let's see what I can get done on this 👍 |
|
@pcon - spent about 2hrs tonight trying to understand what's going on here... Alas, I am woefully confused... I'll figure it out - more a status update for you :) |
|
@pcon - looking at this again today. So here is what I did:
Either I am really confused, or our environments are running differently somehow? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It appears that
delta-pushadds all the.workflowfiles to package regardless of if they have been changed or not.This is a problem because if you have outbound messages in a workflow, the queue becomes paused during a deployment (even during a quick-deploy)
The text was updated successfully, but these errors were encountered: