Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • A arch-boxes
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 8
    • Issues 8
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Releases
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Arch Linux
  • arch-boxes
  • Issues
  • #71

Closed
Open
Created Jan 03, 2020 by Sven-Hendrik Haase@svenstaroContributor

[Bug] is_latest logic is wrong due to year change

Created by: shibumi

Describe the bug The is_latest logic in the controller script is wrong. Right now we are just comparing the month, due to the year change we started at 1 again ( the last version is from december -> 12). Therefore the check turns to True and we never start the build process for January.

To Reproduce Steps to reproduce the behavior:

  1. Run controller script

Expected behavior controller script should start new build even when a year change occurs.

Screenshots

Host Software (please complete the following information):

Additional context

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking