Posts made by jjones

Groups_XML is basically 2 nodes. groups and group.

<groups>
      <group>Administrators</group>
</groups>

Jon,

Did using the Out-Null help to limit the logging?

After looking into this issue further we have determined that sequentially ordering the parameters will resolve the issue.

Thanks,
Jason

Was the -verbose attribute specified in the script? I don't know of any way to suppress this off-hand, perhaps you can try -Verbose:$false or pipe to Out-Null

Taras,

try encrypting without the brackets {}

so encrypt this first:

api:FHGDSFREG-3FrF

your command should exclude {} as well

npm config set _auth=YXBpOntGSEdEU0ZSRUctM0ZyRn0g__newtoken

Hi Andrey,

Generally a feature is included in the Free Edition unless otherwise stated. For LDAP authentication you will need to install the InedoCore extension.

Here are more docs to review
https://inedo.com/support/documentation/various/ldap/ldap-active-directory

Let me know if further help is needed.

Thanks,
Jason

Please refer to this topic for help uninstalling the product.

Hi Garry,
have you looked into adding retention rules to the feed?

Hi Taras,

This has been tested in ProGet, in order to publish with Token authentication:

• You need to create a user in proget
• give that user the Add Package role
• create a new token that impersonates that user.
• encrypt the token to base64

Hi Fabrizio,
It appears that the ProGet source code is fine but the issue is with NuGet symbol & source server.

run:
npm config get registry

if you don't see the correct registry

try:
npm config set regist <urltoregistry>

Hi Paraig, I will have an update for you tomorrow.

Here is what we have documented for publishing npm packages to proget from a command line..

To configure npm to use the npm ProGet feed, run the following command:

npm config set [@scope]:registry http://progetaddress/npm/npm
If your feed does not allow anonymous access, you will also need to run this command:

npm config set always-auth true [--scope:@scope]
To log in to ProGet using npm, run the adduser command and specify a ProGet user account and password:

npm adduser --registry=http://progetaddress/npm/npm [--scope:@scope]

These commands will need to run before trying the publish command. Once this configuration is set up, it shouldn't be required again. But that would need to be confirmed on your end.

This seems to be a known limitation for automating a publish command. Some recommend using npm-cli-login in order to provide login credentials.

Thanks,
Jason

HI Taras,

Please try to either:

Run this in a cmd.exe window with administrator permissions.
Use npm login--registry https://MYNPM_REGISTRY_IN_PGOGET/ before npm publish.
Hope this helps!

Thanks,
Jason

Hi Francois,

The quickest way to get something like this implemented is by going through the feature request process this process really drives our roadmap. as for ETA, I wouldn't want to predict that, but we do release new versions on a frequent basis.

Thanks,
Jason

Hi Darren,

We currently on provide filtering on package name and versions for Docker. However, we are very open to new feature requests.

Thanks!

Hi Francois,

You can grant/revoke access to a feed for specific users here is documentation about that. However, the package version page and the statistics page are both under the View Feed role. Which means you'd have to block the user from seeing both pages.

Thanks,
Jason

Yes. the latest version will work.

Hi Svet,

It looks like your first issue is due to SQL Server 2005 which we no longer support. Your 2nd issue about installing on a Postgres server is going to be something we have created support ticket for will be targeting for the next maintenance release.

Thanks,
Jason

Hi Christopher,

I am not able to recreate this issue locally, can you confirm that your license key is valid, current, and activated. It looks like you were issued a new license key last month 4/16/2019 for ProGet Basic. An invalid or expired key will force the retention policy to execute in dry-run mode so I want to rule that out first.

Thanks,
Jason

Hi Paraig,

This is actually something we are writing documentation for right now. We plan to have it published by the end of the week and I will let you know where to find it.

Thanks,
Jason

That is great news! feel free to reach out if you have any other issues.

You can send me a screen shot, but you want to find the upack folder that contains the file named installedPackages.json this is the file that InedoHub uses to determine what is installed.

Are you still able to launch your instance of ProGet in a web browser?

also, the path C:\ProgramData\upack is in a hidden folder so you may have to type this path directly change your settings to show hidden files.

You can try using the traditional installer. Here is the guide

Assuming you have only ProGet installed, delete the C:\ProgramData\upack directory. This is the location of the directory the Hub installer uses to detect the presence of any of the installed products. If you have any of the other Hub software installed, you'll have to edit the installedPackages.json file in that directory and remove the entry for ProGet.

If you are unable to see ProGet.Service.Exe in C:\Program Files\ProGet\Service\
and you are not seeing a C:\Program Files\ProGet\WebApp\ folder, it would appear to me that it is no longer installed on that machine. Do you see the ProGet web site in your IIS manager?

Looks like it can't find C:\Program Files\ProGet\WebApp\Web.config
is there anything in the C:\Program Files\ProGet\WebApp\ folder?

Also, were you able to complete the other steps I mentioned previously?

Hi Goncalo,

What is the error you are getting?

Also, to un-install please reverse the steps in the manual install process and run these steps.

• Ensure the service is stopped: INEDOPROGETSVC
• Uninstall services by executing "ProGet.Service.exe" from an admin command line in the ProGet\Service directory, and followign the prompts
• Delete the Service and WebApp directories, (and anything else under ProGet you don't want to keep)
• Delete the HKLM\Software\Inedo\ProGet registry key
• Delete the HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\ProGet registry key
• If using IIS, delete the ProGet web app and app pools
• If you really want to delete everything , you can also drop the ProGet SQL database

The error message you are getting (There must be exactly one package.) is essentially saying the file that you are trying to push doesn't exist. And since I can see that the file is created in the previous pack command, My thought is that file creation is not fully complete or the file is still in use by the pack command. I am thinking it might be useful to add a Start-Sleep -s 5 command between the pack and push commands.

Hi Philippe,

I see that the $PiplineStageName is not available at the Release level. So this will only work as a Build variable.

Does this help?

Thanks!
Jason

Hi Vijay,

please refer to this documentation to better understand file masks in our tools.

hope this helps!

Thanks,
Jason

Hi Philippe,

When you add the Release variable does it appear to have the correct connection string on the page? I'm going to try and replicate this error on my end but want to make sure the rendering is working first.

Thanks,
Jason

Philippe,

You will need to use variable value renderers to accomplish this.

then value render text will be your string i.e. Server=$ApplicationName$PipelineStageName.SQL.$DomaineName\$ApplicationName$PipelineStageName;Integrated Security=true;

then you can reference that variable in your application by adding it as a release variable or build variable.

Hi Philippe,

You should be able to use a System Variable (administration/variables) to store the connection string that you want to use over multiple applications.

Also,
Yes. you can define a connection string as per your example.

Does this help?

Thanks,
Jason

Hi Sergey,

It's not built in but you can integrate it with custom directories. Please see
https://inedo.com/support/questions/3991 for a related discussion.