Search results

Unit tests been integrated?

Status: Open.

#27 In sysgain/iotcicd;

· anjanidevio opened on Sep 24, 2018

Azure DevOps able to only find changes within a folder/subfolder?

Status: Open.

#26 In sysgain/iotcicd;

· anjanidevio opened on Sep 24, 2018

Enable github issues tab

Status: Open.

#25 In sysgain/iotcicd;

· anjanidevio opened on Sep 24, 2018

If the solution is available via www.azureiotsolutions.com, the Governing SI takes care of informing Microsoft about the new release

Status: Open.

#24 In sysgain/iotcicd;

· anjanidevio opened on Sep 24, 2018

A new GitHub Release page is created, describing the content of the new release.

Status: Open.

#23 In sysgain/iotcicd;

· anjanidevio opened on Sep 24, 2018

A new Tag is created on the last commit of the master branch, following Semantic Versioning 2.0

Status: Open.

#22 In sysgain/iotcicd;

· anjanidevio opened on Sep 24, 2018

Release Process

Status: Open.

#21 In sysgain/iotcicd;

· anjanidevio opened on Sep 24, 2018

Pull Requests are not created from the last commit of the master branch, but from the commit corresponding to the version affected by the critical bug.

Status: Open.

#20 In sysgain/iotcicd;

· anjanidevio opened on Sep 24, 2018

Hotfixes start with a bug report All bug reports undergo a triage process where the Creator SI and Governing SI decide whether the bug is critical or not.

Status: Open.

#19 In sysgain/iotcicd;

· anjanidevio opened on Sep 24, 2018

Staging environment

Status: Open.

#18 In sysgain/iotcicd;

· anjanidevio opened on Sep 24, 2018

Testing environment

Status: Open.

#17 In sysgain/iotcicd;

· anjanidevio opened on Sep 24, 2018

A Pull Request is considered ready to merge only when its code meets the Production Quality definition, which includes testing a deployment and scanning for security issues.

Status: Open.

#16 In sysgain/iotcicd;

· anjanidevio opened on Sep 24, 2018