Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login
    1. Home
    2. dean-houston
    3. Posts

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    dean-houstonD Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 0
    • Posts 226
    • Groups 1

    Posts

    Recent
    • RE: Pull Maven artifacts - invalid version

      Hi @michal-roszak_0767 , @steviecoaster ,

      Maven versioning is a total mess. v*** is indeed an invalid version, per the which means that (among other things) it must be lexicographically sorted for determining latest version.

      It looks like they knew that enough to use a string... but not enough to use a valid version number. Oh well. /rant

      If you go to Manage Feed Settings, you can enable invalid versions in the feed. The message should make this more clear, so I will clarify that via PG-2977 in the next maintenance release.

      -- Dean

      posted in Support
      dean-houstonD
      dean-houston
    • RE: Extending the migrator utility

      Hi @steviecoaster,

      The current package import tool uses the NuGet API. It's not really easy to use, and I'm afraid our API access code isn't really "portable" -- it's tightly integrated into Connectors, which are tightly integrated into Feeds, etc.

      Here's a guide on how to query all published packages from a NuGet feed:
      https://learn.microsoft.com/en-us/nuget/guides/api/query-for-all-published-packages

      That said, next week we will be releasing a brand-new package importer that will connect to Sona Nexus, Artifactory, AzureDevOps, ProGet, GitHub, and GitLab. These use the provider-specific APIs and work much better than what we have now.

      Functionality it's the same, but now your credentials are stored in ProGet. You can also run it multiple times, and it will only import new packages. This is useful for the cases where you are transitioning usage.

      -- Dean

      posted in Support
      dean-houstonD
      dean-houston
    • RE: Feed creator wizard - proxy creation error

      Hi @michal-roszak_0767 ,

      Thanks for letting us know!

      Unfortunately the Feed Wizard seems to have some quirky behavior when configuring certain combinations of options, as you've noticed. We are actually in the process of rewriting the new feed wizard to be a bit more simpler (esapecially behind-the-scenes), hopefully in the next couple weeks it'll be in a new maintenance release.

      In the meantime, if you encounter these errors... I would just create the connectors on the MAnage Feed page. Which it sounds like you've done :)

      -- Dean

      posted in Support
      dean-houstonD
      dean-houston
    • RE: Stream was too long when editing Universal Package description.

      Hi @daniel-pardo_5658 ,

      The UI-based package editor is intended for small packages, up to 50 MB or so. It looks like there is a platform-enforced limit of 2GB. For now, you will need to download, edit, re-upload.

      That said, I switched the stream that we're using to something that can accommodate larger packages, but I did not test it so I really don't know if it will actually work on these packages. It'll be in the upcoming maintenance release via PG-2964

      -- Dean

      posted in Support
      dean-houstonD
      dean-houston
    • RE: Otterscript: Usage of Success exit code or EXEC operation - clarifications

      Hi @scusson_9923 ,

      Sorry, I misunderstood; I thought you were doing PSExec.

      In this case you are just executing the pwsh process, so you need to figure out how to have that process return an exit code.

      I don't know if that's the same as powershell.exe, but a AI told me "To return an error code from a PowerShell script, the exit statement followed by the desired error code should be used."

      So I guess exit -1 or something like that?

      -- Dean

      posted in Support
      dean-houstonD
      dean-houston
    • RE: Otterscript: Usage of Success exit code or EXEC operation - clarifications

      Hi @scusson_9923 ,

      Exec (or Execute-Process) runs an operating system process, so that's where the return code comes in.

      If you're doing something like a PSCall, then you can create output parameters/variables in the script, and then test those values.

      -- Dean

      posted in Support
      dean-houstonD
      dean-houston
    • RE: Adding an ad-hoc deployment process to an existing application

      Hi mwatt_5816,

      BuildMaster does support "release-less" builds, though you may need to enable it under the application's Settings > Configure Build & Release Features > Set Release Usage to optional. That will allow you to create a build that's not associated with a release.

      It's also possible to do "ad-hoc" builds (i.e. builds with no pipeline), but we don't make it easy to do in the UI because it's almost always a mistake (once you already have pipelines configured). So in your case, I think you should create a secondary pipeline for this purpose.

      -- Dean

      posted in Support
      dean-houstonD
      dean-houston
    • RE: NPM Failed to fetch package tags

      Hi @procha_8465 ,

      I'm afraid we'll need a bit more information here to help you. There are a lot of changes between ProGet 5.2 and ProGet 2024 and between older/newer versions of the npm client.

      If you can put together a reproduction case, ideally on a new instance of ProGet 2024, that'll help us determine what you're trying to do and how to help.

      -- Dean

      posted in Support
      dean-houstonD
      dean-houston
    • RE: Prometheus support?

      Hi @f-medini_8369,

      Here is our documentation on how to use Prometheus:
      https://docs.inedo.com/docs/installation/logging/installation-prometheus

      -- Dean

      posted in Support
      dean-houstonD
      dean-houston
    • RE: Using ProGet with TeamCity

      Hi @simon-marriott_1201,

      If you haven't seen it already, I'd check out How Files and Packages Work in ProGet for Artifactory Users.

      Long story short is, you should consider a more modern approach than the Maven-based file/folder that Artifactory uses. Many have found a lot of success with Universal Feeds & Packages.

      We don't maintain a TeamCity plugin, but it's really easy to create, publish, deploy packages using the pgutil command line (i.e. pgutil upack create); see HOWTO: Create Universal Packages

      Hope that helps!

      -- Dean

      posted in Support
      dean-houstonD
      dean-houston
    • RE: Connector to DevExpress Feed fails with Object reference not set to an instance of an object

      Hi @uwer_4638 ,

      The underlying issue is that you're making a "NuGet v2 API" request to your ProGet feed, which ProGet is then forwarding to connectors, and DevExpress does not support NuGet API V2.

      So, you'll need to track down whatever is making that request (perhaps you're using an old endpoint URL), or simply just disable the V2 API on your feed. This will cause an error on the client, and should show you pretty quickly what's making that outdated call.

      -- Dean

      posted in Support
      dean-houstonD
      dean-houston
    • RE: Unable to upload files to asset directories

      @layfield_8963 great news, that was a really strange error. The UI upload uses some kind of chunking and file appending, so it sounds like that was it.

      posted in Support
      dean-houstonD
      dean-houston
    • RE: Working Rafts_CreateOrUpdateRaftItem example for Otter

      Hi @scusson_9923,

      In this case, you'll likely want to select 5 as the type.

      For reference, here are the valid types:

          //
          // Summary:
          //     Specifies the type of a raft item.
          //
          // Remarks:
          //     All types except BinaryFile and TextFile are "regulated" and only allow well-known
          //     files; for example,
          public enum RaftItemType
          {
              //
              // Summary:
              //     A role configuration plan.
              RoleConfigurationScript = 1,
              //
              // Summary:
              //     [Uninclused] A Script with .otter syntax is prefered
              OrchestrationPlan = 2,
              //
              // Summary:
              //     [Uninclused] A Script with .otter syntax is prefered
              Module = 3,
              //
              // Summary:
              //     A script.
              Script = 4,
              //
              // Summary:
              //     An unclassified binary file.
              //
              // Remarks:
              //     BinaryFiles cannot be edited in a text editor, compared, etc; they are always
              //     treated as raw content
              BinaryFile = 5,
              //
              // Summary:
              //     A deployment plan.
              DeploymentScript = 6,
              //
              // Summary:
              //     An unclassified text file.
              //
              // Remarks:
              //     TextFiles can be edited in UI , may have lines replaced on deploy, and can be
              //     used as templates
              TextFile = 7,
              //
              // Summary:
              //     A pipeline.
              Pipeline = 8,
              //
              // Summary:
              //     [Uninclused] Feature is deprecated
              ReleaseTemplate = 9,
              //
              // Summary:
              //     A job template.
              JobTemplate = 10,
              //
              // Summary:
              //     Files used with build tools like Dockerfile.
              BuildFile = 11
          }
      

      I'm not sure if TextFile (7) will work; in Otter it was intended to be used as a text template, which means lines in it are replacement. You may need to play around and see what works.

      -- Dean

      posted in Support
      dean-houstonD
      dean-houston
    • RE: Working Rafts_CreateOrUpdateRaftItem example for Otter

      Hi @scusson_9923 ,

      What is the file you are uploading? What happens when you upload through the UI?

      Can you share the PowerShell snippet you're using?

      What are you specifying for RaftItemType_Code?

      -- Dean

      posted in Support
      dean-houstonD
      dean-houston
    • RE: Aggregating 2 Feeds in ProGet Free Edition

      @kc_2466 the "invalid feed type" will come up if you have a connector or feed that was created in a newer version of ProGet that wasn't available in an older version of ProGet... and you downgraded to the older version.

      It looks like it's a connector, based on the URL. Easiest way to fix is to just upgrade, delete, downgrade

      posted in Support
      dean-houstonD
      dean-houston
    • RE: Formatting issue on webpage for Cargo aggregate feed

      @kc_2466 thanks for the heads up, we'll target reviewing/fixing this for the following maintenance release (i.e. 2024.27 / Feb 21) via PG-2893

      posted in Support
      dean-houstonD
      dean-houston
    • RE: "Log scope Execution has already been completed" exception after OSCall

      Hi @jimbobmcgee ,

      Thanks for all the details; we plan to review/investigate this via OT-518 in an upcoming maintenance release, likely in the next few two-week cycles.

      -- Dean

      posted in Support
      dean-houstonD
      dean-houston
    • RE: Proget: SCA Event Notifier not working

      Hi @caterina ,

      Looking over the code, I can see that; we will also fix that in the next maintenance release. The notifier should not be dispatched when there are 0 issues.

      -- Dean

      posted in Support
      dean-houstonD
      dean-houston
    • RE: WebApp folder not present

      @cooperje_6513 that error means that the Windows service account user does not have access to the SQL Server database; you'll want to grant NT AUTHORITY\NETWORK SERVICE access

      You can do this with SQL Server Management Studio, or a scritp like this should work:

        CREATE LOGIN [NT AUTHORITY\NETWORK SERVICE] FROM WINDOWS WITH DEFAULT_DATABASE=[ProGet]
        CREATE USER [NT AUTHORITY\NETWORK SERVICE] FOR LOGIN [NT AUTHORITY\NETWORK SERVICE]
        ALTER USER [NT AUTHORITY\NETWORK SERVICE] WITH DEFAULT_SCHEMA=[dbo]
        ALTER ROLE [ProGetUser_Role] ADD MEMBER [NT AUTHORITY\NETWORK SERVICE]
      
      posted in Support
      dean-houstonD
      dean-houston
    • RE: Proget: SCA Event Notifier not working

      Hi @caterina ,

      I was able to find the issues; the correct value should be this:

      $ToJson(%(
          issues: @BuildIssues,
          buildNumber: $BuildNumber,
          releaseNumber: $BuildReleaseNumber,
          projectName: $BuildProjectName
      ))
      

      I've updated the documentation and also ProGet (via PG-2890), which will be in teh next maintenance release. But if you use the above template it should work.

      -- Dean

      posted in Support
      dean-houstonD
      dean-houston
    • 1 / 1