Unfortunately we're not able to diagnose this with the information you provided. That error really doesn't make sense in the place it's happening. Can you please submit a ticket with: Configuration Variables defined at various levels (System, etc) Plan as OtterScript Pipeline as JSON Full Execution log, including the full stack trace you sent

Yep, all of these are things that people use BuildMaster for on a regular basis. Note that, the terminology you're using ("pipelines") is more generalized than the BuildMaster construct (there are Pipelines and Deployment Plans that do a mix of the things you describe), but the general idea is the same.

It's supported using the Legacy Action, which isn't ideal obviously. This will be replaced with a function in v5/OtterScript: # reads at most 250 characters from the file set $hdarfs = $FileContents(c:\hdarfs\info.txt, 250); Log-Information $hdarfs; However, this function is only available in 5.3 (which is shipping this week).

Alana, I knew they are in the legacy side but I couldn't find a easy way to find/use them if I'm creating a new plan but I didn't think of creating a new legacy one then converting it later (firm smack to my forehead!) Thanks!

Whoops, seems like we forgot to update the operations documentation on the site after 1.3. The function is renamed to $GetCredentialProperty (though the old alias should still work) and you can access it like: <code>set $password = $GetCredentialProperty(MyCredential,Password);</code> Note you can see the generated documentation: http://<otter-host-name>/reference/functions

Currently, only NuGet feeds use the license filter, it shouldn't be displayed on npm feeds... We do plan on adding support for better licensing filtering in a future version, as the current implemention is a bit limiting.

Thanks for the pointer. I noticed if I edit the Job Template it doesn't seem to have the right plan 'selected' in the Plan Name dropdown (it defaults to the first in the list every time). I think I saved it without noticing and it ended up attached to the wrong one. Maybe review the edit code that generates this page: https://url/job-templates/edit?jobTemplateId=x

We do, along with a few other types (Gems, PyPi, Composer), but there's no ETA on it right now; once we get private a Docker registry, we will look to refactor the feeds and UI a bit as to allow for easier adding of simple package types.

The "Generate Release Notes Action" in those release notes was referring to the same action as 4.9.7, which was not implemented in 5.0.0. The Generate Release Notes Operation for v5 plans is available as of v5.2.3.

Chocolately packages are, essentially, nothing more than a powershell script that downloads and runs an installer from some url on the internet. It would be virtually impossible to inspect arbitrary powershell scripts and determine what they would download when run, and then download/proxy those installers. So, if you want full control over all aspects of the chocolatey packages (including the installers that are downloaded), you will just have to create your own based on the contents of the open-source packages.

Hi Alana, Any chance of sending that C# code to me as well? We are also facing issues getting multi-domain AD working. TIA

Sorry for a late follow up on this. So one place where this solution falls apart is that your Jenkins add-on for BuildMaster does not support the meta-tags in the version field.

Done... ticket #EDO-1612.... hope it helps, and thanks in advance for all your efforts and attention.

Thank you for the report, it appears to be a regression with that event listener that will be fixed in the next version. A patch is also available for download here, simply extract the zip file and execute the contained SQL file against the BuildMaster database. Note: This patch may only be used for versions of BuildMaster between v5.0.0 and v5.2.3 (inclusive) and will be already included in v5.2.4 and later.

OK, I was supposing it but I didn't find it explicitly in documentation. Thanks for your quicker answer.

A bit late in the game for an answer, but I thought I would add my two cents: Tod is 100% correct, you do not want to use variables within Buildmaster for this, but you do not need to go the length of over-managing either. To resolve this issue: Passwords: Resolve this with the credentials for the database. Database name differences: Have your DBA create a Synonym across the board. For example, if your app is named "DirtyHarry" and on DBDEV is called "RevolverDB" and PRODDEV is called "MagnumDB" just create a synonym "DirtyHarryDB" on both servers, resolving to the actual DB name. Then in all your change scripts use DirtyHarryDB... or just set a synonym on DEV to be the same as PROD DB name or vice-versa. There are quite a few ways you can resolve issues like this, but it is always better to be genericized. We have the same in that we utilize snapshots in DEV that can be in any database location, but in production they are referenced to linked servers. -Kevin

Here are the exceptions that I'm getting when add my extension(nothing descriptive for me): Details: URL: http://localhost:81/administration/extensions Referrer: http://localhost:81/administration User: Admin User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko Stack trace: at System.Web.Hosting.ISAPIWorkerRequestInProcForIIS6.FlushCore(Byte[] status, Byte[] header, Int32 keepConnected, Int32 totalBodySize, Int32 numBodyFragments, IntPtr[] bodyFragments, Int32[] bodyFragmentLengths, Int32 doneWithSession, Int32 finalStatus, Boolean& async) at System.Web.Hosting.ISAPIWorkerRequest.FlushCachedResponse(Boolean isFinal) at System.Web.HttpResponse.Flush(Boolean finalFlush, Boolean async) at System.Web.HttpWriter.WriteFromStream(Byte[] data, Int32 offset, Int32 size) at Inedo.IO.SlimMemoryStream.CopyTo(Stream destination) at Inedo.Web.PageFree.SimplePageBase.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) And another one: URL: http://localhost:81/administration/error-log/entry?messageId=139 Referrer: http://localhost:81/administration User: Admin User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko Stack trace: at System.Web.Hosting.ISAPIWorkerRequestInProcForIIS6.FlushCore(Byte[] status, Byte[] header, Int32 keepConnected, Int32 totalBodySize, Int32 numBodyFragments, IntPtr[] bodyFragments, Int32[] bodyFragmentLengths, Int32 doneWithSession, Int32 finalStatus, Boolean& async) at System.Web.Hosting.ISAPIWorkerRequest.FlushCachedResponse(Boolean isFinal) at System.Web.HttpResponse.Flush(Boolean finalFlush, Boolean async) at System.Web.HttpWriter.WriteFromStream(Byte[] data, Int32 offset, Int32 size) at Inedo.IO.SlimMemoryStream.CopyTo(Stream destination) at Inedo.Web.PageFree.SimplePageBase.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

Update to 4.1.3 has solved this issue for us.

We just updated our server from 4.0.8 to 4.2.0 and now we encounter this problem too. After confirming that the package/version should be deleted, you are redirected back to the feed but the package/version is still there. In the log there are no errors whatsoever and the recent error log shows "There are no recent errors."