Hello,

You can use Environments_ResequenceEnvironment in the native API to reposition your Build environment in the list.

Assuming the ID displayed when you hover over the Build environment is 4 and you have an API key abc123 with the native API enabled, accessing this page in your browser will move the Build environment to the first position:

/api/json/Environments_ResequenceEnvironment?Environment_Id=4&New_Environment_Sequence=1&API_Key=abc123

Hello Jeff,

There is currently a bug in the FeedCleanup task for Docker feeds. PG-1030 has been fixed for the next version of ProGet, but until then, disable the FeedCleanup task for any Docker feeds in /administration/scheduled-tasks.

Hello Peter,

Thanks for the bug report! I was able to reproduce the problem, and it will be fixed in the next minor version of ProGet (4.7.12).

PG-1029

Hello Jason,

It looks like the npm registry started returning empty responses about a week ago. It looks like they're having caching problems.

ProGet 4.7.8 and newer support the npm search API, so indexing isn't needed to search the npm registry, or you can wait for npm to fix the problem on their end.

UPDATE: this has been updated in PG-1632

__

Hello Jonas,

Deleting images isn't in the native API because the stored procedures only delete metadata, but if your CI server has access to the database ProGet is using, you can run the stored procedure to delete the metadata for the image and ProGet will automatically delete the files whenever the FeedCleanup scheduled task next runs.

Assuming your docker image is named proget:443/foo/bar/baz, the foo feed has ID 42, and the digest for the version of the image you want to delete is f52fbd32b2b3b86ff88ef6c490628285f482af15ddcb29541f94bcf526a3f6c7, this SQL statement will work:

EXEC [DockerImages_DeleteImage]
    /* Feed_Id */ 42,
    /* Repository_Name*/ 'bar/baz',
    /* Image_Digest */ 'f52fbd32b2b3b86ff88ef6c490628285f482af15ddcb29541f94bcf526a3f6c7'
GO

If you don't know the digest, https://proget/api/json/DockerImages_GetImages?API_Key=[your API key from /administration/api-keys]&Feed_Id=42&Repository_Name=bar/baz returns metadata including Image_Digest and Published_Date, and https://proget/api/json/DockerImages_GetTags?API_Key=[your API key from /administration/api-keys]&Feed_Id=42&Repository_Name=bar/baz returns metadata including Image_Digest and Tag_Name.

According to the mvn deploy documentation, you'd need this in the POM file for the project:

  <distributionManagement>
    <repository>
      <id>myproget</id>
      <name>My ProGet Feed</name>
      <url>http://progethostname/maven2/feedname</url>
    </repository>
  </distributionManagement>

If the feed requires authentication, you also need this in settings.xml (the <id> values have to match):

    <server>
      <id>myproget</id>
      <username>username</username>
      <password>password</password>
    </server>

If you want your snapshot versions deployed to a separate feed, you can add a <snapshotRepository> to <distributionManagement> in the same format as <repository> above.

After that, the command is just mvn deploy to upload the package to ProGet.

It's been quite a while since I last used Maven, but I think the POM file would look something like this:

<project>
...
  <repositories>
    <repository>
      <id>mysite</id>
      <name>My Site - ProGet</name>
      <url>http://www.mysite.com/maven2/mf</url>
    </repository>
  </repositories>
...
  <dependencies>
    <dependency>
      <groupId>apackages</groupId>
      <artifactId>new-packages-jar</artifactId>
      <version>0.0.1</version>
    </dependency>
  </dependencies>
...
</project>

Your template can look like this:

template MakePair<$First, $Second, out @Pair>
{
    set @Pair = @($First, $Second);
}

And the plan that uses the template can look like this:

set @Fruits = @();

call MakePair
{
    First: Apple,
    Second: Orange,
    Pair => @Fruits
}

Hello Glenn,

For now, the “Release Package Triggers” only work with legacy source control providers. It’s certainly on our roadmap to update this module so that there’s a more natural integration point.

But until then, the best solution is to use a changegroup hook in Mercurial, and the Release/Package API. To do this,

1. Create a key at http://buildmaster/administration/api-keys with at least the Grant access to Release & Deployment API box checked.
2. Create a file with the following contents somewhere in the PYTHONPATH of your Mercurial server:

   import urllib
   import httplib
   import json
   
   api_key = 'YOUR_API_KEY'
   app_id = 1
   
   def create_package(ui, repo, **kwargs):
       h = httplib.HTTPConnection('buildmaster')
       h.request('GET', '/api/releases?' + urllib.urlencode({'key': api_key, 'applicationId': app_id, 'status': 'active'}))
       releases = json.loads(h.getresponse().read())
       h.request('POST', '/api/releases/packages/create?' + urllib.urlencode({'key': api_key, 'releaseId': releases[0]['id']}))
       resp = h.getresponse()
       if resp.status != 200:
           print resp.status, resp.reason
           print resp.read()
       else:
           resp.read()
       h.close()
   

3. Add this to .hg/hgrc on the Mercurial server:

   [hook]
   changegroup.buildmaster = python:path.to.create_package
   

Hello Yannick,

Telerik's repository isn't listing the publishing date of the packages, and ProGet is getting confused and assuming that means the packages were never published. This will be fixed in the next version of ProGet (4.7.11) [PG-1019]

Hello Jorg,

Thanks for the bug report. I've fixed the error for the next version of ProGet (4.7.11) [PG-1018]

Hello Oliver,

Starting with the next version of ProGet (4.7.11) the connectors overview page will require permissions to access: PG-1017

Hello Jim,

Is there anything in Event Viewer → System from Service Control Manager, or anything from ProGet in the Application section of the event viewer?

Hello Tony,

It sounds like the ProGet service can't access the Amazon extension for some reason. In %ProgramData%\ProGet\ExtensionsTemp\Service there should be three folders by default: Amazon, Azure, and VorSecurity. Is Amazon missing?

Hello Jason,

I would suggest making two plans, one with the first two pseudo-code steps and a second with just the third step. Then, use pipeline stages to run the build stage once on the BuildMaster server and the deploy stage on both web servers after the artifact is built.

You can set the build stage to automatically advance to the deploy stage when it succeeds.

Hello Marcus,

In IIS Manager, select your ProGet site and open the configuration editor.

In the section named system.webServer/security/requestFiltering, expand requestLimits. Set maxAllowedContentLength to at least the maximum size of uploads you expect in bytes.

In the section named system.web/httpRuntime, set maxRequestLength to at least the maximum size of uploads you expect in kilobytes.

Hello Yannick,

Telerik is using a custom NPM repository that has two incompatibilities with ProGet:

1. It uses the email address to authenticate. I've added support for this for the next version of ProGet (4.7.10) PG-1012.
2. It doesn't support the NPM search API. This means the feed page will show a big red box with The remote server returned an error: (404) Not Found. in it, but you should still be able to download packages if you know their name (once ProGet 4.7.10 is released).

Here's a PowerShell (File → Open Windows PowerShell) script that will move all the files to the root of the drop path:

Get-ChildItem -Recurse -File | ForEach-Object {Move-Item $_.FullName .}

Make sure you run that inside your drop path, because it could do damage somewhere else.

If you set --targetDirectory on the pack command to an empty or nonexistent directory, the .upack file will be the only file in there, and you can use myDirectory\*.upack to select the upack file for the push command.

Hello Aris,

If you click on the release number (the leftmost column) the user that created the release is displayed in the Details section.