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

use pulumi CLI dev version for running CI #1535

Merged
merged 2 commits into from
Jan 17, 2024
Merged

Conversation

tgummerer
Copy link
Contributor

We recently started publishing dev versions of the pulumi CLI. Use these for the CI builds in this repository, to give it some early exposure, and hopefully catch some bugs early.

@tgummerer tgummerer requested a review from a team December 27, 2023 11:17
@@ -43,7 +43,9 @@ jobs:
with:
dotnet-version: ${{matrix.dotnetversion}}
- name: Install Pulumi CLI
uses: pulumi/actions@v4
uses: pulumi/actions@5ffa6249eba838c2a624d5315a28fb8c7b3dabb7
Copy link
Member

Choose a reason for hiding this comment

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

Do we really want this pinned? Isn't latest v4 always going to be fine for us?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It's pinned just to get the latest changes from pulumi/actions. We should probably do a release there so the latest v4 includes the changes to allow us to install the dev version.

We recently started publishing dev versions of the pulumi CLI. Use
these for the CI builds in this repository, to give it some early
exposure, and hopefully catch some bugs early.
@Frassle
Copy link
Member

Frassle commented Jan 2, 2024

We should also update https://github.com/pulumi/home/wiki/Producing-the-Pulumi-CLI-and-SDKs to say check https://github.com/pulumi/examples/actions/workflows/cron.yml is all green. (And work out why it's not green now)

Copy link
Member

@Frassle Frassle left a comment

Choose a reason for hiding this comment

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

We'll need to bump actions to v5.

Copy link
Contributor

@cnunciato cnunciato left a comment

Choose a reason for hiding this comment

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

I'd prefer that we not have this repo take a dependency on dev CLIs -- at least not without more discussion. If we want to use the examples in this repo for testing dev CLIs, we totally can, but we should do so with a separate workflow that's probably managed outside of this repo. Cloning this repo, for example, in a dedicated pulumi/pulumi GHA workflow job would probably give you what you're looking for.

@tgummerer
Copy link
Contributor Author

@cnunciato happy to discuss this more! The idea here is to enroll repos in the pulumi org to use the dev version of pulumi/pulumi for running CI, so we can catch any potential user facing issues before they are getting released. It is especially helpful to this in this repository since it's one of the biggest collection of pulumi code.

I would really like to keep these changes at least in the cron action. Having a separate job for the dev version there would just mean extra CI time used for running the examples with the same released pulumi version more often. Especially in light of our already increased CI spend (https://github.com/pulumi/home/issues/3244), I would like to avoid adding additional jobs when we can avoid that.

Note that I wouldn't expect "dev" versions to be much less stable than release versions currently are. They all go through the usual automated testing and review process before being merged and becoming a dev version. It's also what we cut a release from currently, and having an early indication of when anything is broken with our current build would be super helpful. This would also mean that the IaC Core team would start paying closer attention to these CI jobs, which would further help with the stability of them as well.

All this said, I'd be happy to discuss this on slack or zoom as well if you prefer.

Copy link
Contributor

@cnunciato cnunciato left a comment

Choose a reason for hiding this comment

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

Thanks again for the discussion @tgummerer!

@tgummerer tgummerer merged commit bbe9871 into master Jan 17, 2024
46 of 50 checks passed
@tgummerer tgummerer deleted the tg/use-dev-version-for-ci branch January 17, 2024 09:18
tgummerer added a commit to pulumi/templates that referenced this pull request Jan 22, 2024
Similar to pulumi/examples#1535, we would like
to use the latest pulumi dev version here instead of just the latest
version.

In face in some places there was some (very outdated and
non-functional) code to attempt that.  Instead of the latest dev
version it downloaded 3.40.0-alpha.1663101047 as of the time of this
writing, which is less than ideal.  Always use the dev version here
unless we explicity request the "latest" version.
tgummerer added a commit to pulumi/templates that referenced this pull request Jan 22, 2024
Similar to pulumi/examples#1535, we would like
to use the latest pulumi dev version here instead of just the latest
version.

In face in some places there was some (very outdated and
non-functional) code to attempt that.  Instead of the latest dev
version it downloaded 3.40.0-alpha.1663101047 as of the time of this
writing, which is less than ideal.  Always use the dev version here
unless we explicity request the "latest" version.
cnunciato pushed a commit to pulumi/templates that referenced this pull request Jan 23, 2024
Similar to pulumi/examples#1535, we would like
to use the latest pulumi dev version here instead of just the latest
version.

In face in some places there was some (very outdated and
non-functional) code to attempt that.  Instead of the latest dev
version it downloaded 3.40.0-alpha.1663101047 as of the time of this
writing, which is less than ideal.  Always use the dev version here
unless we explicity request the "latest" version.
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.

3 participants