Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nant_path is ignored when specified in a JSON or YAML pipeline #8897

Closed
gklittlejohn opened this issue Dec 16, 2020 · 1 comment
Closed

nant_path is ignored when specified in a JSON or YAML pipeline #8897

gklittlejohn opened this issue Dec 16, 2020 · 1 comment
Labels

Comments

@gklittlejohn
Copy link

Issue Type
  • Bug Report
Summary

I can create a pipeline through the UI with a Nant task that has nant_path set however if I export this pipeline to JSON or YAML and read from a repository the pipeline is setup with nant_path ignored.

Environment

Go server running on the docker container.
Go agent running on a Windows machine.

Basic environment details
  • Go Version: 20.10.0
  • JAVA Version: 15.0.1
  • OS: Linux 4.19.121-linuxkit
Steps to Reproduce
  1. Create a pipleline containing a nant task the the path to nant set.
  2. Export the pipeline as json or yaml
  3. Commit the json or yaml file to a repository.
  4. Delete the pipeline in GoCD.
  5. Set up the repository you have commit the file to as a configuration repository.
  6. Open the pipeline in GoCD once it has loaded.
Expected Results

nant path should be set on the task.

Actual Results

nant path is blank.

Log snippets

Not sure if this is relevant:

jvm 1 | 2020-12-16 11:36:55,412 ERROR [qtp582322203-33] VariableReplacer:385 - function ${escape:} type 'escape:' not a valid type
@stale
Copy link

stale bot commented Mar 16, 2021

This issue has been automatically marked as stale because it has not had activity in the last 90 days.
If you can still reproduce this error on the master branch using local development environment or on the latest GoCD Release, please reply with all of the information you have about it in order to keep the issue open.
Thank you for all your contributions.

@stale stale bot added the stale label Mar 16, 2021
@stale stale bot closed this as completed Mar 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant