Settings generator: use single Mac agent for deployment #17
Conversation
ilya-g
force-pushed
the
ig/publishing-agent
branch
from
098c56c to
96a46c3
Compare
|
I've decided to rework the approach a bit: instead of doing it unconditionally, introduce an option for that, because there can be situations where cross-compilation on macs may be insufficient. |
| /** | ||
| * Build all artifacts for publishing and deploy them from a single mac agent. | ||
| */ | ||
| var singleAgentMacDeployment: Boolean = false |
There was a problem hiding this comment.
Perhaps, it'd be better to place it in teamcity DSL block because it affects generated teamcity build configurations?
On the other hand, libraryStagingRepoDescription was recently moved (see the commit 25e3650) from teamcity to publishing/sonatype block, because while it also affects TC configurations, it is semantically closer to sonatype publishing.
WDYT?
There was a problem hiding this comment.
I think "publishing" DSL is the appropriate place for the property. It affects publishing, even if only in TeamCity.
|
Is the ability to publish artifacts for all targets documented somewhere? |
|
Cross-compiling for Linux on Mac hosts existed for a long time, and cross-compiling for Windows was announced in one of recent releases: https://kotlinlang.org/docs/whatsnew16.html#compilation-of-windows-targets-on-any-host But in my experiment, the artifacts I've got on a Mac agent were slightly different, so I'd like to study it a bit more before enabling for production publishing. |
No description provided.