search

amtrack / force-dev-tool

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

Bug: Empty changeset is generated #88

Closed vkolotov closed 7 years ago

vkolotov commented 7 years ago

I make some simple changes to *.cls file. git diff shows that change. When I run the following command, an empty package.xml gets generated.

$ git diff origin/master | force-dev-tool changeset create "changeset-${TIMESTAMP}" -f --dry-run
readable not null
Manifest:
<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <version>38.0</version>
</Package>

exported metadata container to config/deployments/changeset-20170406100256

Please notice "readable not null" line. If I make another change, this line is printed twice (for each changed file).

vkolotov commented 7 years ago

I'm sorry for spam. The reason for that error was running an ancient NodeJS. I have upgraded node and it has disappeared.