Support Q & A Home

Ask A Question

Anyone can ask or answer a question here, but our support engineers actively monitor your questions; we typically answer within a day or two.

Filter
Viewing Page 4 of 135 (20 questions out of 2683)
0
replies

Hello,

I have a valid license for proget from Inedo, and I use the docker image to spin up proget. At present, I manually add the license key and activate it after proget is running. Is there is a way inject the license and activate it as part of docker spin up itself (say as an environment variable)? This will help from an automation point of view.

-Krish

Product: ProGet
Version: 5.1.20

1
replies

We have a working version for proget basic edition serving as a docker repo among other things in one office location. I am trying to demonstrate the value of having it in other locations so we can move to the enterprise edition. I installed the latest free edition on VM in a second location and set it up to match what we have in the first.

This setup includes using IIS on install; https binding with a cert for the proget site.
I also ensured that the NetworkService has full control access to the feed storage location)

When I try to push an image up to the repository I see this:
The push refers to repository [docker.io/<server name>/<feed name>/library/redis]
1694aef55adf: Preparing
88d7964860e0: Preparing
fc3dfaf386f6: Preparing
3c187ef1bb50: Preparing
8037c9e9008e: Preparing
0ac4f5baf9b7: Waiting
63c478d60b8e: Waiting
bc06b22070cd: Waiting
denied: requested access to the resource is denied

The same failure happens using anonymous or for a user I have created on the proget site, given push and view access to; and have done a docker login on the client before trying the push.

Any suggestions on what to try next?

Product: ProGet
Version: 5.1.20

1
replies

We are trying to promote an application build to a particular environment using API, but we can't seem to get it working. We created full (unrestricted) access key for this.
Tried 2 type of calls:

  1. This one returns 404:

http://bmserver:port/api/releases/builds/deploy?buildNumber=3&releaseId=722&applicationId=123&toStage=Development&key=<APIKey>

  1. This one returns 500 server error:

http://bmserver:port/api/json/Builds_PromoteBuild?Application_Id=123&Release_Number=0.0.4&Build_Number=3&Comments_Text=SomeText&ForcePromotion_Indicator=N&PromoteTo_PipelineStage_Name=Development&SetFurthestStage_Indicator=N&key=<APIKey>

  1. Calling another method with the same API key works fine:

http://bmserver:port/api/json/Builds_GetExecution?Execution_Id=25537&key=<APIKey>

Tried switching between releaseId/releaseNumber didn't help much. Can you provide a complete sample call to promote/deploy a build?

Thanks

Product: BuildMaster
Version: 5.8.2

0
replies

Hello everybody,

I'm trying to set a maven repository in ProGet but having some problems with snapshots.

I can deploy and download artifacts normally, for final versions of jars it's working very well. But for snapshots, it's not.

I can effectively upload de snapshot jar to the feed, but the artifact gets uploaded with a timestamp, instead the snapshot name. I don't know if it is a ProGet feature, but in Nexus, for example, the snapshots get uploaded with the "snapshot" part in the name, and inside the folder, the actual timestamps of the artifact.

When I import the artifact in another project, if i put "-SNAPSHOT" in version, the jar doesn't get downloaded.

Am I missing something? Here are my configs in POM.xml:

Code
<distributionManagement>

	<repository>
		<id>server001</id>
		<name>ProGet Internal Repository</name>
		<layout>default</layout>
		<url>http://serverci/maven2/mvn/</url>
	</repository>

	<snapshotRepository>
		<id>server001</id>
		<name>ProGet Snapshots Repository</name>
		<layout>default</layout>
		<url>http://serverci/maven2/mvn/</url>
		<uniqueVersion>false</uniqueVersion>
	</snapshotRepository>

</distributionManagement>

<repositories>
	<repository>
		<id>server001</id>
		<name>ProGet Snapshots</name>
		<releases>
			<enabled>true</enabled>
			<updatePolicy>always</updatePolicy>
			<checksumPolicy>warn</checksumPolicy>
		</releases>
		<snapshots>
			<enabled>true</enabled>
			<updatePolicy>never</updatePolicy>
			<checksumPolicy>fail</checksumPolicy>
		</snapshots>
		<url>http://serverci/maven2/mvn/</url>
		<layout>default</layout>
	</repository>
</repositories>

Product: ProGet
Version: 5.1.15

1
replies

The Otter installation guide contains information that when creating a new server I will get a direct link to the file with the correct version. Unfortunately, I do not receive a link to Otter Agent. Where can I find the link to the agent installer?

Product: Otter
Version: 2.1.2

1
replies

This should have been answered by this Question (#3313)

I run a Maven Feed on a local proget installation (Version 5.1.19 (Build 7)) and try to deploy a package with maven version 3.5.2.
After the compilation of the package the upload starts and fails with this message.

Uploaded to releases: http://local-installation/maven2/maven-releases/test/package/artifact/0.0.1/artifact-0.0.1.jar (18 MB at 4.2 MB/s)
Uploading to releases: http://local-installation/maven2/maven-releases/test/package/artifact/0.0.1/artifact-0.0.1.pom
Progress (1): artifact-0.0.1.pom (1.7 kB)
Uploaded to releases: http://local-installation/maven2/maven-releases/test/package/artifact/0.0.1/artifact-0.0.1.pom (1.7 kB at 6.5 kB/s)
Downloading from releases: http://local-installation/maven2/maven-releases/test/package/artifact/maven-metadata.xml
[WARNING] Could not transfer metadata test.package:artifact/maven-metadata.xml from/to releases (http://local-installation/maven2/maven-releases/): Failed to transfer file: http://local-installation/maven2/maven-releases/test/package/artifact/maven-metadata.xml. Return code is: 500 , ReasonPhrase:Internal Server Error.

The feed then contains the jar and pom file and the Event Log contains two Package Created Events.
The Diagnostic Center shows the following error:

Category:
Web

Message:
An error occurred processing a GET request to http://local-/maven2/maven-releases/test/package/artifact/maven-metadata.xml: Value cannot be null. Parameter name: version

Details: 
System.ArgumentNullException: Value cannot be null.
Parameter name: version
at Inedo.ProGet.Feeds.Maven.MavenVersion.Parse (System.String version) [0x00008] in <1349015ffbf342a689ae698d25b4ab7e>:0 
at Inedo.ProGet.WebApplication.FeedEndpoints.Maven.MavenFeedHandler.ProcessRequestAsync (System.Web.HttpContext context, Inedo.ProGet.Feeds.Maven.MavenFeed feed, System.String relativeUrl) [0x00190] in <dab0761184df4cae8729746ef4194b56>:0 
at Inedo.ProGet.WebApplication.FeedEndpoints.FeedEndpointHandler+FeedRequestHandler.ProcessRequestAsync (System.Web.HttpContext context) [0x000a4] in <dab0761184df4cae8729746ef4194b56>:0

Is this really fixed?

Product: ProGet
Version: 5.1.19

2
replies

Is there way to expand an array for logging? I've tried the following in my Plans, which results in a log entry of "(list)" or generates an error.

set @arr = @("o", "t", "t");

Log-Information @arr;
Log-Information $(@arr);

# Try/Catch
try
{
    Log-Information $Eval(@arr);
}
catch
{
}

which results in

(list)

(list)

Cannot convert property "Text" value "@(o, t, t)" to String type.

Product: BuildMaster
Version: 6.0.9

2
replies

I have created a rubygems feed and the feed list reports the endpoint
https://REDACTED/nuget/private-ruby
however, when I click on the feed, the endpoint is reported as https://REDACTED/rubygems/private-ruby/

If I try to push to the latter (rubygems) URL, it says API endpoint not available.

My account at the proget server has admin privilege

Trying the former (nuget) URL, using my proget username and password I get this

gem push pkg/mypackage-0.1.0.gem --host https://REDACTED/nuget/private-ruby -V
Enter your https://REDACTED/nuget/private-ruby credentials.
Don't have an account yet? Create one at https://REDACTED/nuget/private-ruby/sign_up
   Email:   REDACTED
Password:

GET https://REDACTED/nuget/private-ruby/api/v1/api_key
404 OData method is not implemented.
OData method is not implemented.

If I try using the email address associated with my account, I get this

gem push pkg/mypackage-0.1.0.gem --host https://REDACTED/nuget/private-ruby -V
Enter your https://REDACTED/nuget/private-ruby credentials.
Don't have an account yet? Create one at https://REDACTED/nuget/private-ruby/sign_up
   Email:   REDACTED
Password:

GET https://REDACTED/nuget/private-ruby/api/v1/api_key
401 You are not authorized to view this feed because the user Anonymous does not have the Feeds_ViewFeed privilege.
You are not authorized to view this feed because the user Anonymous does not have the Feeds_ViewFeed privilege.

What am I missing? Documentation seems thin on the ground.

Thanks.

Product: ProGet
Version: 4.7.1

1
replies

So,

a few days ago everything was all good with TFS / Gitlab runners, even being able to push locally from my own machine to Proget.

I updated to the latest version and now everytime I try to upload a package I get a 403 (Forbidden).

I have seen earlier posts regarding scenarios where this can occur but my issue does not seem to match.

On the feed (any of them) I have NO API key. I specify a config file in which I have tried using a ClearTextPassword and Password for the credentials to use. I have tried multiple different credentials (in case there was something wrong). I have used my own account (I am an admin) and also a service account which has all the appropriate permissions given to it.

I have also tried to downgrade Proget, by uninstalling and then reinstalling the previous version and rolling back the database to the backup made prior to upgrade. I still have the same issue.

I have also tried different versions of Nuget.exe to push to Proget - from 3.4.3 (even earlier) to 4.9.2 (and many inbetween). Still no joy....

The error I get is as follows;-

WARNING: No API Key was provided and no API Key could be found for 'https://proget.gmgmt.dimensiondata.com/nuget/Aperture-R1.0'. To save an API Key for a
source use the 'setApiKey' command.
Pushing Aperture.Identity.Connector.Eventing.1.3.242.nupkg to 'https://proget.gmgmt.dimensiondata.com/nuget/Aperture-R1.0'...
PUT https://proget.gmgmt.dimensiondata.com/nuget/Aperture-R1.0/
Using credentials from config. UserName: xxxxxxxxx
The remote server indicated that the previous request was forbidden. Please provide credentials for: https://proget.gmgmt.dimensiondata.com/nuget/Apertur
e-R1.0

I have commented out the username but it is a valid domain account.

I have also created a builtin account and tried that too - but still all I get is

The remote server indicated that the previous request was forbidden

Anything else I could look at?

Product: BuildMaster
Version: 6.1.0

1
replies

Hello,

When I try to push to our internal ProGet Docker Registry, I first perform a Docker Login which is successful when disabling Integrated Authentication, but fails with it enabled. Without a successful login I cannot push to the registry. Is this supported in a later version of the product than we currently have?

Thanks,
Brian

Product: ProGet
Version: 5.1.8

1
replies

Hi

I think it would be cool if the proget would generate documentation for each container based on the manifest file ( in the details tab ).

eg: Author, Release Notes ect similar to what is done for nuget packages.

This would be similar to what is documented by docker hub based on the manifest file.

https://docs.docker.com/docker-hub/publish/publish/#how-the-manifest-information-is-displayed-in-the-ui

Is a features like this in the backlog?

Product: ProGet
Version: 5.1.19

2
replies

I'm running a free version of ProGet Version 5.1.19 (Build 7) on a Windows Server 2016 Standard machine. The ProGet instance has been installed in IIS and uses a local SQL Express database.

Most everything seems to function correctly, except I am unable to push packages to a universal feed. When I run upack.exe push, the package name and version are printed to stdout and then the command just blocks there seemingly doing nothing. There are no error or warning messages to be found in the proget web interface nor in the iis logs.

For example:

upack.exe --version
upack 2.2.3.9
Usage: upack «command»
<snip>

upack.exe push "C:/Path/To/TestApplication-0.1.0.upack" "http://proget.mycompany.local:8000/upack/Test-Packages" --user=api:[RedactedMySuperSecretApiKey]
Package: MyCompany/Sandbox/TestApplication
Version: 0.1.0-ci.33
^C   # Blocks here so I eventually cancel the command...

Any idea what might be wrong?

Product: ProGet
Version: 5.1.19

1
replies

Can i define a package version for 4 part?
For example: HN 1.2.3.4

Product: BuildMaster
Version: 6.1.0

5
replies

Hello

There a conversion problem from convert srting to INT with PsDsc or Ensure-DsC function.

        Ensure-DscResource
        (
            ConfigurationKey: setMaxSQLRAM,
            Name: SqlServerMemory,
            Module: SqlServerDsc,
            Properties: %(ServerName: $ServerName,DynamicAlloc: false,MinMemory: 256,InstanceName:$Instance,Ensure: Present)
        );
        

gives the following error message:

Importing ModuleName...
Échec de conversion de la valeur de la propriété « MinMemory », du type « STRING » au type « SINT32 »
 Ligne : 12, caractère : 2
 Mémoire tampon :
   MinMemory = "256";
};^
blablabla

I try several solutions unsuccessfully.

The PsDsc equivalent in Otter 1.7.2 is working fine

Any answer would be helpfull

Best regards

Philippe

Product: Otter
Version: 2.1.2

0
replies

Hello

I am looking to use the same account for some plan but its password is not the same depending on the environment it is applied.
It can use in the plan $CredentialProperty() and get a different password depending on the environnement it is apply.

Ressource Credential:

ADACCOUNT => login:ADAccount / pwd:simplepassaword assign to TEST environnement
ADACCOUNT => login:ADAccount / pwd:verycomplexpassword assign to PROD environnement

Unfortunately, there is a constraint violation

System.Data.SqlClient.SqlException (0x80131904): 2627`14`1`Credentials_CreateOrUpdateCredential`21`Violation de la contrainte UNIQUE KEY « UQ__Credentials ». blablabla

It is a bug ?
If not, it would be a very useful feature

Adding the ability to assign the credentail to multiple environment would be better:).
(One to TEST, DEV, INTEGRATION and the second one to (PROD and PRA) for example.

Best regards

Philippe

Product: BuildMaster
Version: 6.1.0

0
replies

Hello
when you create a map in application settings in bulk mode, and if there are syntax error, you have an error message.

To solve the problem, you have to remove the variable thru the Administation page, and create it correctly.

If the map is create as pipeline variable, there is no error until you start a step then you have an error.

Test case :

Bulk insert in Settings for an Application

{
  "TESTCASE": {
    "value": "%(Key1:Value1,Key2:`$ServerName,Key3`:OupsMistake)",
    "sensitive": true
  },

Results

System.FormatException: Invalid key name: Key3\` 
at Inedo.ExecutionEngine.Variables.TextProcessor.ReadMap() 
at Inedo.ExecutionEngine.Variables.TextProcessor.ReadVariableOrFunction(Boolean onlyScalar) 
at Inedo.ExecutionEngine.Variables.TextProcessor.ReadNext() 
at Inedo.ExecutionEngine.Variables.ProcessedString.Load(TextReader reader) 
at Inedo.BuildMaster.Variables.BuildMasterVariable.GetProcessedValue(String unprocessedValue, RuntimeValueType type) 
at Inedo.BuildMaster.Variables.BuildMasterVariable..ctor(Variables variable) 
at Inedo.BuildMaster.Variables.BuildMasterVariable.<GetVariablesAccessibleFromScope>d__16.MoveNext() 
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext() 
at Inedo.Web.Controls.Element.<GetControlsFromArgument>d__41.MoveNext() 
at Inedo.Web.Controls.Element..ctor(String elementType, Object[] content) 
at Inedo.BuildMaster.Web.WebApplication.Controls.VariableSummary..ctor(IGenericBuildMasterContext context) 
at Inedo.BuildMaster.Web.WebApplication.Pages.Applications.EditApplicationPage.CreateChildControls() 
at Inedo.BuildMaster.Web.WebApplication.Pages.BuildMasterSimplePage.<InitializeAsync>d__8.MoveNext() 
--- End of stack trace from previous location where exception was thrown --- 
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() 
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) 
at Inedo.Web.PageFree.SimplePageBase.<ProcessRequestAsync>d__46.MoveNext() 
--- End of stack trace from previous location where exception was thrown --- 
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() 
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) 
at System.Web.TaskAsyncHelper.EndTask(IAsyncResult ar) 
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() 
at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step) 
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

Product: BuildMaster  
Version: 6.1.0
1
replies

Hello, We are hosting ProGet OnPremise. In a browser, ProGet displays the feeds for NuGet and Powershell.

Internal Url:
http://usas26:8624/
http://usas26:8624/Feeds
http://usas26:8624/feeds/DrilQuipNuGet
http://usas26:8624/feeds/DrilQuipPowerShell

However, whenever I try to configure a package source in Visual Studio 2017 --> Tools --> Options --> Nuget Package Manager --> Package Sources

I get the following error in Visual Studio 2017:
Error occurred:
[ProGet] The V2 feed at 'http://usas26:8624/feeds/DrilQuipNuGet/Search()?$filter=IsLatestVersion&searchTerm=''&targetFramework=''&includePrerelease=false&$skip=0&$top=26&semVerLevel=2.0.0' returned an unexpected status code '404 Not Found'.

Please advise.

Thanks
Roy

Product: ProGet
Version: 5.1.17

3
replies

We were having some issues with our old SQL db so we had to reinstall ProGet from scratch (upgrading from 4.x to 5.1.18), manually connecting the db and changing all Disk path's for every feed.
Everything seems to work perfectly(pushing,pulling,listing e.t.c) expect for one thing.
On our old ProGet instance we were able to request a list of all available versions of a Maven package by sending a request in this format:

https://progetsever/maven2/Maven/packagepath/packagename/maven-metadata.xml

And if we needed to get the information about the specific version of the package we would send a request like this:

https://progetsever/maven2/Maven/packagepath/packagename/packageversion/maven-metadata.xml

After a fresh reinstall the second request type still seems to function properly but the first one returns and error 500 with the text
'Value cannot be null. Parameter name: version'

And it doesn't even matter if the package exists or not,it still returns 500 unless you specify a version(anything valid works)

We were able to upgrade our old instance of ProGet to 5.1.17 (not a reinstall) and everything works as intended there.This means that there was no API change and that there is probably some config we are missing.

Any help would be greatly appreciated!

Product: ProGet
Version: 5.1.18

7
replies

Hello

I upgraded to Otter 2.1.2, and I have now many of the servers in error during the Collect phase.

Unhandled exception: System.Data.SqlClient.SqlException (0x80131904): 
La transaction (ID de processus 77) a été bloquée sur les ressources verrou par un autre processus et a été choisie comme victime. 
Réexécutez la transaction.

If I force the Check Configuration it is working fine.

Regards

Product: Otter
Version: 2.1.2

1
replies

Hello,

Is there any clue about this error?
Cant connect to container because it fail after couple seconds or minutes:

Attempting to use shared configuration for ProGet.
Shared configuration file loaded from /usr/share/Inedo/SharedConfig/ProGet.config.
No encryption key is configured. Credentials will be stored in plain text.
Starting the messenger...
Messenger endpoint is tcp://localhost:1000
Reading standard license list...
Importing license list into database...
License import complete.
Initializing Scheduled Job Dispatcher...
Scheduled Job Dispatcher initialized.
Running Scheduled Job Dispatcher...
Checking for scheduled jobs...
Ensuring that all required scheduled jobs are configured...
Scheduled job configuration is correct.
Scheduled Job Dispatcher completed.
Initializing Service Heartbeat...
Service Heartbeat initialized.
Running Service Heartbeat...
Service Heartbeat completed.

Unhandled Exception:
System.NullReferenceException: Object reference not set to an instance of an object
at System.Web.Caching.Cache.ExpireItems (System.Object data) [0x00008] in <e2168dd7a1c34bdeb7d248883273aace>:0
at System.Threading.Timer+Scheduler.TimerCB (System.Object o) [0x00007] in <3833a6edf2074b959d3dab898627f0ac>:0
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () [0x00008] in <3833a6edf2074b959d3dab898627f0ac>:0
at System.Threading.ThreadPoolWorkQueue.Dispatch () [0x00074] in <3833a6edf2074b959d3dab898627f0ac>:0
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () [0x00000] in <3833a6edf2074b959d3dab898627f0ac>:0
[ERROR] FATAL UNHANDLED EXCEPTION: System.NullReferenceException: Object reference not set to an instance of an object
at System.Web.Caching.Cache.ExpireItems (System.Object data) [0x00008] in <e2168dd7a1c34bdeb7d248883273aace>:0
at System.Threading.Timer+Scheduler.TimerCB (System.Object o) [0x00007] in <3833a6edf2074b959d3dab898627f0ac>:0
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () [0x00008] in <3833a6edf2074b959d3dab898627f0ac>:0
at System.Threading.ThreadPoolWorkQueue.Dispatch () [0x00074] in <3833a6edf2074b959d3dab898627f0ac>:0

Product: ProGet
Version: 5.1.18

Ask A Question
Page: 1 2 4 6 7 8 9 135