Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

devops: start publishing canary at midnight every day #5343

Conversation

aslushnikov
Copy link
Collaborator

@aslushnikov aslushnikov commented Feb 6, 2021

This patch:

  • starts publishing canary NPM package at 00:10AM UTC
  • canary version is published from default (master) branch and is
    named with a date. E.g. for a version published on Feb 5, 2021, the
    version would be 1.8.0-alpha-feb-5-2021
  • versions from release branches are still published on every commit and have the
    regular commit timestamp suffix

@aslushnikov aslushnikov force-pushed the start-publishing-canary-at-midnight-every-day branch from 4691667 to a662e2b Compare February 6, 2021 03:27
@pavelfeldman
Copy link
Member

We still need driver per commit, does it only slow down publishing npms?

@@ -48,9 +48,6 @@ fi

NPM_PUBLISH_TAG="next"

if [[ $1 == "--tip-of-tree" ]]; then
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

git status check above fails if you update version beforehand.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

}).toString('utf8').trim();
packageJSON.version = `${packageJSON.version}-${timestamp}000`;
} else {
throw new Error('This script must be run with either --timestamp or --current-date parameter');
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: wrong arguments in the message

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

const month = ['jan', 'feb', 'mar', 'apr', 'may', 'jun', 'jul', 'aug', 'sep', 'oct', 'nov', 'dec'][date.getMonth()];
const day = date.getDate();
const year = date.getFullYear();
packageJSON.version = `${packageJSON.version}-alpha-${month}-${day}-${year}`;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just curious, why do we need "alpha"?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just to ensure that all there versions go before all others (there's alphabetical version sorting)

@dgozman
Copy link
Contributor

dgozman commented Feb 7, 2021

We still need driver per commit, does it only slow down publishing npms?

We can try driver-per-day, as long as we roll languages in advance 😄

This patch:
- starts publishing canary version of driver & NPM package at 00:10AM
UTC
- canary versions are published from default (`master`) branch and are
named with a date. E.g. for a version publsihed on Feb 5, 2021, the
version would be `1.8.0-alpha-feb-5-2021`
- release versions are still published on every commit and have the
regular commit timestamp suffix.
@aslushnikov aslushnikov force-pushed the start-publishing-canary-at-midnight-every-day branch from a662e2b to 79b7be0 Compare February 9, 2021 17:22
@aslushnikov aslushnikov merged commit 1240dd4 into microsoft:master Feb 9, 2021
@aslushnikov aslushnikov deleted the start-publishing-canary-at-midnight-every-day branch February 9, 2021 22:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants