search

networknt / light-bot

A microservice based DevOps agent that handles multiple repositories and dependencies
Apache License 2.0
7 stars 3 forks source link

reset overwritten source files to solve "checkout aborting" after a previous build #82

Closed yibogithub closed 5 years ago

yibogithub commented 5 years ago

Hi Dan, this is to make build-all a little bit easier. A status file merge from a previous build will prevent a complete checkout of the same repo in the same directory.

stevehu commented 5 years ago

@yibogithub For every task, it has its workspace. The only reason I can imagine is that the workspace is manually updated by the user somehow. Is there any other reason that checkout can be aborted?

ddobrin commented 5 years ago

The only situation where this happened is that developers work in the same workspace created by the bot for a long time, however run the bot intermittently.

At that time, they could have, in common or utility projects, made changes, while the files have been updated in Git.

This is solved by good development practices

stevehu commented 5 years ago

I am using networknt for local development and running the checkout task every morning to sync the master branch for each repo. All light-bot tasks have their own folders so there shouldn't be any conflicts.