Project

General

Profile

Actions
Copy link

Bug #18494

closed

Nightly packages timestamp are not updated at each build

Added by Félix DALLIDET over 3 years ago. Updated about 2 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Packaging
Target version:
6.1.19
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Priority:
18
Name check:
To do
Fix check:
To do
Regression:

Description

It seems like the nightly build does not force the timestamp on the packages. This lead to non-automatic dependencies when upgrading a nightly:
  • Install a 6.1-nightly
  • upgrade it some days after, the packages have same timestamp so the dependencies of rudder-server-root are not upgraded.
Actions
Copy link
 #1

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.7 to 6.1.8
Actions
Copy link
 #2

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.8 to 6.1.9
  • Priority changed from 22 to 21
Actions
Copy link
 #3

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 6.1.9 to 6.1.10
Actions
Copy link
 #4

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 6.1.10 to 6.1.11
  • Priority changed from 21 to 20
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 6.1.11 to 6.1.12
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 6.1.12 to 6.1.13
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.13 to 6.1.14
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.14 to 6.1.15
  • Priority changed from 20 to 19
Actions
Copy link
 #9

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.15 to 6.1.16
Actions
Copy link
 #10

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.16 to 6.1.17
Actions
Copy link
 #11

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.17 to 6.1.18
  • Priority changed from 19 to 18
Actions
Copy link
 #12

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.18 to 6.1.19
Actions
Copy link
 #13

Updated by Alexis Mousset about 2 years ago

versions are updated at each build, reasons for this behavor include:

  • build failures which prevent update
  • relaxed version dependencies on nightly
Actions
Copy link
 #14

Updated by Alexis Mousset about 2 years ago

  • Status changed from New to Rejected
Actions
Copy link

Also available in: Atom PDF