Skip to content

Releases: tcplugins/tcDebRepository

tcDebRepository TeamCity plugin v1.0.2

12 Dec 09:07
Compare
Choose a tag to compare

Bug fix release to resolve a UI issue found in TeamCity 2017.2, issue #16

TeamCity 2017.2 has been released and runs on Tomcat version 8.5
Previously Teamcity 2017.1 was Tomcat 7.

As part of the Tomcat change, the search path for JSP tag libraries has been reduced. This means that the custom tag bundled with tcDebRepository 1.0.1 is no longer being found.

As a result, the UI was broken when editing repository information where a string was escaped when displayed in the UI. The JSP code has been updated to use the tag library bundled with TeamCity, and the unused code removed.

tcDebRepository TeamCity plugin v1.0.1

09 Feb 11:19
Compare
Choose a tag to compare

This release provides better support for packages with an architecture of "All", including being able to define which architectures an "All" package is indexed into. It also resolves a few other bugs and adds some UI enhancements.

  • List packages of architecture "all" in other architecture Package files. Fixes issue #7
  • UX improvements to address issue #9
  • Use File.seperator to make the tests compatible with Windows. Fixes issue #5
  • Remove references to ConfigActionFactory as it's not used. Fixes issue #6

Download tcPlugins

tcDebRepository TeamCity plugin v1.0

06 Dec 14:21
Compare
Choose a tag to compare

tcDebRepository provides a Debian Package server from within TeamCity.

Build your Debian packages in TeamCity, and tcDebRepository can serve them to your Debian (or Debian based) linux servers.

Then updating your server with the latest TeamCity build is as simple as:

      sudo apt-get update 
      sudo apt-get install package_name 

Installing the plugin will add:

  • A browsable repository of packages and package meta-data.
  • A repository in the structure consumed by APT including a URL from which APT can download the packages.
  • A processor which watches for build events and parses the list of artifacts, filters them and then publishes the package meta-data into matched repositories.
  • A processor which watches for cleanup events and removes the package meta-data from repositories.
  • A UI for creating, editing and removing repositories.
  • A UI for creating, editing and removing the Artifact Filters that the processor uses for indexing packages.