summaryrefslogtreecommitdiff
path: root/src/buildtool/profile/profile.hpp
diff options
context:
space:
mode:
authorKlaus Aehlig <klaus.aehlig@huawei.com>2025-05-07 10:22:39 +0200
committerKlaus Aehlig <klaus.aehlig@huawei.com>2025-05-07 12:25:56 +0200
commit9ff01a766d98359c7dcf199aa6c4fba7fb427140 (patch)
treeeef791d08966568a36b1aa138eb2041c7a91a2f4 /src/buildtool/profile/profile.hpp
parent520bb21a4a0887478dffbcc83997a4015f7e67a4 (diff)
downloadjustbuild-9ff01a766d98359c7dcf199aa6c4fba7fb427140.tar.gz
profile: include remote-execution properties
Include in the profile also the effective remote-execution endpoint, properties, and dispatch list. Software projects are often tested in a variety of environments or hardware configurations; as, obviously, the performance might differ significantly (especially depending on the used hardware) a proper analysis therefore requires the possibility to distinguish the various backends. Adding the effective configuration adds this posibility.
Diffstat (limited to 'src/buildtool/profile/profile.hpp')
-rw-r--r--src/buildtool/profile/profile.hpp2
1 files changed, 2 insertions, 0 deletions
diff --git a/src/buildtool/profile/profile.hpp b/src/buildtool/profile/profile.hpp
index d172ae85..a16d9996 100644
--- a/src/buildtool/profile/profile.hpp
+++ b/src/buildtool/profile/profile.hpp
@@ -25,6 +25,7 @@
#include "nlohmann/json.hpp"
#include "src/buildtool/execution_api/common/execution_response.hpp"
+#include "src/buildtool/execution_api/remote/config.hpp"
#include "src/buildtool/main/cli.hpp"
class Profile {
@@ -36,6 +37,7 @@ class Profile {
}
void Write(int exit_code);
+ void SetRemoteExecutionConfig(RemoteExecutionConfig const&);
void SetTarget(nlohmann::json target);
void SetConfiguration(nlohmann::json configuration);
void NoteActionCompleted(std::string const& id,