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 issue where jobs without specified count caused panic. #89

Merged
merged 1 commit into from
Jan 23, 2018

Conversation

jrasell
Copy link
Member

@jrasell jrasell commented Jan 22, 2018

This issue was caused by the incorrect assumption that jobs with a count not set or set to 0 can not result in a deployment. This was incorrect as an undefined count will result in a default count of 1; or that jobs set to count=0 can be run and deployed to stage the job or disable it.

@mimato and @adamlc this should fix the issue you're seeing and also fixes previously unseen bugs in the deployment process. It has been tested with the following suite of jobs:

  • service with count 1
  • service with count 0
  • service with count undefined
  • batch with count undefined
  • batch with count 1

Closes #87

This issue was caused by the incorrect assumption that jobs with
a count not set or set to 0 can not result in a deployment. This
was incorrect as an undefined count will result in a default count
of 1; or that jobs set to count=0 can be run and deployed to stage
the job or disable it.

Closes #87
@jrasell jrasell added the bug label Jan 22, 2018
@jrasell jrasell merged commit 278b046 into master Jan 23, 2018
@jrasell jrasell deleted the b_gh_87 branch January 23, 2018 09:52
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.

Error when trying to deploy a batch job
1 participant