|
All content with label admin+artifact.
Related Labels:
change
, pending
, versions
, run
, ivy
, compare
, account
, cleanup
, statistics
, results
, external
, overview
, build
, permission
, authentication
, pin
, vcs
, graph
, script
,
number
, project
, take
, login
, server
, history
, implicit
, professional
, teamcity
, pattern
, link
, template
, https
, source
, ant
, label
, custom
, status
, administration
, responsibility
, destination
, utf
, notifier
, enterprise
, mssql
, ui
, url
, dependent
, search
, agent
, comment
, 2005
, key
, migrate
, result
, committer
, tag
, path
, database
, compatible
, diff
, trigger
, filter
, map
, starteam
, plugin
, mysql
, quiet
, guest
, jabber
, e-mail
, property
, draft
, manage
, assign
, license
, queue
, test
, configure
, launch
, runner
, backup
, drafts
, oracle
, add
, download
, reference
, setting
, chart
, downnload
, type
, install
, properties
, administrator
, visible
, requirement
, role
, configuration
, settings
, permalink
, edit
, rule
, dependencies
, extract
, upgrade
, dependency
, user
, report
more »
( - admin
, - artifact
)
Patterns For Accessing Build Artifacts
(TeamCity 4.x Documentation)
page covers: Obtaining Artifacts Use the following patterns to download artifacts: To download artifacts of the latest builds (last finished, successful or pinned) use the following paths: /repository/download/BUILDTYPEID/.lastFinished/ARTIFACTPATH /repository/download/BUILDTYPEID/.lastSuccessful/ARTIFACTPATH ...
|
Patterns For Accessing Build Artifacts
(TeamCity 3.x Documentation)
Patterns For Accessing Build Artifacts This section covers: Obtaining Artifacts #ObtainingArtifacts Obtaining Artifacts from an Archive #ObtainingArtifactsFromArchive Obtaining Artifacts from a BuildScript #ObtainingArtifactsFromBuildScript Links to the Artifacts Containing the TeamCity Build Number #LinksToArtifactsWithBuildNumber Obtaining Artifacts Use ...
|
|
|