Project

General

Profile

Bug #16959

Gather usability data about our current CI

Added by intrigeri about 1 month ago. Updated 4 days ago.

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

0%

Feature Branch:
Type of work:
Communicate
Blueprint:
Starter:
Affected tool:

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).


Related issues

Related to Tails - Feature #16059: Improve UX for scheduling builds for newly pushed branches on the CI Confirmed 10/16/2018
Related to Tails - Bug #16027: Jenkins web interface has broken artifact links Resolved 10/03/2018
Related to Tails - Bug #16150: After hooks should be able to mark the scenario as failed in Jenkins Cucumber report Confirmed 11/23/2018
Related to Tails - Feature #16063: Support restarting tests in CI without rebuilding Resolved 10/17/2018
Related to Tails - Bug #11295: Test jobs sometimes get scheduled on a busy isotester while there are available ones Needs Validation 03/31/2016
Related to Tails - Bug #10601: isotesterN:s are sometimes put offline and never back online Needs Validation 11/23/2015
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 10/22/2017
Blocks Tails - Feature #13284: Core work: Sysadmin (Adapt our infrastructure) Confirmed 06/30/2017

History

#1 Updated by intrigeri about 1 month ago

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

#2 Updated by intrigeri 21 days ago

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

#3 Updated by intrigeri 21 days ago

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

#4 Updated by intrigeri 21 days ago

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

#5 Updated by intrigeri 21 days ago

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

#6 Updated by intrigeri 21 days ago

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

#7 Updated by intrigeri 21 days ago

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

#8 Updated by intrigeri 21 days ago

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 4 days ago

  • 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 4 days ago

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

#11 Updated by intrigeri 4 days ago

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

#12 Updated by intrigeri 2 days ago

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

Also available in: Atom PDF