share properties between builds in teamcity does not work
I have two builds - Build Dev and Deploy Dev. Build Dev is checking out the project which holds a pom.xml for maven build toolings. Therefore in this build I have access to properties like %maven.project.version%. The problem here is that Deploy Dev is actually in need of those properties as well but they are two different builds.
Now I read about Snapshot Dependencies where I can chain two builds into one build chain and they share a snapshot of the sources together. I even enabled the feature that they use the same build agent.
I thought that might be it but it was not. The build agent still is incompatible and there the Deploy Build is never triggered.
It is possible to access the properties of the dependency build (explained here) but only for specific properties it seems. I was not able to access like this %dep.build_dev.maven.project.name%
Can anybody explain how I can share these maven properties between these two build?
maven teamcity
asked Nov 14 '18 at 23:07
xetra11xetra11
7881340
|
show 1 more comment
I have two builds - Build Dev and Deploy Dev. Build Dev is checking out the project which holds a pom.xml for maven build toolings. Therefore in this build I have access to properties like %maven.project.version%. The problem here is that Deploy Dev is actually in need of those properties as well but they are two different builds.
Now I read about Snapshot Dependencies where I can chain two builds into one build chain and they share a snapshot of the sources together. I even enabled the feature that they use the same build agent.
I thought that might be it but it was not. The build agent still is incompatible and there the Deploy Build is never triggered.
It is possible to access the properties of the dependency build (explained here) but only for specific properties it seems. I was not able to access like this %dep.build_dev.maven.project.name%
Can anybody explain how I can share these maven properties between these two build?
maven teamcity
asked Nov 14 '18 at 23:07
xetra11xetra11
7881340
if you can't access%dep.build_dev.maven.project.name%means you did not define parameter with namemaven.project.namefor build configurationbuild_dev
– daggett
Nov 15 '18 at 13:09
it is defined by build step "Maven". All steps afterwards within the build have access to this property. I just want to make it accessable to the next build as well without defining another Maven build step for it because it would be redundant
– xetra11
Nov 15 '18 at 13:30
it should be defined as a parameter in build configuration, then it will be accessible in a dependent build configurations
– daggett
Nov 15 '18 at 14:40
Can you show me exactly what you mean? I know about defining parameters but these would be "hardcoded" but the value changes if the mavenpom.xmlis changing after a commit or something. So I actually have to maintain it manually
– xetra11
Nov 15 '18 at 16:32
not clear why you are referencingpom.xml... do you want to pass properties defined inpom.xml?
– daggett
Nov 15 '18 at 17:42
|
show 1 more comment
I have two builds - Build Dev and Deploy Dev. Build Dev is checking out the project which holds a pom.xml for maven build toolings. Therefore in this build I have access to properties like %maven.project.version%. The problem here is that Deploy Dev is actually in need of those properties as well but they are two different builds.
Now I read about Snapshot Dependencies where I can chain two builds into one build chain and they share a snapshot of the sources together. I even enabled the feature that they use the same build agent.
I thought that might be it but it was not. The build agent still is incompatible and there the Deploy Build is never triggered.
It is possible to access the properties of the dependency build (explained here) but only for specific properties it seems. I was not able to access like this %dep.build_dev.maven.project.name%
Can anybody explain how I can share these maven properties between these two build?
maven teamcity
asked Nov 14 '18 at 23:07
xetra11xetra11
7881340
I have two builds - Build Dev and Deploy Dev. Build Dev is checking out the project which holds a pom.xml for maven build toolings. Therefore in this build I have access to properties like %maven.project.version%. The problem here is that Deploy Dev is actually in need of those properties as well but they are two different builds.
Now I read about Snapshot Dependencies where I can chain two builds into one build chain and they share a snapshot of the sources together. I even enabled the feature that they use the same build agent.
I thought that might be it but it was not. The build agent still is incompatible and there the Deploy Build is never triggered.
It is possible to access the properties of the dependency build (explained here) but only for specific properties it seems. I was not able to access like this %dep.build_dev.maven.project.name%
Can anybody explain how I can share these maven properties between these two build?
maven teamcity
maven teamcity
asked Nov 14 '18 at 23:07
xetra11xetra11
7881340
asked Nov 14 '18 at 23:07
xetra11xetra11
7881340
edited Nov 14 '18 at 23:15
xetra11
asked Nov 14 '18 at 23:07
xetra11xetra11
7881340
asked Nov 14 '18 at 23:07
xetra11xetra11
7881340
asked Nov 14 '18 at 23:07
xetra11xetra11
7881340
7881340
if you can't access%dep.build_dev.maven.project.name%means you did not define parameter with namemaven.project.namefor build configurationbuild_dev
– daggett
Nov 15 '18 at 13:09
it is defined by build step "Maven". All steps afterwards within the build have access to this property. I just want to make it accessable to the next build as well without defining another Maven build step for it because it would be redundant
– xetra11
Nov 15 '18 at 13:30
it should be defined as a parameter in build configuration, then it will be accessible in a dependent build configurations
– daggett
Nov 15 '18 at 14:40
Can you show me exactly what you mean? I know about defining parameters but these would be "hardcoded" but the value changes if the mavenpom.xmlis changing after a commit or something. So I actually have to maintain it manually
– xetra11
Nov 15 '18 at 16:32
not clear why you are referencingpom.xml... do you want to pass properties defined inpom.xml?
– daggett
Nov 15 '18 at 17:42
|
show 1 more comment
if you can't access%dep.build_dev.maven.project.name%means you did not define parameter with namemaven.project.namefor build configurationbuild_dev
– daggett
Nov 15 '18 at 13:09
it is defined by build step "Maven". All steps afterwards within the build have access to this property. I just want to make it accessable to the next build as well without defining another Maven build step for it because it would be redundant
– xetra11
Nov 15 '18 at 13:30
it should be defined as a parameter in build configuration, then it will be accessible in a dependent build configurations
– daggett
Nov 15 '18 at 14:40
Can you show me exactly what you mean? I know about defining parameters but these would be "hardcoded" but the value changes if the mavenpom.xmlis changing after a commit or something. So I actually have to maintain it manually
– xetra11
Nov 15 '18 at 16:32
not clear why you are referencingpom.xml... do you want to pass properties defined inpom.xml?
– daggett
Nov 15 '18 at 17:42
if you can't access
%dep.build_dev.maven.project.name% means you did not define parameter with name maven.project.name for build configuration build_dev– daggett
Nov 15 '18 at 13:09
if you can't access
%dep.build_dev.maven.project.name% means you did not define parameter with name maven.project.name for build configuration build_dev– daggett
Nov 15 '18 at 13:09
it is defined by build step "Maven". All steps afterwards within the build have access to this property. I just want to make it accessable to the next build as well without defining another Maven build step for it because it would be redundant
– xetra11
Nov 15 '18 at 13:30
it is defined by build step "Maven". All steps afterwards within the build have access to this property. I just want to make it accessable to the next build as well without defining another Maven build step for it because it would be redundant
– xetra11
Nov 15 '18 at 13:30
it should be defined as a parameter in build configuration, then it will be accessible in a dependent build configurations
– daggett
Nov 15 '18 at 14:40
it should be defined as a parameter in build configuration, then it will be accessible in a dependent build configurations
– daggett
Nov 15 '18 at 14:40
Can you show me exactly what you mean? I know about defining parameters but these would be "hardcoded" but the value changes if the maven
pom.xml is changing after a commit or something. So I actually have to maintain it manually– xetra11
Nov 15 '18 at 16:32
Can you show me exactly what you mean? I know about defining parameters but these would be "hardcoded" but the value changes if the maven
pom.xml is changing after a commit or something. So I actually have to maintain it manually– xetra11
Nov 15 '18 at 16:32
not clear why you are referencing
pom.xml... do you want to pass properties defined in pom.xml ?– daggett
Nov 15 '18 at 17:42
not clear why you are referencing
pom.xml... do you want to pass properties defined in pom.xml ?– daggett
Nov 15 '18 at 17:42
|
show 1 more comment
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53310085%2fshare-properties-between-builds-in-teamcity-does-not-work%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53310085%2fshare-properties-between-builds-in-teamcity-does-not-work%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
if you can't access
%dep.build_dev.maven.project.name%means you did not define parameter with namemaven.project.namefor build configurationbuild_dev– daggett
Nov 15 '18 at 13:09
it is defined by build step "Maven". All steps afterwards within the build have access to this property. I just want to make it accessable to the next build as well without defining another Maven build step for it because it would be redundant
– xetra11
Nov 15 '18 at 13:30
it should be defined as a parameter in build configuration, then it will be accessible in a dependent build configurations
– daggett
Nov 15 '18 at 14:40
Can you show me exactly what you mean? I know about defining parameters but these would be "hardcoded" but the value changes if the maven
pom.xmlis changing after a commit or something. So I actually have to maintain it manually– xetra11
Nov 15 '18 at 16:32
not clear why you are referencing
pom.xml... do you want to pass properties defined inpom.xml?– daggett
Nov 15 '18 at 17:42