-
Updated
Nov 29, 2018 - PowerShell
artifacts
Here are 70 public repositories matching this topic...
In each of the top level commands - az boards, az pipelines, az repos, az artifacts and az devops, we include the line indicating that this command is a part of azure-devops extension. In addition to this, we need to include the link out to the documentation - https://docs.microsoft.com/en-us/azure/devops/cli/?view=azure-devops as well.
Build stage could be used to execute builds with different Java versions in parallel and then release it using selected Java.
-
Updated
Apr 11, 2020 - TSQL
-
Updated
May 12, 2020 - Go
-
Updated
Jul 7, 2017 - Python
-
Updated
Dec 19, 2018 - HTML
Tag publish tasks
I'm not sure what does it influence exactly, need to read docs:
https://github.com/sbt/sbt/blob/bcd21ba9b64cf89023bc9626bcb5129c155ba90b/main/src/main/scala/sbt/Defaults.scala#L2231
-
Updated
Oct 13, 2018 - Gradle
-
Updated
May 18, 2020 - YARA
-
Updated
Dec 21, 2019 - Shell
-
Updated
May 13, 2020 - Python
-
Updated
Apr 22, 2020 - Kotlin
-
Updated
Oct 3, 2019 - Kotlin
-
Updated
Apr 22, 2020 - Kotlin
-
Updated
Apr 30, 2019 - Python
-
Updated
Oct 30, 2018 - PowerShell
-
Updated
Mar 27, 2020
-
Updated
Jan 15, 2020 - Kotlin
Improve this page
Add a description, image, and links to the artifacts topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the artifacts topic, visit your repo's landing page and select "manage topics."
Right now the tutorial uses WAY more detail than would actually be used in a project. To avoid pushing users into a pitfall of over-specifying their project I need to be more upfront in the docs that the highly specific nature is for demonstration, but not a representation of how an actual project would be specified.