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

update bldr config with new hab package name #8706

Merged
merged 1 commit into from
Jul 2, 2019

Conversation

robbkidd
Copy link
Contributor

@robbkidd robbkidd commented Jul 2, 2019

Description

The table name in .bldr.toml apparently needs to match the package name being built.

Related Issue

This should fix package promotion from unstable->current in expeditor, too.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

  • I have read the CONTRIBUTING document.
  • I have run the pre-merge tests locally and they pass.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.
  • All commits have been signed-off for the Developer Certificate of Origin.

This should fix package promotion from unstable->current in expeditor,
too.

Signed-off-by: Robb Kidd <robb@thekidds.org>
@tas50 tas50 changed the title update bldr config with new package name update bldr config with new hab package name Jul 2, 2019
@tas50 tas50 merged commit 71828de into chef:master Jul 2, 2019
@tas50
Copy link
Contributor

tas50 commented Jul 2, 2019

🤦‍♂

@robbkidd
Copy link
Contributor Author

robbkidd commented Jul 2, 2019

@tas50 Anything to be done about the Amazon image test-kitchen failures in Travis?

@lock
Copy link

lock bot commented Jul 16, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jul 16, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants