You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the package for one of the flavors could not be uploaded during deploy stage, it would be considered a build failure yet the packages that were uploaded during the same build would not be deleted either. This creates desynchronization between revision numbers of packages across different flavors, which in turn leads to the confusion when you're trying to match packages between each other or with the build they were created in.
The text was updated successfully, but these errors were encountered:
You can build and deploy packages only for specific distros: ex el6 and trusty for example what will increase revision only for those 2 distros. Another example: re-build only el7 build and expect revision number to increase only for that repo.
Revision number is Incremental for each distro, it's not shared between all repos, so you won't jump from revision 1 to revision 5 because of synchronization reasons.
Both things are good and handled correctly in build machinery which assumes each distro repository as independent piece.
If the package for one of the flavors could not be uploaded during deploy stage, it would be considered a build failure yet the packages that were uploaded during the same build would not be deleted either. This creates desynchronization between revision numbers of packages across different flavors, which in turn leads to the confusion when you're trying to match packages between each other or with the build they were created in.
The text was updated successfully, but these errors were encountered: