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

remove worker related post habitat build steps and cleanup bootstrap seed list #1858

Merged
merged 1 commit into from
Nov 18, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
31 changes: 4 additions & 27 deletions .expeditor/builder_seed.toml
Original file line number Diff line number Diff line change
Expand Up @@ -8,36 +8,13 @@ packages = [
"core/hab-launcher",
"core/hab",
"core/hab-sup",
]

[[x86_64-linux]]
channel = "LTS-2024"
packages = [
# Builder services
"habitat/builder-api",
"habitat/builder-api-proxy",
"habitat/builder-jobsrv",
"habitat/builder-worker",
"habitat/builder-memcached",

# Utilities
"core/nmap"
]

[[x86_64-linux-kernel2]]
channel = "stable"
packages = [
# Supervisor and prerequisites
"core/hab-launcher",
"core/hab",
"core/hab-sup",

"habitat/builder-worker"
]

[[x86_64-windows]]
channel = "stable"
packages = [
# Supervisor and prerequisites
"core/windows-service",
"core/hab",
"core/hab-sup",

"habitat/builder-worker"
]
74 changes: 0 additions & 74 deletions .expeditor/post_habitat_release.pipeline.yml
Original file line number Diff line number Diff line change
Expand Up @@ -31,80 +31,6 @@ steps:
- GITHUB_USER
soft_fail: true

# We build new releases of habitat/builder-worker now since they
# pull in the new Habitat release we just created (specifically, the
# studio and build program).
#
# We then promote them to the acceptance channel, from which workers
# in our acceptance environment will update themselves. Once we try
# building some packages in acceptance, we can unblock this pipeline
# to have them automatically promoted to the stable channel,
# allowing our production workers to then update.

- label: "[:linux: build habitat/builder-worker]"
command:
- .expeditor/scripts/post_habitat_release/build_worker.sh
expeditor:
executor:
docker:
privileged: true
environment:
- HAB_ORIGIN
- BUILD_PKG_TARGET=x86_64-linux

- label: "[:linux: :two: build habitat/builder-worker]"
command:
- .expeditor/scripts/post_habitat_release/build_worker.sh
expeditor:
executor:
docker:
privileged: true
environment:
- HAB_ORIGIN
- BUILD_PKG_TARGET=x86_64-linux-kernel2

- label: "[:windows: build habitat/builder-worker]"
command:
- powershell .expeditor/scripts/post_habitat_release/build_worker.ps1
expeditor:
executor:
docker:
host_os: windows
environment:
- HAB_ORIGIN
- BUILD_PKG_TARGET=x86_64-windows
- BUILDKITE_AGENT_ACCESS_TOKEN

- wait

- label: "Promote to habitat/builder-worker to acceptance"
command:
- .expeditor/scripts/post_habitat_release/promote_packages_to_channel.sh acceptance
expeditor:
executor:
docker:
privileged: true

- block: "Evaluate habitat/builder-worker in Acceptance"
prompt: |
The previous promotion step made these habitat/builder-worker
packages available in our Acceptance workers. Please try
building packages in acceptance to ensure they behave properly.

When you are satisfied, please unblock this step to promote the
same packages to the stable channel, where they will be consumed
by our Production builders.

- label: "Promote habitat/builder-worker to stable"
command:
- .expeditor/scripts/post_habitat_release/promote_packages_to_channel.sh stable
expeditor:
executor:
docker:
privileged: true

- wait

# We do this after building and promoting new workers to ensure the
# bundle contains those workers.
- label: ":s3: Create new Bootstrap Bundle"
Expand Down