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

--no-cleanup fails with no message if *-artefact branch already exists #17

Open
simesy opened this issue Nov 25, 2017 · 1 comment
Open
Labels
Milestone

Comments

@simesy
Copy link

simesy commented Nov 25, 2017

To reproduce you can have a master-artefact branch in your repo, and try deploying with the --no-cleanup flag. Robo fails with an empty message, the message is not getting picked up properly in the gitcommand component.

@simesy
Copy link
Author

simesy commented Nov 25, 2017

It appears to have caught me because I accidentally ran the artefact command on my repo on a build which had already run the command (that failed). I think the missing error is the bigger problem.

@AlexSkrypnyk AlexSkrypnyk self-assigned this Dec 11, 2017
@AlexSkrypnyk AlexSkrypnyk added this to the v1 milestone Aug 18, 2018
@AlexSkrypnyk AlexSkrypnyk assigned index0h and unassigned AlexSkrypnyk Oct 8, 2022
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

3 participants