2022-08-19 15:59:36 +02:00
|
|
|
// Copyright (C) 2016 The Qt Company Ltd.
|
2022-12-21 10:12:09 +01:00
|
|
|
// SPDX-License-Identifier: LicenseRef-Qt-Commercial OR GPL-3.0-only WITH Qt-GPL-exception-1.0
|
2012-07-25 17:41:01 +02:00
|
|
|
|
2011-07-07 10:43:59 +02:00
|
|
|
#include "abstractremotelinuxdeploystep.h"
|
|
|
|
|
|
2023-01-09 09:28:58 +01:00
|
|
|
#include "deploymenttimeinfo.h"
|
2022-07-15 12:20:23 +02:00
|
|
|
#include "remotelinuxtr.h"
|
2011-07-07 10:43:59 +02:00
|
|
|
|
2023-01-09 09:28:58 +01:00
|
|
|
#include <projectexplorer/deployablefile.h>
|
|
|
|
|
#include <projectexplorer/devicesupport/idevice.h>
|
2012-09-03 18:31:44 +02:00
|
|
|
#include <projectexplorer/kitinformation.h>
|
2023-01-09 09:28:58 +01:00
|
|
|
#include <projectexplorer/projectexplorerconstants.h>
|
|
|
|
|
#include <projectexplorer/target.h>
|
|
|
|
|
|
2023-05-10 21:38:41 +02:00
|
|
|
#include <solutions/tasking/tasktree.h>
|
|
|
|
|
|
2023-01-09 09:28:58 +01:00
|
|
|
#include <utils/qtcassert.h>
|
|
|
|
|
|
|
|
|
|
#include <QDateTime>
|
|
|
|
|
#include <QPointer>
|
2011-07-07 10:43:59 +02:00
|
|
|
|
|
|
|
|
using namespace ProjectExplorer;
|
2023-05-10 19:54:52 +02:00
|
|
|
using namespace Tasking;
|
2023-01-09 09:28:58 +01:00
|
|
|
using namespace Utils;
|
2011-07-07 10:43:59 +02:00
|
|
|
|
|
|
|
|
namespace RemoteLinux {
|
|
|
|
|
namespace Internal {
|
|
|
|
|
|
|
|
|
|
class AbstractRemoteLinuxDeployStepPrivate
|
|
|
|
|
{
|
|
|
|
|
public:
|
|
|
|
|
bool hasError;
|
2023-07-07 11:40:12 +02:00
|
|
|
std::function<expected_str<void>()> internalInit;
|
2023-03-21 16:07:20 +01:00
|
|
|
|
|
|
|
|
DeploymentTimeInfo deployTimes;
|
|
|
|
|
std::unique_ptr<TaskTree> m_taskTree;
|
2011-07-07 10:43:59 +02:00
|
|
|
};
|
|
|
|
|
|
2023-01-09 09:28:58 +01:00
|
|
|
} // Internal
|
|
|
|
|
|
|
|
|
|
using namespace Internal;
|
|
|
|
|
|
2023-03-21 16:07:20 +01:00
|
|
|
AbstractRemoteLinuxDeployStep::AbstractRemoteLinuxDeployStep(BuildStepList *bsl, Id id)
|
2023-03-22 09:34:34 +01:00
|
|
|
: BuildStep(bsl, id), d(new AbstractRemoteLinuxDeployStepPrivate)
|
|
|
|
|
{}
|
2023-01-09 09:28:58 +01:00
|
|
|
|
2023-03-21 16:07:20 +01:00
|
|
|
AbstractRemoteLinuxDeployStep::~AbstractRemoteLinuxDeployStep()
|
2023-01-09 09:28:58 +01:00
|
|
|
{
|
|
|
|
|
delete d;
|
|
|
|
|
}
|
|
|
|
|
|
2023-03-21 16:07:20 +01:00
|
|
|
IDevice::ConstPtr AbstractRemoteLinuxDeployStep::deviceConfiguration() const
|
2023-01-09 09:28:58 +01:00
|
|
|
{
|
2023-03-21 16:07:20 +01:00
|
|
|
return DeviceKitAspect::device(kit());
|
2023-01-09 09:28:58 +01:00
|
|
|
}
|
|
|
|
|
|
2023-03-21 16:07:20 +01:00
|
|
|
void AbstractRemoteLinuxDeployStep::saveDeploymentTimeStamp(const DeployableFile &deployableFile,
|
2023-01-09 09:28:58 +01:00
|
|
|
const QDateTime &remoteTimestamp)
|
|
|
|
|
{
|
|
|
|
|
d->deployTimes.saveDeploymentTimeStamp(deployableFile, kit(), remoteTimestamp);
|
|
|
|
|
}
|
|
|
|
|
|
2023-03-21 16:07:20 +01:00
|
|
|
bool AbstractRemoteLinuxDeployStep::hasLocalFileChanged(
|
2023-01-09 09:28:58 +01:00
|
|
|
const DeployableFile &deployableFile) const
|
|
|
|
|
{
|
|
|
|
|
return d->deployTimes.hasLocalFileChanged(deployableFile, kit());
|
|
|
|
|
}
|
|
|
|
|
|
2023-03-21 16:07:20 +01:00
|
|
|
bool AbstractRemoteLinuxDeployStep::hasRemoteFileChanged(
|
2023-01-09 09:28:58 +01:00
|
|
|
const DeployableFile &deployableFile, const QDateTime &remoteTimestamp) const
|
|
|
|
|
{
|
|
|
|
|
return d->deployTimes.hasRemoteFileChanged(deployableFile, kit(), remoteTimestamp);
|
|
|
|
|
}
|
|
|
|
|
|
2023-07-07 11:40:12 +02:00
|
|
|
expected_str<void> AbstractRemoteLinuxDeployStep::isDeploymentPossible() const
|
2023-01-09 09:28:58 +01:00
|
|
|
{
|
|
|
|
|
if (!deviceConfiguration())
|
2023-07-07 11:40:12 +02:00
|
|
|
return make_unexpected(Tr::tr("No device configuration set."));
|
|
|
|
|
return {};
|
2023-01-09 09:28:58 +01:00
|
|
|
}
|
|
|
|
|
|
2023-07-07 11:40:12 +02:00
|
|
|
void AbstractRemoteLinuxDeployStep::setInternalInitializer(
|
|
|
|
|
const std::function<expected_str<void>()> &init)
|
2019-06-07 16:43:06 +02:00
|
|
|
{
|
|
|
|
|
d->internalInit = init;
|
|
|
|
|
}
|
|
|
|
|
|
2011-07-07 10:43:59 +02:00
|
|
|
bool AbstractRemoteLinuxDeployStep::fromMap(const QVariantMap &map)
|
|
|
|
|
{
|
|
|
|
|
if (!BuildStep::fromMap(map))
|
|
|
|
|
return false;
|
2023-03-22 10:05:26 +01:00
|
|
|
d->deployTimes.importDeployTimes(map);
|
2011-07-07 10:43:59 +02:00
|
|
|
return true;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
QVariantMap AbstractRemoteLinuxDeployStep::toMap() const
|
|
|
|
|
{
|
2020-08-20 11:25:35 +02:00
|
|
|
QVariantMap map = BuildStep::toMap();
|
2023-03-22 10:05:26 +01:00
|
|
|
map.insert(d->deployTimes.exportDeployTimes());
|
2020-08-20 11:25:35 +02:00
|
|
|
return map;
|
2011-07-07 10:43:59 +02:00
|
|
|
}
|
|
|
|
|
|
2019-01-10 15:31:44 +01:00
|
|
|
bool AbstractRemoteLinuxDeployStep::init()
|
2011-07-07 10:43:59 +02:00
|
|
|
{
|
2019-06-07 16:43:06 +02:00
|
|
|
QTC_ASSERT(d->internalInit, return false);
|
2023-07-07 11:40:12 +02:00
|
|
|
const auto canDeploy = d->internalInit();
|
2019-04-24 14:38:01 +02:00
|
|
|
if (!canDeploy) {
|
2023-07-07 11:40:12 +02:00
|
|
|
emit addOutput(Tr::tr("Cannot deploy: %1").arg(canDeploy.error()),
|
2019-04-24 14:38:01 +02:00
|
|
|
OutputFormat::ErrorMessage);
|
|
|
|
|
}
|
2023-07-07 11:40:12 +02:00
|
|
|
return bool(canDeploy);
|
2011-07-07 10:43:59 +02:00
|
|
|
}
|
|
|
|
|
|
ProjectExplorer: Rework the build step run interface
Originally, the build manager used to run all build steps in a dedicated
thread. Communication between the step and the manager happened via a
QFutureInterface that was passed into the step's run() function.
Later, new steps were added that operated asynchronously, so the build
manager had to differentiate between the different kinds of steps for
starting and stopping.
These days, almost all build and deploy steps work asynchronously, which
made the QFuture-based interface look increasingly odd.
With this patch, all build steps are expected to work asynchronously, so
the build manager no longer needs to differentiate. Steps are started
and requested to stop via the run() and cancel() functions,
respectively, and emit the finished() signal when they are done. Build
step implementors no longer have to deal with a QFutureInterface. For
steps whose implementation is inherently synchronous, the BuildStep base
class offers a runInThread() function.
Change-Id: If905c68b234c5a669f6e19f43142eaa57d594803
Reviewed-by: hjk <hjk@qt.io>
2019-01-25 14:26:34 +01:00
|
|
|
void AbstractRemoteLinuxDeployStep::doRun()
|
2011-07-07 10:43:59 +02:00
|
|
|
{
|
2011-09-16 11:33:48 +02:00
|
|
|
d->hasError = false;
|
2023-03-22 10:05:26 +01:00
|
|
|
|
|
|
|
|
QTC_ASSERT(!d->m_taskTree, return);
|
|
|
|
|
|
2023-07-10 09:09:02 +02:00
|
|
|
d->m_taskTree.reset(new TaskTree(runRecipe()));
|
2023-03-22 10:05:26 +01:00
|
|
|
const auto endHandler = [this] {
|
|
|
|
|
d->m_taskTree.release()->deleteLater();
|
|
|
|
|
handleFinished();
|
|
|
|
|
};
|
|
|
|
|
connect(d->m_taskTree.get(), &TaskTree::done, this, endHandler);
|
|
|
|
|
connect(d->m_taskTree.get(), &TaskTree::errorOccurred, this, endHandler);
|
|
|
|
|
d->m_taskTree->start();
|
2011-07-07 10:43:59 +02:00
|
|
|
}
|
|
|
|
|
|
ProjectExplorer: Rework the build step run interface
Originally, the build manager used to run all build steps in a dedicated
thread. Communication between the step and the manager happened via a
QFutureInterface that was passed into the step's run() function.
Later, new steps were added that operated asynchronously, so the build
manager had to differentiate between the different kinds of steps for
starting and stopping.
These days, almost all build and deploy steps work asynchronously, which
made the QFuture-based interface look increasingly odd.
With this patch, all build steps are expected to work asynchronously, so
the build manager no longer needs to differentiate. Steps are started
and requested to stop via the run() and cancel() functions,
respectively, and emit the finished() signal when they are done. Build
step implementors no longer have to deal with a QFutureInterface. For
steps whose implementation is inherently synchronous, the BuildStep base
class offers a runInThread() function.
Change-Id: If905c68b234c5a669f6e19f43142eaa57d594803
Reviewed-by: hjk <hjk@qt.io>
2019-01-25 14:26:34 +01:00
|
|
|
void AbstractRemoteLinuxDeployStep::doCancel()
|
2011-07-07 10:43:59 +02:00
|
|
|
{
|
2011-09-16 11:33:48 +02:00
|
|
|
if (d->hasError)
|
2011-07-07 10:43:59 +02:00
|
|
|
return;
|
|
|
|
|
|
2022-07-15 12:20:23 +02:00
|
|
|
emit addOutput(Tr::tr("User requests deployment to stop; cleaning up."),
|
2017-01-12 10:59:12 +01:00
|
|
|
OutputFormat::NormalMessage);
|
2011-09-16 11:33:48 +02:00
|
|
|
d->hasError = true;
|
2023-03-22 10:05:26 +01:00
|
|
|
|
|
|
|
|
if (!d->m_taskTree)
|
|
|
|
|
return;
|
|
|
|
|
d->m_taskTree.reset();
|
|
|
|
|
handleFinished();
|
2011-07-07 10:43:59 +02:00
|
|
|
}
|
|
|
|
|
|
2023-03-22 09:34:34 +01:00
|
|
|
void AbstractRemoteLinuxDeployStep::addProgressMessage(const QString &message)
|
2011-07-07 10:43:59 +02:00
|
|
|
{
|
2017-01-12 10:59:12 +01:00
|
|
|
emit addOutput(message, OutputFormat::NormalMessage);
|
2011-07-07 10:43:59 +02:00
|
|
|
}
|
|
|
|
|
|
2023-03-22 09:34:34 +01:00
|
|
|
void AbstractRemoteLinuxDeployStep::addErrorMessage(const QString &message)
|
2011-07-07 10:43:59 +02:00
|
|
|
{
|
2017-01-12 10:59:12 +01:00
|
|
|
emit addOutput(message, OutputFormat::ErrorMessage);
|
2020-04-16 13:53:05 +02:00
|
|
|
emit addTask(DeploymentTask(Task::Error, message), 1); // TODO correct?
|
2011-09-16 11:33:48 +02:00
|
|
|
d->hasError = true;
|
2011-07-07 10:43:59 +02:00
|
|
|
}
|
|
|
|
|
|
2023-03-22 09:34:34 +01:00
|
|
|
void AbstractRemoteLinuxDeployStep::addWarningMessage(const QString &message)
|
2011-09-29 15:00:15 +02:00
|
|
|
{
|
2017-01-12 10:59:12 +01:00
|
|
|
emit addOutput(message, OutputFormat::ErrorMessage);
|
2020-04-16 13:53:05 +02:00
|
|
|
emit addTask(DeploymentTask(Task::Warning, message), 1); // TODO correct?
|
2011-09-29 15:00:15 +02:00
|
|
|
}
|
|
|
|
|
|
2011-07-07 10:43:59 +02:00
|
|
|
void AbstractRemoteLinuxDeployStep::handleFinished()
|
|
|
|
|
{
|
2011-09-16 11:33:48 +02:00
|
|
|
if (d->hasError)
|
2022-07-15 12:20:23 +02:00
|
|
|
emit addOutput(Tr::tr("Deploy step failed."), OutputFormat::ErrorMessage);
|
2011-07-07 10:43:59 +02:00
|
|
|
else
|
2022-07-15 12:20:23 +02:00
|
|
|
emit addOutput(Tr::tr("Deploy step finished."), OutputFormat::NormalMessage);
|
2023-03-22 09:34:34 +01:00
|
|
|
|
ProjectExplorer: Rework the build step run interface
Originally, the build manager used to run all build steps in a dedicated
thread. Communication between the step and the manager happened via a
QFutureInterface that was passed into the step's run() function.
Later, new steps were added that operated asynchronously, so the build
manager had to differentiate between the different kinds of steps for
starting and stopping.
These days, almost all build and deploy steps work asynchronously, which
made the QFuture-based interface look increasingly odd.
With this patch, all build steps are expected to work asynchronously, so
the build manager no longer needs to differentiate. Steps are started
and requested to stop via the run() and cancel() functions,
respectively, and emit the finished() signal when they are done. Build
step implementors no longer have to deal with a QFutureInterface. For
steps whose implementation is inherently synchronous, the BuildStep base
class offers a runInThread() function.
Change-Id: If905c68b234c5a669f6e19f43142eaa57d594803
Reviewed-by: hjk <hjk@qt.io>
2019-01-25 14:26:34 +01:00
|
|
|
emit finished(!d->hasError);
|
2011-07-07 10:43:59 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
void AbstractRemoteLinuxDeployStep::handleStdOutData(const QString &data)
|
|
|
|
|
{
|
2017-01-12 10:59:12 +01:00
|
|
|
emit addOutput(data, OutputFormat::Stdout, DontAppendNewline);
|
2011-07-07 10:43:59 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
void AbstractRemoteLinuxDeployStep::handleStdErrData(const QString &data)
|
|
|
|
|
{
|
2017-01-12 10:59:12 +01:00
|
|
|
emit addOutput(data, OutputFormat::Stderr, DontAppendNewline);
|
2011-07-07 10:43:59 +02:00
|
|
|
}
|
|
|
|
|
|
2023-03-21 16:07:20 +01:00
|
|
|
bool AbstractRemoteLinuxDeployStep::isDeploymentNecessary() const
|
|
|
|
|
{
|
|
|
|
|
return true;
|
|
|
|
|
}
|
|
|
|
|
|
2023-07-10 09:09:02 +02:00
|
|
|
Group AbstractRemoteLinuxDeployStep::runRecipe()
|
|
|
|
|
{
|
|
|
|
|
const auto onSetup = [this] {
|
|
|
|
|
const auto canDeploy = isDeploymentPossible();
|
|
|
|
|
if (!canDeploy) {
|
|
|
|
|
addErrorMessage(canDeploy.error());
|
|
|
|
|
handleFinished();
|
|
|
|
|
return SetupResult::StopWithError;
|
|
|
|
|
}
|
|
|
|
|
if (!isDeploymentNecessary()) {
|
|
|
|
|
addProgressMessage(Tr::tr("No deployment action necessary. Skipping."));
|
|
|
|
|
handleFinished();
|
|
|
|
|
return SetupResult::StopWithDone;
|
|
|
|
|
}
|
|
|
|
|
return SetupResult::Continue;
|
|
|
|
|
};
|
|
|
|
|
return Group { onGroupSetup(onSetup), deployRecipe() };
|
2023-03-21 16:07:20 +01:00
|
|
|
}
|
|
|
|
|
|
2011-07-07 10:43:59 +02:00
|
|
|
} // namespace RemoteLinux
|