I really don't see any problem with option two and it's actually what I do in real life. My team seems to like it very much either.
Good to know! So.. if your build file changes but nothing of your code/business logic you still bump up the version, tag it, etc.?
Well, I guess that could happen :)
But as others have stated, I don't see this as a problem, since we should know asap whether those changes affected our deploy anyway.
That said, we don't deploy every commit. So we could simply choose not to deploy a change that only touched infrastructural stuff.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I really don't see any problem with option two and it's actually what I do in real life. My team seems to like it very much either.
Good to know! So.. if your build file changes but nothing of your code/business logic you still bump up the version, tag it, etc.?
Well, I guess that could happen :)
But as others have stated, I don't see this as a problem, since we should know asap whether those changes affected our deploy anyway.
That said, we don't deploy every commit. So we could simply choose not to deploy a change that only touched infrastructural stuff.