Is ‘lazy’ the correct term for timestamp-based skipping? [closed]
Closed 9 years ago.
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.
Caching build results
This is a “technology/concept identification” question.
Is there an industry standard term for a build which uses the production API, but is specifically for internal testing? [closed]
Closed 9 years ago.
Is there an industry standard term for a build which uses the production API, but is specifically for internal testing? [closed]
Closed 9 years ago.
Is there an industry standard term for a build which uses the production API, but is specifically for internal testing? [closed]
Closed 9 years ago.
Is there an industry standard term for a build which uses the production API, but is specifically for internal testing? [closed]
Closed 9 years ago.