bot: status
fails in a setup with multiple bot instances configured to build for (partially) different architectures
#256
Labels
Milestone
Below is part of the log on
Saga
where we run the bot for NESSI. The bot also runs oneX3
andAWS
where it is configured to build for partially different targets.An idea to fix this could be to split the start of the comment for a new job into
New job
,on instance {instance}
,for architecture {architecture}
,for repository {repository}
,in job dir {job_working_directory}
which are configurable via
app.cfg
.Then, the function to parse the comments could use these different parts to
bot: status
commandarch_target_map
)The text was updated successfully, but these errors were encountered: