Ignore Folders from Publish

Hi Team,

It would be great if we have an option to Ignore folders from publish under project folder. Currently, we have an option to ignore xaml files only but not folders.

In REFramework project template, We have folders called Documentation and Tests. It is required while doing development and testing after that we won’t use it anymore after publishing the project. So if we add an option to ignore folders then it will be more helpful to us and also it will reduce package size too.

1 Like

That was good idea , after project development finished and moved to prod there may be cases change in initial requirement and final release where we don’t need some process folders & xaml files

1 Like

You should not place in the project folder files that are not part of the process. What is the usecase you would need some folders in there but you would like to exclude them at publish?

If the files are not needed in your processes they should be removed from the source code.

@alexandru

In ReFramework project template, we have folder called Test and it contains all test cases related xaml files. We may required these files in later stage if we want to do any enhancements to the existing code and do testing but it’s not required for actual process to run in the production.

2 Likes

@alexandru

One more thing Documentation folder contains one file related to ReFramework documentation. It’s also not required for actual process to run.

3 Likes

@lakshman
Agree. Much better than manually setting it for each .xaml file or programmatically editing the project.json file with files which need to be ignored.

@alexandru

For some cumbersome processes we prepare a debugging suite built in the ReFramework which reside in a folder. The debugging files are provided so that the maintainers can use them from our version control software.

Debugging suite contains many .xaml files which are not required for the process to run but extremely important for maintainers when process encounters change requests or needs hot fixes.

If there is a an option to ignore from publish for the entire folder, it will help.

2 Likes

Thanks all for the detailed feedback. Will track this in our internal tool for consideration.

3 Likes

Some of our customers don’t want sensitive data uploaded to Orchestrator Cloud. So it would be good e.g. to be able to exclude the whole .screenshots folder. What we have done before is to delete the .screenshot folder completely which makes debugging very hard.

3 Likes

Thanks for the consideration @alexandru

just as FYI .screenshots folder is ignored at publishing.

2 Likes

@ptrobot

As @alexandru mentioned it will ignore .screenshots folder and also .local folder from publish.

1 Like

@alexandru @lakshman Great! I did not know that! Thank you for the information!

1 Like

I tried to google more information regarding this feature but could not find anything in the UiPath documentation. Has UiPath Studio always ignored folders that starts with “.” when publishing? If not, from which version of Studio was this feature implemented? (Some of our customers are still using older versions of UiPath Studio.)

1 Like

You shouldn’t have those folders inside your project folders. Move them outside the project.

@ptrobot

Not all. Some folders are existing like .data and .settings.

I also didn’t find any documentation for this.
@alexandru - Do we have any documentation regarding publishing project ?

1 Like

@postwick

I guess it’s not a good practice keeping outside the project folder as we may required in the later stage.

No. For anything not specifically related to your code, like documentation and test data, you put that outside your project. Only things you want published with your code should go inside the project.

1 Like

This would be fine, but adds administrative overhead unnecessarily. The UiPath implementation of version control will not correctly handle a GIT repository being set as anything other than the
project folder. So if this documentation/tests need to be version controlled, storing them elsewhere is not a good idea.

3 Likes