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

Retrieve the qmstr binary #2

Open
marcomicera opened this issue Jan 22, 2021 · 1 comment
Open

Retrieve the qmstr binary #2

marcomicera opened this issue Jan 22, 2021 · 1 comment

Comments

@marcomicera
Copy link
Member

At the moment, two out of three builders need the qmstr binary to send build information to the Quartermaster master/orchestrator.

The Python and CMake builder use it (qmstr run ...).
The Maven builder does this by patching the root pom.xml file, injecting the Quartermaster Maven plugin, so it won't need it.

@marcomicera
Copy link
Member Author

  • The Docker image entrypoint should still be the synchronization main.go file: the builder still needs to connect to RabbitMQ and wait for the order from the Orchestrator
  • The callback function (that is invoked as soon as the builder receives the order from the Orchestrator) needs to build the project (e.g., python3 setup.py qmstr for Python, qmstr run cmake ... for C, and mvn package ... for Java)
    • We will include the qmstr binary in this repository to be able to compile C and Python projects. Upon creating the Maven builder, we will revert this.
    • We need to be able to run CLI commands from Golang

@marcomicera marcomicera transferred this issue from another repository Jan 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant