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

Job Templates losing argument format when saving resulting in invalid commands #439

Open
Ataye opened this issue Jun 16, 2022 · 0 comments
Labels
bug Something isn't working

Comments

@Ataye
Copy link

Ataye commented Jun 16, 2022

Describe the bug
When saving a template, new or existing, it removes single quotes. Without single quotes in either the Keyword Arguments or Arguments fields the query for git.pull is messed up and thus produces an error. I am currently only getting this with git.pull since this is currently the only command with these sets of arguments. An example using the Reproduces steps below:

Results

server.local:
ERROR: Command 'git master pull remotename' failed: git: 'master' is not a git command. See 'git --help'.

The most similar command is
	restore

Arguments are out of place, and the repo path appears to be missing altogether.

To Reproduce
Steps to reproduce the behavior:

  1. Open 'Run' and enter a Target, and:
  2. Function=git.pull, Arguments=d://git_folder, Keyword Arguments=opts='remotename master'
  3. Check 'Save as Template' and enter a template name and Save,
  4. Open Job Templates,
  5. Click 'Edit' for the template,
  6. Observe missing quotes.

Expected behavior
The quotes should remain, and the query run with the arguments in the correct order and format.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: uBuntu 20 for Alcali, Windows 11 Brave for UI, Windows Server 2019 minion,
  • Browser: Brave 1.39.122
  • Alcali Version 3003.1.0

Additional context
Add any other context about the problem here.

@Ataye Ataye added the bug Something isn't working label Jun 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant