Skip to main content
Skip table of contents

System artifacts

System artifacts should be placed in the correct folder under GIT:

$\LinkWhopper\Bizbrains.Link.SystemArtifacts

  • InitializeSteps

  • ItinerarySteps

  • TransportTypes

    • Retrieve

    • Send

Under each area (folder) there is a solution to which artifact-projects should be added.

Namespace

The namespace (and assembly-name) for the different areas must be:

InitializeSteps

Bizbrains.Link.Initialize.InitializeSteps.$(MSBuildProjectName)

ItinerarySteps

Bizbrains.Link.SystemArtifacts.ItinerarySteps.$(MSBuildProjectName)

RetrieveTransport

Bizbrains.Link.TransportTypes.Retrieve.$(MSBuildProjectName)

SendTransport

Bizbrains.Link.TransportTypes.Send.$(MSBuildProjectName)

If the above pattern is not used, the project won’t be part of the build pipeline

StepKeyName

Each step in Link must provide a unique name. For our system-steps the following naming convention is required (all keys must be lower-case):

Area

Key Prefix

Example

Initialize Steps

system-initialize-*

system-initialize-edifact-microsoft

Itinerary Steps

system-itinerary-*

system-itinerary-xslt

Send Transport

system-transport-send-*

system-transport-send-as4

Retrieve Transport

system-transport-retrieve-*

system-transport-retrieve-sftp

Deployment of System Itinerary Steps

This section describes how to build and deploy System Artifacts

Build pipeline

A build pipeline which builds the four solution is placed here: https://bizbrains-productteam.visualstudio.com/Link Whopper/_build?definitionId=46

This pipeline builds all artifacts which are part of the solutions.

Ftp deployment

After the build of all projects, the output assemblies will be pushed/deployed to the following FTP account:

Host: ftp.test-link.bizbrains.com
Username: productteam-artifacts
Password: (see Keepass Bizbrains->Product Team->productteam-artifacts)

The output assemblies will be put into folders named with the build-number.

Notice - any dependencies the artifacts might have is not part of this deployment.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.