Skip to content
This repository has been archived by the owner on May 8, 2024. It is now read-only.

Move execution logic to the agent #15

Closed
fkorotkov opened this issue Jul 22, 2020 · 0 comments · Fixed by #32
Closed

Move execution logic to the agent #15

fkorotkov opened this issue Jul 22, 2020 · 0 comments · Fixed by #32

Comments

@fkorotkov
Copy link
Contributor

There is no need for an agent to get the next command as a response from ReportCommand method. Once Execution Behaviour will be exposed through the API we can implement the logic on the agent.
edigaryev added a commit that referenced this issue Aug 10, 2020
@edigaryev
Use execution behavior to determine whether to run the next command
39852dc 
Resolves #15.
@edigaryev edigaryev mentioned this issue Aug 10, 2020
Merged
edigaryev added a commit that referenced this issue Aug 12, 2020
@edigaryev
Use execution behavior to determine whether to run the next command
b5e9407 
Resolves #15.
edigaryev added a commit that referenced this issue Aug 12, 2020
@edigaryev
Use execution behavior to determine whether to run the next command (#32
da40519 
)

* Use execution behavior to determine whether to run the next command

Resolves #15.

* Don't let ON_FAILURE and ALWAYS commands to change the execution course

* Introduce BoundedCommands()

* Sync api package with the new .proto

* Pick up failedAtLeastOnce value from the InitialCommands RPC response

* Try to run all commands
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use execution behavior to determine whether to run the next command cirruslabs/cirrus-ci-agent
1 participant
@fkorotkov