[ https://ovirt-jira.atlassian.net/browse/OVIRT-2169?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-2169:
--------------------------------
Epic Link: (was: OVIRT-400)
> Show important thread information in STDCI build summary
> --------------------------------------------------------
>
> Key: OVIRT-2169
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2169
> Project: oVirt - virtualization made easy
> Issue Type: New Feature
> Components: Standard CI (Pipelines)
> Reporter: Daniel Belenky
> Assignee: infra
>
> When debugging builds on STDCI I want to have quick access to information about thread's execution environment such as: hostname it's being executed on, host's distro and arch, maybe even some basic specs of the host(?) so I won't have to search for this information in Console Output.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2170?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-2170:
--------------------------------
Epic Link: (was: OVIRT-400)
> Link from SCM to STDCI build summary
> ------------------------------------
>
> Key: OVIRT-2170
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2170
> Project: oVirt - virtualization made easy
> Issue Type: New Feature
> Components: Standard CI (Pipelines)
> Reporter: Daniel Belenky
> Assignee: infra
>
> As an STDCI user, I want to have quick access to STDCI build summary so I can see information about my build without having to access it through Jenkins.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2170?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-2170:
--------------------------------
Epic Link: (was: OVIRT-400)
> Link from SCM to STDCI build summary
> ------------------------------------
>
> Key: OVIRT-2170
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2170
> Project: oVirt - virtualization made easy
> Issue Type: New Feature
> Components: Standard CI (Pipelines)
> Reporter: Daniel Belenky
> Assignee: infra
>
> As an STDCI user, I want to have quick access to STDCI build summary so I can see information about my build without having to access it through Jenkins.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2171?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-2171:
--------------------------------
Epic Link: (was: OVIRT-400)
> Add support for HTML artifacts in STDCI build summary
> -----------------------------------------------------
>
> Key: OVIRT-2171
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2171
> Project: oVirt - virtualization made easy
> Issue Type: New Feature
> Components: Standard CI (Pipelines)
> Reporter: Daniel Belenky
> Assignee: infra
> Priority: Low
>
> As an STDCI user, I want to have quick view of HTML artifacts from STDCI build summary so I wont have to search for it under build-artifacts.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2171?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-2171:
--------------------------------
Epic Link: (was: OVIRT-400)
> Add support for HTML artifacts in STDCI build summary
> -----------------------------------------------------
>
> Key: OVIRT-2171
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2171
> Project: oVirt - virtualization made easy
> Issue Type: New Feature
> Components: Standard CI (Pipelines)
> Reporter: Daniel Belenky
> Assignee: infra
> Priority: Low
>
> As an STDCI user, I want to have quick view of HTML artifacts from STDCI build summary so I wont have to search for it under build-artifacts.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2172?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-2172:
--------------------------------
Epic Link: (was: OVIRT-400)
> STDCI build summary to write message when no threads were found
> ---------------------------------------------------------------
>
> Key: OVIRT-2172
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2172
> Project: oVirt - virtualization made easy
> Issue Type: New Feature
> Components: Standard CI (Pipelines)
> Reporter: Daniel Belenky
> Assignee: infra
>
> As an STDCI user I want to see a dedicated message at STDCI build summary that warns me that no threads were executed for my build to prevent cases where I think something runs while it doesn't (currently it shows blank page - users can think it's a bug in the summary.)
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2172?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-2172:
--------------------------------
Epic Link: (was: OVIRT-400)
> STDCI build summary to write message when no threads were found
> ---------------------------------------------------------------
>
> Key: OVIRT-2172
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2172
> Project: oVirt - virtualization made easy
> Issue Type: New Feature
> Components: Standard CI (Pipelines)
> Reporter: Daniel Belenky
> Assignee: infra
>
> As an STDCI user I want to see a dedicated message at STDCI build summary that warns me that no threads were executed for my build to prevent cases where I think something runs while it doesn't (currently it shows blank page - users can think it's a bug in the summary.)
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2173?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-2173:
--------------------------------
Epic Link: (was: OVIRT-400)
> STDCI build summary to include details about the STDCI event
> ------------------------------------------------------------
>
> Key: OVIRT-2173
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2173
> Project: oVirt - virtualization made easy
> Issue Type: New Feature
> Components: Standard CI (Pipelines)
> Reporter: Daniel Belenky
> Assignee: infra
>
> As an STDCI user I want to have quick view of the event details such as who is the change owner, what branch it was pushed to, and etc so I won't have to extract this information from the SCM.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2173?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-2173:
--------------------------------
Epic Link: (was: OVIRT-400)
> STDCI build summary to include details about the STDCI event
> ------------------------------------------------------------
>
> Key: OVIRT-2173
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2173
> Project: oVirt - virtualization made easy
> Issue Type: New Feature
> Components: Standard CI (Pipelines)
> Reporter: Daniel Belenky
> Assignee: infra
>
> As an STDCI user I want to have quick view of the event details such as who is the change owner, what branch it was pushed to, and etc so I won't have to extract this information from the SCM.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2174?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-2174:
--------------------------------
Epic Link: (was: OVIRT-400)
> Show dedicated message to early infra failures on STDCI build summary
> ---------------------------------------------------------------------
>
> Key: OVIRT-2174
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2174
> Project: oVirt - virtualization made easy
> Issue Type: New Feature
> Reporter: Daniel Belenky
> Assignee: infra
>
> As an STDCI user I want to see a dedicated message on STDCI build summary in case STDCI failed before even running my code so I can quickly contact the infra team.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)