Project

Profile

Help

Issue #5581

closed

Cron job in travis may disrupt the release process

Added by ttereshc about 3 years ago. Updated 11 months ago.

Status:
CLOSED - DUPLICATE
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
CI/CD
Sprint:
Quarter:

Description

Ticket moved to GitHub: "pulp/pulpcore/1850":https://github.com/pulp/pulpcore/issues/1850


In case of bad timing, cron job can publish bindings earlier than the release job and in this case the release job will fail.

E.g. pulp_rpm job which publishes bindings to pypi failed saying that such version already exists https://travis-ci.org/pulp/pulp_rpm/builds/598783999.
An hour earlier a cron job published those bindings.

There were multiple issues during release process, so the version of new release stayed unchanged in the master for few hours. That's why cron job released the version of a beta release and not the .dev (nightly) one which is usually set on the master branch.

Maybe it's one more reason to do branching for our releases or some other adjustment for a release process to avoid this problem.

Actions #1

Updated by fao89 about 3 years ago

  • Triaged changed from No to Yes
Actions #2

Updated by dkliban@redhat.com about 2 years ago

  • Tags CI/CD added
Actions #3

Updated by pulpbot 11 months ago

  • Description updated (diff)
  • Status changed from NEW to CLOSED - DUPLICATE

Also available in: Atom PDF