[JIRA] [workflow-plugin] (JENKINS-28447) CpsScmFlowDefinition does not resolve variables
Title: Message Title Patrick Wolf updated an issue Jenkins / JENKINS-28447 CpsScmFlowDefinition does not resolve variables Change By: Patrick Wolf Labels: followup Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28447) CpsScmFlowDefinition does not resolve variables
Title: Message Title Alexander Kanevskiy commented on JENKINS-28447 Re: CpsScmFlowDefinition does not resolve variables bump. without being able to use variables in pipeline from scm is practically making pipeline type of job useless, as can't be integrated e.g. with Github pull requests processing. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28447) CpsScmFlowDefinition does not resolve variables
Title: Message Title Jesse Glick commented on JENKINS-28447 Re: CpsScmFlowDefinition does not resolve variables SCM implementations seem to call Run.getEnvironment(TaskListener) so it is possible an implementation of JENKINS-30910 would automatically fix this, but certainly deserves its own integration tests. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28447) CpsScmFlowDefinition does not resolve variables
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-28447 CpsScmFlowDefinition does not resolve variables Bumping this to critical - integration with things like the Gerrit trigger plugin with scripts from SCM will be problematic without this. Change By: Andrew Bayer Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28447) CpsScmFlowDefinition does not resolve variables
Title: Message Title Nick Irvine commented on JENKINS-28447 Re: CpsScmFlowDefinition does not resolve variables Jesse Glick: I'm just saying, since this bug is several months old, it would appease me at least if the docs were updated to say something like "(Not available in Workflow Step; see JENKINS-28447)". Seems like a reasonable stop-gap solution, coupled with your suggestion above. In fact, I'm willing to contribute a patch if you think that's worthwhile. And provided it's as simple a fix as I imagine – I'm not familiar with the codebase whatsoever. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28447) CpsScmFlowDefinition does not resolve variables
Title: Message Title
Nick Irvine edited a comment on JENKINS-28447
Re: CpsScmFlowDefinition does not resolve variables
This is affecting me as well. The Help documentation for the field advertises it as a feature:{quote}$ \ {ENV_VARIABLE}It is also possible to use environment variables. In this case the variables are evaluated and the result is used as described above.E.g. $ \ {TREEISH}, refs/tags/$ \ {TAGNAME},...{quote}So one of these is a bug.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28447) CpsScmFlowDefinition does not resolve variables
Title: Message Title Jesse Glick commented on JENKINS-28447 Re: CpsScmFlowDefinition does not resolve variables Of course the inline help was written for the plugin when only freestyle projects existed. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28447) CpsScmFlowDefinition does not resolve variables
Title: Message Title
Nick Irvine commented on JENKINS-28447
Re: CpsScmFlowDefinition does not resolve variables
This is affecting me as well. The Help documentation for the field advertises it as a feature:
$
Unknown macro: {ENV_VARIABLE}
It is also possible to use environment variables. In this case the variables are evaluated and the result is used as described above. E.g. $
Unknown macro: {TREEISH}
, refs/tags/$
Unknown macro: {TAGNAME}
,...
So one of these is a bug.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28447) CpsScmFlowDefinition does not resolve variables
Title: Message Title Jesse Glick commented on JENKINS-28447 Re: CpsScmFlowDefinition does not resolve variables Well this would apply to any SCM plugin that has any field which gets variables substituted, I expect. Have not investigated in detail. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28447) CpsScmFlowDefinition does not resolve variables
Title: Message Title Jesse Glick commented on JENKINS-28447 Re: CpsScmFlowDefinition does not resolve variables Mitya Kononchuk not if flow.groovy runs inside the same node it was given. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28447) CpsScmFlowDefinition does not resolve variables
Title: Message Title
Mitya Kononchuk edited a comment on JENKINS-28447
Re: CpsScmFlowDefinition does not resolve variables
Theworkaround@JesseGlickproposeshasonedisadvantage:youhavetoallocateanextranodeforthebuild,whileusing {{ CpsScmFlowDefinition }} youdon't.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28447) CpsScmFlowDefinition does not resolve variables
Title: Message Title Mitya Kononchuk commented on JENKINS-28447 Re: CpsScmFlowDefinition does not resolve variables The workaround @Jesse Glick proposes has one disadvantage: you have to allocate an extra node for the build, while using CpsScmFlowDefinition you don't. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28447) CpsScmFlowDefinition does not resolve variables
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-28447 CpsScmFlowDefinition does not resolve variables Change By: Jesse Glick Summary: Workflowplugin CpsScmFlowDefinition doesnotresolvevariables inSCMplugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28447) CpsScmFlowDefinition does not resolve variables
Title: Message Title
Jesse Glick commented on JENKINS-28447
Re: CpsScmFlowDefinition does not resolve variables
Not quite sure I understand how to reproduce here, but bear in mind that CpsScmFlowDefinition is merely a convenience. For more control you can use CpsFlowDefinition (inline scipt) and just specify something like
node {
checkout(…) // anything supported by the SCM
load 'flow.groovy' // run everything else
}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28447) CpsScmFlowDefinition does not resolve variables
Title: Message Title Nicholas Newland edited a comment on JENKINS-28447 Re: CpsScmFlowDefinition does not resolve variables That'swhatIdid.IsimplyusedtheCpsFlowDefinition.Maybemyexpectationswherewrong,butthisiswhatIwasexpectingtobeabletodo.Freestyleproject:1.Definenewjob2.CheckThisbuildisparameterized3.CreatestringparameterwithnameBuildBranchanddefaultvaluemaster4.UnderSourcecodemanagementselectGit5.inBranchestobuildenter*/$BuildBranch6.whenthebuildrunswiththedefaultvalueitchecksoutthemasterbranchofmygitrepoandrunsthebuild7.Ifadeveloperrunsthebuildandentersfeature/awesomefortheBuildBranchparameter,thefeature/awesomebranchischeckedoutfromgitandthebuildruns.WhenIusetheCpsScmFlowDefinition,IcandoalloftheaboveandselectGitastheSCMandfillin*/$BuildBranchintheBranchestobuildtextbox,butgitalwayscomplainsthatthereisnobranchnamed*/$BuildBranch.Itdoesn'tseemtoberesolvingthebuildparameter. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28447) CpsScmFlowDefinition does not resolve variables
Title: Message Title Nicholas Newland edited a comment on JENKINS-28447 Re: CpsScmFlowDefinition does not resolve variables That'swhatIdid.IsimplyusedtheCpsFlowDefinition.Maybemyexpectationswherewrong,butthisiswhatIwasexpectingtobeabletodo.Freestyleproject:1.Definenewjob2.CheckThisbuildisparameterized3.CreatestringparameterwithnameBuildBranchanddefaultvaluemaster4.UnderSourcecodemanagementselectGit5.inBranchestobuildenter*/$BuildBranch6.whenthebuildrunswiththedefaultvalueitchecksoutthemasterbranchofmygitrepoandrunsthebuild7.Ifadeveloperrunsthebuildandentersfeature/awesomefortheBuildBranchparameter,thefeature/awesomebranchischeckedoutfromgitandthebuildruns.WhenIusetheCpsScmFlowDefinition,IcandoalloftheaboveandselectGitastheSCMandfillin*/$BuildBranchintheBranchestobuildtextbox,butgitalwayscomplainsthatthereisnobranchnamed*/$BuildBranch.Itdoesn'tseemtoberesolvingthebuildparameter. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28447) CpsScmFlowDefinition does not resolve variables
Title: Message Title
Nicholas Newland commented on JENKINS-28447
Re: CpsScmFlowDefinition does not resolve variables
That's what I did. I simply used the CpsFlowDefinition. Maybe my expectations where wrong, but this is what I was expecting to be able to do.
Freestyle project: 1. Define new job 2. Check This build is parameterized 3. Create string parameter with name BuildBranch and default value master 4. Under Source code management select Git 5. in Branches to build enter */$ {BuildBranch} 6. when the build runs with the default value it checks out the master branch of my git repo and runs the build 7. If a developer runs the build and enters feature/awesome for the BuildBranch parameter, the feature/awesome branch is checked out from git and the build runs. When I use the CpsScmFlowDefinition, I can do all of the above and select Git as the SCM and fill in */${BuildBranch}
in the Branches to build text box, but git always complains that there is no branch named */$ {BuildBranch}
. It doesn't seem to be resolving the build parameter.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28447) CpsScmFlowDefinition does not resolve variables
Title: Message Title
Nicholas Newland edited a comment on JENKINS-28447
Re: CpsScmFlowDefinition does not resolve variables
That'swhatIdid.IsimplyusedtheCpsFlowDefinition.Maybemyexpectationswherewrong,butthisiswhatIwasexpectingtobeabletodo.Freestyleproject:1.Definenewjob2.CheckThisbuildisparameterized3.CreatestringparameterwithnameBuildBranchanddefaultvaluemaster4.UnderSourcecodemanagementselectGit5.inBranchestobuildenter*/$BuildBranch6.whenthebuildrunswiththedefaultvalueitchecksoutthemasterbranchofmygitrepoandrunsthebuild7.Ifadeveloperrunsthebuildandentersfeature/awesomefortheBuildBranchparameter,thefeature/awesomebranchischeckedoutfromgitandthebuildruns.WhenIusetheCpsScmFlowDefinition,IcandoalloftheaboveandselectGitastheSCMandfillin*/$ { BuildBranch } intheBranchestobuildtextbox,butgitalwayscomplainsthatthereisnobranchnamed*/$ { BuildBranch } .Itdoesn'tseemtoberesolvingthebuildparameter.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28447) CpsScmFlowDefinition does not resolve variables
Title: Message Title
Nicholas Newland edited a comment on JENKINS-28447
Re: CpsScmFlowDefinition does not resolve variables
That'swhatIdid.IsimplyusedtheCpsFlowDefinition.Maybemyexpectationswherewrong,butthisiswhatIwasexpectingtobeabletodo.Freestyleproject:1.Definenewjob2.CheckThisbuildisparameterized3.CreatestringparameterwithnameBuildBranchanddefaultvaluemaster4.UnderSourcecodemanagementselectGit5.inBranchestobuildenter*/$ { BuildBranch } 6.whenthebuildrunswiththedefaultvalueitchecksoutthemasterbranchofmygitrepoandrunsthebuild7.Ifadeveloperrunsthebuildandentersfeature/awesomefortheBuildBranchparameter,thefeature/awesomebranchischeckedoutfromgitandthebuildruns.WhenIusetheCpsScmFlowDefinition,IcandoalloftheaboveandselectGitastheSCMandfillin*/${BuildBranch}intheBranchestobuildtextbox,butgitalwayscomplainsthatthereisnobranchnamed*/${BuildBranch}.Itdoesn'tseemtoberesolvingthebuildparameter.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
