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

Fix artifacts path for build-darwin-amd64-pkg-tsh drone pipeline #10599

Merged
merged 1 commit into from
Feb 25, 2022

Conversation

r0mant
Copy link
Collaborator

@r0mant r0mant commented Feb 24, 2022

The build-darwin-amd64-pkg-tsh build pipeline was accidentally using artifacts path from build-darwin-amd64-pkg which worked only coincidentally (and unreliably) when two pipelines were running in parallel and oftentimes would lead to the tsh pipeline failing with:

Can't find /tmp/build-darwin-amd64-pkg/go/artifacts/teleport-v7.3.16-darwin-amd64-bin.tar.gz
Downloading from https://get.gravitational.com/ is disabled when a path is provided with -s

@r0mant r0mant enabled auto-merge (squash) February 24, 2022 23:08
Copy link
Contributor

@wadells wadells left a comment

Choose a reason for hiding this comment

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

Does this need to be added to dronegen?

@r0mant r0mant merged commit 4805185 into master Feb 25, 2022
@r0mant r0mant deleted the roman/dronefix branch February 25, 2022 00:30
@webvictim
Copy link
Contributor

@wadells Yes, if we're still using dronegen then all these miscellaneous pipelines should be implemented there. This would have ultimately prevented this typo.

@wadells
Copy link
Contributor

wadells commented Feb 25, 2022

@wadells Yes, if we're still using dronegen then all these miscellaneous pipelines should be implemented there. This would have ultimately prevented this typo.

What I was getting at is: this pipeline is already managed in dronegen:

func darwinTshPkgPipeline() pipeline {
return darwinPkgPipeline("build-darwin-amd64-pkg-tsh", "pkg-tsh", []string{"build/tsh*.pkg"})
}

These changes will be reverted the next time it is run:

walt@work:~/git/teleport$ git status                    
On branch master
Your branch is up to date with 'grav/master'.

nothing to commit, working tree clean
walt@work:~/git/teleport$ make dronegen
go run ./dronegen
walt@work:~/git/teleport$ git diff
diff --git a/.drone.yml b/.drone.yml
index a9fc85875..ed1535308 100644
--- a/.drone.yml
+++ b/.drone.yml
@@ -3113,9 +3113,9 @@ steps:
     ARCH: amd64
     BUILDBOX_PASSWORD:
       from_secret: BUILDBOX_PASSWORD
-    ENT_TARBALL_PATH: /tmp/build-darwin-amd64-pkg-tsh/go/artifacts
+    ENT_TARBALL_PATH: /tmp/build-darwin-amd64-pkg/go/artifacts
     OS: darwin
-    OSS_TARBALL_PATH: /tmp/build-darwin-amd64-pkg-tsh/go/artifacts
+    OSS_TARBALL_PATH: /tmp/build-darwin-amd64-pkg/go/artifacts
     WORKSPACE_DIR: /tmp/build-darwin-amd64-pkg-tsh
 - name: Copy Mac pkg artifacts
   commands:
@@ -5040,6 +5040,6 @@ volumes:
       name: drone-s3-debrepo-pvc
 ---
 kind: signature
-hmac: 2fa9a32bf1f8b0fe5ef6abb7b0cdd30df5cd8813ca2bdbc3fdbd9b1d7296f459
+hmac: 0c5316489efc1bfa9acfd87bed0e2807ec4f2b8e123649c168c9d675e3c8a4cc

@r0mant
Copy link
Collaborator Author

r0mant commented Feb 25, 2022

@wadells Ah good catch. I'll send a follow up PR to update dronegen today.

@r0mant
Copy link
Collaborator Author

r0mant commented Feb 25, 2022

Looks like it's only on master and v9, correct? Older branches don't seem to have dronegen.

@wadells
Copy link
Contributor

wadells commented Feb 25, 2022

Looks like it's only on master and v9, correct? Older branches don't seem to have dronegen.

@russjones removed dronegen from v8 in fadcdaf.

I believe it is still present in v7 and v6.2. v5 and before predate dronegen.

@webvictim
Copy link
Contributor

What I was getting at is: this pipeline is already managed in dronegen:

That makes a lot more sense :)

@russjones removed dronegen from v8 in fadcdaf.

Arguably we should have fixed those affected pipelines in dronegen rather than removing it entirely. The bulk of Drone's YAML is still for publishing artifacts rather than running tests.

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.

4 participants