- 
                Notifications
    
You must be signed in to change notification settings  - Fork 3
 
Fix catalog validation #423
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
Conversation
| 
           /run pipeline  | 
    
| 
           @whoffler Hold off running the pipeline for now, we have hit this quota:  | 
    
| 
           @ocofaigh there doesn't seem to be that many (13)... have we done a clean up on existing instances? whats are we limited to?  | 
    
| 
           @whoffler The quota is about the number of instances we have created in the past 24 hours, not the current total amount. Hence why we are updating all addons tests to use existing SM instance instead of creating a new one in every test.  | 
    
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@whoffler Did you run chmod +x on the script to make sure they are executable?
| 
           yes, they are executable  | 
    
| 
           /run pipeline  | 
    
| 
           🎉 This PR is included in version 2.10.2 🎉 The release is available on: 
 Your semantic-release bot 📦🚀  | 
    
Description
for issue - https://github.ibm.com/GoldenEye/issues/issues/16226
Release required?
x.x.X)x.X.x)X.x.x)Release notes content
Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
Checklist for reviewers
For mergers