1. 08 Oct, 2021 1 commit
  2. 31 Aug, 2021 1 commit
  3. 29 Aug, 2021 1 commit
  4. 07 Aug, 2021 1 commit
  5. 03 Aug, 2021 1 commit
  6. 22 Feb, 2021 1 commit
  7. 26 May, 2020 2 commits
  8. 21 Sep, 2019 1 commit
  9. 21 Aug, 2019 1 commit
    • intrigeri's avatar
      Update Git remote URL (#10093). · 86f245cf
      intrigeri authored
      The Git hook that's supposed to trigger jobs when we push tells Jenkins that
      things have changed at gitolite3@, but before this commit, the Jenkins jobs
      tracked gitolite@, so Jenkins is like "well, whatever, none of my jobs care
      about the gitolite3@ remote, I'll go back to the beach".
      
      Let's teach the Jenkins jobs that they're now tracking gitolite3@,
      so they react as intended to Git pushes.
      86f245cf
  10. 10 May, 2017 1 commit
  11. 21 Nov, 2016 1 commit
  12. 03 Jun, 2016 1 commit
  13. 29 Feb, 2016 2 commits
  14. 28 Feb, 2016 3 commits
  15. 23 Jun, 2015 1 commit
    • bertagaz's avatar
      Reorganize the yaml hierarchy. · 26eb98f2
      bertagaz authored
      Once the automatic build_Tails_ISO jobs generation will be running,
      these jobs will be stored in the corresponding sub-directory, so we have
      to move the actual one in there before to prepare the switch and not
      ending with duplicated jobs configuration.
      26eb98f2
  16. 19 Jun, 2015 1 commit
  17. 18 Jun, 2015 1 commit
  18. 10 Jun, 2015 1 commit
  19. 26 Feb, 2015 1 commit
  20. 21 Jan, 2015 1 commit
  21. 20 Dec, 2014 1 commit
    • intrigeri's avatar
      Reintroduce a pollscm trigger, and set it @weekly. · b1bc8834
      intrigeri authored
      Apparently, without that trigger, the "build on Git push" feature doesn't
      work anymore. No need to trigger a daily build for this reason though.
      
      Revert "Drop the daily pollscm trigger for all jobs that had one."
      
      This reverts commit 2d3e1344.
      b1bc8834
  22. 19 Dec, 2014 1 commit
  23. 16 Dec, 2014 1 commit
    • intrigeri's avatar
      Drop the daily pollscm trigger for all jobs that had one. · 2d3e1344
      intrigeri authored
      We have Git post-update hooks for all of them. And for all ISO builds, we anyway
      have a "timed: @daily" trigger that ensures we build them daily, even if Git
      wasn't modified — e.g. because of APT changes that are not under our control.
      2d3e1344
  24. 08 Dec, 2014 2 commits
  25. 01 Oct, 2014 2 commits
  26. 30 Sep, 2014 2 commits
  27. 17 Sep, 2014 1 commit
  28. 10 Sep, 2013 1 commit
    • intrigeri's avatar
      Don't push tags to Git after building ISOs. · e03bc83f
      intrigeri authored
      That's not needed anymore: the built ISO filenames tell us what commit they were
      built from, as does the Jenkins web interface.
      
      That's annoying: the output of `git tag' is growing beyond control.
      
      Still, keep the push_Tag builder around, since things might be different for
      other, future kinds of builds.
      e03bc83f
  29. 08 Sep, 2013 1 commit
  30. 28 Jul, 2013 1 commit
  31. 20 Jun, 2013 2 commits
  32. 16 Apr, 2013 1 commit