search

amtrack / force-dev-tool

[DEPRECATED] Command line tool supporting the Force.com development lifecycle
MIT License
108 stars 37 forks source link

Changes in profile metadata files are not included in changeset #84

Closed marty-mcfry closed 7 years ago

marty-mcfry commented 7 years ago

Produced in v 0.13.0. Changes to profile metadata files are not added to manifest and src folder when the changeset is created with git diff master | force-dev-tool changeset create build. Changes to certain parts of the file do not register as a change to the force-dev-tool including objectPermissions.

screen shot 2017-03-03 at 11 39 09 am screen shot 2017-03-03 at 11 38 04 am
amtrack commented 7 years ago

Hi @papariz

thanks for reporting. I just tried to reproduce but in my first attempt it just worked.

Is it possible for you to share your git repository with me, so that i can do some investigations?

marty-mcfry commented 7 years ago

Unfortunately our repo is not publicly accessible. If you've tested all the tags in the profile xml then maybe I'm doing something wrong.

Sent from my iPhone

On Mar 4, 2017, at 7:19 AM, Matthias Rolke notifications@github.com wrote:

Hi @papariz

thanks for reporting. I just tried to reproduce but in my first attempt it just worked.

Is it possible for you to share your git repository with me, so that i can do some investigations?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

marty-mcfry commented 7 years ago

@amtrack I believe this was due to the way I was calling git diff. Once I actually committed the changes to the branch, it then registered. Sorry for the confusion.

amtrack commented 7 years ago

No worries! I'm happy that you got it working now :-)

In fact not all parts of the Profile are supported for force-dev-tool changeset create, only the most common things like classAccesses, pageAccesses, objectPermissions, fieldPermissions, ... (see here).

marty-mcfry commented 7 years ago

Interesting good to know. Hopefully we won't hit on anything that is unsupported.