, 16 ноября 2016 г., 23:44:19 UTC+3 пользователь Michael Giroux
> написал:
>>
>> The following log message would be a lot more informative if it provided
>> the job name so we could go adjust the configuration.
>>
>> Git Parameter Version 0.7.0
>
The following log message would be a lot more informative if it provided
the job name so we could go adjust the configuration.
Git Parameter Version 0.7.0
Jenkins 2.19.2 LTS
JDK 1.8
Nov 16, 2016 8:36:01 PM
net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition
getBranch
INFO:
Thanks Mark. Any chance you could quantify "a while"? Perhaps in terms of
weeks? Would like to report to my employer when we can hope for it to be
included.
On Wednesday, March 2, 2016 at 8:58:43 AM UTC-7, Mark Waite wrote:
>
>
>
> On Tuesday, March 1, 2016 at 7:48:02 PM
Created an issue to describe the need for this feature:
https://issues.jenkins-ci.org/browse/JENKINS-33202
On Tuesday, March 1, 2016 at 7:48:02 PM UTC-7, Michael Giroux wrote:
>
> What can I do to get some traction on this pull request (
> https://github.com/jenkinsci/git-plugin
verage.
Michael
On Tuesday, February 23, 2016 at 4:36:37 PM UTC-7, Michael Giroux wrote:
>
> I have submitted a pull request to extend the functionality of LocalBranch
> to make it easier to configure a job that can be used to build any branch
> (via notifyCommit) and also perform m
I have submitted a pull request to extend the functionality of LocalBranch
to make it easier to configure a job that can be used to build any branch
(via notifyCommit) and also perform maven builds on any branch using a
combination of Git Parameter plugin, and LocalBranch extension
hudson.plugins.git.GitSCM buildEnvVars
INFO: LocalBranch configured as: null
Feb 22, 2016 2:56:31 PM hudson.plugins.git.GitSCM buildEnvVars
INFO: Setting GIT_LOCAL_BRANCH: master
On Monday, February 22, 2016 at 2:43:17 PM UTC-7, Michael Giroux wrote:
>
> I'm looking to add a new environment va
I'm looking to add a new environment variable to expose the LocalBranch
name as GIT_LOCAL_BRANCH. I'm looking at the code in GitSCM.checkout and
am not able to figure out why GIT_BRANCH is being set twice.
GIT_BRANCH is set first when checkout sets environment:
EnvVars environment =
Issue:
When performing a maven release, it is necessary that the local branch name
is the same as the remote branch sans "origin/" to allow successful pushes
of the updated pom files.
The maven release plugin does a push as "git push origin
{local_branch}:{local_branch}".
As a result of this,
