Comments (5)
Sounds like a reasonable request, will think about it the next time I'm sober (approx. Tuesday).
Did you see the support for environment variables in template strings in the README?
Sent from my pocket calculator
On 17 Jul 2014, at 06:27, desdrury [email protected] wrote:
Hi,
Firstly, I think bump version is awesome. It solves a lot of problems I have had with versioning in the past. However, there is one capability I wish it had. That is to be able to define the value for the part on the command line, i.e.
$ bumpversion build=$BUILD_NUM
So in this case it would use the provided value rather than increment an existing value.
I ask for this as it would make my workflow much easier. Here's my workflow.
Once I have finished developing some code I use Bumpversion to increase the value of either the major, minor or patch. If there was a build number previously then it is removed.
Bumpversion does the git checkin.
Bamboo sees the newly checked in code. It runs a build job which checks the code out to a local workspace.
Bumpversion is called by Bamboo with the 'build=$BUILD_NUM' argument.
If the build succeeds then Bamboo does a Git checkin and deploys the built artefact to Nexus.
I hope this makes sense?Cheers.
Des
�
Reply to this email directly or view it on GitHub.
from bumpversion.
Hey,
I’ll be hoping that you only have a minor hangover before being sober again ;-)
I did see the support for environment variables in the template strings, and it brought me so close to what I was after it was almost perfect. The problem arose when doing a bump when the environment variable was not set, i.e. when I’m developing. The variable works perfectly on the Bamboo build side though.
Cheers.
Des
On 18 Jul 2014, at 5:05 am, Filip Noetzel [email protected] wrote:
Sounds like a reasonable request, will think about it the next time I'm sober (approx. Tuesday).
Did you see the support for environment variables in template strings in the README?
Sent from my pocket calculator
On 17 Jul 2014, at 06:27, desdrury [email protected] wrote:
Hi,
Firstly, I think bump version is awesome. It solves a lot of problems I have had with versioning in the past. However, there is one capability I wish it had. That is to be able to define the value for the part on the command line, i.e.
$ bumpversion build=$BUILD_NUM
So in this case it would use the provided value rather than increment an existing value.
I ask for this as it would make my workflow much easier. Here's my workflow.
Once I have finished developing some code I use Bumpversion to increase the value of either the major, minor or patch. If there was a build number previously then it is removed.
Bumpversion does the git checkin.
Bamboo sees the newly checked in code. It runs a build job which checks the code out to a local workspace.
Bumpversion is called by Bamboo with the 'build=$BUILD_NUM' argument.
If the build succeeds then Bamboo does a Git checkin and deploys the built artefact to Nexus.
I hope this makes sense?Cheers.
Des
�\
Reply to this email directly or view it on GitHub.
—
Reply to this email directly or view it on GitHub.
from bumpversion.
On second thought, this sounds reasonable (and was on my TODO list for some time, apparently).
I experimented with the current feature set as well with two config files (one for manual bumping, one for bamboo-bumping in your case), but that isn't as elegant.
Let's do this!
from bumpversion.
Awesome!! That's great news :-) Please let me know if there's anything I can do.
Sent from my iPhone
On 25 Jul 2014, at 1:38 am, Filip Noetzel [email protected] wrote:
On second thought, this sounds reasonable (and was on my TODO list for some time, apparently).
I experimented with the current feature set as well with two config files (one for manual bumping, one for bamboo-bumping in your case), but that isn't as elegant.
Let's do this!
—
Reply to this email directly or view it on GitHub.
from bumpversion.
Does anyone work on this? Resolving this issue would make it possible to maintain PEP 440 compatible version identifiers (see #77).
from bumpversion.
Related Issues (20)
- Multi-line `replace` doesn't work for lines starting with `#` HOT 2
- Missing allowed 'part' values in commandline help HOT 2
- All strings matching current version are bumping up in setup.py file. HOT 2
- Issue while using search and replace configurations. HOT 2
- Do not fail on the dirty state during the dry-run HOT 1
- How to keep the metadata part when bumping version?
- bump version number in filename
- Bumpversion --list returned non-zero exit status 1 HOT 1
- Improvement README.rst
- TypeError: 'NoneType' object is not iterable HOT 1
- Release version from working branch
- search-replace falls back to plain version lookup in some cases HOT 1
- help need: error while serialize following pattern (?P<major>\d+)\.(?P<minor>\d+)\.(?P<patch>\d+)\.(?P<build>\d+)
- No Pre-Release Tags if Major Version is 0 HOT 1
- bumpversion w/ added "commit" part adding additional parts to files
- Add ability to specify a value of a part of version only HOT 1
- Need better documentation on multiline support for `search` and `replace`
- Is it possible to allow {current_[part]} / {new_[part]} in search/replace?
- Dependencies versions in pyproject.toml altered casually
- Is it possible to make numbered beta versions like in npm?
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from bumpversion.