Excluding files from delivery
One answer
Hi Ron,
As you rightly guess, the "Add to .jazzignore" action is the way to
prevent a file change from being added to a changeset. Currently it's a
little crufty: if the file/folder is already part of a changeset, the
change will be delivered when the changeset is delivered; but ignored
from then on.
In M0, if you want to prevent a new file from being added to the
repo, the best way is to edit the .jazzignore file by hand. In the
file's directory create a file called ".jazzignore". Add the text to it:
core.ignore= <filename>
where <filename> is the name of the file you will create. Then create
the file. You can also ignore a file by DOS-style patterns (ie, using
'*' and '?').
Alternatively, if you are creating a directory whose contents should
be ignored (such as an output directory), you can just run "Add to
..jazzignore" on the directory as a whole.
The ignore functionality is under heavy development. M1 will contain
many improvements.
e
As you rightly guess, the "Add to .jazzignore" action is the way to
prevent a file change from being added to a changeset. Currently it's a
little crufty: if the file/folder is already part of a changeset, the
change will be delivered when the changeset is delivered; but ignored
from then on.
In M0, if you want to prevent a new file from being added to the
repo, the best way is to edit the .jazzignore file by hand. In the
file's directory create a file called ".jazzignore". Add the text to it:
core.ignore= <filename>
where <filename> is the name of the file you will create. Then create
the file. You can also ignore a file by DOS-style patterns (ie, using
'*' and '?').
Alternatively, if you are creating a directory whose contents should
be ignored (such as an output directory), you can just run "Add to
..jazzignore" on the directory as a whole.
The ignore functionality is under heavy development. M1 will contain
many improvements.
e