estruyf / vsts-file-creator

VSTS File Creator build and release task

File Creator

This is a task that can be used to create a file during a build or release process. With the task you can specify the file you want to create and its content.

Options

Overwrite file

This allows you to specify if you want to overwrite the file if it already exists. By default this is set to false.

File path

With this property you can specify the path of the file including its name. Example: folder/filename.txt.

File content

Specify the content of the file you want to add.

Should file end with a new line

When this is checked, the task will automatically add a new line at the end the created file.

Feedback

Feedback is always welcome. Please submit it via creating an issue in the repository issue list.

Changelog

[6.0.0] 8/10/2020

• #7: Added verbose logging setting
• #8: Fix for SyntaxError in block-scoped declarations
• #9: Added support for creating empty files
• #12: Switched the string setting to filePath to be able to select your path

vsts-file-creator's Issues

Add an option to output the file content at the console (for debugging)

For debugging purpose, I often need to validate the content that is created by the task. If I could select an option to output the content at the console that will do the job.

Unable to create emtpy file

I'd like to create an empty file, but I can't.
Whether I skip the filecontent argument, set it to an empty string or to a single whitespace, I get the error Input required: filecontent.

How to add new line??

I'm not sure is an issue, I put several lines in the content box and all lines shows as a single line in the output file..

Thanks

Would be nice to be able to browse for the file path

Just like it many other built-in tasks offer a browse option, it'd be a nice addition to have a button to browse.

It really helps avoiding issues with checking that we are configuring a valid path

Sample screenshots of the "archive files" task

It would be nice to be able to get the file contents via path

Assuming that in my project I have the following file in the "../config/base.json" directory:

{
  "baseUrl": "$(baseUrl)",
  "user": "$(defaultUser)",
  ...
}

It would be nice to be able to get the file in the task instead of providing the content directly.

Something similar to:

- task: file-creator@6
  inputs:
    filepath: "$(System.DefaultWorkingDirectory)/config/settings.json"
    filecontent: |
      cat $(System.DefaultWorkingDirectory)/config/base.json
    fileoverwrite: true
    verbose: true

Multiple lines

Hi All,

Sorry,Some issues were opened before, but I still haven't solved this problem.

Result ;

So what's wrong? :/

Thanks,

does not work with DevOps Server

see title - the pipeline task never shows up although the installation suceeded.
Tested with fresh installation of Azure DevOps Server 2019 and 2019.1

How to provide destination path to create the file?

I tried with $(SolutionDir)temp/myfile.txt
I tried with $account/branch/temp/myfile.txt
None of them created the file in my desired path in the build workspace.
How to make it work?

Also I want to pass the content from a build custom variable. How to do it?
Thanks in advance.

Error: The string argument contains a character that is not valid:'u0009'. Correct the argument, and then try the operation again. Parameter name: definition.Steps.filecontent

HI

I am getting error while using these file contents,Can you check?

Can not add multiple lines

Hi,
Whenever I try to add multiple lines like this.

ServerIp
BrowserName

It creates\overwrites the file like this
ServerIpBrowserName

Am I doing something wrong? Kindly let me know.

##[warning]Environment variable 'INPUT_FILECONTENT' exceeds the maximum supported length. Environment variable length: 32828 , Maximum supported length: 32766

Hi,

How can we solve the max length of the file creation if exceeds the max var size?

We now get an error: ##[warning]Environment variable 'INPUT_FILECONTENT' exceeds the maximum supported length. Environment variable length: 32828 , Maximum supported length: 32766

thanks,

Daniel

Add an option to skip creating file if content is empty

Hello,

First of all thank. you for the useful VSTS pipeline task.

I would like to request a change/feature that would allow task to skip creating file if content is empty.

Current behaviour is that the task failes with:
##[error]Unhandled: Input required: filecontent

The use case is that, I would like to generate the file with a content filled from Variable defined while queuing a new build. This variable is not mandatoryto fill and therefore making file content empty, this failing vsts-file-creator task.

Workaround: Set the pipeline to continue on task error. Not ideal, but works for now

Variables in file content are not replaced by their values

When using something like this as the file content:
This is my file and this is my var: $(VAR1)
The $(VAR1) is not replaced by the value of VAR1 defined in VSTS.

Task fails with `##[error]Unhandled: Assignment to constant variable.`

I'm using the Create file task to create a Dockerfile that will be consumed by the following tasks.

Below is a screenshot of my task definition

And a screenshot of the console output

Why do I get this ##[error]Unhandled: Assignment to constant variable. ? How can I fix it ?

SyntaxError: Block-scoped declarations

2019-08-26T22:45:07.5107021Z let filecontent = tl.getInput('filecontent', true);
2019-08-26T22:45:07.5107021Z ^^^
2019-08-26T22:45:07.5107021Z SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode