mits in the working copy
> which have not been evaluated as part of the just completed continuous
> integration job), or you accept that you'll lose commits with "git push
> --force".
>
> Mark Waite
>
> --
> *From:* Juliano Picuss
preferred to have a person increment the version
> number at key milestones, but the team preferred the automation of version
> number increment in the build because the version number is used widely in
> the system to version Microsoft.NET assemblies.
>
> Mark Waite
>
> -
ent the version
> number at key milestones, but the team preferred the automation of version
> number increment in the build because the version number is used widely in
> the system to version Microsoft.NET assemblies.
>
> Mark Waite
>
> --
I've got a similar issue:
- I have 2 jenkins jobs for two distinct git branches: master and
release (1 job_master to 1 branch master / 1 job_release for branch release)
- job_master has a post built configuration to push to the release
branch.
- job_release has a post built configuratio
