Class PhaseExecution
- All Implemented Interfaces:
ModelObject
While the phases starts in declared order, they might not complete in that order. Much less previous phase will be completed before next one starts.
There are several reasons for that: provisioning listener is called when the results are
picked up, the agent might have started launching in the meantime. There are plugins that in fact
enforce the launch to complete, before completing the NodeProvisioner.PlannedNode.future
. To avoid any problems this can cause, the
execution of phases is expected to occur in order, the execution will accept attachments
regardless if the next phase started or not. For the time tracking purposes, the phase is
considered completed as soon as the next phase begins. IOW, despite the fact the agent already
started launching, plugin can still append provisioning log.
-
Method Summary
Modifier and TypeMethodDescriptiongetAttachment
(String urlName) <T extends PhaseExecutionAttachment>
List<T>getAttachments
(Class<T> type) getPhase()
long
getUrlName
(PhaseExecutionAttachment attachment)
-
Method Details
-
getAttachments
-
getAttachments
-
getStatus
-
getStarted
-
getStartedTimestamp
public long getStartedTimestamp() -
getPhase
-
getDisplayName
- Specified by:
getDisplayName
in interfaceModelObject
-
getUrlName
@Restricted(org.kohsuke.accmod.restrictions.NoExternalUse.class) @CheckForNull public String getUrlName(@NonNull PhaseExecutionAttachment attachment) -
getAttachment
@Restricted(org.kohsuke.accmod.restrictions.DoNotUse.class) public PhaseExecutionAttachment getAttachment(String urlName)
-