Source code “prints” at release
Is there a best practice for how to document the source code you’re releasing?
Pass extra information with Heroku webhook
We habe Heroku-Github integration for releasing our app. We also have a webhook in Heroku that sends some data when release happens. Is there any way to send an extra information by the webhook to the receiver?
I tried to utilize ‘commit_description’ for this purpose, but it is empty eben though my releasing commit contains a description. It is located here in the webhook request body:
Branching strategy for frequent releases [duplicate]
This question already has answers here: Stopping developers committing to the wrong branch on DVCS (4 answers) Closed 9 years ago. We have very frequent releases and we use Git for version control. When i am mentioning about frequency, please assume it to include bug-fixes and feature release too. All releases are eventually merged into […]
How do you identify bugfix commits on QA environment with Git repository?
I got used to the following approach on bugfixing phase of the project development. The developer should add SVN commit number as a comment to the JIRA issue when resolving it. Latest artifact from CI-server shows build number which include major version, branch name and commit number. This approach helps QA easily to identify whether the bugfix was included in the latest build or not. Even when same issue was reopened and fixed again.
How do you identify bugfix commits on QA environment with Git repository?
I got used to the following approach on bugfixing phase of the project development. The developer should add SVN commit number as a comment to the JIRA issue when resolving it. Latest artifact from CI-server shows build number which include major version, branch name and commit number. This approach helps QA easily to identify whether the bugfix was included in the latest build or not. Even when same issue was reopened and fixed again.
How do you identify bugfix commits on QA environment with Git repository?
I got used to the following approach on bugfixing phase of the project development. The developer should add SVN commit number as a comment to the JIRA issue when resolving it. Latest artifact from CI-server shows build number which include major version, branch name and commit number. This approach helps QA easily to identify whether the bugfix was included in the latest build or not. Even when same issue was reopened and fixed again.
How do you identify bugfix commits on QA environment with Git repository?
I got used to the following approach on bugfixing phase of the project development. The developer should add SVN commit number as a comment to the JIRA issue when resolving it. Latest artifact from CI-server shows build number which include major version, branch name and commit number. This approach helps QA easily to identify whether the bugfix was included in the latest build or not. Even when same issue was reopened and fixed again.
How do I compile my software for all platforms from Ubuntu Linux 64 bit?
I write a lot of open source software that I make available on my website. How do I get my software compiled for all relevant platforms including:
How do I compile my software for all platforms from Ubuntu Linux 64 bit?
I write a lot of open source software that I make available on my website. How do I get my software compiled for all relevant platforms including:
How do I compile my software for all platforms from Ubuntu Linux 64 bit?
I write a lot of open source software that I make available on my website. How do I get my software compiled for all relevant platforms including: