Bug #16959

Gather usability data about our current CI

Added by intrigeri 2019-08-09 16:56:42 . Updated 2020-04-22 14:40:44 .

Status:
In Progress
Priority:
Normal
Assignee:
intrigeri
Category:
Continuous Integration
Target version:
Tails_4.7
Start date:
Due date:
% Done:

0%

Feature Branch:
Type of work:
Communicate
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

This will have a better overview of how our current setup feels to its users, whenever it’ll be time to put this question seriously on the table (and then we can decide what’s the best thing to do, between e.g. switching to GitLab CI, switching to Jenkins pipelines, or merely removing some UX stumbling blocks without changing the big picture of our setup).

Subtasks

Related issues

Related to Tails - Feature #16059: Improve UX for scheduling builds for newly pushed branches on the CI Resolved 2018-10-16
Related to Tails - Bug #16027: Jenkins web interface has broken artifact links Resolved 2018-10-03
Related to Tails - Bug #16150: After hooks should be able to mark the scenario as failed in Jenkins Cucumber report Confirmed 2018-11-23
Related to Tails - Feature #16063: Support restarting tests in CI without rebuilding Resolved 2018-10-17
Related to Tails - Bug #11295: Test jobs sometimes get scheduled on a busy isotester while there are available ones Resolved 2016-03-31
Related to Tails - Bug #10601: isotesterN:s are sometimes put offline and never back online Needs Validation 2015-11-23
Related to Tails - Bug #17070: Finding the Jenkins jobs corresponding to a given branch is bothersome Confirmed
Related to Tails - Bug #17071: Jenkins does not readily expose the full CI pipeline progress & outcome Confirmed
Related to Tails - Bug #14875: Build reproducibility Jenkins tests: confusing UX and implementation Resolved 2017-10-22
Related to Tails - Feature #9760: Prioritize builds from release branches over others Confirmed 2015-07-19
Related to Tails - Bug #10288: Fix newly identified issues to make our test suite more robust and faster In Progress 2015-02-26
Related to Tails - Bug #16960: Make our CI feedback loop shorter In Progress
Related to Tails - Feature #15864: Make onboarding of new developers easier In Progress 2018-08-30
Blocks Tails - Feature #13284: Core work: Sysadmin (Adapt our infrastructure) Confirmed 2017-06-30

History

#1 Updated by intrigeri 2019-08-09 16:56:56

  • blocks Feature #13284: Core work: Sysadmin (Adapt our infrastructure) added

#2 Updated by intrigeri 2019-09-01 13:25:47

  • related to Feature #16059: Improve UX for scheduling builds for newly pushed branches on the CI added

#3 Updated by intrigeri 2019-09-01 13:26:32

  • related to Bug #16027: Jenkins web interface has broken artifact links added

#4 Updated by intrigeri 2019-09-01 13:27:26

  • related to Bug #16150: After hooks should be able to mark the scenario as failed in Jenkins Cucumber report added

#5 Updated by intrigeri 2019-09-01 13:28:28

  • related to Feature #16063: Support restarting tests in CI without rebuilding added

#6 Updated by intrigeri 2019-09-01 13:29:26

  • related to Bug #11295: Test jobs sometimes get scheduled on a busy isotester while there are available ones added

#7 Updated by intrigeri 2019-09-01 13:29:37

  • related to Bug #10601: isotesterN:s are sometimes put offline and never back online added

#8 Updated by intrigeri 2019-09-01 16:53:14

I’ve sent a call for feedback to the FT. My plan is to gather this feedback continuously when I notice it, whether or not it’s explicitly meant to be feedback for this ticket :)
I’ve set a deadline in May 2020 because I don’t see us diving into the “future of our CI” topic before we’ve migrated our code & issues to GitLab.

#9 Updated by intrigeri 2019-09-19 06:13:00

  • Status changed from Confirmed to In Progress
  • Target version set to Tails_4.1

I’ll ping FT & other devs who use Jenkins ~3 months after I’ve sent my initial call for feedback.

#10 Updated by intrigeri 2019-09-19 06:21:40

  • related to Bug #17070: Finding the Jenkins jobs corresponding to a given branch is bothersome added

#11 Updated by intrigeri 2019-09-19 06:33:24

  • related to Bug #17071: Jenkins does not readily expose the full CI pipeline progress & outcome added

#12 Updated by intrigeri 2019-09-20 10:30:33

  • related to Bug #14875: Build reproducibility Jenkins tests: confusing UX and implementation added

#13 Updated by intrigeri 2019-10-24 08:29:47

  • Target version changed from Tails_4.1 to Tails_4.2

#14 Updated by intrigeri 2019-12-16 12:52:38

  • related to Feature #9760: Prioritize builds from release branches over others added

#15 Updated by intrigeri 2019-12-21 15:16:17

  • related to Bug #10288: Fix newly identified issues to make our test suite more robust and faster added

#16 Updated by intrigeri 2019-12-28 09:02:35

  • related to Bug #16960: Make our CI feedback loop shorter added

#17 Updated by intrigeri 2019-12-28 09:11:48

  • Target version changed from Tails_4.2 to Tails_4.6

intrigeri wrote:
> I’ve sent a call for feedback to the FT. My plan is to gather this feedback continuously when I notice it, whether or not it’s explicitly meant to be feedback for this ticket :)
> I’ve set a deadline in May 2020 because I don’t see us diving into the “future of our CI” topic before we’ve migrated our code & issues to GitLab.
> I’ll ping FT & other devs who use Jenkins ~3 months after I’ve sent my initial call for feedback.

Pinged.

#18 Updated by intrigeri 2020-04-22 14:40:44

  • Target version changed from Tails_4.6 to Tails_4.7

#19 Updated by intrigeri 2020-05-08 07:53:48

  • related to Feature #15864: Make onboarding of new developers easier added