Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple agents Run-AlPipeline #3603

Open
akhileshekartha opened this issue Jul 24, 2024 · 1 comment
Open

Multiple agents Run-AlPipeline #3603

akhileshekartha opened this issue Jul 24, 2024 · 1 comment
Assignees

Comments

@akhileshekartha
Copy link

Hi
I have installed multiple build agents on our build server. Our build process includes multiple stages to generate app files for different versions and countries , builds running based on preprocessors. I am trying to run multiple jobs on the same server using different devops agents. The build script is already updated with usePsSession = $false. All agents are running with different admin user accounts. However, when running multiple pipelines in different stages, I'm encountering issues. Can you help me identify what might be missing ?

Scripts used to create container and cause the issue

Run-AlPipeline  -containerName $ContainerName `
  -imageName $imageName `
  -baseFolder $WorkFolder `
  -credential $credential `
  -CreateRuntimePackages `
  -licenseFile $latest_License `
  -BuildArtifactFolder $WorkFolder\AppFiles `
  -accept_insiderEula `
  -previousApps $Previousapp `
  -installApps $DependedApps `
  -pipeline $ProjectName `
  -enableCodeCop `
  -enableAppSourceCop `
  -AppSourceCopMandatoryAffixes @Affixes `
  -enableUICop `
  -azureDevOps `
  -doNotRunBcptTests `
  -doNotBuildTests `
  -doNotRunTests `
  -appFolders @("Project\Main App") `
  -artifact $bcArtifacts `
  -preProcessorSymbols $preProcessorSymbols `
  -PostCompileApp $addtionalScripts `
  -PreCompileApp $PreCompileApp `
  -CustomCodeCops $CustomCop `
  -vsixFile  $AlLanguageExtensionUrl `
  -AppBuild $buildID

image

image

@freddydk
Copy link
Contributor

This
image

looks like somebody is removing the container.

It looks like you are using predictable names for the container - maybe that name is reused in another run pipeline, which deletes your container and then nothing works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants