Hi @atripp,

Yes, the git error is during a build process. There is not much more of the log that share that I can see, this is what I get:

Yes the repository is browsable from the WebUI and shows the latest commit and all files as I would expect.

Thanks,
Justin

Update:

I tried to inspect the script that is checking out the code from git, and there is an error there, when I switch to visual editor:

and in the log:

at System.Collections.Generic.Dictionary2.FindValue(TKey key) at System.Collections.Generic.Dictionary2.ContainsKey(TKey key)
at Inedo.BuildMaster.Web.WebApplication.Pages.OtterScriptEditor.OSVE.BuildOsveStatementDyanmic(ActionStatement statement)
at Inedo.BuildMaster.Web.WebApplication.Pages.OtterScriptEditor.OSVE.BuildOsveStatement(Statement statement)
at Inedo.BuildMaster.Web.WebApplication.Pages.OtterScriptEditor.OSVE.<>c.<BuildOsveScript>b__0_1(Statement s)
at System.Linq.Enumerable.SelectArrayIterator2.MoveNext() at System.Collections.Generic.List1.InsertRange(Int32 index, IEnumerable1 collection) at System.Linq.Enumerable.ConcatIterator1.ToList()
at Inedo.BuildMaster.Web.WebApplication.Pages.OtterScriptEditor.OSVE.BuildOsveScript(ScriptProcessorOutput output)

As well as:

This is the script that is causing the visual editor to crash:

set $NpmPath = C:\Program Files\nodejs\npm.cmd;

Git::Checkout-Code
(
    From: "..........reponame...."
);

# Install Dependencies npm
Exec
(
    FileName: $NpmPath,
    Arguments: install,
    WorkingDirectory: ~\,
    ErrorOutputLogLevel: Warning
);

# Build webpack
Exec
(
    FileName: $NpmPath,
    Arguments: run build:webpack,
    WorkingDirectory: ~\,
    ErrorOutputLogLevel: Warning
);

Create-Artifact
(
    From: Swift/Files
);

Hello,

In my buildmaster application I have a connection to a Git repository, and the build worked fine before yesterday. Now when I try to build, the process says:

The repository named "......." could not be loaded.

I have the debug log checked and no additional information is logged.
I have tried to reconnect the Git repository and that works fine, so it does not seem to be caused by wrong git credentials.

The only thing that has changed is that I have changed the IIS binding to access builmaster (form the default 6262 port to a 443 binding)

What could be the cause of this?

Thanks,

Justin

Hi @atripp

Thanks, that looks easy enough, So I will get to it :-)

Justin

Apologies if the answer to this question is very obvious, but after reading documentation I'm not quite sure how to achieve the following:

I want to be able to automatically trigger a build and deployment to Integration whenever a new version of a certain NuGet package is released. But I can seem tofind where I could setup the trigger that looks at the version of the NuGet package.

Thanks for any pointers!

Justin

Hi @atripp,

Thanks that helped me solve it pretty quickly, just a typo somewhere in the script variables.
Very happy to have learned about the verbose setting :-)

Justin

Hello,

My deployment says it has run succesfully, but I still find that files are not copied over. I use the transfer command to copy files from the working directory to the application folder. According to the log all is well:

But I can see a version marker file is not copied, here is the file in the artifact:

And the file in the application folder is still showing the old file:

Also the Modified date of all other files in the folder are not changed, so it looks like nothing is actually copied over.

Any help figuring out why this is would be much appreciated...

Thanks,

Justin

Hi,

After deployment of my application I need to call some (in the near future probably even a lot) REST API's to finish configuration of the app.
My idea is to set this up with configuration files, which serve as input parameters for the API calls.

• Are their any functions native to OtterSript for calling the API's or would I need to use for example PowerShell to make the actual calls? (And if it must be powershell, how would I access the config files from there?)

• In this scenario, I forsee to en up with hundreds of configuration files, would that cause issues?

Thanks,

Justin

Hey Greg,

Thanks, changing to C:\Temp solved the issue indeed, so I guess the path was too long.
I'm experimenting with the Inedo Agent to make sure I can scale up and not have everything tied to Localhost, seems that was a good call given these subtle differences :-)

Cheers,
Justin

Hello,

I have a build Script that succeeds when executed as just the script, but it fails as part of the release pipeline build step.

When I execute just the script the log is:

As part of the Build step in the release pipeline the log is:

The difference is that the execute script uses the LocalAgent, and in the pipeline I have set the Agent to be an Inedo Agent installed on the local server.
Do I need some additional configuration for the Agent?

Thanks,

Justin

Hi @atripp

Sorry for the delayed response.
Yes, so I created a build, and during the creation of the build you are asked to select a pipeline.

After that the build was successful, but deployment failed. So then I created a release, based on the same build #1, and that does succeed. Where the issue is in the build #1 case the nullreference occurs on the config files.

My overview now shows the deploy from the build failed, but in the release it succeeded:

I could setup buildmaster to be accesible by you, please let me know if that helps.

Justin

Hi,

I think I am misunderstanding something around build vs release and their relation to the Configuration Files.
I have an application with some configuration files, and a pipeline When I go through "Create New Build", with the pipeline selected, the deployment to test fails with:

I created a release based on the same build, and this is succesfully deployed including the configuration files:

Both are connected to the same release pipeline, but there must be a difference in the context and the way I can address variables maybe? In OtteScript I use $PipelineStageName to get the correct configuration file...

Thanks,

Justin

Hi @rhessinger,

My point was actually that I think you might want to rename the second stage in the template for the "Main/Release Branch Pipeline" so this also is "Testing" That way ootb both already match up.
The error message was actually pretty ok, but since I used all defaults I was suprised about the naming difference.

Justin

Hi,

I have noticed when I create a Cofiguration Files, there are stages Integration, Testing, Production that can be associated.
When I create a Pipeline based on the Main/Release Branch template the second stage is named "Test" instead of "Testing", which gave me some trouble understanding why during deployment the configuration file could not be found :-)

Cheers,
Justin

Hi @atripp,

Thanks, that does sound like a good plan.
Altough the script now executes without error, something is wrong, because the log seems to say the artifact was deployed correctly to the working dorectory. but it contains 0 files.

However when I browse the Artifact I can see it does contain files. I must have something wrong still:

Thanks,
Justin

Hi,

I have been working on deployment of a web frontend that is managed by a CMS. In my build artifact I have all the files needed to redeploy, except for a folder "Images" that should be untouched during deployment. The images folder is managed by end users in the CMS.

I'm looking for a solution where I deploy the artifact, but leave the Images folder untouched. I have been trying to first copy the folder out to another folder, and then copy it back after the artifact has been deployed, but this is generating a variety of access denied messages at seemingly random points, which give me the feeling this is not a reliable solution.

Any other approaches that could be applied here?

Best regards,

Justin

Hello,

I'm working to get my first Build up and running. My GitHub repository is succesfully syncing, for a frontend project containing just Razor views (which will be deployed to a CMS).
The csproj file is pretty much just a container, because this project does not need to msbuild. I just need it to "npm install" and "npm run build:webpack" to build the frontend.

Am I right in concluding I should just do this with a PowerShell script or Cmd, working on the $WorkingDirectory, and this is not something I can handle with ProGet::Scan. I do have a ProGet feed setup which should have access to public npm packages, but I think I understand ProGet::Scan is not able to handle this kind of frontend build scenario?

Thanks for any help getting me started :-)

Justin